
Operations
Part of Failed payment recovery in the UK: card vs Bacs
Failed payment recovery in the UK: card vs Bacs
Failed payment recovery in the UK: how card authorisation and Bacs Direct Debit fail on different clocks, and how a dunning sequence serves both.
What to take away
- Failed payment recovery is a sequenceretry, notify, give one clear way to update the payment method, then retry again.
- Card payments and Bacs Direct Debit fail on different clocks, so a single dunning schedule will not serve both.
- Scheme rules limit repeat attempts on the same card transaction, which is why a fresh authorisation beats a blind repeat.
- Cancellation law and data protection rules set the boundary for how hard you can chase.
Involuntary churn is a process failure
Involuntary churn is the revenue you lose when a payment fails for a reason the customer did not choose. Expired cards, reissued card numbers, a bank switch and a thin balance on collection day all land in the same bucket. In reporting it looks like churn. In practice the customer often still wants the product.
Subscription billing engines treat a failure as an invoice event rather than a customer decision. Stripe's How subscriptions work documentation sets out how invoices, payment attempts and retries sit inside the subscription lifecycle, which is the machinery you are configuring.
Two failure paths, two clocks
Card recovery is about authorisation. A re-presentment of the same transaction is constrained by scheme rules and issuer behaviour, so the reliable route is a fresh attempt with the customer present or a new card on file. Fixed-amount recurring payments can sit outside strong customer authentication; a variable amount usually needs the customer to authenticate again.
The card side has two layers of rules. The card schemes, Visa and Mastercard, each set their own rules on repeat attempts, and the issuing bank decides whether to approve each one. Authentication is regulated separately: the FCA explains that the strong customer authentication rules are set in the Payment Services Regulations 2017 (PSRs) and the related technical standards. Check your payment provider's retry settings against both before you add attempts.
Card vs Bacs recovery
Card subscription
- Retry mechanism
- New authorisation per attempt
- Repeat limits
- Scheme rules and issuer
- Customer action
- Update card or authenticate
- Typical window
- 7 to 14 days
- Main risk
- Expired or reissued card
Bacs Direct Debit
- Retry mechanism
- Fresh collection after return
- Repeat limits
- Mandate and Bacs rules
- Customer action
- Fix bank details or mandate
- Typical window
- A few working days
- Main risk
- Indemnity claim
Direct Debit recovery runs on the Bacs cycle. You lodge a collection, it can return unpaid through the ARUDD process, and then you collect again under the notice terms in your mandate. You cannot take the money the next morning.
The Direct Debit side has one scheme owner: Bacs Payment Schemes Limited is the organisation with responsibility for the Direct Debit scheme, and its rules sit behind the unpaid-return and re-collection steps. Two consumer protections shape recovery. Under the Direct Debit Guarantee, a payer is entitled to a full and immediate refund in the event of an error in the payment of a Direct Debit, so a re-collection taken on the wrong date or for the wrong amount can be reversed. And a Direct Debit Instruction that has not been used to collect funds for over 13 months is automatically cancelled by the customer's bank, so a long-paused subscriber may need a new mandate rather than a retry.
Card subscription
- Retry mechanism
- New authorisation request per attempt
- Repeat limits
- Set by scheme rules and the issuer
- Customer action
- Update the card or authenticate
- Typical window
- Attempts spread across 7 to 14 days
- Main risk
- Expired or reissued card
Bacs Direct Debit
- Retry mechanism
- Fresh collection after an unpaid return
- Repeat limits
- Set by your mandate and Bacs rules
- Customer action
- Fix bank details or replace the mandate
- Typical window
- Unpaid items report a few working days after collection
- Main risk
- Indemnity claim under the Direct Debit Guarantee
Build the dunning sequence
A workable sequence runs in this order: retry the payment; tell the customer it failed; give one clear way to update the payment method; retry once the details are updated; and pause the costly parts of the service while keeping that update path open.
Dunning sequence
- Record why the payment failed
- Send first email within an hour
- Pause costly benefits, keep account open
- Retry day three and day seven
- Escalate on day ten, then suspend
Sequence matters more than clever copy. Pairing the retry schedule with subscription lifecycle email automation keeps the reminders consistent whether the failure came from a card or a bank.
Contact rules, consent and cancellation
Chasing a failed payment means contacting someone who still holds the service. That normally rests on legitimate interests under UK data protection law, and the ICO's UK GDPR guidance expects you to document why the contact is expected rather than assume consent.
Cancellation is a separate right. The Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, on legislation.gov.uk, give consumers in England, Wales and Scotland a 14-day cooling-off period on most distance contracts and ban pre-ticked paid extras at checkout. Northern Ireland has equivalent rules. A failed payment is not a cancellation.
Measure recovery, not just failures
Two numbers matter: the share of failed payments recovered within 30 days, and the median days to recovery. A high recovery rate that takes three weeks still costs you a month of service.
Segment by failure reason before you change anything. A card expiry wave and a benefits-driven cancellation look similar in a headline rate but need opposite responses; the same discipline sits behind the methods in how to reduce subscription churn across a base.
Common questions
How many times can I retry a failed card payment in the UK?
Issuers and card scheme rules set limits on repeat authorisations, and a string of identical attempts usually performs worse than a fresh payment link. Three attempts spread across 7 to 14 days is a common starting point.
How soon can a failed Direct Debit be collected again?
The unpaid item comes back through the ARUDD cycle, often within a few working days, and the next collection must respect the notice period in your mandate. Read the return reason first: a cancelled mandate and an empty account need different fixes.
Should a failed payment cancel the subscription?
No. A failed payment is not a cancellation request, and cancelling automatically can break your own terms and the customer's expectations. Pause the costly parts, chase the payment and keep the update path open.



