Test cards you can use in the PCE Sandbox to safely simulate approvals, declines, and common payment scenarios.

Important: Use these numbers only in sandbox/test environments. Do not use real payment cards for testing. Follow your organization’s PCI and security guidelines.

Definitions

AVS (Address Verification Service): Validates the billing address (street/ZIP) against issuer records.
CVV / CVC: Verifies the accuracy of the card security code.
Issuer Response Codes: Numeric codes that indicate the result of a transaction.
Authorization Message: A human-readable message associated with the response code (e.g., “Do Not Honor”).
EMS/Fraud Score: Mastercard’s risk score and reason code derived from fraud screening.

General test cards

Test cards are fake card numbers used in development and testing to safely simulate payment transactions.

Why they matter

No real money involved — safe for testing.
Simulate approvals/declines, fraud, insufficient funds, expired cards, etc.
Validate behavior for AVS, and partial approvals.
Ensure proper error handling and user-friendly messages.
Avoid fraud, chargebacks, or compliance issues that arise from using real cards.
They’re essential for developers, testers, and QA teams working on payment integrations.

Use these in the PCE Sandbox. Expiry date and CVV rules may vary by gateway; follow the gateway’s test guide when a specific CVV/AVS is required.

Card number	Brand	Type
`4242 4242 4242 4242`	Visa	Credit
`4012 8888 8888 1881`	Visa	Credit
`4000 0566 5566 5556`	Visa	Debit
`4123 4000 7332 0224`	Visa	Debit
`3782 822463 10005`	American Express	Credit
`3714 496353 98431`	American Express	Credit
`5200 8282 8282 8210`	Mastercard	Credit
`2222 4000 6000 0007`	Mastercard	Credit (2-series BIN)
`5555 5555 5555 4444`	Mastercard	Debit
`5305 4847 4880 0098`	Mastercard	Debit
`5572 4084 2218 9334`	Mastercard	Prepaid
`6011 1111 1111 1117`	Discover	Credit
`6011 0009 9013 9424`	Discover	Credit
`3530 1113 3330 0000`	JCB	Credit
`3566 0020 2036 0505`	JCB	Credit
`3056 9309 0259 04`	Diners Club	Credit
`3540 5019 9000 9456`	JCB / Diners Club	Credit (co-branded)

Usage tips

Scope: These values are for sandbox only; production gateways will reject most test PANs.
Scenarios: Pair with gateway-specific AVS/CVV values to trigger approvals, soft/hard declines, and error codes.
Logging: Capture request/response payloads to verify error handling and user messages.
Data hygiene: Do not store PANs in logs or screenshots outside approved secure tools.

Issuer response codes

Every payment response includes a responseCode (an integer) and an authMessage. To trigger a specific responseCode in the sandbox, use the brand-specific test cards on the pages below: each card is mapped to one issuer response code so you can exercise approvals, declines, and partial approvals deterministically.

Visa Test Data

AVS/CVV scenarios and per-code Visa test cards.

Mastercard Test Data

AVS/CVV, EMS, and per-code Mastercard test cards.

Amex Test Data

AVS/CVV scenarios and per-code Amex test cards.

Discover Test Data

AVS/CVV, EMS, and per-code Discover test cards.

For the full meaning of each code, see Payment Response Codes.