Payment retry recovery
Track revenue recovered through intelligent retries and see how recoveries break down across retry attempts in the Payment Retry Recovery dashboard.
Monitor retained revenue through intelligent retry strategies, and track how optimized retry logic recovers payments that initially failed. Across Recurly's network, the majority of recovered transactions happen within the first several retry attempts, so this dashboard shows you exactly where your recoveries are coming from.
Filters
| Filter | Description |
| Date Range | The reporting period. Defaults to the past 30 days. |
| Payment Method | Filters by card or alternative payment type (Credit Card, Debit Card, PayPal, and more). |
| Gateway | Filters by payment gateway. |
Key metrics
Each metric is compared against the previous equivalent period, with the change shown as a percentage.
| Metric | Description |
| Recovered Transactions | The count of failed payments successfully processed again through the retry engine during the selected period. |
| Retry Attempts | The total number of payments retried in the period. |
| Revenue at Risk | The total dollar value of all invoices whose first payment failed during the period. |
| Payment Retry Recovered Revenue | Total revenue recovered through successful retries, including intelligent retries, Account Updater, payment method updates, and third parties that report recovery back to Recurly. |
| Recovery Rate | The percentage of at-risk revenue successfully recovered in the period. |
NoteFailures and recoveries are tracked as independent trends and aren't matched on a per-invoice basis. Recovery Rate reflects overall recovery health rather than a precise per-invoice cohort rate, so it won't always equal Recovered Revenue divided by Revenue at Risk.

Charts
Payment recovery over time
This chart shows recovered transactions across the selected date range, so you can spot spikes, dips, and trends in your recovery performance over time.

Success by retry attempt number
This chart shows how many transactions were recovered at each retry attempt number. Recoveries concentrate in the earliest attempts and taper off across later ones, showing you where your retry logic is doing the most work.

Updated 6 days ago
Did this page help you?