How do Braintree's decline codes differ from Stripe's?

Braintree uses numeric processor response codes (2000 = Do Not Honor, 2001 = Insufficient Funds, 2053 = Card Reported Lost or Stolen). Stripe uses string codes like 'insufficient_funds' and 'stolen_card'. Both represent the same underlying scenarios but with different API response formats.

Can I test Braintree with the same cards as PayPal?

Some overlap exists (4111 1111 1111 1111 works in both) but Braintree has its own set of scenario-triggering cards in the 4000 1111 1111 XXXX range. Use the Braintree-specific cards for precise processor response code testing.

How do I test fraud in Braintree?

4111 1111 1111 1137 triggers a gateway_rejected:fraud response. 4111 1111 1111 1152 creates a simulated chargeback when the transaction settles. These let you test your dispute-handling workflow without real fraud.

Braintree Test Cards — Sandbox Card Numbers

Verified Braintree sandbox test cards covering processor response codes, decline scenarios, 3DS, and fraud simulation.

Last updated: April 2026

verifiedVerified against Braintree documentation — April 22, 2026

Official docsopen_in_new

Braintree (owned by PayPal) uses a sandbox environment for all payment testing. Test cards work with both the Drop-in UI and server-side Braintree SDK integrations. Processor responses are simulated based on specific card numbers or amounts.

search

Showing 15 of 15 test cards

Card Number	Network	Scenario	Code	Notes
4111 1111 1111 1111TEST ONLY	Visa	Successful payment — processor: authorizeGlobal	—	Any future expiry, any CVV.
4005 5192 0000 0004TEST ONLY	Visa	Successful payment (US debit)US	—	—
5431 1111 1111 1111TEST ONLY	Mastercard	Successful paymentGlobal	—	—
3782 822463 10005TEST ONLY	Amex	Successful paymentGlobal	—	4-digit CID.
6011 1111 1111 1117TEST ONLY	Discover	Successful paymentUS	—	—
4000 1111 1111 1115TEST ONLY	Visa	Declined — do not honorGlobal	processor_declined	Processor response code: 2000 — Do Not Honor.
4000 1111 1111 1123TEST ONLY	Visa	Declined — insufficient fundsGlobal	insufficient_funds	Processor response code: 2001.
4000 1111 1111 1131TEST ONLY	Visa	Declined — lost or stolen cardGlobal	card_reported_lost_or_stolen	Processor response code: 2053.
4012 0000 3333 0026TEST ONLY	Visa	Declined — card account length errorGlobal	—	—
4000 0000 0000 0085TEST ONLY	Visa	3DS — challenge requiredGlobal	—	Use with Braintree's 3D Secure v2 flow.
4000 0000 0000 0051TEST ONLY	Visa	3DS — authentication unavailableGlobal	—	—
4111 1111 1111 1129TEST ONLY	Visa	CVC — does not matchGlobal	cvv_does_not_match	CVV check fails but authorization may still succeed depending on processor.
4111 1111 1111 1137TEST ONLY	Visa	Fraud — gateway rejectedGlobal	gateway_rejected:fraud	Triggers fraud gateway rejection.
4111 1111 1111 1152TEST ONLY	Visa	Chargeback — simulatedGlobal	—	Creates a chargeback in sandbox when settled.
4111 1111 1111 1160TEST ONLY	Visa	AVS — zip failsUS	—	—

TEST ONLY. These numbers will not process real transactions. Use only in Braintree's sandbox environment with test API credentials.

What it does

Processor response codes

Each decline card maps to a specific Braintree processor response code (2000, 2001, 2053) for precise error handling tests.

3DS v2 test cards

Cards for 3DS challenge and authentication-unavailable scenarios in Braintree's 3D Secure v2 flow.

Fraud simulation

Cards that trigger gateway-rejected:fraud and chargeback simulation for testing fraud-handling code paths.

US debit card

A US debit card test number for testing debit-specific flows.

How to use Braintree Test Cards — Sandbox Card Numbers

1
Set up Braintree sandbox
Create a Braintree sandbox account at sandbox.braintreegateway.com and get your Merchant ID, Public Key, and Private Key.
2
Use the test card
Enter the card number with any future expiry and any CVV in your Drop-in UI or server-side API call.
3
Check the processor response
Braintree returns a transaction.processorResponseCode and processorResponseText describing the outcome.
4
Handle the response
Use the expected processor response code to test your error handling logic.

Braintree vs Stripe sandbox: key differences

Braintree's test environment simulates at the processor level — responses include processor response codes that mirror real issuer responses. Stripe simulates at a higher level and uses string error codes. Braintree also simulates chargebacks when specific cards settle, which Stripe does not. If you're building chargeback handling or dispute workflows, Braintree's sandbox is more comprehensive for that use case.

Frequently Asked Questions

How do Braintree's decline codes differ from Stripe's?: Braintree uses numeric processor response codes (2000 = Do Not Honor, 2001 = Insufficient Funds, 2053 = Card Reported Lost or Stolen). Stripe uses string codes like 'insufficient_funds' and 'stolen_card'. Both represent the same underlying scenarios but with different API response formats.
Can I test Braintree with the same cards as PayPal?: Some overlap exists (4111 1111 1111 1111 works in both) but Braintree has its own set of scenario-triggering cards in the 4000 1111 1111 XXXX range. Use the Braintree-specific cards for precise processor response code testing.
How do I test fraud in Braintree?: 4111 1111 1111 1137 triggers a gateway_rejected:fraud response. 4111 1111 1111 1152 creates a simulated chargeback when the transaction settles. These let you test your dispute-handling workflow without real fraud.