A Braintree test card is a fake card number that the Braintree sandbox approves. The standard Visa test number is 4111 1111 1111 1111, the Mastercard number is 5555 5555 5555 4444, and the Amex number is 3782 822463 10005. No money moves, and no bank sees the transaction. The "v3" in the phrase usually points to the Braintree JavaScript SDK v3 and the Drop-in UI v3, not to a separate set of cards.

braintree test card v9

What does "v3" mean for Braintree test cards?

Braintree does not sell a product called "test card v3." The label mixes two things developers search for at once: sandbox card numbers and the version 3 client SDKs that collect them.

braintree test card v3

Drop-in UI v3 and Hosted Fields v3 render the card form, handle input formatting, and tokenize the card data before it reaches your server. The card numbers you type stay the same across SDK versions. Only the integration code changes.

Braintree Test Card v8: Sandbox Card Numbers and Usage

Which Braintree test card numbers should you use?

These numbers pass the Luhn check and return a successful authorization in the sandbox.

read more

• 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
• Diners Club: 3625 720000 0000 00

Card brand matters when you test card type rules, such as a checkout that accepts Visa and Mastercard but blocks Amex. Braintree also publishes test numbers for other brands, countries, and card categories. Pull the current list from the official test documentation before you build a full test matrix.

What do you enter in the CVV, expiry, and ZIP fields?

In the sandbox, any 3 digits work for the CVV, and any 4 digits work for American Express. The expiration date can be any future date. Normal street address and ZIP values return a successful AVS check.

Braintree maps certain cardholder values to specific responses, including CVV failures and AVS mismatches. Use those values when you want to see how your code reacts to a rejected payment. The current mapping lives in the official test documentation, and it changes as Braintree adds processors.

How do you run a test transaction step by step?

1. Log in to the Braintree Control Panel and switch to the sandbox account.
2. Copy the sandbox merchant ID, public key, and private key into your test environment.
3. Load Drop-in UI v3 or Hosted Fields and submit one of the test card numbers.
4. Open the sandbox Control Panel and confirm the transaction shows the status you expected.
5. Check that your server received the webhook and that your order record updated.

Run the same flow with a production-sized amount and a small amount. Amount rules, currency conversion, and settlement timing behave the same way in sandbox as they do in production, so a mismatch shows up early.

How do you trigger declines and errors on purpose?

Approvals are the easy part. Real checkout code has to handle declines, gateway rejections, and processor timeouts.

Braintree documents test amounts and special card values that return each of these responses. Set the amount to the value that maps to a decline, or use the card value that maps to a CVV failure. Log the response code your server stores so you can confirm the error path works.

If you skip this step, your first live decline becomes a support ticket. Test the failure paths in sandbox before you flip to live keys.

Sandbox versus production: what actually differs?

Sandbox endpoints reject live credentials, and production endpoints reject sandbox credentials. Test cards stop working the moment you switch to live keys, and real cards return errors in sandbox.

PCI DSS still applies to your production flow. Card data that reaches your server has to follow the standard, which is why Drop-in UI and Hosted Fields tokenize the number in the browser. Use test card numbers in development and keep real card data out of your test environment.

Why does a Braintree test card get rejected?

Most sandbox failures come from one of four causes.

• The card number has a typo and fails the Luhn check.
• The expiration date is in the past.
• Your code points at a production endpoint while using sandbox keys.
• The card brand is disabled in your sandbox merchant account settings.

Check the gateway response text in the Control Panel first. It names the rule that rejected the card, which saves time compared with reading your own logs.

Frequently asked questions

Does a Braintree test card charge real money?

No. Sandbox transactions run against test networks and settle nowhere. The only cost is the time you spend testing.

Do test cards work with every Braintree SDK version?

Yes. The numbers belong to the sandbox, not to the SDK. Drop-in UI v3, Hosted Fields v3, and the mobile SDKs all accept the same test cards.

Can I reuse the same test card for many transactions?

Yes. Sandbox limits are loose, so a single card number covers repeated runs. Vary the amount and cardholder data when you need different responses.

Where do I find the newest test card numbers?

Use the official Braintree test documentation. Numbers and test values get added or retired as processors change, and third-party blog lists go stale.