Braintree test card v3 means using Braintree's documented sandbox card numbers with the 3.x client SDK, braintree-web, or Drop-in UI v3. The default Visa number is 4111 1111 1111 1111, entered with any future expiration date, any CVV, and a sandbox client token. It produces a successful authorization with no real money movement and is blocked on live accounts.

related article

What does "v3" refer to in Braintree testing?

The "v3" label points to the third-generation client integration: braintree-web 3.x and Drop-in UI v3. These versions collect card data in the browser and return a payment method nonce instead of passing raw card numbers to your server. The sandbox environment behind them is the same one older integrations used, so the test card numbers did not change.

braintree test card v8

Which test card numbers work in the Braintree sandbox?

• Visa: 4111 1111 1111 1111
• Mastercard: 5555 5555 5555 4444
• American Express: 3782 822463 10005 (use a 4-digit CID)
• Discover: 6011 1111 1111 1117
• JCB: 3530 1113 3330 0000
• Diners Club: 3056 9309 0259 04

Each of these returns a successful authorization when the account is in sandbox mode. Use a future date such as 12/2030 for every card.

braintree test card v10

How do you trigger a declined transaction in sandbox?

Braintree documents a separate set of test values that force processor declines, so you can exercise error handling without guessing. The exact list is published on the Test Values page and is updated from time to time. Confirm the current entry before you hard-code a decline scenario into automated tests.

braintree test card v8

How do you test CVV and AVS responses?

Successful sandbox authorizations accept most CVV values, but specific documented values force a mismatch. AVS works the same way: one postal code returns a match, others return partial or no match. Gateway rules decide whether a mismatch rejects the transaction or only flags it.

How do you use a test card with braintree-web v3?

1. Create a sandbox account and copy the merchant ID, public key, and private key.
2. Generate a client token on your server and initialize Drop-in UI or Hosted Fields with it.
3. Enter one of the numbers above in the sandbox form and submit to receive a payment method nonce.
4. Send the nonce to your server and call the sale method to inspect the result object.

Check the response fields rather than the UI alone, because sandbox errors return the same codes as production. Logging the result object makes decline and validation behavior easier to debug.

Do Braintree test cards work in production?

No. Sandbox test numbers are rejected by live accounts, and real cards are rejected in sandbox, which prevents accidental charges during development. A test card that appears to succeed in production signals a credentials mix-up or a real card number that matches the test pattern.

Why does a valid test card return an error?

The most common cause is running the form against production API keys instead of sandbox keys. Another is using a card brand that the sandbox merchant account does not have enabled. Regenerating the client token after any credential change resolves most remaining cases.