Testing procedure
Card Payments
Test cards
Integration development is made on test environment. Test environment supports any cards for the following international card brands:
- Visa
- V-Pay
- Mastercard
- Maestro
- American Express
It supports also local card brands:
- eftpos – Australia
- Bancontact - Belgium
- Girocard - Germany
- CB - France
All cards can be used (including “the real” ones), but we suggest to use test cards provided in following test applications available at Google Play:
| Application | Link | Cards included |
|---|---|---|
| Visa Mobile CDET | VISA Mobile CDET | Visa |
| HCE Test Tool | HCE Test Tool | Visa, Mastercard, American Express |
| Amex Payment Test Emulator | Amex Payment Test Emulator | American express |
Mock simulator for card payments
On sandbox environment it is possible to to simulate special behavior/response code for the application by using a special amount . This only works when using a terminal profile that is connected to the mock simulator. Please reach out to your integration partner in case of abny doubt or to know which termianl tprofile is connected to the mock simulator.
Respond with a specific ISO response code by using an amount of 42.XX, where XX stands for the required ISO response code
| Transaction amount | Transaction Status | ISO response code | Description |
|---|---|---|---|
| 42.00 | Cleared | 00 | Transaction approved |
| 42.04 | Declined | 04 | Issuer declined card - do not retry |
| 42.05 | Declined | 05 | Authorizaiton declined by Issuer |
| 42.33 | Declined | 33 | Expired card - do not retry |
| 42.55 | Declined | 55 | Incorrect PIN - retry |
| 42.60 | PIN entry | 60 | SCA required – transaction to be continued |
| 42.80 | Declined | 80 | Amount no longer available - retry |
| 42.xx | Declined | xx | Any other response code |
Respond after a specified timeout by using an amount of 43.XX, where XX stands for the delay in seconds For example 43,20 - the transaction will be approved after 20 seconds.
Respond with an error by using an amount of 44.XX, where XX stands for the type of error For example 44,20 - the transaction will fail with a server error. The error code after the decimal point can only been seen at the backend but not at the mobile.
Mock simulator for DCC transactions
On sandbox environment it is possible to to simulate DCC transactions if DCC is enabled for the terminal. This only works when using a terminal profile that is connected to the mock simulator. Please reach out to your integration partner in case of any doubt or to know which terminal profile is connected to the mock simulator.
For Visa transactions, DCC is offered for any amount of the transaction As of bacend v6.5 (November 2026), DCC is also offered for any amount of the transaction for Mastercard. Before backend v6.5 DCC was only offered for an amount above CVM limit.
| Amount | Description |
|---|---|
| amount > 500.00 | return reglementary rate (ecbIndicator = true) |
| amount < 500.00 | return no reglementary rate (ecbIndicator = false) |
| amount == 999.00 | DCC server error, HTTP 500 |
| amount == 399.00 | DCC Declined (for no reglementary rate option) |
| amount == 699.00 | DCC Declined (for reglementary rate option) |
| amount == 300.00 | DCC Invalid Merchant (for no reglementary rate option) |
| amount == 600.00 | DCC Invalid Merchant (for reglementary rate option) |
| amount > 100.00 | return dcc disclaimers (both display and receipt) |
| amount < 100.00 | return no dcc disclaimers (nor display nor receipt) |
If the terminal (local currency) is configured for EUR, the DCC offer will be in USD (foreign currency) If the terminal (local currency) is configured for a non-EUR cuurency, DCC offer will be in EUR (foreign currency) DCC conversion does not take in account the currency of the testcard.
Rates are set at the backend and are fixed
| Local Currecncy | Foreign Currecny | Conversation rate |
|---|---|---|
| EUR | USD | 1,05 |
| USD | EUR | 0,95 |
| CHF | EUR | 1,06 |
| PLN | EUR | 0,24 |
| CZK | EUR | 0,04 |
| DEF | EUR | 0,50 |
Alternative Payment Methods
Based on QR Codes:
- TWINT
- AliPay
- Wero
Mock simulator for QR-payments
On sandbox environment it is possible to to simulate special behavior/response code for the application by using a special amount . This only works when using a terminal profile that is connected to the mock simulator. Please reach out to your integration partner in case of abny doubt or to know which termianl tprofile is connected to the mock simulator.
When using the mock for APM, no customer app is needed, checkin and confirmation is all handled by the mock.
For DEFAULT AMOUNT the behavior is as follows (default amount is any amount except the special amount s that are listed in the below table):
- Checkin successful (CHEKINED) after 5s
- Payment successful (ACCEPTED) after 5s
- Confirm/cancel always succeed
- Refund successful after 5s
SPECIAL AMOUNTS
| Amount | Description |
|---|---|
| 10 | Checkin DECLINED after 5s |
| 11 | Checkin DECLINED after 10s |
| 20 | Checkin EXPIRED after 5s |
| 21 | Checkin EXPIRED after 10s |
| 30 | Checkin SUCCESSFUL after 10s |
| 31 | Checkin will never response |
| 40 | Payment DECLINED after 5s |
| 41 | Payment DECLINED after 10s |
| 50 | Payment EXPIRED after 5s |
| 51 | Payment EXPIRED after 10s |
| 60 | Payment SUCCESSFUL after 10s |
| 61 | Payment will never response |
| 70 | Reserved for backend testing |
| 71 | Reserved for backend testing |
| 72 | Reserved for backend testing |
| 73 | Reserved for backend testing |
| 74 | Reserved for backend testing |
| 100 | Refund/Credit CONFIRMED after 5s |
| 110 | Refund/Credit CANCELLED after 5s |
| 120 | Refund/Credit DECLINED after 5s |
| 130 | Refund/Credit left in ACCEPTED status (auto reversal success) |
| 140 | Auth delayed confirm 15s |
| 141 | Refund/Credit delayed confirm 15s |
| 170 | Reserved for backend testing |
| 171 | Reserved for backend testing |
| 172 | Reserved for backend testing |
| 173 | Reserved for backend testing |
| 174 | PaymenNotification is sent after process ends: 10s |
BLIK Payments
On sandbox environment it is possible to to simulate special behavior/response code for the application by using a special amount . This only works when using a terminal profile that is connected to the mock simulator. Please reach out to your integration partner in case of abny doubt or to know which termianl tprofile is connected to the mock simulator.
Based on 1-time codes generated by banking app:
Mock simulator for BLIK payments