Resources

Bank Debit Failures: ACH & SEPA Returns Decoded

Card failures announce themselves: an answer comes back in seconds, with a reason that tells you what to do next. Bank debit failures play by different rules.

An ACH debit or a SEPA direct debit can look accepted, sit in settlement for days, and then come back as a return — sometimes after you have already shipped the product, extended the service, or marked the subscription paid. Operators who run bank debit with a card mindset misread every part of that: they retry too fast, celebrate too early, and re-debit accounts they should have stopped touching. This guide decodes the return-reason families at concept level and lays out the slower, stricter discipline bank debit demands.

How bank debit differs from a card charge

With cards, authorisation happens before settlement: the issuer approves or declines in real time based on the account state at that moment. With bank debit, the merchant submits an instruction to pull funds under a mandate the customer previously authorised, and the banking system processes it over days. There is no live issuer interview at the moment of submission. The debit can be returned afterwards if the account cannot or will not honour it.

Three practical consequences follow:

• Success is provisional for longer. A submitted debit is a claim in progress, not a settled fact, until the return window has passed and the funds have cleared through the scheme.
• Failure news arrives late and batched. Returns surface in files and reports after the fact, not as instant responses attached to a checkout session.
• The reason language is different. Returns speak about accounts and mandates — closed, invalid, revoked, unfunded — rather than about card credentials and issuer risk decisions.

ACH is the bank debit system used in the United States, operating under its network rules for debit entries against checking and savings accounts. SEPA direct debit serves euro-denominated payments across the Single Euro Payments Area, built around a signed mandate from the debtor to the creditor. The schemes differ in forms, timelines, and dispute mechanics, but for subscription operators the operational shape is shared: mandate first, slow settlement, returns afterwards. The mix context for offering bank debit at all is covered in our guide to the payment method mix for subscriptions.

The return-reason families, decoded

Individual schemes publish long lists of specific return and refusal codes. Operators do not need to memorise the catalogue; they need to recognise the family a return belongs to, because the family decides the correct response. Keep the full mapping for your scheme close at hand — our decline code cheat sheet is the style of one-page reference worth adapting for your return codes too.

Return family	What it means	Correct response
Insufficient funds	The account was open and the mandate valid, but the balance could not cover the debit at processing time	Timed re-debit may be appropriate within scheme rules, coordinated with a customer notice
Account closed	The bank account no longer exists	Never re-debit. Request a new payment method from the customer
Invalid or unrecognisable account details	The account number or identifier does not resolve to a real, debitable account	Never re-debit blindly. Ask the customer to re-enter and verify their details
Authorisation revoked or stopped	The customer has withdrawn the mandate or instructed their bank to stop these debits	Stop immediately. Any new debit needs a fresh mandate and a genuine conversation
No valid mandate on file	The debit was submitted without a mandate the scheme accepts, or the mandate reference cannot be evidenced	Stop and repair the mandate process. This is an operations and compliance failure, not a customer failure
Debtor or bank refusal and disputes	The customer or their bank contests the debit under the scheme consumer protections	Pause billing, gather the mandate evidence, and handle the dispute through the scheme process

Read the table as two groups. The first family is a timing problem and is the only one where another attempt, carefully governed, makes sense. Every other family is a stop signal: the account, the details, or the permission itself is gone, and re-debiting converts a billing problem into a trust and compliance problem.

Insufficient funds on bank debit is not the same as on cards

Funding failures dominate subscription payments generally — across 5.4M failed payments, insufficient funds is the largest decline category at 40.6%, according to Churnkey's published analysis of Stripe data. On bank debit, though, the operator sees less and knows it later. A card decline tells you the moment was wrong. An ACH or SEPA return tells you days afterwards that the moment was wrong, by which time the balance picture has changed entirely.

That delay changes the retry logic. A re-debit should be scheduled from when you learn of the return, not from the original attempt date, and timed for when funds are plausibly present, such as after common pay cycles. Scheme rules govern whether and how a returned debit may be re-presented, so the schedule lives inside those rules. Customers should also hear from you before a re-debit, so it does not arrive as a surprise on a bank statement.

Slower settlement changes access and fulfilment decisions

Because bank debit truth arrives late, operators must decide how much trust to extend during the settlement window. Granting access on submission is common for digital subscriptions, but a returned debit then means clawing back service. Holding access until clearance is safer financially and worse commercially, especially at signup.

Most operators land on a tiered approach:

• At signup: grant access on submission, since the attended mandate setup is a strong good-faith signal, and monitor first-debit returns as a distinct metric.
• On renewal: keep service running through the normal settlement window, and treat the return, when it arrives, as the start of the recovery clock rather than a retroactive offence.
• After a return: apply your delinquency policy consistently — notice, grace period, then restriction — measured from confirmed failure, not from the original debit date.
• For physical goods: align despatch timing with settlement reality for high-value orders, so a return does not leave you chasing both payment and product.

Whatever you choose, define it before you need it. Our explainer on payment failure rate helps separate bank debit returns from card declines in your reporting, so a slow-settling method does not distort your headline numbers.

Re-debit discipline: the rules that keep you safe

1. Only funding failures are re-debit candidates, ever. Closed accounts, revoked mandates, invalid details, and disputes are stops, not retries. This is the bank debit equivalent of never retrying a hard card decline.
2. Respect scheme limits on re-presentment. Bank debit schemes restrict how a returned item may be handled. Build those limits into your billing configuration and your recovery tooling, not into a wiki page nobody reads at 2 a.m.
3. Space attempts by pay reality, not impatience. Back-to-back re-debits against an account that was empty yesterday mostly manufacture repeat returns, bank fees on the customer side, and anger. Fewer, better-timed attempts preserve both the account relationship and the mandate.
4. Notify before you pull again. A customer who knows a re-debit is coming can move money and save the payment. A customer surprised by one calls their bank, and bank calls are how mandates get revoked.
5. Know when to move the customer to another method. After repeated funding returns, the right move is often a card on file or another method entirely, offered plainly as a way to keep the subscription running. Some accounts will never suit pull payments on your billing dates.

Protecting the mandate

The mandate is the asset underneath every bank debit subscription. It is the customer permission your debits stand on, and it is fragile in a specific way: customers who feel ambushed by amounts, timing, or unrecognisable descriptors revoke mandates and dispute debits, and their banks support them under scheme consumer protections. Clear advance notice of amount changes, recognisable statement descriptors, debits that land on the promised dates, and accessible cancellation all protect the mandate far more cheaply than any recovery flow protects revenue after it is revoked.

Where Swipe Again fits

Swipe Again runs failed-payment recovery across nine platforms — Stripe, Recharge, Seal Subscriptions, Skio, Loop Subscriptions, Chargebee, Recurly, Braintree, and Paddle — for $179/mo flat ($1,799/yr), with no percentage of recovered revenue and no MRR tiers, a 14-day trial with a card upfront, and a 90-day backfill on connect. Its model is decline-aware by design: up to 6 smart retry attempts over ~16 days where timing can help, hard failures never retried, branded dunning emails and card-update pages, SMS in the sequence, and cancel deflection with Discount, Pause, and Service offers. Applied to bank debit, the same discipline matters more, not less: route by failure family, stop on stop signals, time reattempts to funding reality, and keep the customer informed in your brand voice. Our guarantee stands in its one form: "Recover $179 in 30 days, guaranteed — or Swipe Again is free the next 30 days".

The bottom line

Bank debit fails slowly, speaks a different language from cards, and punishes impatience. Learn the return families, treat only insufficient funds as a timing problem, let settlement windows set your access decisions, and guard the mandate like the revenue asset it is. Run with that discipline and bank debit delivers its real advantage — a durable credential that can carry a subscription for years — without the returns chaos that gives the method a bad name among operators who imported a card playbook.

Frequently asked questions

What is an ACH return?

An ACH return is a debit that the receiving bank sends back unpaid after submission, with a reason attached. Returns cover situations such as insufficient funds, a closed account, invalid account details, or the customer revoking authorisation. Unlike a card decline, a return can arrive days after the debit was submitted and appeared to be processing normally.

How is a SEPA direct debit failure different?

The shape is similar — mandate-based pulling, delayed settlement, and returns or refusals after submission — but SEPA operates under its own scheme rules, mandate requirements, and consumer refund protections for euro payments. The operational lesson transfers: classify the return by family, stop on mandate and account problems, and time any re-debit carefully.

Can I re-debit after an insufficient funds return?

Generally, a returned debit for insufficient funds is the one family where a further attempt can make sense, but only within your scheme rules for re-presentment, timed from when you learned of the return and aligned to when funds are likely to be present. Notify the customer, and do not repeat the attempt on a rapid fixed cadence.

Why did a debit show as paid and then reverse?

Because bank debit settlement is provisional until the return window passes. The debit moves through processing before the account-holding bank confirms it can be honoured, so an account problem may only surface afterwards as a return. Building access and fulfilment policies around confirmed failure dates, rather than submission dates, prevents most of the confusion this causes.

What should I do when a customer revokes their mandate?

Stop debiting that account immediately. A revoked mandate means the permission your debits depend on has been withdrawn, and further attempts create disputes and compliance exposure. Contact the customer to understand what happened, and only resume bank debit under a fresh mandate if they genuinely want to continue that way.