Adyen Auto Rescue and subscription payment recovery: a measurement checklist

Adyen Auto Rescue is designed to retry eligible shopper-not-present refusals, including subscription renewals. The operational question is not merely whether Auto Rescue is enabled; it is whether the rescue window, retry outcomes, shopper communications, and final payment states are visible enough to evaluate.

Use the rescue process as an evidence trail

Adyen documents that Auto Rescue uses webhooks to report retry results, future scheduled retries, the end of the rescue process, and—when enabled—a payment link after an unsuccessful rescue. Those events are the foundation for distinguishing a payment still being rescued from one that needs customer action or a different decision. Adyen Auto Rescue

Measure four states across a defined period

• First recurring-payment refusals, grouped by the provider evidence available.
• Payments recovered during the rescue window.
• Payments still in a scheduled rescue path, kept distinct from final exposure.
• Payments that reached the end of rescue or require a shopper payment-update journey.

Do not force every refusal through the same journey

Adyen notes that some failures, such as insufficient funds, can succeed later while permanent scenarios should not be treated as candidates for ordinary rescue. The customer-facing path and operational follow-up should reflect that distinction rather than treating every refusal as a timing problem.