Contents

Testing

 

Use the credentials provided on this page to test your solution.

When you sign up with us, you will be provided with a “live” account and a “test” account (the latter is prefixed with “test_”).
When testing, ensure requests submitted to Secure Trading reference your test sitereference.

Warning
It is important to thoroughly test your integration using your test sitereference before processing live payments.

Info

Before you begin testing…

Please be aware of the following notes:

 

  • Most fields submitted to our test system will be accepted. Any data breaching its defined specification will return an error message.
  • Any test data that generates a successful response when submitted while a merchant is in test mode, will produce a declined response when a merchant is switched into live mode. In some cases, the test data may return an error response.
  • Our test system attempts to simulate responses in a similar fashion to the live system. However, depending on your acquirer you may find some responses differ slightly from those given by the test system.
  • In the interest of security, we recommend against using real payment details while your account is in test mode.
  • We recommend specifying the main amount “10.50” when testing. Other amounts can be used but may return unexpected responses.

 


 

Test card details

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

Warning
Do not use these credentials when processing transactions on your live site reference.
Info
While testing, all card types are supported, but after your account is switched live, you will receive an error if you do not have a valid merchant number for the payment type submitted.

 

 

APM
When testing Apple Pay transactions, you must use the cards provided by Apple in order to be returned the expected response. Refer to this resource for a full list:

https://developer.apple.com/support/apple-pay-sandbox/

 

Card type Authorisation Decline Expiry date Security code
AMEX 340000000000611 340000000000512 12/2030 1234
DINERS 3000000000000111 3000000000000012 12/2030 123
DISCOVER 6011000000000301 6011000000000202 12/2030 123
JCB 3528000000000411 3528000000000312 12/2030 123
MAESTRO 5000000000000611 5000000000000512 12/2030 123
MASTERCARD 5100000000000511 5100000000000412 12/2030 123
2221000000000991 2221000000000892 12/2030 123
MASTERCARDDEBIT 5124990000000101 5124990000000002 12/2030 123
VPAY 4370000000000061 4370000000000012 12/2030 123
VISA 4111110000000211 4111110000000112 12/2030 123
DELTA (AKA Visa Debit) 4310720000000091 4310720000000042 12/2030 123
ELECTRON 4245190000000311 4245190000000212 12/2030 123
PURCHASING 4484000000000411 4484000000000312 12/2030 123

 

Padlock
Maestro cards must be processed using 3-D Secure (Mastercard SecureCode).

 


 

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.

Info
Only the billingpremise, billingpostcode and securitycode 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
TE45 6ST 55555 2 Matched
TE12 3ST 12345 4 Not Matched
TE33 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

 


 

Testing 3-D Secure

If you haven’t already, please read our 3-D Secure documentation before testing.

 

Enrollment

Use the following test card details to simulate authorisations with cards that are either enrolled or not enrolled in the card issuer’s 3-D Secure scheme:

Card type Enrolled ‘Y’ Enrolled ‘N’ Enrolled ‘U’
MAESTRO (International) 5000000000000611 5000000000000421 5000000000000801
MAESTRO (UK) 6759000000000711 6759000000000521 6759000000000901
MASTERCARD 5100000000000511 5100000000000321 5100000000000701
2221000000000611 2221000000000991 2221000000000801
MASTERCARDDEBIT 5124990000000911 5124990000000721 5124990000000101
VPAY 4370000000000111 4370000000000921 4370000000002307
VISA 4111110000000211 4111110000000021 4111110000000401
DELTA (AKA Visa Debit) 4006260000002473 4006260000002481 4006260000002408
ELECTRON 4245190000000311 4245190000000121 4245190000000501
PURCHASING 4484000000000411 4484000000000221 4484000000000601

 

Status

To test for different 3-D Secure status values, process a THREEDQUERY request with one of the enrolled cards listed above, and access the URL returned in the acsurl field. You will be displayed our test ACS page (as shown below), where you can enter different values to test for different cases. In the textbox provided, enter the PIN from the table on the left that represents the test case you would like to process.


 

 


After the payment has been processed, the errorcode and status values returned in the AUTH response are used to convey the final outcome.

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

 


 

Testing non-card payment methods

URL
The procedure to follow when testing non-card payment methods will vary. For the most relevant testing information, please refer to the documentation provided for the specific payment method.

 


 

Testing Protect Plus

If you haven’t already, please read our Protect Plus document before testing.

Use the following baseamount values in RISKDEC requests to simulate the different possible responses from the Protect Plus checks:

baseamount Possible fraudcontrolresponsecode returned fraudcontrolshieldstatuscode returned
1011, 2011, 3011 0100, 0150 “ACCEPT”
1033, 2033, 3033 0300, 0330, 0500 “CHALLENGE”
1044, 2044, 3044 0250, 0400, 0600, 0700, 0800, 1300 “DENY”

 

Info
The fraudcontrolshieldstatuscode and fraudcontrolresponsecode values returned in RISKDEC responses may vary when not using the baseamount values listed in the table, above.

 


 

Testing DCC

If you haven’t already, please read our DCC before testing.

The card numbers listed in this test section are associated with specific local currencies. During your integration, you can use the following international test card details in order to test your system for successful and declined DCC transactions.

Successful authorisations

Country code Currency code Visa Credit Mastercard Credit
DE EUR 4500000000000007 5500000000000004
GB GBP 4300000000002211 5311110000001511
JP JPY 4900400000000005 5590410000000006
US USD 4900460000000009 5590470000000018

Declined authorisations

Country code Currency code Visa Credit Mastercard Credit
DE EUR 4500000000002482 5500000000002422
GB GBP 4300000000002492 5311110000002402
JP JPY 4900400000002472 5590410000002432
US USD 4900460000002492 5590470000002402

 

Info
You can also use an amount of 70000 in the final currency to generate a decline response.