What are recurring payments?

What are Recurring Payments?

Recurring payments are automatic charges that repeat on a defined schedule like weekly, monthly, annually without the customer having to initiate each transaction. The customer authorises the charge once; the billing system handles every subsequent payment until the subscription is cancelled or the payment method fails.

The mechanism underpins most subscription businesses, SaaS products, and any service model where customers pay continuously for ongoing access. It's also one of the more operationally complex billing patterns to run well, because every failure in the cycle such as expired cards, declined authorisations, network errors needs to be caught, handled, and resolved without losing the customer.

How Recurring Payments Work

When a customer enters their payment details for a subscription, the business stores a tokenised representation of that credential with their payment gateway. On each billing date, the billing system sends a charge instruction to the gateway, which uses the stored token to attempt the transaction against the customer's bank. If the authorisation succeeds, the payment is captured and revenue is recognised. If it fails, the billing system needs to decide what to do next.

This sounds straightforward. The complexity accumulates at the edges: customers whose cards expire between billing cycles, customers who cancel partway through a billing period and need a prorated refund, customers who upgrade mid-cycle and need to be charged the difference immediately, and customers in different countries who need to be charged in their local currency through a gateway that supports it.

Recurring Payments vs. One-Time Payments

The Billing Infrastructure Requirements

Scheduling and timing

The billing system needs to know exactly when to charge each customer. Annual contracts have different renewal dates. Monthly subscribers may have all signed up on different days of the month. Billing systems that run all charges on the first of the month create a spike in transaction volume that gateways need to handle, and produce prorated charges that don't align with customers' actual start dates.

Proration

When a customer upgrades, downgrades, or cancels mid-cycle, the billing system needs to calculate the credit or charge for the partial period.

A customer on a $120/month plan who upgrades to $240/month on the 15th of a 30-day month should be charged $60 for the remaining 15 days of the premium plan, and credited $60 for the unused portion of the standard plan. Billing systems that handle this correctly improve revenue accuracy and reduce the customer disputes that come from unexpected charges.

Failed payment recovery

Payment failures are a fact of recurring billing. Cards expire. Banks decline transactions for fraud reasons. Accounts run out of funds the day before a renewal. A well-designed recurring payment system routes each failure type into an appropriate recovery flow, like automatic retries for soft declines, customer notifications for expired cards, and escalation to cancellation for hard declines that won't resolve on their own. The alternative is silent involuntary churn: customers whose subscriptions lapse because nobody caught the failed payment in time.

Compliance and Authorisation Requirements

Recurring payments carry regulatory obligations that one-time payments don't. Depending on jurisdiction, businesses must obtain explicit consent for recurring charges, notify customers before the first charge in a series, provide clear cancellation mechanisms, and comply with payment scheme rules around credential storage and usage. In Europe, Strong Customer Authentication (SCA) requirements under PSD2 add friction to the initial authorisation that needs to be handled at checkout. Getting this wrong creates both regulatory exposure and customer disputes.

Recurring payments by bank: SEPA Direct Debit, Bacs, iDEAL, pay by bank

Cards are not the only way to collect a recurring payment. In Europe most B2B and much of B2C recurring revenue is collected from the bank account, which costs less per transaction and does not expire the way a card does. The four methods that matter are SEPA Direct Debit in the euro area, Bacs Direct Debit in the UK, iDEAL in the Netherlands and pay by bank through open banking.

The trade-off is predictability versus speed. Direct debit is pulled by the seller, so it fits a fixed billing cycle, but it settles in days and can be returned. iDEAL and pay by bank settle at once and cannot be reversed by the payer, but the payer has to approve each payment unless a mandate was captured, which makes them better for the first payment or for one-off top-ups than for a monthly cycle.

How to set up recurring payments for an online subscription business

1. Collect a mandate or a card on file at signup. For bank collection, capture the SEPA or Bacs mandate with the required wording and a reference. For cards, run a zero-amount or first-payment authorisation with the recurring flag set.

2. Store the token at the payment service provider, not in your own database. The PSP returns a token or mandate reference; the billing system stores only that.

3. Schedule the charge from the billing cycle. The invoice date, not the signup date, decides when the charge is attempted. Send the SEPA pre-notification at least the number of days before the debit that the mandate states.

4. Retry on failure with a schedule that matches the method. Cards can be retried within days; a returned direct debit should wait for the return reason before any retry. Route failures into dunning.

5. Send the invoice with the charge. The customer should receive the invoice and the payment confirmation together, with the mandate reference or the last four card digits on the document.

Recurring and one-time payments on the same account

Most subscription accounts also carry one-off charges: a setup fee, a hardware purchase, a usage overage, a professional services block. These should be collected with the same stored payment method and appear on the same invoice as the recurring fee, not as a separate payment flow. Example: a customer signs up for a €400 monthly platform fee with a €1,500 onboarding fee. The first invoice is €1,900 and is collected in one charge against the mandate. From month two the invoice is €400. The billing system has to know which lines recur and which do not, so that month two is right without anyone editing it.

Best ways to manage recurring payments

• Set a retry schedule per payment method and per failure reason, and stop retrying when the reason is final (closed account, revoked mandate).

• Track mandate expiry and card expiry ahead of the billing date, and ask for a new instrument before the charge fails rather than after.

• Use the card networks' account updater so replaced cards keep working without customer action.

• Send the SEPA pre-notification on time, with the amount and date, so the debit is expected and not returned as unauthorised.

• Alert finance and the customer on the day a payment fails, with the invoice and the reason, and pause the dunning sequence the moment a payment lands.

Frequently Asked Questions

What are recurring payments?

Recurring payments are automatic charges taken from a stored payment method on a repeating schedule, under an authorisation the customer gave once. They are the collection mechanism behind subscriptions and most consumption billing.

What is the difference between recurring payments and a subscription?

The subscription is the commercial agreement. Recurring payments are the mechanism that collects against it. A subscription can be collected by invoice and bank transfer without any recurring card payment involved.

What authorisation is required?

The customer must consent to future charges, and in Europe strong customer authentication under PSD2 applies to the initial setup, with subsequent merchant-initiated transactions typically exempt if the mandate was established correctly.

How are recurring payments affected by variable amounts?

Consumption billing produces a different amount each period, which some mandate types and jurisdictions constrain. Direct debit schemes in particular often require advance notice of the amount before collection.

What happens when a recurring payment fails?

It enters a dunning sequence: timed retries plus escalating customer communication, ideally with an account updater service supplying refreshed card details before any retry is attempted.

What is tokenisation?

Replacing card details with a token stored by the processor, so the merchant can charge again without holding card data. It is the mechanism that makes recurring payments possible without full PCI scope.

What are A2A recurring payments?

Account-to-account (A2A) recurring payments move money directly from the payer's bank account to the seller's, without a card network in between. SEPA Direct Debit and Bacs are the established forms. Open banking pay by bank and UK variable recurring payments are the newer, real-time forms. A2A costs less per transaction and does not expire, but direct debit can be returned and open-banking payments need the payer's approval unless a mandate exists.

Can recurring payments run on pay by bank?

Partly. In most EU markets pay by bank is single-payment: the payer authorises each payment in their banking app. The UK's variable recurring payments (VRP) let a customer give a standing consent with limits, which does allow true recurring collection. Elsewhere the usual pattern is to take the first payment by pay by bank or iDEAL and capture a SEPA mandate for the rest.

Related

• Dunning. Recovering failed recurring payments.

• Subscription management. The commercial layer above the payment.

• Payment gateway. Where the charge is authorised.

• ACH. Bank-based recurring collection in the US.

• Prepaid and postpaid billing. When the payment is taken relative to delivery.