insufficient_fundsSafe to retryStripe decline code: Insufficient funds
The account lacked the balance to cover the charge.
Recovery outlook
Safe to retry. A soft decline. The charge can succeed on a later attempt. The win is retry timing, not another immediate hit.
What it means
The card is valid, but the account behind it didn't have enough available balance or credit to cover the amount at the moment Stripe attempted the charge.
Why it happens
Balances move constantly. A subscription renewal that lands the day before payday, or right after a large purchase, hits an account that will be funded again within days.
Can you retry it?
This is the most recoverable decline there is. Don't retry immediately. Retry on a schedule that lines up with when money is likely to land (early morning, and around common payday cycles). A smart retry beats a fixed 24-hour retry by a wide margin.
Recovery playbook
- 1Wait, don't hammer: an immediate retry hits the same empty account.
- 2Retry in the early morning and around the 1st/15th, when deposits clear.
- 3After 2–3 failed attempts, start a dunning email so the customer can top up or switch cards.
- 4Cap attempts so you don't rack up issuer retry penalties.
How Reecova handles insufficient_funds
Reecova classifies insufficient_funds as a soft decline and schedules retries with timing tuned to when the charge is likely to clear, instead of a blind fixed-interval retry that hits the same wall. It runs across your whole Stripe account automatically, and shows the dollars each code is costing you.