Testing
-
Show Hide
ACH
The difference between using the hosted payment page or not using the hosted payment page is not described.
Positives
Please find below positive test case input definitions with the expected results in the last column.
Routing Number Account Number Currency Country Payment product ID Payment status ID 121000248 4942590324 USD US 730 800 Negatives
There are no negative test cases for this product.
Refunds in sandbox
Transactions are not refundable on status completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
AfterPay - Installments
Please be advised that the credentials to test a transaction will be provided to you during the boarding process.
-
Show Hide
AfterPay - Invoice
Please be advised that the credentials to test a transaction will be provided to you during the boarding process.
-
Show Hide
American Express
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 371449635398431 123 11006 USD US 2 OK1443 Y P 600 371449635398431 999 1100 USD US 2 OK1456 Y P 600 371449635398431 999 11008 USD US 2 OK2318 Y P 600 371449635398431 123 733 CAD CA 2 OK2424 Y M 600 371449635398431 123 1000 USD US 2 OK1131 0 M 600 Currencies
To be able to test every single currency as listed in the currency table, please use following details.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result 371449635398431 432 1000 See curr. table NL 2 OK1131 0 M Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
3D secure
On payment product id 117 (maestro) 3d secure is enabled as all Maestro transaction are mandated to be processed with 3D secure.
AVS
Address verification is enabled on all cards that support it. Different cases give different AVS result. In case the card type isn’t supporting AVS, the result will always be 0.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Card verification
Also known as 0$ authorization. This type of transaction is triggered with an amount of 0 and will only return a validated response resulting in a status of 300 and only works on a recurring model.
Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
3D secure handling
For the handling of transaction with 3D secure a redirect takes place for the consumer. In the Sandbox it will not show a login screen but a functional HTML form that needs to post the 3D secure validation to the payment platform. Please use that process to simulate the authentication process. The post action triggers the right action to be able to finish the payment.
The redirect behavior back and forward are as it would be in real production systems.
Sample of the form:
-
Show Hide
Apple Pay
Testing Apple Pay in pre-production
If you want to test Apple Pay in our pre-production environment, you can use the the test data provided by Apple on their Sandbox testing page.
You will need to create a Sandbox Tester Account, by following the steps described by Apple. To create a Sandbox Tester Account, you will need to be enrolled in the Apple Developer Program. From the Apple Developer Program you can access the App Store Connect.
The cards mentioned on the Apple Pay Sandbox Testing page can be added to the device you use for testing, after you have logged into that device with the Sandbox Tester Account you created.
Testing Apple Pay in production
The test cards provided by Apple on their sandbox testing page, can only be used in the pre-production environment. In the production environment it is recommended to use real credit cards. Please note that testing in production means that actual money will be deducted from the card you use.
-
Show Hide
Argencard
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 5011053417303125 123 1003 ARS AR 140 109196 0 0 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 5011053417303125 123 1017 ARS AR 140 430424 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Aura
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 5078608877345328 321 1008 BRL BR 146 130170 0 0 8001 1 Payment product 146 doesn't support delayed settlement.
Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Bank Transfer
The test data is related to the sandbox environment and only describes the different test cases. The difference in using the hosted payment page or not is not described.
The following currencies are supported in the sandbox environment, please note that these currencies do not reflect the total number of supported currencies. These are indicated at the top of this page.
- Australian dollar (AUD)
- Bahraini dinar (BHD)
- Bulgarian lev (BGN)
- Canadian dollar (CAD)
- Colombian peso (COP)
- Croatian kuna (HRK)
- Czech koruna (CZK)
- Danish krone (DKK)
- Euro (EUR)
- Hong Kong dollar (HKD)
- Hungarian forint (HUF)
- Indian rupee (INR)
- Indonesian rupiah (IDR)
- Japanese yen (JPY)
- Kuwaiti dinar (KWD)
- Malaysian ringgit (MYR)
- Mexican peso (MXN)
- New Taiwan dollar (TWD)
- New Zealand dollar (NZD)
- Norwegian krone (NOK)
- Polish zloty (PLN)
- Pound sterling (GBP)
- Qatari riyal (QAR)
- Romanian new leu (RON)
- Russian ruble (RUB)
- Singapore dollar (SGD)
- South African rand (ZAR)
- Swedish krona (SEK)
- Swiss Franc (CHF
- Turkish lira (TRY)
- United States dollar (USD)
MorePositives
Below are the positive test case input definitions with the expected results in the last column. Positive in this context means that the payments gets accepted, it doesn’t relate to an authorization.
MoreCountry code Currency code Payment product ID Fiscal number Payment status ID AD EUR 11 800 AF USD 11 800 AG USD 11 800 AI USD 11 800 AL EUR 11 800 AM RUB 11 800 AN USD 11 800 AO ZAR 11 800 AQ NOK 11 800 AS USD 11 800 AT EUR 11 800 AU AUD 11 800 AW USD 11 800 AZ RUB 11 800 BA EUR 11 800 BB USD 11 800 BD INR 11 800 BD USD 11 800 BE EUR 11 800 BF EUR 11 800 BG BGN 11 800 BH BHD 11 800 BI EUR 11 800 BJ EUR 11 800 BM USD 11 800 BN HKD 11 800 BO USD 11 800 BQ USD 11 800 BS USD 11 800 BT INR 11 800 BV NOK 11 800 BW ZAR 11 800 BY RUB 11 800 BZ USD 11 800 CA CAD 11 800 CC AUD 11 800 CD EUR 11 800 CF EUR 11 800 CG EUR 11 800 CH CHF 11 800 CI EUR 11 800 CK NZD 11 800 CL USD 11 800 CM EUR 11 800 CN USD 11 800 CO COP 11 800 CO USD 11 800 CR USD 11 800 CV EUR 11 800 CW USD 11 800 CX AUD 11 800 CY EUR 11 800 CZ CZK 11 800 DE EUR 11 800 DJ EUR 11 800 DK DKK 11 800 DM USD 11 800 DO USD 11 800 DZ EUR 11 800 EC USD 11 800 EE EUR 11 800 EG EUR 11 800 EG USD 11 800 EH EUR 11 800 ER USD 11 800 ES EUR 11 800 ET USD 11 800 FI EUR 11 800 FJ AUD 11 800 FK GBP 11 800 FM USD 11 800 FO DKK 11 800 FR EUR 11 800 GA EUR 11 800 GB GBP 11 800 GD USD 11 800 GE RUB 11 800 GF EUR 11 800 GG GBP 11 800 GH USD 11 800 GI GBP 11 800 GL DKK 11 800 GM USD 11 800 GN EUR 11 800 GP EUR 11 800 GQ EUR 11 800 GR EUR 11 800 GS GBP 11 800 GT USD 11 800 GU USD 11 800 GW EUR 11 800 GY USD 11 800 HK GBP 11 800 HK HKD 11 800 HK USD 11 800 HM AUD 11 800 HN USD 11 800 HR HRK 11 800 HT USD 11 800 HU HUF 11 800 ID IDR 11 800 ID USD 11 800 IE EUR 11 800 IL USD 11 800 IM GBP 11 800 IN INR 11 800 IN USD 11 800 IO USD 11 800 IQ USD 11 800 IT EUR 11 800 JE GBP 11 800 JM USD 11 800 JO USD 11 800 JP JPY 11 800 KE USD 11 800 KG RUB 11 800 KH HKD 11 800 KI AUD 11 800 KM EUR 11 800 KN USD 11 800 KR USD 11 800 KW KWD 11 800 KY USD 11 800 KZ RUB 11 800 LA HKD 11 800 LB LBP 11 800 LB USD 11 800 LC USD 11 800 LI CHF 11 800 LK INR 11 800 LK USD 11 800 LR USD 11 800 LS ZAR 11 800 LT EUR 11 800 LU EUR 11 800 LV EUR 11 800 LY EUR 11 800 MA EUR 11 800 MC EUR 11 800 MD RUB 11 800 ME EUR 11 800 MG EUR 11 800 MH USD 11 800 MK EUR 11 800 ML EUR 11 800 MM HKD 11 800 MN HKD 11 800 MO HKD 11 800 MP USD 11 800 MQ EUR 11 800 MR EUR 11 800 MS USD 11 800 MT EUR 11 800 MU EUR 11 800 MV INR 11 800 MV USD 11 800 MW USD 11 800 MX MXN 11 800 MX USD 11 800 MY MYR 11 800 MZ ZAR 11 800 NA ZAR 11 800 NC EUR 11 800 NE EUR 11 800 NF AUD 11 800 NG USD 11 800 NI USD 11 800 NL EUR 11 800 NO NOK 11 800 NP INR 11 800 NP USD 11 800 NR AUD 11 800 NU NZD 11 800 NZ NZD 11 800 OM USD 11 800 PA USD 11 800 PF EUR 11 800 PG AUD 11 800 PH USD 11 800 PK INR 11 800 PK USD 11 800 PL PLN 11 800 PM EUR 11 800 PN NZD 11 800 PR USD 11 800 PS USD 11 800 PT EUR 11 800 PW USD 11 800 PY USD 11 800 QA QAR 11 800 RE EUR 11 800 RO EUR 11 800 RO RON 11 800 RS EUR 11 800 RU RUB 11 800 RW EUR 11 800 SA USD 11 800 SB AUD 11 800 SC USD 11 800 SE SEK 11 800 SG SGD 11 800 SG USD 11 800 SH GBP 11 800 SI EUR 11 800 SJ NOK 11 800 SK EUR 11 800 SL USD 11 800 SM EUR 11 800 SN EUR 11 800 SO USD 11 800 SR USD 11 800 ST EUR 11 800 SV USD 11 800 SX USD 11 800 SZ ZAR 11 800 TC USD 11 800 TD EUR 11 800 TF EUR 11 800 TG EUR 11 800 TH USD 11 800 TJ RUB 11 800 TK NZD 11 800 TM RUB 11 800 TN EUR 11 800 TO AUD 11 800 TP HKD 11 800 TR EUR 11 800 TR TRY 11 800 TR USD 11 800 TT USD 11 800 TV AUD 11 800 TW TWD 11 800 TZ USD 11 800 UA RUB 11 800 UG USD 11 800 UM USD 11 800 US USD 11 800 UY USD 11 800 UZ RUB 11 800 VA EUR 11 800 VC USD 11 800 VE USD 11 800 VG USD 11 800 VI USD 11 800 VN HKD 11 800 VU AUD 11 800 WF EUR 11 800 WS AUD 11 800 YE USD 11 800 YT EUR 11 800 YU EUR 11 800 ZA ZAR 11 800 ZM ZAR 11 800 ZW ZAR 11 800 AU AUD 500 800 BR BRL 51 28001238938 800 Negatives
The negative cases for bank transfers only occur when invalid data is submitted (eg. Not supported currency/country combination).
Refunds in sandbox
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Boleto Bancário
Positives
Below is the positive test case input definitions with the expected results in the last column.
Country code Currency code Payment product ID Statecode Zip Amount Payment status ID FISALNUMBER BR BRL 1503 RJ 21200654 2200 55 21298750091 Negatives
There is an easy negative case defined for this product, please use below info to reproduce.
Country code Currency code Payment product ID Amount Event ID Payment status ID FISALNUMBER BR BRL 1503 2200 800200 100 99999999 Payment Steps
After initializing the payment, a form should be shown to the consumer to take to the Boleto Bancário office.
Payments cannot be simulated to go to the status completed with the status ID 800 or higher.
Refunds in Sandbox
Transactions are not refundable on status Completed with status ID 800, as for that, a separate process is scheduled to have the payment end up on a refundable status. Please wait 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Bpay
The test data is related to the Sandbox environment, and only describes different test cases. The difference in using the hosted payment page (or not), is not described.
Positives
The positive test case input definitions can be found below. The expected results are in the last column. Positive in this context means that the payments gets accepted, it doesn’t relate to an authorization.
Country code Currency code Payment product ID Payment status ID AU AUD 500 800 Negatives
The negative cases for bank transfers only occur when invalid data is submitted (e.g. not supported currency/country combination).
Refunds in Sandbox
Transactions are not refundable on status ‘Completed’ with status ‘ID 800’; for that, a separate process is scheduled to have the payment end up on a refundable status. Please wait 1 hour for all your test transactions to reach status ‘Completed’ with status ‘ID 800’ to be processed like this and set to be ready for refunds.
-
Show Hide
Cabal
Unfortunately we do not have test data for this card -
Show Hide
Carte Bancaire
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 5017670000001800 321 1100 EUR FR 130 varies C 0 600 5017670000002600 321 1100 EUR FR 130 varies C 0 600 5017670000004200 321 1100 EUR FR 130 varies C 0 600 5017670000005900 321 1100 EUR FR 130 varies C 0 600 5017670000006700 321 1100 EUR FR 130 varies C 0 600 5017670000007500 321 1100 EUR FR 130 varies C 0 600 5017670000008300 321 1100 EUR FR 130 varies C 0 600 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
China UnionPay
Please be advised that currently no test scenarios are supported for China UnionPay. We are working on a solution and will update this page as soon as the status has been changed.
-
Show Hide
Consumax
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 6034163498674939 321 1004 ARS AR 141 109196 0 0 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 6034163498674939 321 10022 ARS AR 141 485000 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Depósito Identificado
The test data is related to the Sandbox Environment and only describes the different test cases. The difference in using the hosted payment page or not is not described.
Positives
Below are the positive test case input definitions with the expected results in the last column. Positive in this context means that the payments gets accepted, it doesn’t relate to an authorisation.
Country code Currency code Payment product ID Fiscal Number Payment status ID BR BRL 51 99999999 800 Negatives
The negative cases for bank transfers only occur when invalid data is submitted (e.g. Not supported currency/country combination).
Refunds in Sandbox
Transactions are not refundable on status completed with Status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Diners Club
Currencies
To be able to test every single currency as listed in the currency table, please use following details.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result 3000000000000004 432 3500 USD NL 132 OK2000 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the response.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Direct Debit UK
The difference between using the hosted payment page or not using the hosted payment page is not described.
Positives
Please find below positive test case input definitions with the expected results in the last column.
Bank code Accountnumber Currency Country Payment product ID Payment status ID 601613 31926819 GBP GB 705 600 Negatives
There are no negative test cases for this product.
Refunds in sandbox
Transactions are not refundable on status completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Discover
Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 6011000991300009 123 1101 USD US 128 430285 X 0 6011000991300009 123 1102 CAD CA 128 430285 X 0 6011000991300009 123 2100 USD US 128 430409 X 0 6011000991300009 123 3100 USD US 128 430285 X 0 Currencies
To be able to test every single currency as listed in the currency table, please use following details.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result 6011000991300009 123 1091 USD NL 128 OK3372 X M 6011000991300009 123 1091 CAD NL 128 OK3372 X M Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
ELO
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 6277805454536223 321 1009 BRL BR 147 130170 0 0 600 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 =
For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
eNETS
Below are the positive test case input definitions, with the expected results in the last column.
Country code Currency code Payment product ID Amount Payment status ID SG SGD 810 100 800 For testing negative payment flow, please use below data.
Country code Currency code Payment product ID Amount Event ID Payment status ID SG SGD 810 101 400702 100 -
Show Hide
ePrzelewy
ePrzelewy does not offer a test environment; the full transaction cycle can only be tested in production.
Test Payment Steps (Production only)
After initializing the payment, the consumer needs to be redirected to the ePrzelewy environment. The landing page looks as below:
Select your bank and click on “Dalej” (Next) at the bottom of the page. Follow the instructions on the bank page to finalize the payment.
-
Show Hide
Giropay
Positives
Below are the positive test case input definitions with the expected results in the last column.
Country code Currency code Payment product ID Amount IBAN Payment status ID DE EUR 816 1000 DE46940594210000012345 800 Negatives
For testing negative payment flow, please cancel the payment at any time after the redirect. The payment status will result in 125 with event ID 400701.
Payment steps
A redirection needs to happen after initializing the payment. The page will look like the following:
Enter these values:
- "Anmeldename order legitimations-ID": sepatest1
- PIN: 45613
Click "Anmelden".
Click ‘Weiter’.
Enter these values:
- "TAN": 123412
Click "absenden".
Click ‘giropay beenden + zuruck zum Shop’ to go back. The payment ends up on status 800.
-
Show Hide
Google Pay
Test cards
Google Pay™ can be tested with the sample cards provided by Google. You can request access to the test card suite of Google by requesting it here for the Google account with which you would like to test. It is Google who provides you access to this user group. Our pre-production environment is set to use the TEST environment of Google. Please note that the payload you receive from Google for a non-tokenized card (PAN_ONLY) is always the same, regardless of the card network you selected while paying your Google Pay test transaction.
In case you want to test the decryption of the Google Pay payload from your website or your app on your own servers, you can find more details on Google's website related to testing with sample tokens. Our integration uses version ECv2.
Pre-production and production testing
The test cards provided in the test card suite of Google should only be used in the pre-production environment. In the production environment it is recommended to use real credit cards. Please note that testing in production means that actual money will be deducted from the card you use.
-
Show Hide
Hiper
Unfortunately we do not have test data for this card -
Show Hide
Hipercard
Unfortunately we do not have test data for this card -
Show Hide
iDEAL
The test data is related to the sandbox environment and only describes the different test cases. The difference between using the hosted payment page or not using the hosted payment page is not described.
Below are the positive test case input definitions with the expected results in the last column.
Country code Currency code Issuer ID PP ID Amount PStatus ID NL EUR INGBNL2A 809 100 800 NL EUR INGBNL2A 809 200 800 For testing negative payment flow, please use below data.
Country code Currency code Issuer ID PP ID Amount Event ID PStatus ID NL EUR INGBNL2A 809 2000 400870 50 NL EUR INGBNL2A 809 1200 400880 50 Payment steps
After initializing the payment a redirect needs to happen. The page automatically takes you to the returnurl. The payment ends up on the status Completed with the status ID 800.
Refunds in sandbox
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Invoice
For the sandbox no test data is available for this product.
-
Show Hide
Italcred
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 5043380343417303 123 1002 ARS AR 139 109196 0 0 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 5043380343417303 123 1005 ARS AR 139 430285 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
JCB
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 3566000020000410 123 11001 CAD CA 125 OK2847 0 0 600 3566000020000410 123 11008 CAD CA 125 OK3032 0 0 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 3566000020000410 123 2100 CAD CA 125 430409 0 0 3566000020000410 123 3100 USD US 125 430285 0 0 Currencies
To be able to test every single currency as listed in the currency table, please use following details.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result 3566000020000410 432 11001 AUD NL 125 OK2847 0 0 3566000020000410 432 11001 CNY NL 125 OK2847 0 0 3566000020000410 432 11001 HKD NL 125 OK2847 0 0 3566000020000410 432 11001 MYR NL 125 OK2847 0 0 3566000020000410 432 11001 SGD NL 125 OK2847 0 0 3566000020000410 432 11001 THB NL 125 OK2847 0 0 3566000020000410 432 11001 TWD NL 125 OK2847 0 0 3566000020000410 432 11001 CHF NL 125 OK2847 0 0 3566000020000410 432 11001 BRL NL 125 OK2847 0 0 3566000020000410 432 11001 BHD NL 125 OK2847 0 0 3566000020000410 432 11001 PHP NL 125 OK2847 0 0 3566000020000410 432 11001 CAD NL 125 OK2847 0 0 3566000020000410 432 11001 GBP NL 125 OK2847 0 0 3566000020000410 432 11001 EUR NL 125 OK2847 0 0 3566000020000410 432 11001 USD NL 125 OK2847 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Konbini
The GlobalCollect platform has not integrated a Konbini and Pay-easy end-to-end testing environment for merchants.
-
Show Hide
Maestro
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 6331101999990073 321 8300 GBP FR 117 10000 U U 6001 633478111298873700 321 8200 GBP FR 117 10000 U U 600 6304939304310009610 321 8200 GBP FR 117 10000 U U 600
1 3D secure transactions will not go directly to 600 status, but only after authentication steps when applicable.
Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
3D secure
On payment product id 117 (maestro) 3d secure is enabled as all Maestro transaction are mandated to be processed with 3D secure.
AVS
Address verification is enabled on all cards that support it. Different cases give different AVS result. In case the card type isn’t supporting AVS, the result will always be 0.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Card verification
Also known as 0$ authorization. This type of transaction is triggered with an amount of 0 and will only return a validated response resulting in a status of 300 and only works on a recurring model.
Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
3D secure handling
For the handling of transaction with 3D secure a redirect takes place for the consumer. In the Sandbox it will not show a login screen but a functional HTML form that needs to post the 3D secure validation to the payment platform. Please use that process to simulate the authentication process. The post action triggers the right action to be able to finish the payment.
The redirect behavior back and forward are as it would be in real production systems.
Sample of the form:
-
Show Hide
Mas
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 6034935354535357 321 1015 ARS AR 142 109196 0 0 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 6034935354535357 321 1051 ARS AR 142 430175 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Mastercard
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Expiry Date Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 5424180279791732 123 1144 CAD CA 3 OK2341 X 600 5424180279791732 123 3500 CAD CA 3 OK2345 X N 600 5424180279791732 321 2000 CAD CA 3 OK2346 X U 600 5424180279791732 321 1500 USD US 3 OK2348 Z 600 5424180279791732 123 11006 CAD CA 3 OK1433 N 0 600 5424180279791765 123 99900 CAD CA 3 OK1440 X 0 600 5424180279791732 123 11003 USD US 3 OK1452 N 0 600 5434842555555556 123 100 CAD CA 3 OK2323 Z P 600 5424180279791732 123 2200 CAD CA 3 OK2336 X M 600 5424180279791732 123 1144 CAD CA 3 OK2341 X 0 600 5424180279791732 123 3500 USD US 3 OK2345 X N 600 5424180279791732 123 2000 USD US 3 OK2346 X U 600 5424180279791732 123 1500 USD US 3 OK2348 Z 0 600 5424180279791732 123 11001 CAD CA 3 OK2390 N 0 600 5424180279791732 123 113 CAD CA 3 OK2384 X 0 600 5424180279791732 123 11008 USD US 3 OK5836 N 0 600 5424180279791732 123 1200 CAD CA 3 OK5839 Y 0 600 5424180279791732 123 1300 CAD CA 3 OK5840 X 0 600 5424180279791732 123 1400 CAD CA 3 OK5841 A 0 600 5481040000020035 123 1000 USD US 3 OK1131 X M 600 5354201978641111 123 1000 CAD CA 3 OK1131 X M 600 5469123084370553 123 12/2024 1000 RUB RU 3 600 5469125367380696 123 12/2024 1000 RUB RU 3 600 5486733999143033 123 12/2024 1000 RUB RU 3 600 5486732185168077 123 12/2024 1000 RUB RU 3 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 5424180279791732 123 2997 USD US 3 430285 X P 5424180279791732 123 4467 CAD CA 3 430285 X N 5424180279791732 123 31001 CAD CA 3 430475 0 0 5424180279791732 123 1600 USD US 3 430409 X 0 5424180279791732 123 2100 CAD CA 3 430409 X 0 5424180279791732 123 31006 USD US 3 430285 X 0 5424180279791740 123 99900 CAD CA 3 430285 Y 0 Currencies
To be able to test every single currency as listed in the currency table, please use following details.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result 5424180279791732 123 2200 See curr. table NL 3 OK2336 X M Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
3D secure
On payment product id 117 (maestro) 3d secure is enabled as all Maestro transaction are mandated to be processed with 3D secure.
AVS
Address verification is enabled on all cards that support it. Different cases give different AVS result. In case the card type isn’t supporting AVS, the result will always be 0.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Card verification
Also known as 0$ authorization. This type of transaction is triggered with an amount of 0 and will only return a validated response resulting in a status of 300 and only works on a recurring model.
Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
3D secure handling
For the handling of transaction with 3D secure a redirect takes place for the consumer. In the Sandbox it will not show a login screen but a functional HTML form that needs to post the 3D secure validation to the payment platform. Please use that process to simulate the authentication process. The post action triggers the right action to be able to finish the payment.
The redirect behavior back and forward are as it would be in real production systems.
Sample of the form:
-
Show Hide
Mastercard Debit
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 5424180279791732 123 2200 USD US 119 OK2336 X M 600 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
3D secure
On payment product id 117 (maestro) 3d secure is enabled as all Maestro transaction are mandated to be processed with 3D secure.
AVS
Address verification is enabled on all cards that support it. Different cases give different AVS result. In case the card type isn’t supporting AVS, the result will always be 0.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Card verification
Also known as 0$ authorization. This type of transaction is triggered with an amount of 0 and will only return a validated response resulting in a status of 300 and only works on a recurring model.
Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
3D secure handling
For the handling of transaction with 3D secure a redirect takes place for the consumer. In the Sandbox it will not show a login screen but a functional HTML form that needs to post the 3D secure validation to the payment platform. Please use that process to simulate the authentication process. The post action triggers the right action to be able to finish the payment.
The redirect behavior back and forward are as it would be in real production systems.
Sample of the form:
-
Show Hide
Mir
AnyPositives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Request AuthType Card number CVV Expiry Date Amount Currency code Country code Payment product ID Payment status ID Purchase 3 2200000000000061 123 12/2024 Any RUB RU 164 935 Pre-auth 2 2200000000000061 123 12/2024 Any RUB RU 164 680 Capture 2 2200000000000061 123 12/2024 Any RUB RU 164 925 Purchase 3 2202201502887108 123 12/2020 Any RUB RU 164 935 Pre-auth 2 2202201502887108 123 12/2020 Any RUB RU 164 680 Capture 2 2202201502887108 123 12/2020 Any RUB RU 164 925 Purchase 3 2202207558945880 123 12/2020 Any RUB RU 164 935 Pre-auth 2 2202207558945880 123 12/2020 Any RUB RU 164 680 Capture 2 2202207558945880 123 12/2020 Any RUB RU 164 925 Purchase 3 2200159223618891 123 12/2020 Any RUB RU 164 935 Pre-auth 2 2200159223618891 123 12/2020 Any RUB RU 164 680 Capture 2 2200159223618891 123 12/2020 Any RUB RU 164 925 Purchase 3 2200151893711247 123 12/2020 Any RUB RU 164 935 Pre-auth 2 2200151893711247 123 12/2020 Any RUB RU 164 680 Capture 2 2200151893711247 123 12/2020 Any RUB RU 164 925 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
AuthType Card number CVV Amount Currency code Country code Payment product ID Event code 2 / 3 2200000000000079 123 Any RUB RU 164 430360 2 / 3 2200000000001002 123 Any RUB RU 164 430345 Delayed settlement
- By default all transactions are set to Delayed settlement.
- In Sale mode, payment will lead to status 935.
- In Auth/Capture mode, a payment will lead to status 680, which subsequently requires to do a ApprovePayment to make the status go to 925.
- After transaction (Sale or Auth/Capture) is reported by acquirer status will change to 975.
- Reversal is available in status 680.
- Refund is available in status 975.
3D secure handling
For the handling of transaction with 3D secure a redirect takes place for the consumer. In the Sandbox it will not show a login screen but a functional HTML form that needs to post the 3D secure validation to the payment platform. Please use that process to simulate the authentication process. The post action triggers the right action to be able to finish the payment.
The redirect behavior back and forward are as it would be in real production systems.
Sample of the form:
-
Show Hide
Naranja
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 5895620033330020 123 1000 ARS AR 136 109196 0 0 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 5895620033330020 123 1051 ARS AR 136 430175 0 0 5895620033330020 123 1039 ARS AR 136 430694 0 0 5895620033330020 123 1005 ARS AR 136 430285 0 0 5895620033330020 123 1017 ARS AR 136 430424 0 0 5895620033330020 123 10022 ARS AR 136 485000 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Nativa
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 4870179877664434 321 1007 ARS AR 145 130170 0 0 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 4870179877664434 321 1005 ARS AR 145 430285 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
3D secure
On payment product id 117 (maestro) 3d secure is enabled as all Maestro transaction are mandated to be processed with 3D secure.
AVS
Address verification is enabled on all cards that support it. Different cases give different AVS result. In case the card type isn’t supporting AVS, the result will always be 0.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Card verification
Also known as 0$ authorization. This type of transaction is triggered with an amount of 0 and will only return a validated response resulting in a status of 300 and only works on a recurring model.
Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
3D secure handling
For the handling of transaction with 3D secure a redirect takes place for the consumer. In the Sandbox it will not show a login screen but a functional HTML form that needs to post the 3D secure validation to the payment platform. Please use that process to simulate the authentication process. The post action triggers the right action to be able to finish the payment.
The redirect behavior back and forward are as it would be in real production systems.
Sample of the form:
-
Show Hide
Nevada
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 5043630279791737 123 1001 ARS AR 137 109196 0 0 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 5043630279791737 123 1039 ARS AR 137 430694 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Nordea Finland
Below are the positive test case input definitions, with the expected results in the last column.
Country code Currency code Payment product ID Amount Payment status ID FI EUR 802 100 800 For testing negative payment flow, please use ‘cancel’ buttons after the redirects. These actions will result in status pending merchant and status id 130 for the payments.
After initializing the payment a redirect needs to happen. The page looks like below:
Click OK, you will end up on the next page:
Enter 1234 in the text box and click ‘ Vahvista’
Click the button to get back on the return URL. The payment ends up on the status completed with the status ID 800.
-
Show Hide
Pago Fácil
Pago Fácil does not offer an end to end testing environment for merchants.
-
Show Hide
PayPal
The following currencies are supported in the sandbox environment.
- Australian dollar (AUD)
- Canadian dollar (CAD)
- Czech koruna (CZK)
- Danish krone (DKK)
- Euro (EUR)
- Hong Kong dollar (HKD)
- Hungarian forint (HUF)
- Japanese yen (JPY)
- Mexican peso (MXN)
- New Zealand dollar (NZD)
- Norwegian krone (NOK)
- Polish zloty (PLN)
- Pound sterling (GBP)
- Russian ruble (RUB)
- Singapore dollar (SGD)
- Swedish krona (SEK)
- Swiss franc (CHF)
- Thai baht (THB)
- United States dollar (USD)
Positives
Below are the positive test case input definitions with the expected results in the last column.
MoreCountry code Currency code Payment product ID Amount Paypal account usr Paypal account pwd Payment status ID AU AUD 840 100 "gcsstag@outlook.com gcs2live" 800 CA CAD 840 100 "gcsstag@outlook.com gcs2live" 800 CH CHF 840 100 "gcsstag@outlook.com gcs2live" 800 CZ CZK 840 100 "gcsstag@outlook.com gcs2live" 800 DK DKK 840 100 "gcsstag@outlook.com gcs2live" 800 NL EUR 840 100 "gcsstag@outlook.com gcs2live" 800 GB GBP 840 100 "gcsstag@outlook.com gcs2live" 800 HK HKD 840 100 "gcsstag@outlook.com gcs2live" 800 HU HUF 840 100 "gcsstag@outlook.com gcs2live" 800 JP JPY 840 100 "gcsstag@outlook.com gcs2live" 800 MX MXN 840 100 "gcsstag@outlook.com gcs2live" 800 NO NOK 840 100 "gcsstag@outlook.com gcs2live" 800 NZ NZD 840 100 "gcsstag@outlook.com gcs2live" 800 PL PLN 840 100 "gcsstag@outlook.com gcs2live" 800 RU RUB 840 100 "gcsstag@outlook.com gcs2live" 800 SE SEK 840 100 "gcsstag@outlook.com gcs2live" 800 SG SGD 840 100 "gcsstag@outlook.com gcs2live" 800 TW TWD 840 100 "gcsstag@outlook.com gcs2live" 800 US USD 840 100 "gcsstag@outlook.com gcs2live" 800 Negatives
For testing negative payment flow, please cancel the payment after redirect, status of the payment will be 125.
Refunds in sandbox
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds
Payment test steps
After initializing the payment a redirect needs to happen. The page will look like below.
Please fill in the following data:
- Paypal password: gcs2live
- Email: gcsstag@outlook.com
Click ‘pay now’, you will automatically be redirected to RETURNURL. The payment ends up on status Completed with status ID 800.
-
Show Hide
Paysafecard
The test data is related to the sandbox environment and only describes the different test cases. The difference in using the hosted payment page or not is not described.
The following currencies are supported in the sandbox environment, please note that these currencies do not necessarily reflect the total number of supported currencies. These are indicated at the top of this page.
- Czech koruna (CZK)
- Danish krone (DKK)
- Euro (EUR)
- Mexican peso (MXN)
- Norwegian krone (NOK)
- Polish zloty (PLN)
- Pound sterling (GBP)
- Romanian new leu (RON)
- Swedish krona (SEK)
- Swiss franc (CHF)
Positives
Below are the positive test case input definitions with the expected results in the last column.
Country code Currency code Payment product ID Amount PIN Payment status ID CH CHF 830 100 0000 0000 0990 0828 800 CZ CZK 830 100 0000 0000 0990 0828 800 DK DKK 830 100 0000 0000 0990 0828 800 DE EUR 830 100 0000 0000 0990 0828 800 GB GBP 830 100 0000 0000 0990 0828 800 MX MXN 830 100 0000 0000 0990 0828 800 NO NOK 830 100 0000 0000 0990 0828 800 PL PLN 830 100 0000 0000 0990 0828 800 RO RON 830 100 0000 0000 0990 0828 800 SE SEK 830 100 0000 0000 0990 0828 800 Negatives
For testing negative payment flow, please cancel the payment after redirect, status of the payment will be Rejected with status ID 130 and eventid 400702.
Payment steps
After initializing the payment a redirect needs to happen. The page will look like below:
- 16 digit pin 0000 0000 0990 0828
- Tick the box ‘yes, I agree…….’
- Click ‘Pay’
The screen will change to the one shown below:
This is the final page and you will automatically be redirected to the return URL. The payment ends up on status Completed with status ID 800.
Refunds in sandbox
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Pyme Nacion
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 5049105546746461 321 1006 ARS AR 144 109196 0 0 600 Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 5049105546746461 321 1039 ARS AR 144 430694 0 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
3D secure
On payment product id 117 (maestro) 3d secure is enabled as all Maestro transaction are mandated to be processed with 3D secure.
AVS
Address verification is enabled on all cards that support it. Different cases give different AVS result. In case the card type isn’t supporting AVS, the result will always be 0.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Card verification
Also known as 0$ authorization. This type of transaction is triggered with an amount of 0 and will only return a validated response resulting in a status of 300 and only works on a recurring model.
Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
3D secure handling
For the handling of transaction with 3D secure a redirect takes place for the consumer. In the Sandbox it will not show a login screen but a functional HTML form that needs to post the 3D secure validation to the payment platform. Please use that process to simulate the authentication process. The post action triggers the right action to be able to finish the payment.
The redirect behavior back and forward are as it would be in real production systems.
Sample of the form:
-
Show Hide
SEPA Direct Debit
The test data is related to the sandbox environment and only describes the different test cases. The difference between using the hosted payment page or not using the hosted payment page is not described.
Positives
Below are the positive test case input definitions with the expected results in the last column.
IBAN Currency code Country code Payment product ID Payment status ID NL08 INGB 0000000 555 EUR NL 770 600 DE46 7202007 00359 736690 EUR DE 770 600 FR14 2004 1010 0505 0001 3M02 606 EUR FR 770 600 Negatives
For testing negative payment flow, please use below data.
IBAN Currency code Country code Payment product ID Event ID Payment status ID NL08INGB0001234567 EUR NL 770 420080 100 DE46 7202007 00359 666555 EUR DE 770 420080 100 FR14 2004 54654649871 EUR FR 770 420080 100 Refunds in sandbox
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Skrill
The test data is related to the sandbox environment and only describes the different test cases. The difference in using the hosted payment page or not is not described.
The following currencies are supported in the sandbox environment, please note that these currencies do not reflect the total number of supported currencies. These are indicated at the top of this page.
- Australian dollar (AUD)
- Bulgarian lev (BGN)
- Canadian dollar (CAD)
- Croatian kuna (HRK)
- Czech koruna (CZK)
- Danish krone (DKK)
- Euro (EUR)
- Hong Kong dollar (HKD)
- Hungarian forint (HUF)
- Icelandic króna (ISK)
- Indian rupee (INR)
- Israeli new shekel (ILS)
- Japanese yen (JPY)
- Malaysian ringgit (MYR)
- New Zealand dollar (NZD)
- Norwegian krone (NOK)
- Polish zloty (PLN)
- Pound sterling (GBP)
- Romanian new leu (RON)
- Singapore dollar (SGD)
- South African rand (ZAR)
- South Korean won (KRW)
- Swedish krona (SEK)
- Swiss franc (CHF)
- Thai baht (THB)
- Turkish lira (TRY)
- United States dollar (USD)
Positives
Below are the positive test case input definitions with the expected results in the last column. The payment will end at a status completed with the status ID 800.
MoreCountry code Currency code Payment product ID Amount Payment status ID AU AUD 843 100 800 BG BGN 843 100 800 CA CAD 843 100 800 CH CHF 843 100 800 CZ CZK 843 100 800 DK DKK 843 100 800 EE EEK 843 100 800 FR EUR 843 100 800 GB GBP 843 100 800 HK HKD 843 100 800 HR HRK 843 100 800 HU HUF 843 100 800 IL ILS 843 100 800 IN INR 843 100 800 IS ISK 843 100 800 JP JPY 843 100 800 KR KRW 843 100 800 MY MYR 843 100 800 NO NOK 843 100 800 NZ NZD 843 100 800 PL PLN 843 100 800 RO RON 843 100 800 SE SEK 843 100 800 SG SGD 843 100 800 TH THB 843 100 800 TR TRY 843 100 800 TW TWD 843 100 800 US USD 843 100 800 ZA ZAR 843 100 800 Negatives
Please use following details, the payments will stay at the status ‘pending payment, which has the status ID 50.
MoreCountry code Currency code Payment product ID Amount Payment status ID AU AUD 843 404 50 BG BGN 843 404 50 CA CAD 843 404 50 CH CHF 843 404 50 CZ CZK 843 404 50 DK DKK 843 404 50 EE EEK 843 404 50 FR EUR 843 404 50 GB GBP 843 404 50 HK HKD 843 404 50 HR HRK 843 404 50 HU HUF 843 404 50 IL ILS 843 404 50 IN INR 843 404 50 IS ISK 843 404 50 JP JPY 843 404 50 KR KRW 843 404 50 MY MYR 843 404 50 NO NOK 843 404 50 NZ NZD 843 404 50 PL PLN 843 404 50 RO RON 843 404 50 SE SEK 843 404 50 SG SGD 843 404 50 TH THB 843 404 50 TR TRY 843 404 50 TW TWD 843 404 50 US USD 843 404 50 ZA ZAR 843 404 50 Refunds in sandbox
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
Payment steps
After initializing the payment a redirect must happen. The page will look like below:
After you click ‘LOGIN’, you will automatically be redirected to RETURNURL. The payment ends up on 800 status.
-
Show Hide
Sofort
The test data is related to the sandbox environment and only describes the different test cases. The difference in using the hosted payment page or not is not described.
The following currencies are supported in the sandbox environment. Please note that these currencies do not reflect the total number of supported currencies. These are indicated at the top of this page.
- Euro (EUR)
- Polish zloty (PLN)
- Pound sterling (GBP)
- Swiss franc (CHF)
Positives
Below are the positive test case input definitions with the expected results in the last column.
Country code Currency code Payment product ID Amount Payment status ID CH CHF 836 100 800 DE EUR 836 100 800 GB GBP 836 100 800 PL PLN 836 100 800 Negatives
For testing negative payment flow, please cancel the payment upon redirection, the status of the payment will be 125 with eventid 400700.
Payment steps
After initializing the payment a redirect needs to happen. The page will look like the following. Type "demo" and select the "Demo Bank":
You can use any details on this page. Please click "Next".
Please type 12345 as instructed on the page. Click Next to complete the transaction. The status ID of the transaction will be 800.
The following is how a page looks like on a mobile device:
Refunds in sandbox
Transactions are not refundable on status Completed with status ID 800. A separate process is scheduled for the payment to end up on a refundable status for that. Please wait for an hour for all your test transactions at status Completed with status ID 800 to be processed and set for refunds.
-
Show Hide
Tarjeta Shopping
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 6034885454536229 232 1008 ARS AR 149 130170 0 0 600 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
-
Show Hide
Trustly
On the sandbox environment all supported combinations for countries and currencies are available. By submitting a transaction you will be redirected to the checkout page of Trustly. Follow the instructions on the page to complete your test.
-
Show Hide
UnionPay International - ExpressPay
Test Data
The testing system is set-up in such a manner that any scenario that is not listed below will result in a positive test case.
All of the below test cases are controlled purely by amount, the card number, CVV, expiry date and currency do not affect the test cases.
Any of the below card details may be used for any of the test cases:
Card number CVV Expiry Date 6250930000000002 123 1233 6250930000000010 123 1233 6250930000000028 123 1233 6250930000000036 123 1233 6250930000000044 123 1233 6250930000000051 123 1233 6250930000000069 123 1233 6250930000000077 123 1233 6250930000000085 123 1233 6250930000000093 123 1233 Test Cases
The default case is positive so every scenario not listed in the below table is positive; any combination of test data and currency will result in a successful authorization.
The below table differentiates between synchronous responses and asynchronous response, the synchronous response is an "acknowledgement" and the asynchronous response is the actual response.
In the context of an authorization, this means that a synchronous OK indicates that technically our request for processing an authorization was accepted, but the authorization request has yet to be processed, the asynchronous response will contain the actual authorization request result.
We also allow for granular testing based on transaction type, to summarize how to trigger each of them:
Transaction Type Trigger Sale Default or explicitly by setting authorizationMode to SALE Pre-authorization Set authorizationMode to PRE_AUTHORIZATION Capture Pre-authorization Call approvePayment on a pre-authorization transaction Refund Call doRefund on a settled transaction Void Sale Call cancelPayment on a sale transaction Reverse Pre-authorization Call cancelPayment on a pre-authorization transaction that is at status PENDING_MERCHANTVoid Pre-authorization Call cancelPayment on a pre-authorization transaction that is at status CAPTUREDTo be able to test all test cases, you need to combine "default" positive non-listed scenarios with listed scenarios.
For example, if you wish to trigger the negative scenario for capturing a pre-authorization transaction that results in a rejection with reason 430433 - TOO_MUCH_USAGE, you first need to create a pre-authorization transaction with the amount (of at least) 811 to be able to call approvePayment with 811 to trigger the negative scenario.
Do note that all asynchronous responses listed in the below table will occur after 15 minutes.
Transaction Type Amount Synchronous Response Asynchronous Response Sale 1 OK OK Sale 10 430409 - OTHERS Sale 20 430409 - OTHERS Sale 101 430409 - OTHERS Sale 320 430409 - OTHERS Sale 780000 430409 - OTHERS Sale 601 430409 - OTHERS Sale 64000 430409 - OTHERS Sale 650 430409 - OTHERS Sale 670 430409 - OTHERS Sale 690 430409 - OTHERS Sale 720 430409 - OTHERS Sale 730 430409 - OTHERS Sale 810 430409 - OTHERS Sale 2 OK 430285 - DO_NOT_HONOR Sale 21 OK 430424 - SYSTEM_MALFUNCTION Sale 102 OK 430315 - FORMAT_ERROR Sale 321 OK 430412 - RESTRICTED Sale 811 OK 430433 - TOO_MUCH_USAGE Sale 391 OK 430430 - TIMEOUT Sale 602 OK 430409 - REFERRED Sale 721 OK 430396 - NOT_PERMITTED_TO_CARDHOLDER Sale 780001 OK 430175 - AMOUNT_TOO_LARGE Sale 64001 OK 430360 - LOW_FUNDS Sale 651 OK 430324 - INCORRECT_PIN_NA Sale 671 OK 430165 - ALLOWABLE_PIN_TRIES_EXCEEDED_NA Sale 730 OK 430306 - EXPIRED_CARD Pre-authorization 1 OK OK Pre-authorization 200 430409 - OTHERS Pre-authorization 1000 430409 - OTHERS Pre-authorization 3200 430409 - OTHERS Pre-authorization 7800000 430409 - OTHERS Pre-authorization 6000 430409 - OTHERS Pre-authorization 6400000 430409 - OTHERS Pre-authorization 6500 430409 - OTHERS Pre-authorization 6700 430409 - OTHERS Pre-authorization 6900 430409 - OTHERS Pre-authorization 7200 430409 - OTHERS Pre-authorization 7300 430409 - OTHERS Pre-authorization 8100 430409 - OTHERS Pre-authorization 2 OK 430285 - DO_NOT_HONOR Pre-authorization 201 OK 430424 - SYSTEM_MALFUNCTION Pre-authorization 1001 OK 430315 - FORMAT_ERROR Pre-authorization 3201 OK 430412 - RESTRICTED Pre-authorization 8101 OK 430433 - TOO_MUCH_USAGE Pre-authorization 3901 OK 430430 - TIMEOUT Pre-authorization 6001 OK 430409 - REFERRED Pre-authorization 7201 OK 430396 - NOT_PERMITTED_TO_CARDHOLDER Pre-authorization 7800001 OK 430175 - AMOUNT_TOO_LARGE Pre-authorization 6400001 OK 430360 - LOW_FUNDS Pre-authorization 6501 OK 430324 - INCORRECT_PIN_NA Pre-authorization 6701 OK 430165 - ALLOWABLE_PIN_TRIES_EXCEEDED_NA Pre-authorization 7301 OK 430306 - EXPIRED_CARD Capture Pre-authorization 1 OK OK Capture Pre-authorization 10 430409 - OTHERS Capture Pre-authorization 20 430409 - OTHERS Capture Pre-authorization 101 430409 - OTHERS Capture Pre-authorization 320 430409 - OTHERS Capture Pre-authorization 780000 430409 - OTHERS Capture Pre-authorization 601 430409 - OTHERS Capture Pre-authorization 64000 430409 - OTHERS Capture Pre-authorization 650 430409 - OTHERS Capture Pre-authorization 670 430409 - OTHERS Capture Pre-authorization 690 430409 - OTHERS Capture Pre-authorization 720 430409 - OTHERS Capture Pre-authorization 730 430409 - OTHERS Capture Pre-authorization 810 430409 - OTHERS Capture Pre-authorization 3 OK OK Capture Pre-authorization 21 OK 430424 - SYSTEM_MALFUNCTION Capture Pre-authorization 102 OK 430315 - FORMAT_ERROR Capture Pre-authorization 321 OK 430412 - RESTRICTED Capture Pre-authorization 811 OK 430433 - TOO_MUCH_USAGE Capture Pre-authorization 390 OK 430430 - TIMEOUT Capture Pre-authorization 602 OK 430409 - REFERRED Capture Pre-authorization 721 OK 430396 - NOT_PERMITTED_TO_CARDHOLDER Capture Pre-authorization 780001 OK 430175 - AMOUNT_TOO_LARGE Capture Pre-authorization 64001 OK 430360 - LOW_FUNDS Capture Pre-authorization 651 OK 430324 - INCORRECT_PIN_NA Capture Pre-authorization 671 OK 430165 - ALLOWABLE_PIN_TRIES_EXCEEDED_NA Capture Pre-authorization 731 OK 430306 - EXPIRED_CARD Refund 1 OK OK Refund 900 430409 - OTHERS Refund 20 430409 - OTHERS Refund 101 430409 - OTHERS Refund 320 430409 - OTHERS Refund 780000 430409 - OTHERS Refund 601 430409 - OTHERS Refund 64000 430409 - OTHERS Refund 650 430409 - OTHERS Refund 670 430409 - OTHERS Refund 690 430409 - OTHERS Refund 720 430409 - OTHERS Refund 730 430409 - OTHERS Refund 810 430409 - OTHERS Refund 4 OK OK Refund 44 OK 430285 - DO_NOT_HONOR Refund 103 OK 430315 - FORMAT_ERROR Refund 324 OK 430412 - RESTRICTED Refund 814 OK 430433 - TOO_MUCH_USAGE Refund 390 OK 430430 - TIMEOUT Refund 604 OK 430409 - REFERRED Refund 724 OK 430396 - NOT_PERMITTED_TO_CARDHOLDER Refund 780004 OK 430175 - AMOUNT_TOO_LARGE Refund 64004 OK 430360 - LOW_FUNDS Refund 654 OK 430324 - INCORRECT_PIN_NA Refund 674 OK 430165 - ALLOWABLE_PIN_TRIES_EXCEEDED_NA Refund 734 OK 430306 - EXPIRED_CARD Void Sale 1 OK OK Void Sale 123 430409 - OTHERS Void Sale 20 430409 - OTHERS Void Sale 101 430409 - OTHERS Void Sale 320 430409 - OTHERS Void Sale 780000 430409 - OTHERS Void Sale 601 430409 - OTHERS Void Sale 64000 430409 - OTHERS Void Sale 650 430409 - OTHERS Void Sale 670 430409 - OTHERS Void Sale 690 430409 - OTHERS Void Sale 720 430409 - OTHERS Void Sale 730 430409 - OTHERS Void Sale 810 430409 - OTHERS Void Sale 4 OK 430424 - SYSTEM_MALFUNCTION Void Sale 107 OK 430315 - FORMAT_ERROR Void Sale 327 OK 430412 - RESTRICTED Void Sale 817 OK 430433 - TOO_MUCH_USAGE Void Sale 397 OK 430430 - TIMEOUT Void Sale 607 OK 430409 - REFERRED Void Sale 727 OK 430396 - NOT_PERMITTED_TO_CARDHOLDER Void Sale 780007 OK 430175 - AMOUNT_TOO_LARGE Void Sale 64007 OK 430360 - LOW_FUNDS Void Sale 657 OK 430324 - INCORRECT_PIN_NA Void Sale 677 OK 430165 - ALLOWABLE_PIN_TRIES_EXCEEDED_NA Void Sale 737 OK 430306 - EXPIRED_CARD Reverse Pre-authorization 1 OK OK Reverse Pre-authorization 10 430409 - OTHERS Reverse Pre-authorization 20 430409 - OTHERS Reverse Pre-authorization 101 430409 - OTHERS Reverse Pre-authorization 320 430409 - OTHERS Reverse Pre-authorization 780000 430409 - OTHERS Reverse Pre-authorization 601 430409 - OTHERS Reverse Pre-authorization 64000 430409 - OTHERS Reverse Pre-authorization 650 430409 - OTHERS Reverse Pre-authorization 670 430409 - OTHERS Reverse Pre-authorization 690 430409 - OTHERS Reverse Pre-authorization 720 430409 - OTHERS Reverse Pre-authorization 730 430409 - OTHERS Reverse Pre-authorization 810 430409 - OTHERS Reverse Pre-authorization 8 OK 430424 - SYSTEM_MALFUNCTION Reverse Pre-authorization 108 OK 430315 - FORMAT_ERROR Reverse Pre-authorization 1111 OK 430412 - RESTRICTED Reverse Pre-authorization 818 OK 430433 - TOO_MUCH_USAGE Reverse Pre-authorization 398 OK 430430 - TIMEOUT Reverse Pre-authorization 608 OK 430409 - REFERRED Reverse Pre-authorization 728 OK 430396 - NOT_PERMITTED_TO_CARDHOLDER Reverse Pre-authorization 780008 OK 430175 - AMOUNT_TOO_LARGE Reverse Pre-authorization 64008 OK 430360 - LOW_FUNDS Reverse Pre-authorization 658 OK 430324 - INCORRECT_PIN_NA Reverse Pre-authorization 678 OK 430165 - ALLOWABLE_PIN_TRIES_EXCEEDED_NA Reverse Pre-authorization 738 OK 430306 - EXPIRED_CARD Void Pre-authorization 11 OK OK Void Pre-authorization 111 430409 - OTHERS Void Pre-authorization 220 430409 - OTHERS Void Pre-authorization 111 430409 - OTHERS Void Pre-authorization 332 430409 - OTHERS Void Pre-authorization 770000 430409 - OTHERS Void Pre-authorization 661 430409 - OTHERS Void Pre-authorization 6400 430409 - OTHERS Void Pre-authorization 665 430409 - OTHERS Void Pre-authorization 678 430409 - OTHERS Void Pre-authorization 669 430409 - OTHERS Void Pre-authorization 772 430409 - OTHERS Void Pre-authorization 773 430409 - OTHERS Void Pre-authorization 881 430409 - OTHERS Void Pre-authorization 4444 OK 430285 - DO_NOT_HONOR Void Pre-authorization 119 OK 430315 - FORMAT_ERROR Void Pre-authorization 1119 OK 430412 - RESTRICTED Void Pre-authorization 819 OK 430433 - TOO_MUCH_USAGE Void Pre-authorization 399 OK 430430 - TIMEOUT Void Pre-authorization 609 OK 430409 - REFERRED Void Pre-authorization 782 OK 430396 - NOT_PERMITTED_TO_CARDHOLDER Void Pre-authorization 770009 OK 430175 - AMOUNT_TOO_LARGE Void Pre-authorization 6409 OK 430360 - LOW_FUNDS Void Pre-authorization 659 OK 430324 - INCORRECT_PIN_NA Void Pre-authorization 679 OK 430165 - ALLOWABLE_PIN_TRIES_EXCEEDED_NA Void Pre-authorization 739 OK 430306 - EXPIRED_CARD Fraud Services
Fraud services are unsupported for UnionPay ExpressPay.
3D secure
3D Secure is unsupported for UnionPay ExpressPay.
AVS
AVS is unsupported for UnionPay ExpressPay.
Delayed settlement
Delayed settlement can be triggered by using authorizationMode with value PRE_AUTHORIZATION, in which case the transaction will first go to status PENDING_MERCHANT on a successful asynchronous response, after which you can use the approvePayment API call to control when you wish to settle.
Card verification
Card verification is currently unsupported for UnionPay ExpressPay.
Refunding
Transactions can be refunded after they have been successfully settled.
-
Show Hide
UnionPay International - SecurePay
Unfortunately we do not have test data for this card -
Show Hide
Visa
Positives
Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.
Card number CVV Expiry Date Amount Currency code Country code Payment product ID Auth code AVS result CVV result Payment status ID 4012000033330026 123 3500 USD US 1 OK2334 Y 0 600 4567350000427977 123 4005 USD US 1 OK1131 0 0 600 4012000033330026 999 1100 USD US 1 OK1131 0 0 600 4012000077777777 123 999 CAD CA 1 OK1419 Y 0 600 4012000033330026 123 1700 CAD CA 1 OK1175 0 P 600 4012000033330026 123 1000 CAD CA 1 OK1178 0 P 600 4012000033330026 123 1100 USD US 1 OK1180 0 0 600 4012000033330026 124 1100 CAD CA 1 OK2316 N 0 600 4500600000000061 123 10100 USD US 1 OK2319 B 0 600 4500600000000061 123 10200 CAD CA 1 OK2322 C 0 600 4012000033330026 123 9200 CAD CA 1 OK2324 Y M 600 4012000033330026 123 8744 USD US 1 OK232C Y 0 600 4012000033330026 123 5500 USD US 1 OK2329 Y S 600 4012000033330026 123 2000 USD US 1 OK2331 Y 0 600 4012000033330026 123 3500 CAD CA 1 OK2334 Y 0 600 4012000033330026 123 11065 USD US 1 OK2371 Z P 600 4012000033330026 123 111 CAD CA 1 OK2372 Z P 600 4012000033330026 123 11062 USD US 1 OK2404 Z P 600 4012000033330026 123 1101 USD US 1 OK2419 Z P 600 4012000033330026 125 1100 CAD CA 1 OK5830 N 0 600 4012000033330026 123 11012 CAD CA 1 OK5833 Z P 600 4012000033330026 123 1200 USD US 1 OK5834 Y 0 600 4012000033330026 123 1500 USD US 1 OK5835 U 0 600 4063651370499176 123 1000 CAD CA 1 OK1131 X M 600 4063651370499176 123 1100 USD US 1 OK1131 N M 600 4012001038443335 123 1000 CAD CA 1 OK1131 X M 600 4187603025743962 123 1000 CAD CA 1 OK1131 X M 600 4063651370499176 123 321 USD US 1 OK1131 X M 600 4063651370499176 123 500 USD US 1 OK1131 X M 600 4063651370499176 123 0 CAD CA 1 OK1131 X 0 3001 4539791001730106 123 140 CAD CA 1 OK1131 0 0 600 4063651370499176 123 2345 CAD CA 1 OK1131 X M 600 4276025067630158 123 12/2024 1000 RUB RU 1 OK1131 600 4276024450233308 123 12/2024 1000 RUB RU 1 OK1131 600 4584118188287409 123 12/2024 1000 RUB RU 1 OK1131 600 4584112640348586 123 12/2024 1000 RUB RU 1 OK1131 600 1 Card verification transactions will only end up in status 300 and will not be settled. Be aware this only works on initial attempt for recurring orders.
Negatives
The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.
Card number CVV Amount Currency code Country code Payment product ID Event code AVS result CVV result 4457010000000009 123 100 USD US 1 430424 0 0 4012000033330026 123 3156 CAD CA 1 430475 0 0 4012000033330026 123 3100 USD US 1 430327 0 0 4543059790016721 123 3099 USD US 1 430424 0 0 4012000033330026 123 2100 USD US 1 430409 Y 0 4012000033330026 123 3155 CAD CA 1 430285 Y M 4012000033330026 123 4100 USD US 1 430330 Y 0 4012000033330026 123 6100 CAD CA 1 430306 Y 0 4012000033330026 123 7100 USD US 1 430260 Y 0 4012000033330026 123 8100 CAD CA 1 430403 Y 0 4012000088888886 123 999 USD US 1 430475 0 0 4263971921001307 123 100 CAD CA 1 430424 0 0 4012000033330026 123 2995 CAD CA 1 430285 Y 0 4012000033330026 123 5200 USD US 1 430285 Y 0 Currencies
To be able to test every single currency as listed in the currency table, please use following details.
Card number CVV Amount Currency code Country code Payment product ID Auth code AVS result CVV result 4012000033330026 123 3500 See curr. table NL 1 OK2334 Y 0 Fraud Services
Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:
City Fraud Result Payment status Amsterdam A(ccept) 600/800 Calais C(hallenged) 525 Denver D(eny) 160 For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).
It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.
3D secure
On payment product id 117 (maestro) 3d secure is enabled as all Maestro transaction are mandated to be processed with 3D secure.
AVS
Address verification is enabled on all cards that support it. Different cases give different AVS result. In case the card type isn’t supporting AVS, the result will always be 0.
Delayed settlement
By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.Card verification
Also known as 0$ authorization. This type of transaction is triggered with an amount of 0 and will only return a validated response resulting in a status of 300 and only works on a recurring model.
Refunding
Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.
3D secure handling
For the handling of transaction with 3D secure a redirect takes place for the consumer. In the Sandbox it will not show a login screen but a functional HTML form that needs to post the 3D secure validation to the payment platform. Please use that process to simulate the authentication process. The post action triggers the right action to be able to finish the payment.
The redirect behavior back and forward are as it would be in real production systems.
Sample of the form:
-
Show Hide
Visa Debit
Unfortunately we do not have test data for this card -
Show Hide
Visa Electron
Unfortunately we do not have test data for this card -
Show Hide
WebMoney
Unfortunately we cannot provide test data for WebMoney. Please find below screenshots of the checkout flow.
The consumer places the order and fills out the account details.
In the next step, the consumer has to fill out the CAPTCHA and the system will check if the certificate is installed.
If the certificate is present the consumer will be able to complete the order.
-
Show Hide
WeChat Pay
WeChat Pay has no sandbox environment.
The test capabilities are limited on Pre-Production see below. Test on Pre-production when test are succesfull. We advise you to do a penny test on production to a end to end test in all supported currencies.
Pre-Production test capabilities
- Tests can be done only in USD.
- Desktop/Mobile integrations can be tested
- Test until status CAPTURED
- Can’t test refunds
Countries and currencies:
The following countries and currencies are supported:
Currency Code
Currency
Decimals
Countries
USD United States Dollar 2 All countries Positive Case
Below are the positive test case input definitions with the expected results in the last column.
Countries Currency code Payment Product Id Amount Payment Status Id All countries USD 863 50 CAPTURED Negative caseFor testing negative payment flow, please cancel the payment after redirect or leave the 2 hour session open, the resulting status of the payment will remain REDIRECTED.Countries Currency code Payment Product Id Amount Payment Status Id All countries CNY 863 50 ERROR Refunds
Refunds can be only done in production environment.
Payment test steps
MyHostedCheckout
-
Show Hide
WL Account-Based Payments
Redirect to partialRedirectUrl which lands you on the following page:
Select Instant Bank Transfer as your product.
You are re-directed to the following page where a couple of steps have to be taken:
Select United Kingdom as your country.
Select the Volt Mock Bank
Agree to the terms and conditions.
Press the 'CONTINUE TO PAYMENT' button which will lead you to the following page:
Press the 'CONTINUE ON DESKTOP' button as we have no capabilities for testing this with QR with this bank.
As this is a test account there is no re-direct to a bank but the payment will be completed at this point.
Please keep in mind that this is only applicable for testing purposes and with real payments the customer will be redirected to their bank page where he or she will have to login to complete the payment.
If you have any issues during testing please feel free to let us know.
