What message should I show for an insufficient funds decline?

Show a specific message like "Your card has insufficient funds. Please use a different payment method or contact your bank." This is more helpful than a generic "your payment was declined" and reduces support contacts.

Should I retry on insufficient funds?

No. Insufficient funds is a hard decline — the cardholder genuinely doesn't have the funds available. Retrying will always fail. Show the user a message directing them to use a different card or payment method.

Insufficient Funds Test Card Numbers

Test card numbers that trigger an insufficient funds decline response across Stripe, PayPal, Adyen, Braintree, Square, and Razorpay.

Last updated: April 2026

verifiedVerified against All Providers documentation — April 22, 2026

Official docsopen_in_new

Test card numbers that trigger an insufficient funds decline across all major payment providers. Use these to test how your checkout handles the most common real-world decline reason.

search

Showing 8 of 8 test cards

Card Number	Network	Scenario	Code	Notes
4000 0000 0000 9995TEST ONLY	Visa	Declined — insufficient fundsGlobal	insufficient_funds	[Stripe]
4111 1111 1111 1115TEST ONLY	Visa	Declined — insufficient fundsGlobal	INSUFFICIENT_FUNDS	[PayPal]
4000 0000 0000 9995TEST ONLY	Visa	Declined — insufficient fundsGlobal	Refused:InsufficientFunds	[Adyen]
4000 1111 1111 1123TEST ONLY	Visa	Declined — insufficient fundsGlobal	insufficient_funds	[Braintree] Processor response code: 2001.
4000 0000 0000 1042TEST ONLY	Visa	Declined — insufficient fundsGlobal	INSUFFICIENT_FUNDS	[Square]
4000 0000 0000 9995TEST ONLY	Visa	Declined — insufficient fundsIndia	BAD_REQUEST_ERROR	[Razorpay]
4000 0000 0000 9995TEST ONLY	Visa	Declined — insufficient fundsEU	insufficient_funds	[Mollie]
4444 2222 3333 4444TEST ONLY	Visa	Declined — insufficient fundsGlobal	51	[Worldpay]

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

What it does

Cross-provider insufficient funds cards

One card from each major provider that triggers insufficient_funds response.

Provider-specific error codes

Stripe returns insufficient_funds, Adyen returns Refused:InsufficientFunds, Braintree returns 2001. All shown side by side.

Real-world scenario

Insufficient funds is the most common real decline — test that your checkout handles it gracefully.

How to use Insufficient Funds Test Card Numbers

1
Pick the card for your provider
Select the insufficient funds card labeled with your payment provider.
2
Submit in checkout
Enter the card in your payment form. The provider returns insufficient_funds or equivalent.
3
Verify the user message
Your checkout should show "Your card has insufficient funds" or a similar helpful message — not a generic error.

Insufficient funds: most common real-world decline

Across payment providers, insufficient funds accounts for roughly 15-25% of all card declines in production. It's the single most common specific decline code. Testing that your checkout handles it specifically — not just generically — directly affects conversion rates. Users who see a generic "payment failed" message are more likely to abandon than users who see "your card has insufficient funds, please try another card."

Frequently Asked Questions

What message should I show for an insufficient funds decline?: Show a specific message like "Your card has insufficient funds. Please use a different payment method or contact your bank." This is more helpful than a generic "your payment was declined" and reduces support contacts.
Should I retry on insufficient funds?: No. Insufficient funds is a hard decline — the cardholder genuinely doesn't have the funds available. Retrying will always fail. Show the user a message directing them to use a different card or payment method.