Test cards and credentials

CAUTION: These cards are for use on the integration environment only (which is simulating the payment authorization). Using a card which is not listed here will not allow you to progress with the transaction beyond the main payment page of the gateway.

If you are looking for a way how to perform the acceptance test transactions required by the bank after contract conclusion in order to activate the payments on your page, please use the following test cases in the Activation of the production environment guide. Use only the cards listed in the guide.

---

Within the integration environment, the payment gateway performs verification and subsequent authorization of the payment for test cards against the simulator.

The verification result depends on the selected test card number. If a payment confirmation is required for the appropriate test card, a verification screen is displayed and the customer enters a numeric (OTP) code. According to the entered value, the simulator returns the result of the payment verification. If the verification is successful, the subsequent payment authorization depends only on the entered CVC/CVV code.

Test cards

The following test cards are designed to test payment verification from a customer's browser.

Card number	Description
4000007000010006	Simulation of successful verification without the need to confirm payment by the customer. A browser fingerprint is required to be processed for this card. Authorization proceeds.
4000007000020005	Simulation of failed verification (no need to confirm payment by the customer). A browser fingerprint is required to be processed for this card. Authorization does not proceed.
4000007000030004	Simulation of payment verification including payment confirmation by the customer. A browser fingerprint is required to be processed for this card. The customer will see an authentication screen for entering the OTP code. Depending on the value entered, the verification result is simulated: 1234 = successful verification (authorization proceeds) any other code = verification denied, authorization does not proceed.

The following test cards are designed to test payment verification performed from a mobile application with integrated 3DS SDK.

Card number	Description
4000007000050002	Simulation of successful verification without the need to confirm payment by the customer. Authorization proceeds.
4000007000060001	Simulation of failed verification (no need to confirm payment by the customer). Authorization does not proceed.
4000007000070000	Payment verification simulation including payment confirmation by the customer. The customer will see an authentication screen for entering the OTP code. Depending on the value entered, the verification result is simulated: 1234 = successful verification (continues with authorization) any other code = verification denied, authorization does not proceed.

Testing OneClick payments in an integration environment

To make an initial OneClick payment, on which a payment template is created, use the card 4000007000030004 at the payment gateway, enter any expiration, CVC 100 and enter the OTP code 1234 in the payment confirmation.

For a subsequent OneClick payment, the simulation of the verification result will depend on the total amount of the payment - set the totalAmount parameter within oneclick/init to the appropriate value listed in the table below (this is the total payment price in hundredths of the base currency, while the currency parameter can be chosen arbitrarily).

The following combinations listed below enables to test payment verification with or without browser fingerprint (if browser fingerprint is required a structure actions.fingerprint.browserInit is returned in response of oneclick/init call). These tests cover OneClick payments with the presence of the customer, (parameter clientInitiated is set to true).

totalAmount	Description
100 (1 CZK) or 10000 (100 CZK)	Simulation of successful verification without the need to confirm payment by the customer. A browser fingerprint is required to be processed for this card. Authorization proceeds, payment is confirmed.
200 (2 CZK) or 20000 (200 CZK)	Simulation of failed verification (no need to confirm payment by the customer). A browser fingerprint is required to be processed for this card. Authorization does not proceed, payment is declined.
300 (3 CZK) or 30000 (300 CZK)	Simulation of successful verification without the need to confirm payment by the customer. A browser fingerprint is not required to be processed for this card. Authorization proceeds, payment is confirmed.
400 (4 CZK) or 40000 (400 CZK)	Simulation of failed verification (no need to confirm payment by the customer). A browser fingerprint is not required to be processed for this card. Authorization does not proceed, payment is declined.
500 (5 CZK) or 50000 (500 CZK)	Simulation of payment verification, including payment confirmation by the customer. A browser fingerprint is not required to be processed for this card. The customer will see an authentication screen for entering the OTP code. Depending on the value entered, the verification result is simulated: 1234 = successful verification (authorization proceeds, payment is confirmed) any other code = verification denied, authorization does not continue, payment is rejected.
XXX	Any amount other than the above simulates payment verification, including payment confirmation by the customer. A browser fingerprint is required to be processed for this card. The customer will see an authentication screen for entering the OTP code. Depending on the value entered, the verification result is simulated: 1234 = successful verification (authorization proceeds, payment is confirmed) any other code = verification denied, authorization does not continue, payment is rejected.

Testing Apple Pay and Google Pay payments in an integration environment

For Apple Pay and Google Pay payments, the real card number is not used in the integration environment, the test card is replaced based on the total payment amount - set the totalAmount parameter within applepay/init or googlepay/init to the appropriate value specified in table below (this is the total price of the payment in hundredths of the base currency, while the currency parameter can be chosen arbitrarily).

The following combinations listed below enables to test payment verification with or without browser fingerprint (if browser fingerprint is required a structure actions.fingerprint.browserInit is returned in response of init call).

totalAmount	Description
100 (1 CZK) or 10000 (100 CZK)	Simulation of successful verification without the need to confirm payment by the customer. A browser fingerprint is required to be processed for this card. Authorization proceeds, payment is confirmed.
200 (2 CZK) or 20000 (200 CZK)	Simulation of failed verification (no need to confirm payment by the customer). A browser fingerprint is required to be processed for this card. Authorization does not proceed, payment is declined.
300 (3 CZK) or 30000 (300 CZK)	Simulation of successful verification without the need to confirm payment by the customer. A browser fingerprint is not required to be processed for this card. Authorization proceeds, payment is confirmed.
400 (4 CZK) or 40000 (400 CZK)	Simulation of failed verification (no need to confirm payment by the customer). A browser fingerprint is not required to be processed for this card. Authorization does not proceed, payment is declined.
500 (5 CZK) or 50000 (500 CZK)	Simulation of payment verification, including payment confirmation by the customer. A browser fingerprint is not required to be processed for this card. The customer will see an authentication screen for entering the OTP code. Depending on the value entered, the verification result is simulated: 1234 = successful verification (authorization proceeds, payment is confirmed) any other code = verification denied, authorization does not continue, payment is rejected.
XXX	Any amount other than the above simulates payment verification, including payment confirmation by the customer. A browser fingerprint is required to be processed for this card. The customer will see an authentication screen for entering the OTP code. Depending on the value entered, the verification result is simulated: 1234 = successful verification (authorization proceeds, payment is confirmed) any other code = verification denied, authorization does not continue, payment is rejected.

Testing of Issuer and Regional Limitations

Card number	Description
4407520211155310	If you intend to limit your card acceptance to ČSOB cards only, please use this card for testing. All other cards will not be usable - you will receive the in-line validation error "merchant accepts ČSOB cards only" when entering the card to the gateway.
4550550001000207	Designed for the card restriction test of cards issued in the Czech Republic and Slovakia. This card will be used during testing only by merchants who want to accept only cards issued in the Czech Republic and Slovakia. The card simulates a card issued in another European country.
4543320001000205	Simulates card issued outside of Europe. Use this card in case you want to test acceptance limitation to cards issued only in Europe. This card simulates a card issued in the USA.

Transaction Authorization Rules

CVC/CVV value

CVC/CVV	Description
200	general decline
300	insufficient funds
400	blocked card
500	simulation of authorization technical error (result will be shown only after 30 seconds timeout)
xxx	any other value results in successful authorization when you use the above listed test cards

Expiry Date

You can enter any current or future value for MM/YY. The value does not impact the result of the authorization in any way.