Failed payment recovery: win back what others decline.
Payment recovery is the set of retries a platform runs after a card is declined: classifying the decline, re-presenting it through a different acquirer or a network token, and timing the retry to when funds are likely to be there.
Most processors return a decline and move on. Paybyrd treats it as the start of the flow: classify the reason, repair what can be repaired, and re-present through a different acquirer before the customer notices.
- recovered this month
- €127,482
- cohort blended vs prior provider
- +3.12pp
- same-session retry, invisible to the shopper
- <1s
One decline,
followed all the way to revenue.
A single transaction, from the moment the issuer says no to the moment the money lands. Every step is a decision the platform makes without asking you.
The issuer says no
An authorisation comes back declined with reason code 05 — do not honour. It is the most common decline in card payments, and it almost never means what merchants assume it means.
Illustrative simulation. The transaction is generated for this page; the decline classification, retry scheduling and acquirer sequencing mirror production behaviour.
You already paid
for the customer who just got declined.
Every declined transaction is a customer who found you, chose you, and reached for their card. The acquisition cost is spent. The inventory is reserved. The only thing missing is an authorisation — and most processors treat that as somebody else's problem.
- 01
A decline is not a verdict on the customer
The most common decline code in card payments is 05 — do not honour. It is a refusal with no stated reason. It does not mean the card is bad, the customer is broke, or the purchase was fraudulent; it means one issuer, at one moment, through one acquirer, said no. Send the same card through a different acquirer — ideally one holding a licence in the cardholder's own market — and the answer frequently changes. Nothing about the customer changed. Only the route did.
- 02
The economics are unlike anything else you can buy
Improving conversion normally means spending more: better creative, more traffic, deeper discounts. Recovery is the opposite. The customer is already at the payment step with intent proven and cost sunk. A point of approval rate on €100M of volume is €1M, and it arrives without a single additional visitor. There is no other line item in a payments contract where the return is this direct.
- 03
Most processors are structurally unable to fix it
A single-acquirer processor can only retry against the acquirer that just declined — asking the same question twice and expecting a different answer. That is why their recovery rates are low, and why the topic rarely appears in their reporting. It is not negligence; it is architecture. Multi-acquirer routing is the prerequisite, and it has to be built before the first decline, not after.
- 04
On subscriptions, a decline is churn you never chose
For recurring revenue the cost compounds. A card expires or is reissued, a renewal fails silently, and a customer who never decided to leave is gone. This is involuntary churn, and it is routinely larger than the voluntary kind. Network tokens keep a stored credential valid through reissue, and funds-related declines get retried against payday behaviour rather than a fixed timer — so the subscription survives without anyone being asked to re-enter a card.
The revenue was always there. It just needed a different route.
Recovery is not a feature bolted onto the payment flow. It is what the payment flow should have been doing from the beginning — and on Paybyrd it runs on every transaction you already send us, with nothing to integrate and no retry logic to maintain.
Four reasons a card says no.
Three of them are recoverable.
Recovery is not retrying blindly — that burns issuer trust and can breach scheme rules. Every decline is classified first, and only the recoverable ones are re-presented.
- Soft decline Recoverable
Insufficient funds, temporarily
Re-presented on a schedule tuned to payday cycles and issuer behaviour rather than a fixed timer. The customer is never asked again.
- Issuer routing Recoverable
The acquirer was the problem, not the card
The same card is re-presented through a different acquirer — often one with a local licence in the cardholder's market, where issuer trust is higher.
- Stale credential Recoverable
Card expired or was reissued
Network tokens follow the cardholder through reissue, so a stored credential keeps working after the plastic changes.
- Hard decline Not retried
Stolen, blocked, or refused outright
Never retried. Re-presenting a hard decline damages your issuer standing and breaches scheme retry rules — so we stop.
Approval rate is not a metric.
It is revenue.
One percentage point of approval rate on €100M of volume is €1M. Recovery is the cheapest percentage point you will ever buy, because the customer already decided to pay.
- Approval lift
- +3.12pp
- Recovery · 30d
- €260k
cohort blended vs prior provider
at €100M annual volume
The customer already wanted to pay. Recovery is the difference between capturing that and writing it off.
One thousand attempts,
and where they actually end up.
The gap between a 92% processor and a 96% one is not luck. It is what happens in the four seconds after the first decline.
- 1,000 Attempts
- 920 First-try approved
- 80 Declined
- 80 Retry · alternate acquirer
- 47 Recovered
Recovery, without the hand-waving.
Is retrying a declined card allowed?
Yes, within limits the card schemes set — and those limits are the point. Visa and Mastercard cap retry attempts and require that hard declines (stolen, blocked, do-not-honour with a permanent reason code) are never re-presented. Paybyrd classifies every decline against those rules before deciding, so recovery never puts your issuer standing or your scheme compliance at risk. Retrying blindly is the practice that gets merchants fined; this is the opposite of it.
Will my customer be charged twice?
No. A retry only ever happens on an attempt that was declined, meaning no funds were captured. The authorisation is re-presented, not duplicated, and idempotency keys on our side prevent a double capture even if your system sends the same request twice. If a retry succeeds, the customer sees exactly one charge.
Does the customer know a retry happened?
Usually not, and that is the design goal. Same-session retries through an alternate acquirer resolve in under a second, so the shopper sees a normal approval. Scheduled retries for soft declines happen server-side against a stored credential — the customer is not asked to re-enter anything, and only hears from you if every attempt fails.
How is this different from my current processor's retries?
Most single-acquirer processors can only retry against the same acquirer that just declined, which is why their recovery rates are low — they are asking the same question twice. Paybyrd is multi-acquirer, so a retry can go to a different acquirer entirely, often one holding a local licence in the cardholder's market where issuer trust is materially higher. That routing decision is the recovery.
What happens to subscription and stored-card payments?
This is where recovery pays for itself fastest. Network tokenisation keeps a stored credential valid through card reissue and expiry, so recurring charges that would otherwise fail silently keep working. Combined with soft-decline scheduling tuned to payday cycles, involuntary churn on subscriptions drops without you writing a single line of retry logic.
Do I need to change my integration to get this?
No. Recovery runs inside the payment flow you already use — hosted checkout, embedded components or direct API. There is no separate product to integrate and no retry logic to maintain on your side. If you are already sending payments through Paybyrd, it is already running.
See what you are writing off.
Send us a month of declined transactions and we will show you what recovery would have returned — no integration, no commitment.