Testing card payments

The tables below list test card numbers and customer information that can be submitted to our test bank, along with the responses that should be expected in return.

  Do not use these credentials when processing transactions on your live site reference.

  While testing, all card types are supported, but when using your live account, you will receive an error if you do not have a valid merchant number for the payment type submitted.

 

The basics

When testing, you can use the following test card details to simulate a “Successful” response:

  • Visa card "4111 1111 1111 1111" or Mastercard "5200 0000 0000 1096".
  • Set expiry date to any valid date in the future.
  • Use security code “123”.

You can also send different amount values to affect the outcome of the request:

  • 700.00 will always return a declined response from the test bank.
  • 600.10 will always return a bank system error from the test bank.
  • 10.50 is a safe value that will not return an error unless the card number sent is used to simulate an error response, as described below.

  The cards above will return a not enrolled value for 3-D Secure and should only be used for the most basic testing. Once you have successfully processed requests using the details provided above, please ensure you fully test your 3-D Secure integration using the test credentials provided below.

 

3-D Secure version 2

You must perform a full suite of test payments using all 3-D Secure v2 cards provided below, ensure your system handles each scenario correctly and that it displays the correct message to the customer:

  3DS status field values "N" and "R" do not proceed to authorisation where the AUTH request is initiated using Payment Pages and/or JavaScript Library.

 

(3DSv2) Test Case 1: Successful Frictionless 3-D Secure Authentication & Successful Authorisation
Successful frictionless authentication representing the cardholder being authenticated by their card issuer.
Card type PAN Handling the response
AMEX 340000000001007 THREEDQUERY
Enrolled: Y
Status: Y
AUTH
Error code: 0 – Ok
DINERS / DISCOVER 6011000000001143
JCB 3337000000000008
MASTERCARD 5200000000001005
VISA (3-D Secure v2.1.0) 4000000000001000
VISA (3-D Secure v2.2.0) 4000000000002701

 

(3DSv2) Test Case 2: Failed Frictionless 3-D Secure Authentication & Failed Authorisation
Authentication failed by card issuer without challenge.
Card type PAN Handling the response
AMEX 340000000001015 THREEDQUERY
Enrolled: Y
Status: N
AUTH
Error code: 60022 – Unauthenticated
DINERS / DISCOVER 6011000000001010
JCB 3337000000000990
MASTERCARD 5200000000001013
VISA (3-D Secure v2.1.0) 4000000000001018
VISA (3-D Secure v2.2.0) 4000000000002925

 

(3DSv2) Test Case 3: Attempts Stand-In Frictionless 3-D Secure Authentication & Successful Authorisation
Cardholder is enrolled in 3-D Secure, however the card issuer is not supporting the program, resulting in a stand-in authentication experience.
Card type PAN Handling the response
AMEX 340000000001023 THREEDQUERY
Enrolled: Y
Status: A
AUTH
Error code: 0 -Ok
DINERS / DISCOVER 6011000000001028
JCB 3337000000007045
MASTERCARD 5200000000001021
VISA (3-D Secure v2.1.0) 4000000000001026
VISA (3-D Secure v2.2.0) 4000000000002719

 

(3DSv2) Test Case 4: Unavailable Frictionless 3-D Secure Authentication from the Issuer & Successful Authorisation
Authentication is unavailable at the current time.
Card type PAN Handling the response
AMEX 340000000001031 THREEDQUERY
Enrolled: Y
Status: U
AUTH
Error code: 0 – Ok
DINERS / DISCOVER 6011000000001036
JCB 3337000000000735
MASTERCARD 5200000000001039
VISA (3-D Secure v2.1.0) 4000000000001034
VISA (3-D Secure v2.2.0) 4000000000002313

 

(3DSv2) Test Case 5: Rejected Frictionless 3-D Secure Authentication by the Issuer & Failed Authorisation
Rejected authentication by the card issuer not requiring a challenge.
Card type PAN Handling the response
AMEX 340000000001049

THREEDQUERY
Enrolled: Y
Status: R
AUTH
Error code: 60022 – Unauthenticated

The subsequent AUTH should NOT be processed.

DINERS / DISCOVER 6011000000001044
JCB 3337000000000321
MASTERCARD 5200000000001047
VISA (3-D Secure v2.1.0) 4000000000001042
VISA (3-D Secure v2.2.0) 4000000000002537

 

(3DSv2) Test Case 6: 3-D Secure Authentication Not Available on Lookup & Successful Authorisation
Authentication not available on lookup due to a system error.
Card type PAN Handling the response
AMEX 340000000001056 THREEDQUERY
Enrolled: U
Status: None
AUTH
Error code: 0 – Ok
DINERS / DISCOVER 6011000000001051
JCB 3337000000006765
MASTERCARD 5200000000001054
VISA (3-D Secure v2.1.0) 4000000000001059
VISA (3-D Secure v2.2.0) 4000000000002990

 

(3DSv2) Test Case 9: Successful Step Up 3-D Secure Authentication & Successful Authorisation
Successful traditional step up (challenge) authentication transaction.
Card type PAN Handling the response
AMEX 340000000001098 THREEDQUERY
Enrolled: Y
Status: C
AUTH
Error code: 0 – Ok
DINERS / DISCOVER 6011000000001093
JCB 3337000000200004
MASTERCARD 5200000000001096
VISA (3-D Secure v2.1.0) 4000000000001091
VISA (3-D Secure v2.2.0) 4000000000002503

 

(3DSv2) Test Case 10: Failed Step Up 3-D Secure Authentication & No Authorisation
Traditional step up (challenge) authentication transaction with failed cardholder challenge.
Card type PAN Handling the response
AMEX 340000000001106 THREEDQUERY
Enrolled: Y
Status: C
AUTH
Not performed
DINERS / DISCOVER 6011000000001101
JCB 3337000000200087
MASTERCARD 5200000000001104
VISA (3-D Secure v2.1.0) 4000000000001109
VISA (3-D Secure v2.2.0) 4000000000002370

 

(3DSv2) Test Case 11: Step Up 3-D Secure Authentication is Unavailable & Successful Authorisation
Step up authentication is unavailable.
Card type PAN Handling the response
AMEX 340000000001114 THREEDQUERY
Enrolled: Y
Status: C
AUTH
Error code: 0 – Ok
DINERS / DISCOVER 6011000000001119
JCB 3337000000200079
MASTERCARD 5200000000002664
VISA (3-D Secure v2.1.0) 4000000000001117
VISA (3-D Secure v2.2.0) 4000000000002420

 

(3DSv2) Test Case 12: Error on 3-D Secure Authentication & No Authorisation
A system error occurred while attempting to process the authentication request.
Card type PAN Handling the response
AMEX 340000000001122 THREEDQUERY
Enrolled: Y
Status: C
AUTH
Not performed
DINERS / DISCOVER 6011000000001127
JCB 3337000000200046
MASTERCARD 5200000000001120
VISA (3-D Secure v2.1.0) 4000000000001125
VISA (3-D Secure v2.2.0) 4000000000002644

 

(3DSv2) Test Case 13: Bypassed 3-D Secure Authentication & Successful Authorisation
A decision has been made to bypass the issuer-requested challenge for this transaction.
Card type PAN Handling the response
AMEX 340000000001080 THREEDQUERY
Enrolled: B
Status: None
AUTH
Error code: 0 – Ok
DINERS / DISCOVER 6011000000001085
JCB 3337000000000537
MASTERCARD 5200000000001088
VISA (3-D Secure v2.1.0) 4000000000001083
VISA (3-D Secure v2.2.0) 4000000000002560

 

3-D Secure status testing

To test for different 3-D Secure status values, follow the instructions displayed in the authentication prompt shown on the page (an example is shown below). In the textbox provided, you can enter different PIN values to test for different cases.

  Displaying the test ACS page


For Payment Pages:

With 3-D Secure enabled on your site reference, process a payment using one of the card numbers listed above and your browser will display an authentication prompt with instructions.

 

For JavaScript Library implementations:

After your payment form has been updated to reference our JavaScript library, process a payment using one of the card numbers listed above and your browser will display an authentication prompt with instructions.

 

For Mobile SDK implementations:

After your Android or iOS app has been updated to utilise our Mobile SDK, process a payment using one of the card numbers listed above and your app will display an authentication prompt with instructions.

 

The authentication prompt will only be displayed for non-frictionless test card details

Frictionless cards will bypass authentication. In this case, the payment will be processed immediately (without being prompted by the browser for information).

 


Follow the instructions displayed within the authentication prompt to complete the payment:

CU1-EN.png

 

  When the status is “N”, indicating the customer failed authentication, the errorcode “60022” will be returned.

 

Testing AVS and security code checks

If you haven’t already, please read our AVS and Security code documentation before testing.

The following tables list test details that can be submitted to obtain different responses from the AVS and Security Code Checks. These details can be used with most major payment types.

  Only the billing premisebilling postcode and security code field values dictate the outcome of the AVS and security code checks performed. As such, entering any details into the other address fields will not affect the outcome of these checks.

 

Premise

Billing premise Security response Security response caption
No 789 2 Matched
No 123 4 Not Matched
No 333 1 Not Checked
Leave blank 0 Not Given

 

Postcode / ZIP code

Billing postcode Security response Security response caption
UK US
TR45 6ST 55555 2 Matched
TR12 3ST 12345 4 Not Matched
TR33 3ST
33333 1 Not Checked
Leave blank Leave blank 0 Not Given

 

Security code

Security code AMEX security code Security response Security response
123 1234 2 Matched
214 2144 4 Not Matched
333 3333 1 Not Checked
Leave blank Leave blank 0 Not Given
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request