What are Recurring Payments
Written by Arnon Shimoni
✓ Expert
Last updated on:
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
Recurring Payments | One-Time Payments | |
|---|---|---|
Authorisation | Once, at signup | Each transaction |
Billing complexity | High: schedules, retries, renewals | Low: charge and close |
Revenue predictability | High: committed future revenue | Low: depends on repeat behaviour |
Failure handling | Critical: failed payments drive churn | Lower stakes: customer can retry |
PCI scope | Requires tokenisation of stored credentials | Simpler: no stored credentials |
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.
Requirement | Applies to | Common framework |
|---|---|---|
Explicit recurring consent | All jurisdictions | Terms of service + checkout flow |
Pre-notification of charge | Varies by country | Email 7 days before renewal |
Easy cancellation | EU, UK, US (varies by state) | Self-serve cancellation required |
Credential storage rules | All card scheme merchants | PCI DSS tokenisation |
SCA / 3DS | EU, UK | PSD2 |
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.
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.
Ready for billing v2?
Solvimon is monetization infrastructure for companies that have outgrown billing v1. One system, entire lifecycle, built by the team that did this at Adyen.
