# FreedomPay test cards

> The test cards FreedomPay gave us and our own tests use in FreedomPay's sandbox, and the result each one gives.

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

You need a UAT test store first. The stores FreedomPay supplied, and their settings, are listed in [UAT credentials](/payment-providers/freedompay-uat-credentials/).

:::note[Where these details come from]
These are the test details FreedomPay gave us, and the ones our own tests use, as of 19 October 2026. FreedomPay doesn't publish its test cards openly: its testing pages, including "Magic Cards for Testing", sit in FreedomPay's own documentation site, which isn't open to the public. FreedomPay can change them at any time, and we can't confirm that they work in your sandbox account. Ask FreedomPay for the current details.
:::

## How to choose a test result

- The test store you connect decides how results are triggered: FreedomPay's UAT stores are either "Amount Trigger" stores or "Magic Card" stores ([UAT credentials](/payment-providers/freedompay-uat-credentials/)). The cards below are the ones our own tests use, on the Amount Trigger store.
- FreedomPay's amount triggers and magic cards aren't public, so ask FreedomPay for them. We send the amount as you type it in the checkout (for example `100.00`), so enter an amount trigger exactly as FreedomPay gives it in major units.
- To test 3D Secure, connect the Amount Trigger store for eComm GBP and, in the gateway settings, tick **Enable Ecommerce** then **Enable 3DS** beneath it. On any other store, untick **Enable 3DS** ([UAT credentials](/payment-providers/freedompay-uat-credentials/)). FreedomPay's 3D Secure test cards aren't public, so ask FreedomPay for them.
- With **Enable 3DS** ticked, we decline a payment whose 3D Secure result is not authenticated, not available, unknown or bypassed, unless you tick the matching **Allow 3DS Not Authenticated**, **Allow 3DS Not Available**, **Allow 3DS Unknown** or **Allow 3DS Bypassed** setting beneath **Enable 3DS**. A failed authentication is always declined ([Connecting FreedomPay](/payment-providers/freedompay-connect/)).
- Use a current browser for e-commerce payments: we decline a payment from a browser more than five years old with "Your browser is too old, please update to a current version". To allow it, tick **Enable Ecommerce**, then **Security Overrides**, then **Allow Old Browsers** in the gateway settings ([Connecting FreedomPay](/payment-providers/freedompay-connect/)).
- Address checks depend on the **Address Verification** setting under **Enable Ecommerce** and **Enable MOTO** (Disabled, Zip Only or Full Address), which must match the store's set-up at FreedomPay. FreedomPay's address and CVC check test values aren't public, and our tests run with address checks off.

## Cards

Our tests use CVC `123`, ZIP `12345`, and an expiry in December of the current year (`06/36` for the timeout card).

### Successful payments

| Card | Number | Notes |
| --- | --- | --- |
| Visa | `4111 1111 1111 1111` | Approved. Used in our own tests for payments, authorisations, captures, refunds, saved cards and recurring payments. |

### Declines and errors

| Number or trigger | Result |
| --- | --- |
| `4111 1234 0000 0152` | Fails: FreedomPay returns an error. Used in our own tests. |
| `4111 1234 0005 8150` | Fails: FreedomPay returns an error. Used in our own tests. |
| `4111 1234 0005 3060` | Times out. We wait 35 seconds, cancel the payment, ask FreedomPay to reverse it, and show "Cancelled due to timeout". Used in our own tests. |