When a subscription charge fails, a smart retry system decides when to try again, how many times, and through which path. A naive system retries at 1, 3, and 7 days. A smart system looks at the decline code, the card brand, the merchant category, and the historical success rate of retry timing for that specific scenario - then schedules the next attempt at the moment most likely to succeed.
What "smart" means in practice
- Decline-code aware - "insufficient funds" retries align with payday patterns; "do not honor" retries skip immediate retry because the card is flagged; "expired card" triggers update-card outreach instead of retrying.
- Time-aware - retrying at 10 AM on a Tuesday outperforms retrying at 3 AM on a Sunday. Banks process differently across windows.
- Card-network aware - Visa, Mastercard, and Amex have different decline-and-retry patterns; the system adapts.
- Card-updater integrated - when a card has expired or been replaced, the system pulls the updated card number from the network before retrying, rather than retrying with the dead card.
Operational structure
- Charge fails - system reads decline code, classifies the failure (recoverable vs. terminal).
- If recoverable - schedule retry based on decline-code-specific success curve. Typically 3–4 retry attempts over 7–14 days.
- If terminal (lost card, fraud block) - skip retries, send card-update email to the customer.
- In parallel - send payment reminder emails and trigger card-updater calls.
- After final retry fails - move subscription to a dunning state with a paused billing flag, do not auto-cancel immediately.
Expected lift
Compared to a basic 1/3/7-day fixed retry schedule, well-tuned smart retries typically recover 15–40% more failed payments. For a store with 5% involuntary churn that translates to 0.75–2 points of total churn recovered - a measurable retention lift with no acquisition spend. See payment retries and dunning management.