To test Pay by Bank, follow the RedirectURL in the API response to access the simulator.Use the credentials below to simulate the user’s login to their bank, depending on the Country.Other testing data is provided if available. The BankName value skips the bank selection step, and the IBAN may make it possible to avoid a second authentication step (note that in Production, the BIC is required as well). See the guide for details.
For testing direct debits, you can use the following bank account data and mock values. Note that it is not possible to test direct debit email notifications in Sandbox.
When testing direct debit mandates and pay-ins, you can set a specific value for the FirstName parameter of the Natural User who owns the bank account for the mandate.
Successful - Results in an active mandate. You must do a pay-in with this mandate for the status to be updated.
Invalid - For Bacs only, results in a failed mandate due to incorrect bank account information.
Penniless - Results in a failed pay-in due to lack of funds (with the 001830).
Fickle - Results in a successful pay-in which is disputed by the user and hence a dispute is created.
It is not possible to initiate a refund for a direct debit pay-in until the 8th day following the day of the pay-in’s CreationDate (to avoid a conflict with possible late failures).On POST Create a Refund you can set the Tag to the mock value ignore_mindate to ignore the minimum date restriction and test refunds within 7 days. Note that you can only create a refund if the pay-in Status is SUCCEEDED, which you can achieve with the Successful mock value above.
To test Apple Pay, create a sandbox Apple ID and then use this ID to log in on your device. Once logged in as a sandbox tester, add an Apple Pay test card to your Apple wallet to test your integration on your device.
To test Bancontact pay-ins on web, follow the RedirectURL in the API response to access Mangopay’s simulator. The simulator gives options to test successful and failed payment scenarios.For mobile, the DeepLinkURL returned by the API in Sandbox is a placeholder. Bancontact doesn’t provide a testing environment, so the only way to complete the payment in Sandbox is by using Mangopay’s web-based simulator, accessible via the RedirectURL value.
The only way to test Bizum is via Mangopay’s simulator. To test Bizum, follow the RedirectURL in the API response to access Mangopay’s simulator. The simulator gives options to test successful and failed payment scenarios.In Sandbox, the RedirectURL is returned in all cases, because it is the only way to complete the transaction. In Production, the RedirectURL is not returned if Phone is sent.
To test BLIK, follow the RedirectURL in the API response to access Mangopay’s simulator. The simulator gives options to test successful and failed payment scenarios.
You can use Google Pay’s test card suite to test your Google Pay integration with Mangopay. Once you have joined the test card suite group, you can use the following cards in Sandbox:
4111111111111111 - The Visa card triggers a challenge flow (requiring 3DS redirection)
5555555555554444 - The Mastercard card triggers a frictionless flow (not requiring 3DS redirection)
To test iDEAL, follow the RedirectURL in the API response to access Mangopay’s simulator. The simulator gives options to test successful and failed payment scenarios.
To test Klarna, follow the RedirectURL returned in Sandbox to access Klarna’s simulator.Klarna’s Sample customer data allows you to test successful and failed payment scenarios. The sample data relating to disputes is available but can’t be used to simulate disputes on the Klarna’s sandbox Merchant Portal.Note: If you use data other than the samples provided, it will be used to create a new Klarna account during the payment process.
To test Multibanco, follow the RedirectURL in the API response to access Mangopay’s simulator. The simulator gives options to test successful and failed payment scenarios.
To test Payconiq pay-ins on web, follow the RedirectURL in the API response to access Mangopay’s simulator. The simulator gives options to test successful and failed payment scenarios.For mobile, the QRCodeURL and DeepLinkURL returned by the API in Sandbox are placeholders. The only way to complete the payment in Sandbox is by using Mangopay’s web-based simulator, accessible via the RedirectURL value.
When PayPal is activated in Sandbox, Mangopay provides you with credentials to a PayPal account that can be used for testing.To test PayPal, follow the RedirectURL in the API response to access the PayPal payment page and log in using the test account provided.
To test Satispay, follow the RedirectURL in the API response to access Mangopay’s simulator. The simulator gives options to test successful and failed payment scenarios.
To test Swish, follow the RedirectURL in the API response to access Mangopay’s simulator. The simulator gives options to test successful and failed payment scenarios.For mobile, the QRCodeURL and DeepLinkURL are not returned by the API in Sandbox. The only way to complete the payment in Sandbox is by using Mangopay’s web-based simulator, accessible via the RedirectURL value.
To test TWINT, follow the RedirectURL in the API response to access Mangopay’s simulator. The simulator gives options to test successful and failed payment scenarios.
