Braintree test card v1 is the sandbox number most developers use first: Visa 4111 1111 1111 1111, with any future expiration date and CVV 123. Braintree sells no product called "v1 test card." The label comes from early Braintree API guides where the sample card table carried a version tag, and that tag spread into blog posts and support threads.

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

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

Braintree's API shipped in numbered versions, and older integration docs stamped the card table with a version label. Readers copied that label, so the phrase now acts as shorthand for the original sandbox Visa number. Current Braintree documentation lists one table with no version tag.

read more

The version label has no effect on how testing works. Sandbox behavior depends on your sandbox account, not on which doc revision you read.

read more

Which Braintree test card numbers work in the sandbox?

Braintree publishes at least one card for every major network. Use any future expiry date, plus a CVV of 123 for Visa, Mastercard, Discover, JCB, and Diners Club, or 1234 for American Express (Amex uses a four digit code).

related article

• Visa: 4111 1111 1111 1111, and 4012 8888 8888 1881
• Mastercard: 5555 5555 5555 4444
• American Express: 3782 822463 10005, and 3714 496353 98431
• Discover: 6011 1111 1111 1117
• JCB: 3530 1113 3330 0000
• Diners Club: 3056 9309 0259 04

Every one of these numbers passes the Luhn checksum, so your form accepts them at the point of entry instead of rejecting them as malformed. Check Braintree's testing page before you freeze the list into a test suite, because card networks retire sandbox numbers.

How do you run a test transaction with a Braintree test card?

1. Create a sandbox account in the Braintree Control Panel.
2. Copy your sandbox merchant ID, public key, and private key from Settings, then API Keys.
3. Render Drop-in UI or Hosted Fields with your sandbox tokenization key.
4. Enter a test card number, a future expiry date, and the matching CVV.
5. Submit the transaction and confirm the result in Transactions inside the Control Panel.

A sale that returns an authorized status in the sandbox is the same code path your production integration will follow. Treat a sandbox approval as a green light for wiring, not as proof that your live merchant account is configured right.

How do you trigger a decline or a CVV failure on purpose?

Braintree documents trigger values that force specific processor responses. Entering 200 as the CVV on a Visa test card, for example, produces a CVV mismatch rather than an approval. Billing address and postal code values map to AVS responses in the same way.

Those trigger values change when processors update sandbox behavior, so read Braintree's testing page instead of copying a list from a forum. When a test card returns a code you did not expect, that page is the source of truth.

Handle the failure branch in code, not just in a manual test. Log the processor response code, show a clear message to the customer, and confirm that your retry logic does not loop on a hard decline.

What else can you test with sandbox cards?

A single authorized sale covers a small slice of payment work. The sandbox supports the rest of the lifecycle with the same card numbers.

• Voids and full refunds on a settled transaction
• Partial refunds and partial settlements
• Subscription and recurring billing cycles
• PayPal and Venmo sandbox checkout flows
• Vault storage, so a card is saved and charged again later
• 3D Secure challenge and frictionless scenarios

Each flow returns its own status values, so confirm what your app does with each one before launch.

Do Braintree test cards work in production?

No. Test numbers are blocked in the live environment, and a production account returns a decline or an error for any of them. Braintree also forbids using sandbox data to move real money.

Holding real card data for testing breaks PCI DSS rules. Keep live cardholder data in production and keep test data in the sandbox, with separate API keys for each.

Common mistakes with Braintree test cards

• Using live API keys against test card numbers, which returns confusing errors.
• Sending a three digit CVV for Amex, which expects four digits.
• Assuming AVS will match, since sandbox addresses are not tied to any real billing record.
• Reusing a trigger card, such as the CVV mismatch case, and then wondering why every later test fails.
• Testing one network only, which hides formatting bugs in card type detection.

Frequently asked questions

Is 4111 1111 1111 1111 a real card?

No. Card networks reserve it for testing and keep it out of circulation. Any approval it produces exists inside a sandbox and nowhere else.

Which expiration date should I use?

Any date in the future. The sandbox does not contact a real issuer, so the month and year only need to pass your own form validation. A past date is the fastest way to test your expiry check.

Can I reuse one test card for many orders?

Yes. Sandbox transactions do not consume a card, so one number handles hundreds of runs. Switch networks when you want to test issuer specific behavior.

Does the sandbox support 3D Secure with test cards?

Yes, Braintree provides sandbox scenarios for 3D Secure, including authentication failures. Check the 3D Secure testing page for the card and value pairings that apply to your region.