Recurring Payments and Direct Debit for Small Business Skip to content
CentriWeb
Not sure where to start?

Tell us how the business runs. We'll tell you what we'd build first.

Book a call
For builders and tradesPreBuildMore homeowner enquiries, more trust, more jobs won. For sole tradersOwner CFOA financial operating system for owners who do the books.
Need something of your own?

We build custom software too.

Talk to us

Recurring payments and direct debit for a small business

Cards or bank direct debit, what to set up before the first charge, and a simple routine for the day a recurring payment fails.

Recurring payments let you collect an agreed amount from a customer on a schedule, without sending and chasing an invoice each time. A small business has two main ways to do it, a card saved on file or a direct debit from the customer’s bank account, and the two fail in different ways, so most of the work is in the set-up and in knowing what to do on the day a payment does not go through.

Cards and direct debit: how the two kinds of recurring payments differ

A card on file is quick to set up. It fails mostly because the card expired, was replaced after a loss, or hit its limit, and the customer often has no idea until you tell them.

A direct debit pulls money from the customer’s bank account under a standing authority they have signed. It is common for retainers, memberships, rent, and other amounts that repeat for months or years. The payment is not confirmed on the spot. Stripe’s documentation says an Australian debit can take up to 2 working days to report its final result, and a United States ACH debit up to 4 working days, so a debit that looks fine on Monday can still fail on Wednesday.

Neither is better in every case. Cards suit a customer who wants to start today and does not mind the card being on file. Bank debit suits larger or longer-running amounts where the customer would rather not think about a card expiring. Many businesses offer both and let the customer choose.

How direct debit for a small business differs by country

There is no single worldwide direct debit. Each country or region runs its own scheme, with its own paperwork, notice periods and protections for the payer. Before you offer it, check the rules for the country your customer’s bank is in, and check them with your bank or payment provider.

As at November 2026, Stripe’s retry documentation lists these automatic retry limits for payments that fail on insufficient funds. They apply to Stripe only, so check your own provider’s page for its figures.

Scheme Country or region Stripe retries
ACH Direct Debit United States Up to 2, within 40 days
BECS Direct Debit Australia Up to 4, within 30 days
BECS Direct Debit New Zealand 1, within 5 calendar days
Bacs Direct Debit United Kingdom Up to 2, within 30 days
Pre-authorised debit Canada 1, within 30 days
SEPA Direct Debit Euro area Up to 2, within 30 days

The protections for your customer differ too, and they affect you. In the United Kingdom, the Direct Debit Guarantee says the payer is told in advance of changes to the amount, date or frequency, can get a full refund from their bank if an error is made, and can cancel at any time through their bank. Stripe’s page on Australian BECS debits says a customer can dispute a payment through their bank for up to 7 years on a “no questions asked” basis. Its page on ACH debits says a United States customer can generally dispute a debit on a personal account for up to 60 calendar days.

The practical lesson is the same everywhere: a debit you cannot show the customer agreed to is a debit you may lose.

What to set up before the first payment

Do these once, before anyone is billed. They prevent most of the failures you would otherwise chase later.

  1. A written agreement the customer accepts. For bank debits this is a mandate, called a Direct Debit Request in Australia. Stripe’s pages say you must collect it before debiting and keep a record of when and how it was accepted. Use your provider’s standard wording rather than your own.
  2. A plain statement of the amount and the dates. Say what is charged, how often, and on which day. If the amount can vary, say how it is worked out.
  3. Notice before each debit, or before any change. Stripe’s ACH page says you must give at least 7 calendar days notice if you change the timing of recurring debits. For Australia, it says scheme guidelines recommend notifying at least 14 calendar days before a payment, though this is not mandatory. Check what applies to you.
  4. A name the customer will recognise on their statement. A debit labelled with a name they do not know is how disputes start.
  5. A page where the customer can update their details themselves. Stripe’s customer email settings can send failed-payment, renewal and expiring-card emails that link to such a page. Other providers offer similar settings.
  6. One named person who owns failed payments. Without an owner, nobody follows up.

If you take payments by invoice rather than by schedule, our guide on how tradies get paid faster covers the invoice side, and the comparison of Stripe and Square for Australian small businesses covers choosing a provider.

What to do when a recurring payment fails

A failed payment is usually not a lost customer. The card expired, the account was briefly short, or a new card was issued. The customer wants to keep the service and does not know you were not paid. Your job is to tell them quickly, make it easy to fix, and stop short of treating them like a debtor.

Work out first what kind of failure it is.

  • Insufficient funds. Often temporary. A retry a few days later, after typical pay days, can work. Stripe’s documentation describes automatic retries for this on bank debits, within the limits in the table.
  • Expired or replaced card. A retry will not help. The customer has to give you the new card.
  • A hard decline from the card issuer. Stripe’s page says it cannot retry these without a new payment method, and lists codes such as lost card and stolen card. Ask for a new card.
  • A cancelled mandate or closed account. Stripe’s pages say a cancelled authority invalidates future debits, so you need a new agreement before collecting again.

A failed-payment routine you can run from one page

This is an example schedule. Adjust the days to your billing cycle and to the retry limits of your provider.

When What happens
Day 0, the payment fails The customer gets an automatic email or text saying what failed, the amount, and a link to update their details.
Day 2 to 3 The system retries if the failure type allows it. If it fails again, a short personal message goes out from a named person.
Day 7 A phone call or a direct message. Ask whether something has changed on their side.
Day 14 A final written notice saying what happens next, such as pausing the service on a stated date.
After that Pause or cancel as you said you would, and record why.

Stripe’s documentation says its subscription settings let you choose what happens after the last retry: cancel the subscription, mark it unpaid, leave it overdue, or pause it. For many service businesses pausing is the kinder and more reversible choice. Whichever you pick, put it in the agreement so nobody is surprised.

A message that works for most customers:

Hi [Name], your payment of [amount] for [service] did not go through today. This often happens when a card has expired. You can update your details here: [link]. If anything has changed on your side, reply to this message and we will sort it out together.

Refunds, disputes and keeping records

Keep what you would need to answer a query: the accepted agreement with its date, the amounts and dates charged, and the notices you sent. Stripe’s pages say disputes raised within the main windows on Australian and United States bank debits are final, so contact the customer directly first.

If you refund a customer while their bank is also processing a dispute, they can be paid twice. Stripe’s pages warn about this, so tell the customer you are refunding and ask them not to also contact the bank.

A weekly check that takes ten minutes

Once a week, one person looks at three lists: payments that failed, payments still processing, and cards expiring in the next month. Nothing should sit on the first list for more than a week without a message sent. A shared spreadsheet is enough to start.

After a month you will see a pattern. If most failures are expired cards, expiring-card emails help. If bank debits fail on insufficient funds, try a debit date just after the customer’s usual pay day.

When a tool is enough and when to build something

For most small businesses, a payment provider’s subscription settings and its built-in emails do the job. Turn on the failed-payment email, retries and a customer page, and you are done. That is the right answer if you have a few dozen customers and one price.

It stops being enough when payments need to talk to other systems: marking an account as paused in your CRM, sending the failed-payment text from the same number your customers already use, or tying a debit to a booking, a project or a client portal. CentriWeb sets up payments for businesses in that position and connects them to the CRM and the rest of the system, and looks after what it builds. If your volume is low and one tool covers it, you do not need us. The wider systems guides cover the other pieces.

This article is general information and is not financial or legal advice. Check the rules for your country and your provider’s current terms before you start debiting.

Common questions.

Is direct debit or a card better for recurring payments?

Cards are quick to set up and confirm fast, but they expire and get replaced. Bank direct debit suits larger or longer-running amounts, but takes working days to confirm and has country-specific rules. Many businesses offer both.

What should I do when a direct debit fails?

Find out why first. If funds were short, a retry a few days later may work. If the account is closed or the authority was cancelled, you need a new agreement. Tell the customer promptly and make it easy to update their details.

Do I need the customer's permission for direct debit?

Yes. Bank debit schemes generally need the customer to accept a written authority before you debit, and the details differ by country. Check the rules with your bank or payment provider.

How many times should I retry a failed payment?

A provider's limits set the ceiling. Stripe's documentation, for example, lists between one and four automatic retries for bank debits depending on the scheme. Check your own provider's page and pair the retries with a message to the customer.

Related guides.

Payments and systems · 6 min read

Website backup: how often, where, and how to test one

Talk to CentriWeb about this

CentriWeb sets up payments, business email, hosting and backups so they run quietly in the background.

CentriWeb is based in New Zealand and works online with businesses worldwide.

Want this working in your business? We'll map it with you on a call.

A 30 minute call. You'll leave knowing what we'd build first.

Book a call