Stripe Bacs Direct Debit: pending states, failures and reconciliation

We build the collection side of a UK telecom billing platform, including Stripe card and Direct Debit payments, part payments, one charge covering several invoices, Bacs pending states and automatic reconciliation of payouts, refunds and disputes. The facts below come from Stripe’s Bacs documentation, read on 30 October 2026. Check it again when you build, since details change.

Submissions on a non-business day, or after the cut-off, move to the next business day. Stripe also exposes an estimated expected_debit_date on the charge, which is useful for customer-facing text as long as you describe it as an estimate. Notice the gap: the customer’s money may have left before your system knows the payment worked. If they tell you they’ve paid, they may be right.

A card payment goes from unpaid to paid in one request. Bacs doesn’t. Add a pending state to your receipt, and decide what it means for everything else. That is usually the bigger piece of work.

checkout.session.completed catches people out. It means the customer submitted the form, not that any money arrived. And while a payment is pending, make sure your dunning, your credit control and your “pay now” link all know about it. Otherwise you will chase a customer who has already paid, or take the money twice.

Stripe’s test accounts show the behaviour of the main failure codes. The platform we built for a UK client turns them into plain-language reasons for staff and customers, because “debit_not_authorized” means nothing to a credit controller.

The last two matter for planning. Stripe’s default limit is £10,000 per Bacs transaction. New users also have a weekly limit of £10,000, which rises as they process more. A B2B biller moving existing customers onto Direct Debit can hit this on its first run, so talk to Stripe well before then.

For retries, Stripe’s Direct Debit retries cover insufficient-funds failures, up to 2 times within 30 days of the original attempt, for Billing invoices. If you run your own invoicing and collection, you have to build the equivalent. A customer on a payment arrangement may need a hold; the platform we built for a UK client supports payment holds so that nothing goes out while one is in place.

Stripe warns that a bank may report failure after a payment was marked successful, in which case it appears as a dispute. Bacs disputes differ from card disputes in ways that affect your design:

• There is no set time limit for the customer to file, so a ledger entry from long ago can be reversed.
• You can’t submit evidence or appeal. The bank’s decision stands.
• Stripe deducts the amount and a fee from your balance when it creates the dispute.
• Disputes are for the full amount only. There are no partial disputes.

Refunds carry a trap. They are sent separately from the Bacs scheme, as a credit, within 180 days of the payment. Because a customer can still dispute afterwards, you could lose both the refund and the disputed amount. Stripe advises telling the customer you are refunding, so that they don’t also go to their bank, and refunding only once the payment has settled.

Use Checkout unless you have a strong reason not to. It collects bank details and the mandate, and Stripe handles the required notifications by default. Note that the Payment Element can’t create a Bacs SetupIntent, so saving details for later needs Checkout in setup mode. A custom mandate form needs Stripe’s approval, and must meet the collection requirements, including exact checkbox wording.

Customers see Stripe’s name on their bank statement by default, unless you enable Custom Branding, which Stripe lists at £50 per active month and which typically takes 10 working days to activate. Bacs also doesn’t support per-transaction statement descriptors, so customers won’t see your invoice number on their statement. Put the debit date and amount in your own communications, because that’s how people will recognise it.

On automatic payouts, wait for payout.reconciliation_completed, then list what the payout contains:

curl -G https://api.stripe.com/v1/balance_transactions \
  -u "<<YOUR_SECRET_KEY>>:" \
  -d payout=po_xxx \
  -d "expand[]=data.source"

Each balance transaction has a type, such as charge, refund or stripe_fee, and a source that you can match back to your receipt. The finance integration map shows how the result fits a clearing account.

Stripe’s test bank details use sort code 108800, with account numbers for each outcome. Use the versions with a three-minute delay, such as 90012345 for success and 92222227 for insufficient funds, since these behave most like a real debit. Then test what happens when a customer pays by card while a debit is pending, and when a dispute arrives for an invoice from a closed period. Those two cases find more bugs than the happy path.