FakecreditcardHow Braintree test cards work
The Braintree sandbox is a separate environment from production, with its own login, merchant ID and API keys. Nothing carries over between the two. The sandbox only accepts the documented test numbers, so a randomly generated card is rejected even if it passes Luhn.
Braintree splits test outcomes in two. The card number decides whether a card verification succeeds. The amount decides what happens to a transaction. So 4111 1111 1111 1111 with an amount of 2001.00 is declined for insufficient funds, while the same card with 10.00 succeeds.
CVV and postal code values produce specific AVS and CVV responses, but they only reject transactions if you have enabled AVS or CVV rules in the sandbox control panel.
Cards for unsuccessful card verification
These numbers make a card verification fail (for example when you vault a card with verifyCard: true). They don’t affect transaction outcomes.
| Brand | Number | Result | Copy |
|---|---|---|---|
| Visa | 4000 1111 1111 1115 | Verification: processor declined | |
| Mastercard | 5105 1051 0510 5100 | Verification: processor declined | |
| American Express | 3787 344936 71000 | Verification: processor declined | |
| Discover | 6011 0009 9013 9424 | Verification: processor declined | |
| Diners Club | 3852 000000 9814 | Verification: processor declined | |
| JCB | 3566 0020 2036 0505 | Verification: failed (3000) |
Card type indicators and fraud tools
Use these to test logic that depends on card metadata, such as blocking prepaid cards. The last three trigger Braintree’s premium fraud tools when they are enabled.
| Brand | Number | Result | Copy |
|---|---|---|---|
| Visa | 4012 0043 3850 8385 | Card type indicators: prepaid = "Yes", debit = "Yes" | |
| Visa | 4009 0400 0000 0009 | Card type indicator: commercial = "Yes" | |
| Visa | 4012 0000 3333 0125 | Card type indicator: debit = "Yes" | |
| Visa | 4012 0000 3333 0224 | Card type indicator: payroll = "Yes" | |
| Visa | 4012 0000 3333 0422 | Card type indicators: all values = "No" | |
| Visa | 4012 0000 3333 0323 | Card type indicators: all values = "Unknown" | |
| Visa | 4111 1400 0000 0002 | Status authorized, Fraud Protection decision: Review | |
| Visa | 4000 1111 1111 1511 | gateway_rejected, reason: fraud | |
| Visa | 4111 1300 0000 0003 | gateway_rejected, reason: risk_threshold |
3D Secure 2 test cards (Visa and Mastercard)
For all 3D Secure test cards, use expiry month 01 and the current year + 3. Braintree lists the same scenarios for American Express, Discover and Elo.
| Brand | Number | Result | Copy |
|---|---|---|---|
| Visa | 4000 0000 0000 2701 | 3DS Successful No-Challenge Authentication | |
| Mastercard | 5200 0000 0000 2235 | 3DS Successful No-Challenge Authentication | |
| Visa | 4000 0000 0000 2925 | 3DS Failed No-Challenge Authentication | |
| Mastercard | 5200 0000 0000 2276 | 3DS Failed No-Challenge Authentication | |
| Visa | 4000 0000 0000 2719 | 3DS Attempt No-Challenge Authentication | |
| Mastercard | 5200 0000 0000 2482 | 3DS Attempt No-Challenge Authentication | |
| Visa | 4000 0000 0000 2537 | 3DS Rejected No-Challenge Authentication by the Issuer | |
| Mastercard | 5200 0000 0000 2185 | 3DS Rejected No-Challenge Authentication by the Issuer | |
| Visa | 4000 0000 0000 2313 | 3DS Unavailable No-Challenge Authentication from the Issuer | |
| Visa | 4000 0000 0000 2990 | 3DS Authentication Not Available on Lookup | |
| Visa | 4000 0000 0000 2446 | 3DS Error on Lookup | |
| Visa | 4000 0000 0000 2354 | 3DS Timeout on Lookup | |
| Visa | 4000 0000 0000 2503 | 3DS Successful Challenge Authentication | |
| Mastercard | 5200 0000 0000 2151 | 3DS Successful Challenge Authentication | |
| Visa | 4000 0000 0000 2370 | 3DS Failed Challenge Authentication | |
| Mastercard | 5200 0000 0000 2490 | 3DS Failed Challenge Authentication | |
| Visa | 4000 0000 0000 2644 | 3DS Error on Authentication | |
| Mastercard | 5119 7379 4756 5580 | 3DS Data Only Successful |
Transaction amounts that trigger results
In the sandbox, the transaction amount decides the outcome. For processor declines, the response code equals the amount — 2001.00 returns 2001 (Insufficient Funds), 2004.00 returns 2004 (Expired Card).
| Amount | Authorization / settlement result |
|---|---|
| 0.01 - 1999.99 | Authorized / Settled |
| 2000.00 - 2999.99 | Processor Declined with a processor response equal to the amount / n/a |
| 3000.00 - 3000.99 | Failed with a 3000 processor response / n/a |
| 3001.00 - 4000.99 | Authorized / Settled |
| 4001.00 - 4001.99 | Authorized / Settlement Declined on certain transaction types with a processor response equal to the amount; Settled on all others |
| 4002.00 - 4002.99 | Authorized / Settlement Pending on PayPal transactions with a processor response equal to the amount; Settled on all others |
| 4003.00 - 5000.99 | Authorized / Settlement Declined on certain transaction types with a processor response equal to the amount; Settled on all others |
| 5001.00 | Gateway Rejected with a reason of Application Incomplete / n/a |
| 5001.01 | Processor Declined on PayPal transactions in the Mocked PayPal flow with a 2038 processor response; Authorized on all others / n/a on PayPal transactions; Settled on all others |
| 5001.02 | Authorized / Processor Unavailable on certain transaction types with a processor response of 3000; Settled on all others |
| 5002.00 and up | Authorized / Settled |
| 2099 | simulates 2099 - Cardholder Authentication Required soft decline (3DS testing page) |
CVV and AVS test values
- CVV
200(CID2000) → N, does not match ·201(2011) → U, not verified ·301(3011) → S, issuer does not participate · no value → I · any other value → M, matches. - Billing postal code
20000→ N ·20001→ U ·30000→ E, AVS system error ·30001→ S, issuer does not support AVS · any other value → M. - Street address with number
200(e.g. 200 N Main St) → N ·201→ U · any other value → M.
Server-side tests can skip the client SDK by using test nonces such as fake-valid-nonce or fake-processor-declined-visa-nonce.
Testing Braintree payments step by step
- Sign up for a sandbox account and use its merchant ID, public key and private key.
- Create a transaction with
4111 1111 1111 1111and an amount under 2000.00 to test the success path. - Repeat with amounts from the table to test processor declines (2000.00–2999.99), network errors (3000.00) and settlement declines.
- Vault a card with verification enabled and use the failed-verification cards to test that path.
- Run 3D Secure through the Drop-in or Hosted Fields flow with the 3DS cards.
Common errors and fixes
- “Credit card number is not an accepted test number”
- The sandbox only accepts documented numbers. Use one from the tables on this page.
- Decline card still succeeds
- The decline cards only affect card verification. To decline a transaction, change the amount.
- CVV 200 does not fail
- Enable CVV rules in the sandbox control panel first.
Sources
Every number on this page was copied from Braintree’s official documentation and passes the Luhn check. Checked October 2026; gateways change their test data from time to time, so if a number stops working, check the source:
- Braintree docs – Testing (General reference)
- Braintree docs – 3D Secure Testing
- Braintree docs – Processor Authorization Responses
Frequently asked questions
What is the Braintree test card number?
4111 1111 1111 1111 (Visa) is the most common. Use an amount between 0.01 and 1999.99 for a successful transaction.
How do I simulate a declined transaction in Braintree?
Use an amount between 2000.00 and 2999.99. The processor response code equals the amount, for example 2001.00 for insufficient funds or 2004.00 for an expired card.
Does Braintree have 3D Secure test cards?
Yes. For example 4000 0000 0000 2701 authenticates without a challenge and 4000 0000 0000 2503 succeeds after a challenge. Use expiry month 01 and the current year + 3.
Can I use these test cards on another gateway?
Usually not. Each gateway only recognises its own documented test numbers in its own sandbox. Some numbers, such as 4111 1111 1111 1111, appear in several lists, but the results they trigger differ. For format-only testing on your own forms, use our card generator.