Direct debit
What is direct debit?
Direct debit is a payment method where a payer authorizes a merchant to take money directly from their bank account on agreed dates. The permission is recorded as a mandate, and each collection is initiated by the merchant rather than by the payer, which makes direct debit a .
An amount marked as "debited" on a bank statement is money that has left the account. Direct debit is the arrangement that makes those withdrawals automatic and repeatable: once the mandate is in place, the payer doesn't approve each individual collection. That's why it's the standard rail for utility bills, insurance premiums, loan instalments, and for subscription services.
Key facts
- Also known as: automatic bank debit. Scheme names differ by region: Direct Debit in the euro area, debit in the US, Direct Debit in the UK.
- Direction: pull, not push. The merchant's bank requests the funds and the payer's bank releases them.
- Authorization: one mandate, signed once, valid until the payer cancels it.
- Rails: bank-to-bank clearing with no card network in the flow, so no card number, expiry date, or CVV is involved.
- Common uses: subscriptions, utility and telecom bills, insurance premiums, instalment credit, B2B invoices.
- Refund rights (SEPA Core, euro area): a payer can request a refund for any collection within eight weeks of the debit date with no reason given, and within 13 months if no valid mandate existed.
How it works
Four parties take part in every collection:
- Payer: the account holder who signs the mandate.
- Payer's bank: holds the account, checks the mandate, and releases the funds.
- Originator: the merchant collecting the money, called the creditor under SEPA and the service user under Bacs. Each originator is registered with an identifier, a Creditor Identifier in SEPA and a Service User Number (SUN) in Bacs, which appears on mandates and notices.
- Originator's bank or : submits collection files to the scheme and credits the merchant.
- Mandate setup. The payer signs a mandate naming the merchant, the account to be debited, and whether collections are one-off or recurring. Each mandate carries a unique reference that identifies it in later collections.
- Pre-notification. The merchant tells the payer the amount and the date before submitting the collection. Notice periods are set by the scheme rulebook.
- Collection request. The merchant submits the instruction through its bank or payment service provider, which routes it to the payer's bank for the due date.
- Debit and settlement. The payer's bank checks the mandate and the available balance, debits the account, and the money reaches the merchant at .
- Return window. If the account is short of funds, the mandate is invalid, or the payer claims the debit back, the payer's bank returns the collection and the amount is taken back out of the merchant's balance. A collection sent back this way is a returned direct debit.
When a direct debit leaves the account
Timing is set by each scheme, so the same monthly bill moves on a different schedule in each region:
- Bacs (UK): collections run on a three-working-day cycle. The file is submitted on day one, processed on day two, and the payer's account is debited on day three. Under the , payers get advance notice of 10 working days before the first collection or any change to the amount or date, unless they agree otherwise.
- SEPA Core (euro area): the pre-notification reaches the payer at least 14 calendar days before collection unless creditor and payer agree a shorter period. Bank cut-offs for submitting the file vary by bank and by whether it's a first or repeat collection.
- ACH (US): debits settle on the same business day or later, depending on the processing option the originator chooses.
Direct debit vs other recurring payment methods
Repeating payments differ in who starts each payment and who controls the amount.
| Method | Who starts each payment | Amount | Payer's authorization |
| Direct debit | Merchant, through bank clearing | Can change, with pre-notification | One mandate |
| Card recurring payment | Merchant, through the card network | Can change | Card stored at signup |
| Standing order | Payer's bank | Fixed by the payer | Payer sets it up and edits it |
| (UK) | Merchant, through open banking | Varies within payer-set limits | One consent with limits |
Why it matters
- Collections aren't tied to a card, so an expired or reissued card can't break a renewal. Recovery work shifts from card-update prompts to on returned collections.
- Scheme fees are typically fixed per collection rather than a share of the amount, so collecting a large invoice doesn't cost proportionally more than a small one.
- In markets where paying from a bank account is the norm, direct debit reaches payers who hold no credit card at all.
- Due dates are known in advance, so expected inflows can be matched against bank statements during .
Common issues
- Insufficient funds. A frequent return reason. The collection is reversed after the debit attempt rather than declined at the moment of submission.
- Invalid or lapsed mandate. A closed account, a mistyped , or a mandate left unused long enough to expire under scheme rules causes the payer's bank to reject the request.
- Delayed failure signal. Returns arrive days after the due date, so a failed collection surfaces later than a card decline and revenue recognition lags behind the billing date.
- Refund and return claims. Payers keep refund rights well past the collection date, and in the US returns fall into their own categories, covered under . In the UK, the Direct Debit Guarantee lets a payer claim an immediate refund from their own bank for a collection taken in error. A issued by the merchant and a scheme-level return are settled through different processes.
- Checkout friction. Mandate capture adds fields and a bank verification step that a card form doesn't require.
