Testing
Use the credentials provided on this page to test your solution.
When you sign up, you will be provided with a “live” account and a “test” account (the latter is prefixed with “test_”).
When testing, ensure requests submitted to Trust Payments reference your test sitereference.

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 when using your test account.
- We recommend specifying the main amount “10.50” when testing. Other amounts can be used but may return unexpected responses.
- For those using Payment Pages, if you’re unsure where to start with your testing, you may find this resource helpful.
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.


- A baseamount of 70000 (£700.00) will always return a declined response from the test bank.
- A baseamount of 60010 (£600.10) will always return a bank system error from the test bank.
- Using baseamount 1050 (£10.50) will not generate an error.
3-D Secure v2
The following payment credentials can be used for testing 3-D Secure v2 (a form of SCA):
(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 | 6011000000001002 | |
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 |
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 7: Error on Lookup & Successful Authorisation |
||
An error occurred downstream while attempting authentication processing. | ||
Card type | PAN | Handling the response |
AMEX | 340000000001064 | THREEDQUERY Enrolled: U Status: None AUTH Error code: 0 – Ok |
DINERS / DISCOVER | 6011000000001069 | |
JCB | 3337000000000016 | |
MASTERCARD | 5200000000001062 | |
VISA (3-D Secure v2.1.0) | 4000000000001067 | |
VISA (3-D Secure v2.2.0) | 4000000000002446 |
(3DSv2) Test Case 8: Timeout on cmpi_lookup Transaction & Successful Authorisation |
||
Timeout encountered while processing the cmpi_lookup message, resulting in an error on the transaction. | ||
Card type | PAN | Handling the response |
AMEX | 340000000001072 | THREEDQUERY Enrolled: U Status: None AUTH Error code: 0 – Ok |
DINERS / DISCOVER | 6011000000001077 | |
JCB | 3337000000000081 | |
MASTERCARD | 5200000000001070 | |
VISA (3-D Secure v2.1.0) | 4000000000001075 | |
VISA (3-D Secure v2.2.0) | 4000000000002354 |
(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 | 5200000000001112 | |
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 v1
The following payment credentials can be used for testing 3-D Secure v1 (a form of SCA):
(3DSv1) Test Case 1: Successful 3-D Secure Authentication & Successful Authorisation |
||
Cardholder enrolled; successful authentication; successful signature verification. | ||
Card type | PAN | Handling the response |
AMEX | 340000000003961 | THREEDQUERY Enrolled: Y Status: None AUTH Error code: 0 – Ok |
DINERS | 3005000000006246 | |
DISCOVER | 6011000000000004 | |
JCB | 3520000000000922 | |
MASTERCARD | 5200000000000007 | |
VISA | 4000000000000002 |
(3DSv1) Test Case 2: Failed Signature & No Authorisation |
||
Cardholder enrolled; successful authentication; unsuccessful signature verification. | ||
Card type | PAN | Handling the response |
AMEX | 340000000006022 | THREEDQUERY Enrolled: Y Status: None AUTH Not performed |
DINERS | 3005000000004373 | |
DISCOVER | 6011000000000012 | |
JCB | 3520000000002811 | |
MASTERCARD | 5200000000000015 | |
VISA | 4000000000000010 |
(3DSv1) Test Case 3: Failed Authentication & No Authorisation |
||
Cardholder enrolled; unsuccessful authentication; successful signature verification. | ||
Card type | PAN | Handling the response |
AMEX | 340000000000033 | THREEDQUERY Enrolled: Y Status: None AUTH Not performed |
DINERS | 3005000000005925 | |
DISCOVER | 6011000000000020 | |
JCB | 3520000000009931 | |
MASTERCARD | 5200000000000023 | |
VISA | 4000000000000028 |
(3DSv1) Test Case 4: Attempts/Non-Participating & Successful Authorisation |
||
Passive authentication – cardholder not prompted for authentication credentials. | ||
Card type | PAN | Handling the response |
AMEX | 340000000003391 | THREEDQUERY Enrolled: Y Status: A AUTH Error code: 0 – Ok |
DINERS | 3005000000005271 | |
DISCOVER | 6011000000000038 | |
JCB | 3520000000004767 | |
MASTERCARD | 5200000000000908 | |
VISA | 4000000000000101 |
(3DSv1) Test Case 5: Timeout |
||
Timeout encountered while processing the cmpi_lookup transaction. | ||
Card type | PAN | Handling the response |
AMEX | 340000000008309 | THREEDQUERY Enrolled: U Status: None AUTH Error code: 0 – Ok |
DINERS | 3005000000001890 | |
DISCOVER | 6011000000000046 | |
JCB | 3520000000001284 | |
MASTERCARD | 5200000000000049 | |
VISA | 4000000000000044 |
(3DSv1) Test Case 6: Not Enrolled & Successful Authorisation |
||
Cardholder not enrolled. Issuing bank not participating. | ||
Card type | PAN | Handling the response |
AMEX | 340000000008135 | THREEDQUERY Enrolled: N Status: None AUTH Error code: 0 – Ok |
DINERS | 3005000000007269 | |
DISCOVER | 6011000000000053 | |
JCB | 3520000000006903 | |
MASTERCARD | 5200000000000056 | |
VISA | 4000000000000051 |
(3DSv1) Test Case 7: Unavailable & Successful Authorisation |
||
Authentication unavailable (lookup message response). | ||
Card type | PAN | Handling the response |
AMEX | 340000000007780 | THREEDQUERY Enrolled: U Status: None AUTH Error code: 0 – Ok |
DINERS | 3005000000006030 | |
DISCOVER | 6011000000000061 | |
JCB | 3520000000002423 | |
MASTERCARD | 5200000000000064 | |
VISA | 4000000000000069 |
(3DSv1) Test Case 8: Merchant Not Active & Successful Authorisation |
||
Merchant not able to execute transactions due to a “not active” state. | ||
Card type | PAN | Handling the response |
AMEX | 340000000008416 | THREEDQUERY Enrolled: U Status: None AUTH Error code: 0 – Ok |
DINERS | 3005000000004837 | |
DISCOVER | 6011000000000079 | |
JCB | 3520000000006549 | |
MASTERCARD | 5200000000000072 | |
VISA | 4000000000000077 |
(3DSv1) Test Case 9: cmpi_lookup error & Successful Authorisation |
||
Error response to cmpi_lookup message. | ||
Card type | PAN | Handling the response |
AMEX | 340000000006337 | THREEDQUERY Enrolled: U Status: None AUTH Error code: 0 – Ok |
DINERS | 3005000000009877 | |
DISCOVER | 6011000000000087 | |
JCB | 3520000000002175 | |
MASTERCARD | 5200000000000080 | |
VISA | 4000000000000085 |
(3DSv1) Test Case 10: cmpi_authenticate error & No Authorisation |
||
Cardholder enrolled; error response to cmpi_authenticate message. | ||
Card type | PAN | Handling the response |
AMEX | 340000000009299 | THREEDQUERY Enrolled: Y Status: None AUTH Not performed |
DINERS | 3005000000005602 | |
DISCOVER | 6011000000000095 | |
JCB | 3520000000006861 | |
MASTERCARD | 5200000000000098 | |
VISA | 4000000000000093 |
(3DSv1) Test Case 11: Authentication Unavailable & Successful Authorisation |
||
Cardholder is enrolled but authentication is unavailable. | ||
Card type | PAN | Handling the response |
AMEX | 340000000000116 | THREEDQUERY Enrolled: Y Status: None AUTH Error code: 0 – Ok |
DINERS | 3005000000007376 | |
DISCOVER | 6011000000000103 | |
JCB | 3520000000005780 | |
MASTERCARD | 5200000000000031 | |
VISA | 4000000000000036 |
(3DSv1) Test Case 12: Bypassed Authentication & Successful Authorisation |
||
Bypass used to simulate a scenario where merchant has elected to bypass the consumer authentication flow via Cardinal Rules Engine configuration. | ||
Card type | PAN | Handling the response |
AMEX | 340099000000001 | THREEDQUERY Enrolled: B Status: None AUTH Error code: 0 – Ok |
DINERS | 3000990000000006 | |
DISCOVER | 6011990000000006 | |
JCB | 3500990000000001 | |
MASTERCARD | 5200990000000009 | |
VISA | 4000990000000004 |
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.

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:

Testing AVS and security code checks
If you haven’t already, please read our AVS and Security code documentation before testing:
Link to Payment Pages docs / Link to API docs
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.

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 non-card payment methods

Link to Payment Pages docs / Link to Webservices API docs
Testing recurring payments
Testing for the acquirer advice code
When processing recurring payments, some acquirers may return an acquirer advice code in the response. The acquirer advice code is a numeric value used to indicate if further recurring payments can be processed for the given card.
Code | Description | Action |
0 | N/A | No action required |
1 | New account information available (Mastercard only) | Query customer for updated payment details |
2 | Cannot approve at this time | Try again later. If you are continuing to have difficulties, please contact your acquiring bank |
4 | Do not try again | Do not process further recurring transactions |
8 | Payment blocked by card scheme |
Where to find the acquirer advice code
- This code is returned in your daily subscription email report.
- It’s viewable within MyST by selecting the additional field to be displayed on the transaction search page. It can also be viewed on the single transaction view.
- Additionally, for those who have processed a recurring AUTH transaction using the API, the code is returned in the acquireradvicecode field in the response.
How to test for different acquirer advice codes
You can test that your system responds appropriately to different acquirer advice codes by processing transactions with the following attributes:
Visa | ||
Acquirer advice code returned | Card number | Base amount |
0 | 4111111111111111 | 1050 |
2 | 4000000000000671 | 1002 |
4 | 4000000000000671 | 1004 |
8 | 4000000000000671 | 1008 |

Mastercard | ||
Acquirer advice code returned | Card number | Base amount |
0 | 5100000000000511 | 1050 |
1 | 5100000000000271 | 1001 |
2 | 5100000000000271 | 1002 |
4 | 5100000000000271 | 1004 |
8 | 5100000000000271 | 1008 |
Testing Protect Plus
Please refer to the following resources when testing Protect Plus:
- Testing Protect Plus using Payment Pages
- Testing Protect Plus using JavaScript Library
- Testing Protect Plus using iOS SDK
Testing DCC
Please refer to the following resources when testing DCC: