Use these provider-published numbers to test approvals, declines and 3-D Secure flows in sandbox mode. For input masks, length checks and form-only QA, use the credit card generator. Follow your provider’s expiry and CVV requirements alongside each table.
Source-check dates are shown with each provider reference. These record a documentation comparison, not a payment executed in a sandbox. The selected cases are not an exhaustive provider test suite.
Stripe
Use test credentials in your Stripe sandbox. For interactive card entry, use a future expiry and a CVC of the required length. Automated integrations should use Stripe’s documented test PaymentMethods where supported. Account settings, Radar and the request still affect the flow; a card number is not the entire test configuration.
| Card number | Scenario | Sandbox expectation |
|---|---|---|
| 4242424242424242 | Visa | Successful sandbox card scenario |
| 4000056655665556 | Visa debit | Successful sandbox card scenario |
| 5555555555554444 | Mastercard | Successful sandbox card scenario |
| 2223003122003222 | Mastercard 2-series | Successful sandbox card scenario |
| 5200828282828210 | Mastercard debit | Successful sandbox card scenario |
| 378282246310005 | American Express | Successful sandbox card scenario |
| 6011111111111117 | Discover | Successful sandbox card scenario |
| 3056930009020004 | Diners Club | Successful sandbox card scenario |
| 3566002020360505 | JCB | Successful sandbox card scenario |
| 6200000000000005 | UnionPay | Successful sandbox card scenario |
Source: Stripe testing documentation. Selected fixtures checked 2026-11-08. These local checks do not call Stripe.
| Card number | Scenario | Sandbox expectation |
|---|---|---|
| 4000000000000002 | Generic | card_declined / generic_decline |
| 4000000000009995 | Funds | card_declined / insufficient_funds |
| 4000000000009987 | Lost | card_declined / lost_card |
| 4000000000009979 | Stolen | card_declined / stolen_card |
| 4000000000000069 | Expired | expired_card |
| 4000000000000127 | Cvc | incorrect_cvc |
| 4000000000000119 | Processing | processing_error |
| 4000000000006975 | Velocity | card_declined / card_velocity_exceeded |
| 4242424242424241 | Checksum | incorrect_number |
Source: Stripe testing documentation. Selected fixtures checked 2026-11-08. These local checks do not call Stripe.
| Card number | Scenario | Sandbox expectation |
|---|---|---|
| 4000000000003220 | 3DS required | Authentication required; default Radar rules request 3DS. Complete the test challenge. |
| 4000008400001629 | Authenticate, then decline | Successful authentication followed by card_declined. Authentication is not payment success. |
| 4000000032200000 | Frictionless 3DS | Required authentication completes through a frictionless flow. |
| 4000008400001280 | 3DS lookup error | Authentication lookup fails; payment returns card_declined. |
Source: Stripe testing documentation. Selected fixtures checked 2026-11-08. These local checks do not call Stripe.
The deliberately incorrect-number fixture fails Luhn. Use the Stripe integration guide for server-order checks and the 3DS section below for challenge recovery. This selected set is shared by those guides; it is not an exhaustive copy of Stripe’s reference.
PayPal
PayPal’s sandbox splits the work differently: the card number selects the brand, and the cardholder name selects the outcome. That is unusual enough to catch people out.
| Card number | Brand |
|---|---|
| 4012 8888 8888 1881 | Visa |
| 4005 5192 0000 0004 | Visa |
| 2223 0000 4840 0011 | Mastercard |
| 3714 496353 98431 | American Express |
| 3646 1510 0000 39 | Diners Club |
| 6304 0000 0000 0000 | Maestro |
| 3636 5000 0000 0260 | JCB |
| 6200 6800 0000 0004 | UnionPay |
The following selected cases apply to Expanded Checkout card payments with a sandbox client ID and sandbox API endpoints. The capture result must be checked separately from order creation. Use the same documented Visa fixture with the appropriate name trigger:
| Scenario | First Name / Name on Card | Expected sandbox result |
|---|---|---|
| Successful payment | Ordinary test name; no rejection trigger | Successful sandbox card capture scenario |
| Insufficient funds | CCREJECT-IF | 5120 / INSUFFICIENT_FUNDS |
| Card refused | CCREJECT-REFUSED | 0500 / DO_NOT_HONOR |
| Expired card response | CCREJECT-EC | 5400 / EXPIRED_CARD |
| Security code check failure | CCREJECT-CVV_F | 00N7 / CVV2_FAILURE_POSSIBLE_RETRY_WITH_CVV |
For these selected cases use Visa 4012888888881881, any future date and any 3 digits. Rejection triggers are case-sensitive. Choose and copy a complete test setup, or follow the PayPal sandbox guide to inspect the capture state.
Source: PayPal card testing. Selected cases checked 2026-11-08.
Braintree
Scope: Sandbox card verification and transactions.
Use separate sandbox credentials. Card verification depends on the number; transaction responses depend on the amount, regardless of currency. AVS/CVV rules can affect results.
| Card number | Brand | Verification fixture |
|---|---|---|
| 4111111111111111 | Visa | Normal |
| 5555555555554444 | Mastercard | Normal |
| 2223000048400011 | Mastercard 2-series | Normal |
| 378282246310005 | Amex | Normal |
| 4000111111111115 | Visa | Processor declined |
| 5105105105105100 | Mastercard | Processor declined |
| Input / route | Documented expectation | Check in your application |
|---|---|---|
| Amount 0.01–1999.99 | Authorized; settlement path: Settled | Assert both stages separately. |
| Amount 2000.00–2999.99 | Processor declined | Keep the order unpaid. |
| Amount 3000.00–3000.99 | Failed; processor response 3000 | Keep failure distinct from decline. |
| Amount 5001.00 | Gateway rejected: application incomplete | Check the rejection reason. |
| Verify 4000111111111115 | Verification: processor declined | Do not infer a transaction result from verification. |
Authorization is not settlement. Submit for settlement when testing that stage; use the documented testing routes to advance it. These are selected cases.
Braintree documentation · Source checked . Documentation comparison; not a live sandbox execution.
Adyen
Scope: Test environment; payment-method-specific fixtures.
Use the test account and the exact expiry and security-code instructions for the chosen payment method. Co-badged numbers do not have one universal CVC requirement.
| Card number | Payment method / route | Expiry | Security code |
|---|---|---|---|
| 4111111111111111 | Visa | 03/2030 | 737 |
| 5555555555554444 | Mastercard | 03/2030 | 737 |
| 370000000000002 | Amex | 03/2030 | 7373 |
| 8171999927660000 | UnionPay ExpressPay | 10/2030 | 737 |
| 6771798021000008 | Maestro | 03/2030 | 737 |
| 5127880999999990 | Bancontact (BCMC route) | 03/2030 | None |
| 5127880999999990 | Mastercard Debit route | 03/2030 | 737 |
| Input / route | Documented expectation | Check in your application |
|---|---|---|
| Co-badged fixture through BCMC | No CVC; simulator login: user / password | Keep this route separate from Mastercard. |
| Same co-badged fixture through Mastercard | Security code 737 | Do not reuse the BCMC field contract. |
| Online Maestro payment | 3D Secure required | Observe authentication and payment separately. |
Online Maestro requires 3D Secure. A number alone does not select every authentication or refusal outcome. Follow the linked integration instructions for the enabled route.
Adyen documentation · Source checked . Documentation comparison; not a live sandbox execution.
Square
Scope: Web Payments SDK / In-App Payments SDK; card-not-present sandbox.
Use a future expiry. USD, CAD and GBP payments require a valid postal code; Japan does not support postal codes. Tokenize with the sandbox SDK, then submit the token to CreatePayment.
| Card number | Brand | CVV |
|---|---|---|
| 4111111111111111 | Visa | 111 |
| 5105105105105100 | Mastercard | 111 |
| 6011000000000004 | Discover | 111 |
| 340000000000009 | Amex | 1111 |
| 3569990010095841 | JCB | 111 |
| Input / route | Documented expectation | Check in your application |
|---|---|---|
| CVV 911 | Card CVV incorrect | Show the failed field. |
| Postal code 99999 | Card postal code incorrect | Keep the cart available. |
| Expiry 01/40 | Card expiration date incorrect | Use this trigger, not a past date. |
| Card 4000000000000002 | Card declined | Do not mark the order paid. |
| Card 4000000000000010 | Card-on-file authorization declined | Check the saved-card path. |
The error triggers below act when CreatePayment processes the token. Card-present testing is unsupported here. Server-only tests have separate documented source IDs.
Square documentation · Source checked . Documentation comparison; not a live sandbox execution.
Authorize.Net
Scope: Separate sandbox account, credentials and endpoint.
Keep the sandbox account in Live Mode; this is still the sandbox, not production. Test Mode does not store transactions and returns transaction ID 0. Use a future expiry and a brand-appropriate security-code length.
| Card number | Brand |
|---|---|
| 4111111111111111 | Visa |
| 4007000000027 | Visa (13 digits) |
| 5424000000000015 | Mastercard |
| 2223000010309703 | Mastercard 2-series |
| 370000000000002 | Amex |
| 6011000000000012 | Discover |
| 3088000000000017 | JCB |
| 38000000000006 | Diners Club |
| Input / route | Documented expectation | Check in your application |
|---|---|---|
| Billing ZIP 46282 | Response code 2: declined | Keep the order unpaid. |
| Billing ZIP 46203 | AVS E: invalid or disallowed | Inspect AVS independently. |
| Billing ZIP 46205 | AVS N: address and ZIP mismatch | Apply the configured AVS policy. |
| Card code 900 | CVV M: match | Also inspect transaction status. |
| Card code 901 | CVV N: no match | Preserve the failed check. |
| Card code 904 | CVV P: not processed | Do not convert this to a match. |
General transaction responses, AVS and CVV results are separate fields. Check each applicable response and your configured handling; a CVV match alone is not payment approval.
Authorize.Net documentation · Source checked . Documentation comparison; not a live sandbox execution.
Other gateways in brief
For a provider outside the selected tables, start with its own product-specific testing instructions:
Check the product, region, credentials and response stage before copying a fixture. A card-entry flow, a stored-card payment and a subscription may require different setup even within the same provider.
Commonly reused examples
These familiar values can exercise your own form’s formatting and checksum rules. Their appearance in several references does not give them a portable sandbox outcome. Hosted payment fields may require the provider’s own fixtures even before a payment request is submitted.
| Number | Brand | Notes |
|---|---|---|
| 4111 1111 1111 1111 | Visa | Appears in several provider references |
| 4012 8888 8888 1881 | Visa | Common in older documentation |
| 5555 5555 5555 4444 | Mastercard | 5-series |
| 5105 1051 0510 5100 | Mastercard | 5-series |
| 2223 0031 2200 3222 | Mastercard | 2-series — test your 2-series support |
| 3782 822463 10005 | American Express | 15-digit |
| 3714 496353 98431 | American Express | 15-digit |
| 6011 1111 1111 1117 | Discover | 16-digit |
| 3530 1113 3330 0000 | JCB | 16-digit |
| 3056 9309 0259 04 | Diners Club | 14-digit |
These familiar examples are intended for testing. A number appearing in a dataset does not prove the whole dataset is synthetic or safe to share. Inspect local format and checksum results with the card validator, and generate fresh equivalents per network from the Visa and Mastercard pages.
Reproduce the reference checks
The Stripe tables above render from stripe-fixtures.json, which is included in the offline guide project
. This executed check catches duplicate fixture identifiers and unintended checksum changes:
const stripeFixtures=read('stripe-fixtures.json');
test('Provider reference IDs are unique and checksum expectations are explicit', () => {
assert.equal(new Set(stripeFixtures.cards.map(c=>c.id)).size,stripeFixtures.cards.length);
for (const card of stripeFixtures.cards) assert.equal(luhnValid(card.number),card.luhnValid,card.id);
assert.ok(stripeFixtures.cards.some(c=>!c.luhnValid));
});The Braintree, Adyen, Square and Authorize.Net sections also render from the shared gateway reference data
in that ZIP. Run node --test gateway-reference.test.mjs to check fixture shape and the route-specific exceptions described above. These tests preserve the documented distinctions; they do not contact a provider.
The complete Stripe test file supplies read, test, assert and luhnValid; extract the ZIP and run node --test payment-guide-examples.test.mjs with Node.js 22 or later. This is a local reference-integrity check. It does not assert that a gateway produced a decline. Run provider scenarios separately in the correct sandbox and compare the documented error field, which may be an error code rather than a nested decline code.
3-D Secure and SCA testing
Authentication, payment authorization and capture are separate outcomes. A frictionless flow can complete authentication without an interactive challenge, while a challenge flow asks the customer to act. Provider settings, the scenario and applicable authentication requirements affect which path occurs.
Use the shared Stripe 3DS table above for specific sandbox cases. A successful authentication can still be followed by a declined payment. The 3D Secure testing guide covers cancellation, lookup errors and both browser/server arrival orders. For another provider, use its current authentication documentation rather than assuming Stripe’s fixture behavior transfers.
Setting up a sandbox account
The pattern is the same nearly everywhere: register a developer account, and you get a pair
of API keys — one test, one live — that select the environment. Stripe and Square ship both
in a single dashboard with a toggle. PayPal and Braintree issue a separate sandbox business
account with its own credentials. Adyen provisions a test company account on request.
Authorize.Net has a dedicated sandbox portal at sandbox.authorize.net, distinct from the
production login.
Never commit test API keys to a public repository. Even test keys reveal your account structure, and several providers rate-limit or disable keys they find in public code.
Which one do I need?
| What you are testing | Use |
|---|---|
| Input mask, digit grouping | Generated numbers |
| Card brand detection (logo switching) | Generated numbers |
| Length and Luhn validation | Generated numbers |
| CVV field length by brand | Generated numbers |
| Bulk test fixtures and database seeding | Generated numbers |
| Successful authorisation | Gateway sandbox |
| Specific decline codes (insufficient funds, expired, lost or stolen) | Gateway sandbox |
| 3-D Secure and SCA challenge flows | Gateway sandbox |
| Refunds, partial refunds, voids | Gateway sandbox |
| Disputes and chargebacks | Gateway sandbox |
| Subscriptions and recurring billing | Gateway sandbox |
| Webhook delivery | Gateway sandbox |
| Multi-currency behaviour | Gateway sandbox |
Generated data is useful for form logic and storage that you control. Hosted fields and provider SDKs can apply their own checks before your server receives anything. For those components and all processor responses, follow the relevant provider’s test setup.
Generated numbers vs sandbox numbers
| Generated numbers | Gateway sandbox numbers | |
|---|---|---|
| Passes Luhn and format checks | Depends on the configured positive or negative case | Some negative cases deliberately fail |
| Exercises brand detection | According to the selected local profile | According to the provider and route |
| Fixture variety | Locally generated datasets | Provider-defined cards, tokens and scenarios |
| Portable gateway behavior | Not established | Follow the specific product documentation |
| Returns an authorisation response | No | A correctly configured sandbox can simulate one |
| Triggers named decline codes | No | Yes |
| Drives 3-D Secure flows | No | Yes |
| Exercises refunds and disputes | No | Yes |
Common testing mistakes
- Using a test card with live keys. It fails at the network, and repeated attempts feed the card-testing fraud signals processors watch on your merchant account.
- Letting test numbers reach a production database. Seed data has a way of migrating. Tag it at creation so it can be found and removed later.
- Assuming sandbox behaviour equals production behaviour. The usual gap is 3-D Secure: sandboxes frequently skip a challenge that production will demand.
- Backdating the expiry to test an expired card. Most sandboxes reject a past date at validation, so you test your own form instead of the processor. Use the documented expired-card number instead.
- Sending a three-digit CVV with an American Express number. Amex uses a four-digit code, and a length check keyed to the brand is exactly the kind of bug a test suite should catch.
- Never testing 2-series Mastercard. The 2221–2720 range has been live since 2017 and
validation written against
^5[1-5]still rejects it.2223 0031 2200 3222takes one line to add.
Related pages and tools
The tool directory lists every generator on the site, the FAQ covers what a Luhn-valid number does and does not prove, and our editorial policy explains the six-month re-check cycle this page sits in.