A-12 Integration Testing

You will be provided with unique test Merchant Account IDs during the onboarding process. Refer to section 1.6 for more information. 

Test Merchant Accounts are not connected to our Simulator and not to an actual Acquirer. The Simulator will emulate the function of an Acquirer and provide simulated responses and authorisation codes.

A-12.1 Test Amounts

When testing the transaction amount can be used to trigger different authorisation and settlement outcomes as follows:

Any other amount will return a responseCode of 66311 (Invalid Test Amount). 

The settlement outcome only applies to transactions which reach settlement due to being successfully authorised and captured and not cancelled. The amount captured is used when determining the settlement outcome rather than the amount authorised.

The range 5000 to 9999 can be used to test manual authorisations. If the transaction does not contain an authorisationCode request field, then the Simulator will return a responseCode of 1 (CARD REFERRED). If it does, then it will return a responseCode of 0 (SUCCESS), with an amount between 50000 and 7499 being accepted at settlement and an amount of 7500 to 9999 being rejected. 

The range 20000 to 29999 can be used to test SCA soft declines. If the transaction is eligible1 to request SCA then the Simulator will return a responseCode of 65 (SCA REQUIRED). If not, then it will return a responseCode of 0 (SUCCESS) for the range 20000 to 24999 or 5 (DO NOT HONOR) for the range 25000 to 29999. Successful transactions will be approved at settlement. 

A-12.2 Test Cards

The test accounts will only accept card numbers that are designated for test purposes. These test cards cannot be used on production accounts. 

To test AVS and CV2 verification then the associated CVV and billing addresses are provided for each card. If a different value is used, then the Simulator will mark the responses as ‘not matched’. 

Unless stated otherwise an expiry date sometime in the near future should be used.

A-12.2.1 Visa Credit 

A-12.2.2 Visa Debit

A-12.2.3 Electron

A-12.2.4 Mastercard Credit

A-12.2.5 Mastercard Debit

A-12.2.6 UK Maestro

A-12.2.7 JCB

A-12.2.8 American Express

A-12.2.9 Diners Club

A-12.3 3-D Secure Testing

Your test accounts are connected to our 3-D Secure Product Integration Testing (PIT) system rather than to the production 3-D Secure servers. 

You can use any of the test cards provided in section A-12.2 with this PIT system and can test various enrolment and authentication scenarios as follows. 

A-12.3.10 3-D Secure version 1

For 3-D Secure v1 all the standard test card numbers will show as enrolled except for:

The desired authentication status (threeDSAuthenticated) can be selected on the challenge dialog shown by the PIT Access Control Server.

A-12.3.11 3-D Secure version 2

For 3-D Secure v2 all the standard test cards will show as enrolled, and the authentication status returned by the Directory Server (for frictionless flow simulation) can be selected using the value of the card expiry month as follows: 

An expiry month of 12 will simulate the non frictionless flow and desired authentication status (threeDSAuthenticated) can be selected on the challenge dialog shown by the PIT Access Control Server. 

When using an expiry month from the above table please use a suitable expiry year to ensure the date is sometime in the near future.