Before you start processing real transactions with MultiSafepay, we recommend testing each payment method in your MultiSafepay test account.
If you encounter any issues during testing, see Handling errors.
You can’t test the following methods in your MultiSafepay test account. You can only make test payments in your MultiSafepay live account.
For all payment methods except AfterPay, you need your site’s test API key.
Initiate a payment in your ready-made integration or via our API:
https://testapi.multisafepay.com/v1/json/
Enter the test payment details for the payment method you are testing, or select a payment scenario, and complete the test payment.
To check the transaction details, sign in to your test dashboard.
Go to Transactions > Transactions overview.
In the Transactions overview list, select the transaction to view the Transaction details page.
To check that you have succesfully connected to our system, under Offline actions, check that you’ve correctly received the notifyMerchantTrans action. For information about errors, see HTTP errors.
Use the following test payment details for testing different scenarios.
Test a Bancontact order
Card number | Scenario | Description |
---|---|---|
67034500054620008 | Completed | Transaction was completed (3D enrolled). Also use this card number when creating orders to test refunds and API refunds. |
67034500054610009 | Declined | Transaction was declined (card must be 3D enrolled). |
67039902990000045 | Declined | Transaction was declined (3D authentication failed). |
67039902990000011 | Declined | Transaction was declined (3D authentication successful, but insufficient funds). |
You can see the reason the transaction was declined in your MultiSafepay test account under Notes.
Test a Bancontact QR code
IBAN | Scenario | Description |
---|---|---|
NL87ABNA0000000001 | Initialized/ Completed | Transaction is initiated. After 2 minutes, this changes to Completed. Also use this for testing refunds. |
NL87ABNA0000000002 | Initialized/ Expired | Transaction is initiated. After 2 minutes, this changes to Expired. |
NL87ABNA0000000004 | Initialized/ Declined | Transaction is initiated. After 2 minutes, this changes to Declined. |
Any other IBAN | Initialized/ Expired | Transaction is initiated. After 5 days, this changes to Expired. |
Note: You can’t test making direct API requests with an IBAN to test different transaction statuses.
locale
parameter to at_AT
.RZOOAT2L420
.
NOLADE22XXX
.
You can also test the following scenarios:
Scenario | Description |
---|---|
Declined | Transaction was declined. |
Open Completed | Transaction is initiated. After 1 minute, this changes to Completed. |
Open Declined | Transaction is initiated. After 1 minute, this changes to Declined. |
IBAN | Scenario | Description |
---|---|---|
NL87ABNA0000000001 | Initialized/ Completed | Transaction is initiated. After 2 minutes, this changes to Completed. Also use this IBAN to test refunds and API refunds. |
NL87ABNA0000000002 | Initialized/ Declined | Transaction is initiated. After 2 minutes, this changes to Declined. |
NL87ABNA0000000003 | Initialized/ Uncleared/ Completed | Transaction is initiated. After 2 minutes, this changes to Uncleared. After 1 more minute, it changes to Completed. |
NL87ABNA0000000004 | Initialized/ Uncleared/ Declined | Transaction is initiated. After 2 minutes, this changes to Uncleared. After 1 more minute, it changes to Declined. |
1. Request a test API key from AfterPay via either:
AfterPay shares the test key with MultiSafepay.
2. To enable AfterPay in your MultiSafepay test account, email [email protected]
Test an AfterPay order
Test declining an order
To decline an order, in your test account under Order summary, click Decline.
The transaction and order statuses change to Void.
Test AfterPay rejecting an order
To test AfterPay rejecting an order, in your direct or redirect API request, use the following email address: [email protected]
The transaction and order statuses change to Declined.
Change the order status
You can change the order status to Shipped or Cancelled. To change the order status, either:
Notes:
You can’t test:
Test an order
Test declining an order
To decline an order, in your test account under Order summary, click Decline.
The order and transaction statuses change to Void.
Test shipping an E-Invoicing order
To test shipping an order, make an update order API request with status "shipped"
. You receive the invoice_url
in the API response.
Test an in3 order
Create an order > Pay later order (Example: in3 direct/redirect). Use the following customer details:
For redirect orders:
01-01-1999
Select the checkbox to accept in3’s payment terms and privacy statement, and then click Afronden.
On the Test platform page, from the Test scenario list, select Completed.
Click Test.
On the in3 page, click Terug naar webshop.
The payment is processed in the test environment as Successful, with order status Completed, and transaction status Uncleared.
Test in3 declining an order
Use the following customer details:
The order and transaction statuses change to Declined.
Test shipping an order
To test shipping an order, either:
shipped
, orReceive an invoice
You can only test invoicing in your MultiSafepay live account. To do this, change the order status to Shipped.
Test refunding an order
To test refunding an order:
shipped
.Test an API refund
To test refunding an order via the API:
shipped
.
Test credentials:
Test a Klarna order
Test declining an order
To decline an order, in your test account under Order summary, click Decline.
The transaction and order statuses change to Void.
Change the order status
You can change the order status to Shipped or Cancelled. To change the order status, either:
Test refunding an order
To refund an order:
Receive an invoice
You can only test invoicing in your MultiSafepay live account. To do this, change the order status to Shipped.
Notes:
You can’t test:
For more information about integrating Klarna with MultiSafepay, see Klarna.
Create an order > Card order. See also the Examples for the specific card scheme.
For co-branded cards, see the Credit card redirect example, and set the locale
parameter:
fr_FR
da_DK
it_IT
On the payment page:
123
.On the 3D payment page:
Card number | Scenario | Description |
---|---|---|
Amex: 378282246310005 Maestro: 6759000000005 Mastercard: 5500000000000004 Visa/co-branded: 4111111111111111 |
Completed | Transaction was completed (3D enrolled) |
Visa/co-branded: 4012001038443335 |
Completed | Transaction was completed (not 3D enrolled) |
Visa/co-branded: 4917300000000008 |
Uncleared | Transaction is uncleared. After 3 minutes, this changes to Void. |
Amex: 378734493671000 Visa/co-branded: 4462000000000003 |
Uncleared | Transaction is uncleared. After 3 minutes, this changes to Completed. |
Amex: 374200000000004 Visa/co-branded: 4012001037461114 |
Declined | Transaction was declined (3D authentication failed) |
Visa/co-branded: 4012001038488884 |
Declined | Transaction was declined (3D authentication was successful, but insufficient funds) |
Note: You can see the reason a transaction was declined in your MultiSafepay test account under Notes.
You can test the following gift cards:
Test a gift card order
111115
Use the following card numbers to test different gift card balances.
Card numbers | Balance |
---|---|
111115 | € 100 |
111112 | € 5 |
111110 | No balance |
Any other card number receives an “Invalid card number” error.
Other gift cards
You can’t test other gift cards in your MultiSafepay test account. You can only make test payments in your MultiSafepay live account. You make a small payment and the amount is actually deducted from the gift card.
Note: You can’t test Alipay declining transactions.
Compatible devices
For compatible devices, see Apple – Devices compatible with Apple Pay.
If you don’t own an Apple device, we recommend using the Appetize.io emulator. When you try to complete a test payment on the payment page, you get a This device is not supported error. But the emulator creates an order with the Apple Pay gateway preselected to check if there is an existing connection to our server. However, you can’t fully complete the test transaction.
Testing prerequisites
If these requirements are not met, Apple Pay doesn’t appear on the checkout page.
Testing Apple Pay redirect
To test your Apple Pay redirect integration, there are two ways:
To test, follow these steps:
Testing Apple Pay direct
See Apple Pay direct integration – Test your integration.
To test Google Pay payments, follow these steps:
In your checkout, click the Google Pay button.
Complete payment using your Google account.
Your real card details are never processed in our testing environment, but you must add at least one chargeable card to your Google account.
Depending on your card’s authentication method, you may or may not be redirected to authenticate:
Check the status of the payment in your test dashboard.
For support, email [email protected]
Test a PayPal order
Note: Since MultiSafepay does not collect payments on behalf of PayPal, the transaction status remains Initialized and can’t be changed to Completed.
Change the order status
You can change the order status to:
Status | Description | Test scenario |
---|---|---|
Completed | Order was completed | Completed |
Void | Order was cancelled | Cancelled |
Initialized/ Completed | Payment blocked by PayPal, then accepted after 2 minutes | Initialized completed |
To change the order status, on the Test platform page, from the Test scenario list, select the relevant test scenario.
You can test cancelling orders for the following methods:
To test cancelling an order:
Payment methods
Payment methods
Feedback
Propose a change on GitHub
or
send an email to [email protected]
Other languages
For an explanation in another language, contact your account manager.