What happened
Adyen's latest billing updates focus on three areas: intelligent payment routing to reduce decline rates at the processor level, failure-reason-aware retry schedules to avoid unnecessary retries that create card network compliance issues, and Account Updater services that automatically refresh card-on-file data before charges run.
The routing improvements are designed for high-volume subscription businesses where payment traffic spikes, like renewals concentrated on the 1st and 15th of the month, can degrade approval rates as issuer systems queue up. Smart routing redistributes those transactions to optimize approval at the network level.
On retries, Adyen's data shows the strategy needs to match the failure reason:
Technical failures
Processor errors and network timeouts. Retry immediately, with up to 70% success rate.
Insufficient funds
Align retries with pay cycles, which in the US peak at the start and middle of the month.
Do not honor
Retry both short and long term, with a 5-7% success rate.
Expired or lost cards
Skip retries entirely. Deploy Account Updater instead.
Account Updater itself, available in the US, UK, Canada, Ireland, Italy, and Greece, can reduce involuntary churn by 2-3% by catching expired cards before they hit the billing cycle.
Why it matters
Adyen's updates are genuinely useful infrastructure improvements, and they highlight a broader trend: payment processors are investing heavily in the first layer of subscription failure prevention. Better routing, smarter retries, and card updater services are all designed to prevent failures before they happen.
But the 10% failure rate exists even with Adyen-level infrastructure in place. The 8-9% recovery window that Adyen's own documentation cites exists after their retry logic runs, which means the recovery opportunity is not at the processor level. It is in what happens after a charge fails and before the customer churns.
The gap every processor leaves
Stripe, Adyen, Braintree, all of them handle the retry mechanics. The customer communication layer (why the charge failed, how to update payment info, when the retry will run) is left to the business. That is where involuntary churn happens.
What this means for subscription businesses
Adyen's retry recommendations are worth implementing directly if you are on Adyen. But the more important takeaway is structural: even a best-in-class processor leaves a meaningful recovery window that requires outreach to the customer, not just mechanical retries.
Segment recovery by decline code, not just days since failure
Adyen's own data shows insufficient funds and do_not_honor need completely different timing. Your dunning emails should reflect the same segmentation.
Do not assume retry logic is enough
A 70% technical-failure retry rate is high, but that still leaves 30% unresolved, and the other categories are far lower. Email sequences run in parallel with retries, not instead of them.
Time recovery emails around pay cycles
In the US, the start and middle of the month see higher payment success. An email that lands mid-month has a better shot than one that lands in the last week.
Account Updater does not replace communication
The 2-3% churn reduction is real, but coverage is not 100%. Customers whose cards slip through still need a clear card-update prompt.
Approximately 10% of transactions fail across industries, but 8-9% of those failures can be recovered using appropriate techniques and tools.
The bottom line
Adyen's billing updates make the processor layer smarter. But the 10% failure rate that persists even with smart routing and optimized retries is not a processor problem, it is a customer communication problem. The businesses that recover the most involuntary churn run both layers: good processor infrastructure and automated recovery sequences that follow up on every failure the processor cannot resolve mechanically. One without the other leaves money on the table.
Sources