Test Card Details

This document provides details for test cards which can be used to make test payments and simulate various decline states within the Access PaySuite infrastructure used by the Secure Bureau Service (Public Sector) and by the Evolve payment facilitator platform.

Please note – these cards should only be used on test systems, and should not be used to attempt transactions through a live system. Misuse of test card numbers can result in termination of merchant accounts by the acquiring bank.

Test Card Numbers

The following table contains test card numbers which, if used with a future expiry date, will return with an AUTHORISED / DECLINED message during testing. 

Please note: The underlying configuration of the payment applications may restrict the acceptance of certain card types.

Please contact your Account / Project  Manager for further info.

3D Secure Testing

Your site may be configured either for original 3DS v1 or the newer 3DS v2. 

3D Secure v1

3DS1 is enabled for the above Visa and Mastercard test cards only. 

Passwords take the form:  Test_xxxx where xxxx is the last 4 digits of the card number being used.  To test a 3D Secure fail / decline, you can press ‘cancel’ in the 3DS / VbV (Verified by Visa) screen. Entering an incorrect password prompts you to re-enter it.

3D Secure v2

3DS2 is enabled for the above Visa and Mastercar test cards only.  To simulate the 3DS2 validation, just click the button when presented on screen.

Recurring Payment Card Test

The following table contains test card numbers used for testing DECLINES of Recurring Payments. 

All card numbers below will return with an AUTHORISED with the INITIAL AUTH of the card number (and any amount), but DECLINE any SUBSEQUENT PAYMENT requests (with any amount)

This will only work if the card has been stored with the correct ‘Continuous Payment Authority’ flags as per the interface specifications. Please contact your Account / Project Manager for further info. 

These cards are enabled for 3D Secure, which will be required when entering the card details to create the schedule (see above for 3D Secure testing).
 

Foreign Cards Test Card Numbers

Note: These card numbers are intended chiefly for the use of PRP customers, as an aid to testing their PRP setup.

The following table contains non-UK test card numbers. By default, these cards will authorise. You can configure your PRP system to decline some or all of them based on the country code.

Advanced Testing

AVS/CSC Testing

This table includes data which allows you to test various AVS / CSC Outcomes.  The following will mainly be used for API testing. 

By entering the exact details in the table below, you will be returned the MATCHED VALUE OUTCOME as shown. 

*  The Access PaySuite Authorisation System will automatically decline and reverse transactions depending on the AVS CSC Results.
DECLINED transactions will not complete whereas AUTH will return with an Auth code. This emulates what happens in the Live environment. 
Response codes/messages are usually only seen if making a payment directly against an API – front-end systems such as Payment Portal will not display the specific error, but show either a “payment declined” or “system error” page.  Details on the reason for ‘payment declined’ should never be known to the cardholder.

** Only the numerics of a postcode are used when performing Address Verification – when submitting a payment using a payment API, only the numerics are to be provided in the request.  For payments taken via a Payment Portal, a full postcode will need to be entered but the specific letters used are irrelevant.  For example, if the table above lists the postcode as “46”, a tester could enter either “OL4 6BT” or “SK4 6KL” and both would result in a match.

AVS / CSC Results Explained

AVS/CSC results are encoded in a six-digit string as follows:

E.g. 211000 => CSC matched, address and postcode not checked