Sandbox and Test Data
Use named test profiles rather than ad hoc card details wherever possible. This makes execution repeatable and evidence review easier.
Recommended v1 named profiles:
| Profile ID | Scheme | Purpose | PAN | CSC | Amount |
|---|---|---|---|---|---|
TD-VISA-APPROVAL-01 | Visa | Standard approval | 4000 0000 0000 0002 | 123 | 1000 |
TD-MC-APPROVAL-01 | Mastercard | Standard approval | 5100 0000 0000 0008 | 123 | 1000 |
TD-VISA-DECLINE-01 | Visa | Generic decline | 4000 0000 0000 0002 | 333 | 3333 |
TD-VISA-AVSA-01 | Visa | AVS address failure | 4000 0000 0000 0002 | 344 | 3344 |
TD-VISA-AVSP-01 | Visa | AVS postcode failure | 4000 0000 0000 0002 | 355 | 3355 |
TD-VISA-CSC-01 | Visa | CSC failure | 4000 0000 0000 0002 | 366 | 3366 |
TD-VISA-FRAUD-01 | Visa | Fraud decline | 4000 0000 0000 0002 | 377 | 3377 |
TD-VISA-COMMS-01 | Visa | Communication error | 4000 0000 0000 0002 | 666 | 6666 |
The profile ID is the shorthand used in pack tables. For example, TD-VISA-APPROVAL-01 means “the first standard Visa approval dataset defined on this page”.
TD-VISA-APPROVAL-01
| Field | Value |
|---|---|
| Purpose | Standard Visa approval |
| PAN | 4000 0000 0000 0002 |
| Expiry | 04/28 |
| CSC | 123 |
| Amount | 1000 |
| Billing profile | default known-good address |
| Expected auth outcome | approved |
| Expected 3DS outcome | pack-dependent |
TD-MC-APPROVAL-01
| Field | Value |
|---|---|
| Purpose | Standard Mastercard approval |
| PAN | 5100 0000 0000 0008 |
| Expiry | 04/28 |
| CSC | 123 |
| Amount | 1000 |
| Billing profile | default known-good address |
| Expected auth outcome | approved |
| Expected 3DS outcome | pack-dependent |
TD-VISA-DECLINE-01
| Field | Value |
|---|---|
| Purpose | Standard generic decline |
| PAN | 4000 0000 0000 0002 |
| Expiry | 04/28 |
| CSC | 333 |
| Amount | 3333 |
| Billing profile | default known-good address |
| Expected auth outcome | decline 090 |
| Expected 3DS outcome | not applicable unless explicitly combined with a 3DS-specific scenario |
The current sandbox cards are:
| Card Number | Scheme | Type | CSC Length |
|---|---|---|---|
3743 871880 19714 | Amex | Credit | 4 |
3014 445396 5469 | Diners | Credit | 3 |
3528 0000 0000 0007 | JCB | Credit | 3 |
4000 0000 0000 0002 | Visa | Credit | 3 |
4659 0100 0000 0005 | Visa | Debit | 3 |
5100 0000 0000 0008 | Mastercard | Credit | 3 |
5573 4700 0000 0001 | Mastercard | Debit | 3 |
4508 7500 0000 0009 | Visa Electron | Debit | 3 |
4857 7900 0000 0002 | Visa Business | Debit | 3 |
Published v1 examples should focus on Visa and Mastercard unless scheme-specific behaviour is being tested.
The current test gateway maps amounts and CSC values to fixed outcomes.
| Amount | CSC | Behaviour | Response |
|---|---|---|---|
3333 | 333 | Generic decline | 090 |
3344 | 344 | AVS address failure | 095 |
3355 | 355 | AVS postcode failure | 096 |
3366 | 366 | CSC failure | 094 |
3377 | 377 | Fraud decline | 091 |
4444 | 444 | Referral | 089 |
6666 | 666 | Communication error | F006 |
5544 | 544 | AVS address failure if AVS is configured | 095 |
5555 | 555 | AVS postcode failure if AVS is configured | 096 |
5566 | 566 | CSC failure if CSC is configured | 094 |
Policy-dependent AVS and CSC cases should be recorded clearly in the scenario evidence, because they depend on merchant configuration as well as the test values.
For API-led 3DSv2 testing, the current CSC mappings are:
| CSC | Behaviour |
|---|---|
731 | Frictionless processing, not authenticated |
732 | Frictionless processing, account verification count not performed |
733 | Frictionless processing, verification rejected |
741 | Frictionless attempts processing |
750 | Frictionless authenticated |
761 | 3DS error |
| Any other value | Challenge request |
Use these mappings to classify the expected 3DS outcome for API / server-led + 3DS scenarios. Where a hosted flow abstracts these details, record the intended outcome and the returned authentication result.
Use the following defaults for v1 pack execution unless a scenario says otherwise:
| Field | Value |
|---|---|
| Expiry | 04/28 |
| First name | Test |
| Last name | Customer |
test.customer@example.com | |
| Address line 1 | 999 Nowhere Lane |
| Town / City | Fakeville |
| Postcode | ZZ9 9ZZ |
| Country | GB |
There is currently no clean, realistic “bad address” data profile in the test gateway. Treat address-variation testing beyond the fixed mappings as deferred.