A Braintree test card v10 is not a real card and not one specific number. The phrase refers to a versioned list of sandbox test card numbers that Braintree publishes so developers can simulate successful and declined payments inside a test environment. If you search for "braintree test card v10," you are most likely looking for the current set of fake card numbers, the matching CVV and expiry rules, and an explanation of why a sandbox charge succeeds or fails.

read more

Why the "v10" label appears

Braintree updates its developer documentation over time. Test card lists get revised when card networks add ranges, when a processor changes how it maps a number to a response, or when the sandbox adds new simulation behavior. Some third-party blog posts and internal team wikis copy those lists and stamp them with a version number such as v10 to track which snapshot they used. The label is a bookmark, not a product. The numbers underneath it come from Braintree's own sandbox documentation.

Braintree Test Card v8: Sandbox Card Numbers and Usage

Common Braintree sandbox test numbers

These are the widely documented fake numbers used in sandbox mode. They pass standard checksum validation but are not issued to anyone.

Braintree Test Card V7: Sandbox Numbers That Work

• Visa: 4111 1111 1111 1111
• Mastercard: 5555 5555 5555 4444
• American Express: 3782 822463 10005
• Discover: 6011 1111 1111 1117
• JCB: 3530 1113 3330 0000
• CVV: any three-digit value, commonly 123
• Expiry: any future date

Braintree's documentation also lists numbers that are wired to return specific decline responses, so you can test your error handling without guessing. Which number maps to which response depends on the processor and the merchant account settings in your sandbox.

Braintree Test Card v6: Sandbox Testing Guide

How to use a test card in the sandbox

1. Confirm your API keys are sandbox keys, not production keys. Mixing them up is the most common cause of confusing results.
2. Enter the test number in your own checkout form or in the Braintree control panel's test transaction screen.
3. Use any future expiry and any three-digit CVV unless your test is checking CVV rules.
4. Submit the charge and read the gateway response object, not just the success or failure flag.

Test cards are not real card data

Sandbox numbers exist precisely so that no live card data ever touches a development environment. Real card numbers, CVVs, and expiration dates must stay inside systems that meet PCI DSS requirements, and they should never be pasted into a demo shop, a staging server, or a shared spreadsheet. A test card number is safe to store in a repository because it cannot be charged. A real one creates legal and financial exposure the moment it lands somewhere it should not be.

Why a test card fails

• You are pointed at the production endpoint instead of the sandbox endpoint.
• The card number does not match the card type your form selected.
• Your merchant account in the sandbox is not enabled for that card brand.
• You reused a token or nonce that was already consumed.
• An old copy of the list, such as a v10 snapshot, contains a number the sandbox has since reassigned.

When a charge behaves oddly, pull the full gateway response and compare the card number against Braintree's live documentation rather than a cached version of the list. That single habit resolves most sandbox confusion.