This is list of cards used to do tests on test environment

Last updated: 2018-10-15

Testing

Test transactions can be performed by using the test data in this section to process test transactions. The response received from the Payment Gateway will depend on the card number used. The responses are simulated and are intended to allow testing of common scenarios when processing Credit and Debit cards.

It is recommended that the following scenarios are tested as a minimum:

  • Successful Authorisation including 3-D Secure authentication with different amounts
  • Unsuccessful Authorisation
  • Failed 3-D Secure authentication Each merchant must ensure the interaction between the Payment Gateway and their own e-commerce system is behaving as expected.

Below are card numbers that are behaving on a predefined way. They are an excellent help when integrating and in testing/debugging of various scenarios.

Please note – magic cards are provided for Accreditation only and NOT intended for use in the Production Environment.

MasterCard Test Data

Test Card Number Return Code Description Sample Message
5573470000000001 1 Authorised with random auth code AUTH CODE
5573470000000027 14 Test Server Response Payment Gateway Busy Please Retry
5573470000000035 440 Test Server Response Payment Gateway Busy
5573470000000050 661 Test Server Response Unknown Error
5573470000000068 653 Test Server Response Failure at Bank

Maestro Test Data

Test Card Number Return Code Description Sample Message
5001630100011248 1 Authorised with random auth code AUTH CODE
5001630100011255 7 Test Server Response DECLINED
5001630100011263 7 Test Server Response DECLINED

Visa Test Data

Test Card Number Return Code Description Sample Message
4929498311405001 1 Authorised with random auth code AUTH CODE
4978056100000019 7 Decline the transaction DECLINED

Test Data for 3-D Secure

Any of the magic card numbers can be used while integrating 3-D Secure. The response will be determined first by the 3-D Secure configuration on your account, and then by the expiry month of the test card number.

In order to generate specific responses, please use the card expiry month shown below:

Test card expiry month Test system response
01 Card is enrolled
02 Card is not enrolled
03 No result received from the directory server
04 3DS Invalid VERes from DS - Failed to parse VERes
05 3DS Invalid VERes from DS - invalid protocol value 'SET'
06 3DS invalid VEReq
07 Unable to verify
08 Card is enrolled
any other value Unable to verify