Braintree test card v1 is the set of sandbox card numbers developers use to simulate transactions without touching real cardholder data. The standard Visa test number is 4012888888881881, which approves when paired with any future expiration date and the CVV 123. These numbers work only in the Braintree sandbox and are rejected in production.

Braintree Test Card v10: What It Is and How to Test Safely

What are the Braintree sandbox test card numbers?

Each card brand has a dedicated test number that follows the normal card number format. Braintree publishes the current list in its Test Values documentation because numbers are retired and added over time.

more on this topic

• Visa: 4012888888881881
• Visa Debit: 4005519200000004
• Mastercard: 5555555555554444
• Mastercard Debit: 5200828282828210
• Mastercard Prepaid: 5105105105105100
• American Express: 378282246310005
• Discover: 6011111111111117
• JCB: 3530111333300000
• Diners Club: 30569309025904

What does the "v1" in Braintree test card v1 mean?

There is no formal product called Braintree test card v1. The label reflects the first list of test values a developer learns, or an internal version label on a test fixture file. Treat any version number as informal and confirm values against the live Braintree test documentation before relying on them.

Braintree Test Card v8: Sandbox Card Numbers and Usage

How do you set expiration, CVV, and postal code in the sandbox?

Use any expiration date in the future, such as 12/2030, and the CVV 123 for approved transactions. Braintree also documents specific CVV and postal code values that return mismatch responses so you can test your failure paths. Pass these values through Hosted Fields or the client SDK and send the resulting payment method nonce to your server.

Braintree Test Card V7: Sandbox Numbers That Work

How do you trigger declines in the Braintree sandbox?

Braintree provides dedicated test values that force processor declines and gateway rejections. Developers typically run one approved card, one declined card, and one CVV or AVS failure through the same checkout flow to confirm each branch. Sandbox declines do not affect your merchant account or billing.

Do Braintree test cards work in production?

No. Production traffic is routed to live card networks, so test numbers return errors and can flag your account for review. Real card data belongs only in PCI-compliant systems, not in a sandbox or a test fixture file.

What are safe testing practices?

Keep test credentials out of source control and use environment variables for API keys. Never paste a real card number into a sandbox form, even to reproduce a bug, because that breaks PCI DSS handling rules. If you need to model a specific issuer behavior, request a purpose-built test value from Braintree support instead.