The core answer before you spend a cent

You cannot buy a Braintree test card v4, because no such product exists. Braintree publishes its sandbox test card numbers, expiration placeholders, and decline triggers in its public developer documentation at no cost, and the "v4" label is community shorthand that gets attached to downloaded or scraped copies of that same list. If a seller is charging you for a "v4 test card pack," you are paying for a free text file, and in many listings the seller is also mixing in real or stolen card data. Treat any paid listing as a scam signal and go to the official sandbox reference instead. The rest of this guide covers what to check in a test card reference, which parameters actually change your test outcomes, and the mistakes that quietly break integration testing.

braintree test card v9

What the "v4" label refers to

Payment gateways revise their test documentation over time, adding card brands, updating decline simulation amounts, and adjusting CVV mismatch rules. Resellers and forum posters often stamp a version number onto a snapshot of that list to make it look exclusive. Braintree itself does not certify a "test card v4" standard, does not sell card numbers, and does not license third parties to resell sandbox credentials. The only authoritative source is the gateway's own sandbox documentation, which is linked from your Braintree control panel and updated whenever the test matrix changes.

read more

What to look for in a test card reference

• Card brand coverage: Visa, Mastercard, American Express, and Discover, each with at least one success number and one decline number.
• Card type coverage: credit and debit variants, plus any commercial or prepaid cards your production traffic actually uses.
• Verification triggers: which CVV and postal code values force a mismatch so you can test your risk rules.
• Amount based responses: the exact transaction amounts that map to specific decline codes.
• 3D Secure and authentication flows, if your integration handles SCA or liability shift.
• A stated last-updated date, so you know the list matches the current API version.

Parameter bands that matter

Card numbers

Sandbox numbers are grouped by brand. Use a Visa test number for Visa behavior, a Mastercard number for Mastercard, and so on, because gateway routing, interchange assumptions, and decline simulation differ by brand. Never test only one brand and assume the others behave the same way.

Braintree Test Card v8: Sandbox Card Numbers and Usage

CVV and expiry

American Express uses a four digit verification code and a different card number format, while Visa, Mastercard, and Discover use three digits. Sandbox expiry dates must be set in the future, and the sandbox accepts a specific set of CVV values. Some values are reserved to simulate a CVV mismatch, and a separate reserved value simulates a postal code mismatch. Confirm the current reserved values in the documentation, since these change between API versions.

braintree test card v4

Amounts that trigger declines

Braintree's sandbox uses transaction amount as a control signal. Round amounts such as 2000.00 and 2001.00 are commonly mapped to specific decline responses, including do-not-honor and insufficient funds, while ordinary amounts like 10.00 succeed. Build a test matrix that runs one success amount and each decline amount through the same code path.

Pitfalls to avoid

• Using real cardholder data in the sandbox. It violates PCI DSS requirements, exposes you to breach liability, and is unnecessary because test numbers exist for this purpose.
• Assuming a test number works in production. Sandbox credentials are rejected by the live environment, and a live card number in the sandbox often triggers fraud controls.
• Trusting a scraped list without verifying against the current docs. Stale numbers produce confusing failures that look like integration bugs.
• Testing only the happy path. Declines, CVV mismatches, expired cards, and network timeouts are where most production incidents originate.
• Buying or trading card data of any kind. Possession of real card numbers without authorization is a criminal exposure in most jurisdictions, regardless of whether the cards are active.

FAQ

Is there an official Braintree test card v4?

No. There is no versioned product called a v4 test card. Braintree publishes a sandbox test card list and revises it as needed.

Where do I get test card numbers?

From the gateway's own developer documentation, free of charge, and from the test tooling inside your merchant control panel.

Do test cards cost anything?

No. Sandbox transactions do not move real money and do not incur processing fees.

Can I validate my full checkout with them?

Yes, in sandbox mode. Sandbox transactions exercise authorization, capture, refund, void, and webhook delivery exactly like production, minus the money movement.

What if I need to test a specific decline code?

Use the amount based simulation table, then confirm the resulting response code matches the one your application expects to handle.