# Trust Payments test cards

> Test card numbers and other details for Trust Payments' sandbox, and the result each one gives.

Use these details to try payments in a Trust Payments sandbox (test) account. They work only in the sandbox: never use them in live, and never put real card or bank details into a sandbox.

Connect Trust Payments with your test site reference. The payment amount also affects the result: see [Declines and errors](#declines-and-errors).

:::note[Where these details come from]
These are Trust Payments' test details, not ours. They were copied from Trust Payments' [Testing card payments](https://help.trustpayments.com/hc/en-us/articles/4403290773905-Testing-card-payments) page on 19 October 2026, and were correct on that date as far as that page shows. Trust Payments can change or withdraw them at any time, and we can't confirm that they work. Check Trust Payments' page for the current details, and ask Trust Payments if one doesn't behave as described.
:::

## How to choose a test result

- In the checkout, we always run 3D Secure through Trust Payments, so the card number sets the 3D Secure result and whether the payment then goes ahead. Staff-entered (MOTO) payments don't use 3D Secure ([Testing card payments](https://help.trustpayments.com/hc/en-us/articles/4403290773905-Testing-card-payments)).
- The amount can force a result: enter `700.00` for a decline or `600.10` for a bank system error, exactly as you would type any amount in the checkout. Use another amount, such as `10.50`, for every other test.
- The billing postcode and the security code set the address and security code check results. Keep **Require address (AVS)** switched on in the Trust Payments connection settings (it is on by default), or the checkout doesn't ask for the billing address.
- Trust Payments' billing premise values (house number or name) can't be used here: we don't send the premise as a separate field, but send address lines 1 to 3 together as the street.

## Cards

Use any future expiry date: a past date returns an invalid field error. To pass the security code check, use `123` for Visa, Mastercard and Discover, or `1234` for American Express. An amount of `10.50` is safe: it doesn't cause an error on its own.

### Successful payments

Trust Payments' page lists only 3D Secure test cards. Its cards here go through 3D Secure without a challenge (frictionless), then are approved. Trust Payments doesn't list a Maestro test card. The last two rows aren't on Trust Payments' page: our own tests with Trust Payments' sandbox use them, with a future expiry date and security code `123`, for payments that don't go through 3D Secure, such as staff-entered (MOTO) payments.

| Card | Number | Notes |
| --- | --- | --- |
| Visa | `4900 4900 0000 0501` | |
| Mastercard | `5591 3900 0000 0504` | |
| American Express | `3400 000000 04001` | Security code `1234` |
| Discover | `6573 7000 0000 0009` | |
| Visa | `4111 1111 1111 1111` | Used in our own tests, on payments without 3D Secure |
| Visa | `4000 0000 0000 2701` | Used in our own tests, on payments without 3D Secure |

### Declines and errors

| Number or trigger | Result |
| --- | --- |
| Amount `700.00` | Declined by the test bank |
| Amount `600.10` | Bank system error from the test bank |

### 3D Secure

Trust Payments asks you to run its full set of 3D Secure test cases and check that each is handled correctly. Cards that need a challenge show an authentication prompt with instructions; frictionless cards skip it. Each row gives the Visa and Mastercard numbers; Trust Payments lists the matching American Express and Discover numbers, and further cases, on its [Testing card payments](https://help.trustpayments.com/hc/en-us/articles/4403290773905-Testing-card-payments) page.

| Number | Result |
| --- | --- |
| `4900 4900 0000 0501` or `5591 3900 0000 0504` | Frictionless: authenticated (Y), then approved |
| `4900 4900 0000 0519` or `5591 3900 0000 0520` | Frictionless: authentication failed (N), not authorised |
| `4900 4900 0000 0527` or `5591 3900 0000 0538` | Frictionless: authentication attempted (A), then approved |
| `4900 4900 0000 0535` or `5591 3900 0000 0546` | Frictionless: authentication unavailable (U), then approved |
| `4900 4900 0000 0543` or `5591 3900 0000 0553` | Frictionless: authentication rejected (R), not authorised |
| `4900 4900 0000 0626` or `5591 3900 0000 0611` | Enrolment check unavailable, then approved |
| `4900 4900 0000 0576` or `5591 3900 0000 0587` | Authenticated (Y) after a retry, then approved |
| `4900 4900 0000 0667` or `5591 3900 0000 0645` | Challenge, completed: then approved |
| `4900 4900 0000 0568` or `5591 3900 0000 0579` | Challenge, failed: not authorised |
| `4900 4900 0000 0584` or `5591 3900 0000 0595` | System error during the challenge: not authorised |

### Address and CVC checks

Only the billing premise (house number or name), the billing postcode and the security code decide these checks. The other address fields make no difference. The premise values can't be used here, because we don't send the premise as a separate field.

| Value | Result |
| --- | --- |
| Premise `No 789` | Address matched |
| Premise `No 123` | Address not matched |
| Premise `No 333` | Address not checked |
| Premise left blank | Address not given |
| Postcode `TR45 6ST` (UK) or `55555` (US) | Postcode matched |
| Postcode `TR12 3ST` (UK) or `12345` (US) | Postcode not matched |
| Postcode `TR33 3ST` (UK) or `33333` (US) | Postcode not checked |
| Postcode left blank | Postcode not given |
| Security code `123` (`1234` for American Express) | Security code matched |
| Security code `214` (`2144` for American Express) | Security code not matched |
| Security code `333` (`3333` for American Express) | Security code not checked |
| Security code left blank | Security code not given |