What is a Braintree test card?

A Braintree test card is a card number that works only inside the Braintree sandbox. You use it to run charges, refunds, voids, and subscription flows without moving real money. Braintree accepts these numbers on test API credentials and rejects them on live credentials.

braintree test card v10

Does a "v10" version of Braintree test cards exist?

No. Braintree does not version its test cards. Card numbers change only when a card brand retires a test range or when Braintree adds a new scenario, and the reference page is edited in place.

read more

The "v10" label comes from blog posts, forum threads, and reposted tables. Those pages often list stale numbers or blend Braintree values with values from other gateways. Treat the Braintree developer docs as the source of truth.

braintree test card v5

How do you find the current Braintree test values?

1. Sign in to the Control Panel and switch to a sandbox account.
2. Open the test values page in the developer docs, or look for it in the Control Panel settings area.
3. Copy the card numbers, CVV values, and AVS values into a fixtures file in your test suite.
4. Re-check that page after any SDK upgrade, since mappings shift.

Common Braintree sandbox card numbers

The sandbox accepts the card brand test numbers that pass Luhn validation. These are not real accounts and carry no credit line.

braintree test card v4

• Visa: 4111 1111 1111 1111
• Mastercard: 5555 5555 5555 4444
• American Express: 3782 822463 10005
• Discover: 6011 1111 1111 1117

Which expiration date and security code should you use?

Pick any expiration date in the future. The sandbox checks the format and the date, not an issuer record. Use a three digit CVV for Visa, Mastercard, and Discover, and a four digit CID for American Express.

Do these numbers work with any amount?

Most do. Braintree also maps some amounts to specific processor responses, so an unusual amount can force a decline even on a valid test card. Read the amount column in the test values table before you assume a bug.

How do you test CVV and AVS responses?

Braintree returns a code for each verification check, and the sandbox lets you force each outcome. A match, a mismatch, and a "not verified" result each have a value you can send.

AVS covers two fields: the street address and the postal code. You can send a matching postal code with a wrong street, or a matching street with a wrong postal code, and watch how your checkout reacts. Wire each result to a clear next step, such as approve, hold for review, or decline.

How do you trigger a decline?

Sandbox declines come from three places: the card number, the amount, and the verification values. The test values table lists which input maps to which processor response code. Build one test per code you care about.

Cover the basics: do not honor, insufficient funds, expired card, incorrect CVV, and processor timeout. Each case should produce a different message in your UI. A checkout that prints "card declined" for every code gives the customer nothing to act on.

Why does a test card fail in the sandbox?

• The request goes to the production environment instead of the sandbox.
• The API credentials are live, not test.
• The card number fails Luhn validation, so the request stops before the processor.
• The amount matches a decline trigger on purpose.
• Merchant account rules, such as a CVV requirement, reject the transaction.
• The card brand test range was retired and the docs now list a new number.

Best practices for sandbox testing

• Store test values in one config file. Hardcoded numbers rot fast.
• Write tests for the approval path and for each decline path.
• Log the processor response code in your test output so failures point to the cause.
• Run a small live charge with a real card before launch, then refund it.
• Keep sandbox credentials and test numbers out of production code paths.

FAQ

Is a Braintree test card a real credit card?

No. Test numbers pass Luhn checks, but no bank issues them and no account backs them. Numbers sold as "working cards" for live payments are stolen payment data, and using them is card fraud.

Can you use the same test cards on Braintree, Stripe, and PayPal?

Some numbers overlap because they come from shared card brand test ranges. The decline triggers do not carry over. A number that returns "do not honor" on Braintree may approve on another gateway.

Do test cards work with 3D Secure?

Only with the sandbox values Braintree lists for 3DS. A plain test card cannot force a challenge or an authentication failure, so you need the 3DS test values to exercise that flow.

How often do Braintree test values change?

Rare. Updates are small and land in the docs. If a number stops working, check the reference page before you rewrite your tests.

Can you test recurring billing with a test card?

Yes. Create a subscription on a sandbox card and let the billing cycles run, or advance the clock if your plan supports it. Refunds and voids behave the same way in the sandbox.