Braintree does not publish a "test card v7." Braintree sandbox card numbers are not versioned releases, so no list carries a v7 label inside Braintree's own documentation. The numbers that circulate under that name are the same fixed test numbers Braintree has documented for years, and they work in any sandbox account.

braintree test card v5

The short answer for most developers: use 4111 1111 1111 1111 with any future expiration date and any three digit CVV to produce a successful Visa authorization in the sandbox.

read more

What is a Braintree test card?

A Braintree test card is a card number that only works inside the Braintree sandbox, a separate environment that never reaches a real issuing bank. Sandbox transactions return simulated responses so you can build checkout, refund, and error handling without moving money.

Braintree Test Card v8: Sandbox Card Numbers and Usage

Every Braintree account includes sandbox credentials alongside production ones. The gateway rejects test numbers in production and rejects real card numbers in the sandbox.

related article

Does Braintree publish a "v7" test card list?

No. Braintree's developer documentation maintains a single test card page and updates it in place rather than shipping numbered versions. Blog posts and forum threads often add version labels like v7 to copied lists, which is why the phrase shows up in search results.

Treat any v7 list as an unofficial mirror. Cross check each number against Braintree's own documentation before you hard code it into a test suite.

Which test card numbers approve in the Braintree sandbox?

• Visa: 4111 1111 1111 1111
• Mastercard: 5555 5555 5555 4444
• Mastercard 2 series: 2223 0000 4841 0010
• American Express: 3782 822463 10005
• Discover: 6011 1111 1111 1117
• JCB: 3530 1113 3330 0000
• Diners Club: 3056 9309 0259 04
• Maestro: 6304 0000 0000 0000

All of these approve by default with any future expiry date and any CVV. Card type detection, last four handling, and card level fees in your sandbox behave the same way they will in production.

How do you trigger specific declines and errors?

Braintree keys many failure responses off the transaction amount rather than the card number. A charge of 2000.00 returns a do not honor response, and 2001.00 returns insufficient funds. A charge of 3000.00 produces a generic processor decline.

Those amount based triggers are stable across sandbox accounts and are the most reliable way to test decline paths. If your integration reads specific status codes, log the exact response for each amount and assert against it.

What CVV and AVS values should you test with?

The sandbox accepts any three digit CVV, or a four digit value for American Express, and reports a match by default. A CVV of 200 forces a CVV mismatch so you can test a gateway rejection rule. For address verification, the postal code 20000 forces an AVS mismatch, while most other five digit codes return a full match.

Do test cards work in production?

No. The production gateway rejects documented test numbers, so sending one with live credentials returns a decline instead of an authorization. Sandbox accounts reject real card numbers, which means a test run cannot charge a customer by accident.

Never place real card data in a sandbox account or a shared test fixture. Use only documented test numbers, and keep production API keys out of developer machines and CI environments.

Frequently asked questions

Is there an official Braintree test card v7?

No. Braintree does not number its test card lists. The v7 suffix comes from third party reposts, not from Braintree documentation.

Can I use 4242 4242 4242 4242 with Braintree?

That number belongs to another processor's documentation and is not on Braintree's list. Use 4111 1111 1111 1111 for a Visa approval instead.

Why does my test card get declined in the sandbox?

Check the transaction amount first, because amounts like 2000.00 and 2001.00 are designed to decline. Then confirm you are pointed at the sandbox API endpoint rather than production.

Do Braintree test cards expire?

The card numbers themselves do not expire, but the expiration date you submit must be in the future. Any future month and year pair passes sandbox validation.