A Braintree test card is a sandbox-only card number that the Braintree gateway accepts for trial payments. Version 5 of the Braintree SDKs does not change the card list: the same numbers work in Drop-in UI, Hosted Fields, the JavaScript SDK, and the v5 iOS and Android libraries. Nothing you do with these numbers reaches a real bank account or moves real money.

braintree test card v3

Which test card numbers does Braintree accept?

Use any number below with sandbox API credentials. The gateway treats each one as a valid card and returns a payment method nonce.

read more

• Visa: 4111 1111 1111 1111
• Mastercard: 5555 5555 5555 4444
• Mastercard: 5105 1051 0510 5100
• American Express: 3782 822463 10005
• American Express: 3714 496353 98431
• Discover: 6011 1111 1111 1117
• JCB: 3530 1113 3330 0000
• Diners Club: 3056 9309 0259 04
• UnionPay: 6200 0000 0000 0005

Each entry in the official sandbox list carries a note about the response it returns. Some cards approve, others return a set decline code or a CVV mismatch. Braintree adds and retires numbers between sandbox releases, so check the current list before you lock test cases into a CI suite.

Braintree Test Card v8: Sandbox Card Numbers and Usage

Does Braintree SDK v5 change how test cards behave?

No. The v5 label covers the client-side SDK release line, not the gateway. Card validation happens on Braintree's servers, so a payment made through Drop-in v5, a native v5 mobile app, or a server-side card object all hit the same sandbox rules.

braintree test card v8

What does shift between major versions is the shape of the response. In v5 you still get a payment method nonce and a result object, but callback names, promise handling, and error arrays differ from v3 and v4. Log the full result object while testing instead of trusting a single boolean.

What CVV, expiry, and postal code should you type?

• CVV: any three digits for Visa, Mastercard, Discover, JCB, and UnionPay. American Express takes four.
• Expiry: any date in the future. The sandbox does not tie it to a real account.
• Postal code: any value passes unless the test card is flagged for AVS mismatch testing.
• Name: any string. Cardholder names are not verified.

A plain 123 for the CVV and 12/2030 for the expiry covers most cases. If a specific test card in the docs calls for a different CVV or a bad postal code, follow that entry instead.

How do you force a decline or an error?

Braintree maps certain test amounts to specific processor responses, which lets you simulate a do-not-honor or insufficient-funds decline without swapping the card. The amount-to-response mapping lives in the sandbox documentation and has changed over time, so pull it fresh rather than hardcoding old values.

Two other ways to break a payment on purpose:

• Pick a test card the docs list as declined.
• Send a truncated or already-used nonce and read the validation error.

How do you run a full sandbox payment with a test card?

1. Create a Braintree sandbox account and open the API keys page.
2. Generate a client token on your server with the sandbox credentials.
3. Render Drop-in or Hosted Fields v5 with that token.
4. Enter a test card, a future expiry, and 123 as the CVV.
5. Submit the form and capture the returned nonce and status.
6. Confirm the transaction in the sandbox control panel.

Run the same flow with two or three card brands. Visa, Mastercard, and Amex cover the formatting edge cases you will hit in production, including the four-digit Amex CVV field.

Common questions about Braintree test cards

Do test cards work in production?

No. Sandbox numbers are rejected or routed to a decline by live processors. Keep the two lists in separate config files so a test card never lands in a live build.

Why is a valid test card declined?

The usual causes are a test amount that triggers a decline, a nonce that was already consumed, or a missing currency on the transaction call. Check the transaction status and the processor response code before assuming the card is wrong.

Can I use a real card in the sandbox?

Never. A live card number typed into a test form creates a data-handling problem with no upside. Test numbers exist so that real card data stays out of your development and staging systems.

Does Braintree test PayPal the same way?

No. PayPal testing uses sandbox personal and business accounts instead of card numbers. You link a sandbox PayPal account to your sandbox Braintree account, then approve the payment in the PayPal test flow.

Habits that keep sandbox testing clean

Keep test credentials and live credentials in different environment files. A sandbox API key cannot charge a live card, but a copy-paste slip in the other direction can expose customer data.

Store nothing. Pass the payment method nonce to your server, charge it once, and drop the card details. Then promote the same code path to production unchanged, minus the test numbers.