A Braintree test card is a card number that works only in the Braintree sandbox and is used to simulate payments during development. A normal test run uses a documented number such as 4111111111111111, any future expiration date, and any three-digit CVV, and no real money moves.

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

What a Braintree test card actually is

Braintree separates its environments. In sandbox, card numbers are checked for format and brand, then routed to simulated responses instead of a real card network. That lets you build checkout, subscription, and refund flows before you have a merchant account in production.

braintree test card v8

The same number that approves in sandbox will fail in production. If a test card appears to charge successfully on a live account, the credentials you are using almost certainly point to sandbox.

braintree test card v10

Where the official list lives

Braintree publishes its test card numbers in the testing section of its developer documentation, grouped by brand: Visa, Mastercard, American Express, Discover, and JCB. The page also lists numbers that force specific outcomes, such as processor declines or CVV mismatches. Because Braintree adds scenarios over time, treat the documentation as the source of truth and check it before you write automated test suites.

braintree test card v4

Common test numbers developers use

• Visa: 4111111111111111 and 4012888888881881
• Mastercard: 5555555555554444 and 5105105105105100
• American Express: 378282246310005 and 371449635398431
• Discover: 6011111111111117
• JCB: 3530111333300000

These are public test values that pass the Luhn check and route to the correct brand inside the sandbox. They are not cardholder data, and they should never appear in a production request.

What to enter for CVV, expiry, and postal code

In sandbox, use a future expiration date and a CVV of 123, or 1234 for American Express. Braintree passes CVV and AVS values through the sandbox and returns response codes you can log, which is useful for testing your error handling. If you need a specific mismatch, use a number documented for that result rather than guessing.

Simulating declines and gateway errors

Approval-only testing hides bugs. Braintree documents dedicated numbers for declines, CVV failures, and gateway rejections, and those mappings are not identical across processors. Build a small matrix of cases: approved, declined, CVV failure, expired card, and duplicate transaction. Run each one and verify that your UI shows a clear message and that your order state stays consistent.

Sandbox versus production keys

Test numbers only work with sandbox credentials. Keep sandbox API keys and production keys in separate configuration files, and confirm which environment your client token or API request uses before you run tests. A surprising number of "test card not working" reports come down to a production key in a local environment file.

Handling test data safely

Do not use real card numbers in test flows, even your own. PCI DSS requirements apply to any environment that stores, processes, or transmits cardholder data, and a real number in a laptop file or repository creates a compliance problem that is hard to unwind. Use Braintree's hosted fields or drop-in UI so the number never reaches your server, in sandbox and production alike.

Troubleshooting checklist

• Card declined in sandbox: confirm the expiration date is in the future and the number is valid for the brand.
• No CVV response: check that the CVV field is included in the transaction request.
• Token creation fails: verify the environment, merchant ID, and public or private key pair.
• Verification behaves oddly: check whether you are running a zero-dollar or one-dollar auth, since verification rules differ.

With a documented Braintree test card and the right sandbox keys, you can cover approvals, declines, and verification behavior before a single real transaction runs.