Decline Code Intelligence
Not all payment failures are created equal. "Insufficient funds" needs a retry. "Card stolen" needs a different card. Rezoki knows the difference — and acts accordingly.
Get StartedRezoki's decline code intelligence engine maps every Stripe decline code and raw issuer response to an optimized recovery strategy. Instead of treating all failures the same, each decline type triggers a tailored response: smart retry timing for soft declines, immediate email outreach for hard declines, customer education for fraud-related declines, and graceful handling of terminal declines. The system continuously learns from recovery outcomes to refine its strategy mapping.
The Problem
Stripe returns over 50 distinct decline codes, and raw issuer responses add even more granularity. Most SaaS companies treat them all the same — retry a few times, send a generic email. But a "card_declined" code for insufficient funds has a completely different optimal recovery path than "card_declined" for a stolen card. Treating them identically wastes retry attempts on unrecoverable declines and misses optimal timing for recoverable ones.
How It Works
Decline Code Capture
When a payment fails, Rezoki captures the Stripe decline code, raw issuer response, and transaction metadata for comprehensive analysis.
Code Classification
The decline is classified into categories: soft decline (retryable), hard decline (needs customer action), fraud-related (needs education), or terminal (unrecoverable). Sub-classifications drive specific actions.
Strategy Assignment
Each classification maps to a specific recovery strategy: retry timing, email template type, voice call trigger, or combination. High-confidence recoverable declines get aggressive retries; low-confidence ones get immediate outreach.
Continuous Learning
Recovery outcomes feed back into the intelligence engine. If a particular decline code is recovering better with a different approach, the system adapts automatically.
Key Benefits
Right Action for Every Decline
Stop wasting retries on unretryable declines and stop sending generic emails when a simple retry would work. Each decline gets precisely the right response.
Higher Overall Recovery Rate
By optimizing the response per decline type, overall recovery rates increase 20-30% compared to one-size-fits-all approaches.
Reduced Issuer Blocking Risk
Retrying terminal declines (stolen card, closed account) risks getting your merchant ID flagged. Decline intelligence prevents these harmful retries.
Transparent Recovery Insights
See exactly why payments are failing, which decline codes are most common, and how each type is being recovered. Data-driven visibility into your payment health.
Real-World Use Cases
Scenario
A payment fails with "insufficient_funds"
Outcome
Decline intelligence schedules a retry for the subscriber's likely payday (based on past payment patterns) and holds off on sending an email. The retry succeeds 3 days later without the customer ever knowing.
Scenario
A payment fails with "fraudulent"
Outcome
The system recognizes this as a false-positive fraud flag. It sends the customer an email explaining their bank may have blocked the charge and provides steps to whitelist the merchant.
Scenario
A payment fails with "expired_card"
Outcome
No retry is attempted (retrying an expired card is futile). Instead, an immediate pre-dunning-style email is sent with a card update link, and the customer is flagged for card updater service check.
50+
Decline codes mapped
+28%
Recovery rate improvement
40%
Unnecessary retries prevented
Related Features
Frequently Asked Questions
How many decline codes does Rezoki support?+
Can I customize the recovery strategy for specific decline codes?+
How does the learning system work?+
Does Rezoki distinguish between soft and hard declines?+
Can I see which decline codes are most common for my business?+
Try Decline Code Intelligence Today
Set up Rezoki in 5 minutes and let AI-powered recovery start saving your revenue automatically.
Start Free Trial