What is a Braintree test card v2?

A Braintree test card is a fake card number that runs in the Braintree sandbox, the test copy of the payment gateway. It returns simulated approvals and declines so you can build a checkout flow without moving real money. "V2" is not an official Braintree product name. It appears either as an API or SDK version label, or as a second revision of a test card list posted by a blog or forum thread.

related article

The useful takeaway: test card numbers stay the same across Braintree API versions. When a page tags its list "v2," compare the digits to the sandbox reference before you rely on them.

related article

Which test card numbers work in the Braintree sandbox?

These numbers come from the standard test set that Braintree and most gateways publish. Every one of them works in sandbox mode only.

read more

• Visa: 4111111111111111
• Visa debit: 4005519200000004
• Mastercard: 5555555555554444
• American Express: 378282246310005
• Discover: 6011111111111117
• JCB: 3530111333300000
• Diners Club: 30569309025904

Use a future expiration date, a CVV of 123 for a passing check, and a billing ZIP in the format your form expects. These numbers pass a Luhn check, so one wrong digit fails before the request ever reaches Braintree.

Braintree Test Card V7: Sandbox Numbers That Work

How do you run a test transaction in Braintree?

1. Sign in to the Braintree Control Panel and switch to your sandbox account.
2. Copy the sandbox merchant ID, public key, and private key into your test environment.
3. Point the SDK at sandbox instead of production.
4. Submit a test card with a future expiration date and CVV 123.
5. Read the response object for status, response code, and the CVV or AVS result.
6. Repeat the run with the special values that trigger declines, then check the transaction in the Control Panel.

Log each run with the card number, amount, and response code. That record saves hours when a real transaction behaves in a way your test never did.

What triggers declines and CVV mismatches?

Braintree publishes CVV values that return mismatch, unverified, and not-submitted responses, plus amounts that map to processor decline codes. Those values sit in the sandbox reference and get updated from time to time, so read the current page rather than an old screenshot. The purpose is error handling: you want to see how your checkout reacts when a bank says no.

Test the full chain, not just the happy path. Authorization, capture, void, refund, and partial refund each return their own codes, and a card that approves can still fail at settlement in sandbox scenarios.

Why do some pages call it "test card v2"?

API and SDK version labels

Braintree ships versioned APIs and SDKs, and its Drop-in UI moved from v2 to v3. A page titled "Braintree v2" often describes the older integration, not a new card set.

Second revision of a card list

Documentation gets edited. A writer who updates a card list may tag the page v2, v3, and onward. The tag says nothing about the gateway itself. Either the digits match the sandbox reference or they don't.

Can you use Braintree test cards on a live account?

No. Live accounts route to real card networks, and test numbers either fail the Luhn check or come back as declines from an issuer that has never heard of them. Nothing settles, and repeated attempts against production keys can flag your account for review.

A test card is not a working card and not free money. It is a digit string the sandbox recognizes. Buying, selling, or using real card data without the cardholder's permission is card fraud, and in the United States it falls under 18 U.S.C. 1029.

Common mistakes when testing Braintree payments

• Running test cards against production keys, which returns hard declines.
• Reusing one card number for every scenario, so refund and partial-capture paths stay untested.
• Skipping 3D Secure and authentication flows, which use their own test values.
• Trusting a card list from years ago instead of the current sandbox reference.
• Hard-coding test numbers in code that later ships to production.
• Ignoring the response code and reading only the pass or fail status.

Frequently asked questions

Is there an official Braintree test card v2 list?

No. Braintree keeps one sandbox reference. Any "v2" label comes from a third party or from a version number attached to an API or SDK.

What CVV should I use with Braintree test cards?

123 returns a passing response for the standard test numbers. Other values trigger specific mismatch and unverified codes, which you use to test your error messages.

Do Braintree test cards expire?

The numbers do not expire. The expiration date you type must be in the future, or the form rejects the entry before the request is sent.

Where do I check the current numbers and codes?

The Braintree developer documentation from PayPal holds the live sandbox reference, including the response codes tied to each test value.