Testing

To test your integration, you can simulate actions with the API in a test mode.

For example, you can send requests and receive responses with a link to the Checkout page. In order to designate your transactions as test transactions within the system, you should use the Merchant Test Key as the value for the merchant_key parameter.

To ensure that you have the required settings for working with test transactions, it is advisable to reach out to your administrator.

Test Cards

Credit Cards
Wallets

Use the expiry code 01/39 and CVV2 value 100 to get a successful authorization/payment in an end-to-end testing flow.
Please note that the card(s) listed with * will not work for subsequent authorizations or payments.

Test Card	Purpose	Card Number	3DS1 Enrolled	3DS2 Enrolled	Method Url	tranStatus	ECI
MasterCard	3DS2 - Challenge (Method URL provided)	5123450000000008 2223000000000007	Yes	Yes	Yes	C	-
MasterCard	3DS2 - Frictionless (Method URL provided)	5123456789012346	Yes	Yes	Yes	Y	02
MasterCard	3DS2 - Frictionless (No Method URL)	5555555555000018*	Yes	Yes	No	Y	02
Visa	3DS2 - Challenge (No Method URL provided)	4440000009900010	Yes	Yes	No	C	-
Visa	3DS2 - Frictionless (Method URL provided)	4440000042200014	Yes	Yes	Yes	Yes	05

In the case of a "C" transStatus, the following outcomes are possible via drop-down selection in the 3DS Emulator:

Description	transStatus	challengeCancel	eci
Successful authentication	Y	-	05 / 02
Failed authentication	N	-	07 / 00
Cancelled authentication	N	1	07 / 00
Unable to authenticate	U	-	07 / 00
Authentication rejected	R	-	07 / 00

Testing

Test Cards​

Test Cards