Recurring billing

Also known as: recurring payments

On this page 7

Recurring billing is the practice of automatically charging a customer’s stored payment method on a defined schedule, such as monthly or yearly, under an agreement the customer accepted once. In E-commerce and in the field of checkout & payments, it is the engine behind subscriptions, memberships, replenishment orders and usage-based plans, and it is often called recurring payments.

Unlike a one-time checkout, recurring billing turns a single purchase decision into a continuing payment relationship. That shift changes almost everything downstream: how the payment credential is stored, how authentication rules apply, how failed charges are recovered and how revenue is recognized.

How recurring billing works end to end

Recurring billing works by capturing customer consent and a reusable credential at signup, then letting a billing system create and submit charges on later dates without the customer present. The first transaction is customer-initiated; every later charge is a merchant-initiated transaction (MIT) that references the original agreement.

The card number itself is rarely stored by the merchant. Instead, the payment gateway or processor returns a token that stands in for the card, and card networks may also issue a network token that survives card reissuance. The billing engine keeps the schedule, the plan price, proration rules and the dunning policy, and it passes each charge to the gateway when it falls due.

The following table shows the main stages of a typical recurring billing lifecycle and the system responsible for each one.

StageWhat happensMain system involved
EnrollmentCustomer selects a plan and accepts termsCheckout page
Credential storageCard or account is tokenizedPayment gateway or vault
Initial authorizationFirst charge with authenticationIssuer and 3D Secure
Scheduled chargeMerchant-initiated charge on due dateBilling engine and processor
DunningRetries and reminders after a declineBilling engine and email system
Cancellation or changePlan upgraded, paused or endedCustomer portal
Stages of the recurring billing lifecycle

Recurring billing models and pricing structures

Recurring billing models differ mainly in how the amount is determined and when the charge is triggered. A streaming service, a coffee bean subscription and a cloud software plan all use recurring billing, yet each calculates the invoice differently.

The comparison below summarizes the most common models and where each fits best.

ModelHow the amount is setTypical use
Fixed subscriptionSame price every cycleMedia, memberships, software seats
Tiered plansPrice depends on chosen tierSaaS with feature levels
Usage-based billingMetered consumption per periodCloud services, telecom, APIs
Hybrid billingBase fee plus overagePlatforms with included quotas
ReplenishmentProduct price per shipmentConsumables such as pet food
InstallmentsFixed share of a known totalLarge purchases split over months
Common recurring billing models

Two mechanics appear across all models. Proration adjusts the charge when a customer changes plans mid-cycle, crediting unused time on the old plan. Billing anchors fix the day of the cycle on which charges occur, which simplifies accounting and customer expectations. Installment plans resemble recurring billing technically, but they have a defined end date and total, which also distinguishes them from buy now, pay later products where a third-party lender carries the credit risk.

Authentication and compliance rules for recurring payments

Recurring payments are subject to specific network and regulatory rules because the customer is absent when most charges occur. In the European Economic Area, strong customer authentication under PSD2 requires authentication when the mandate is set up, after which properly flagged merchant-initiated transactions are out of scope for further challenges. The coming PSD3 framework and the related Payment Services Regulation keep this logic while tightening fraud and transparency obligations.

Card networks add their own requirements. Visa and Mastercard expect merchants to store a network transaction identifier from the first charge and to send it with each later charge, so issuers can link them to the original consent. Networks also require clear disclosure of terms, reminders before free trials convert, and an easy cancellation path. In the United States, state automatic renewal laws and Federal Trade Commission rules on negative option marketing impose similar duties.

The table below maps the key obligations to the moment in the lifecycle where they apply.

MomentObligationConsequence of failure
SignupClear price, frequency and cancellation termsDisputes and regulatory penalties
First chargeAuthentication where SCA appliesIssuer declines
Each later chargeCorrect MIT flag and transaction referenceSoft declines or challenges
Trial conversionAdvance reminder to the customerChargebacks and network fines
CancellationSimple, comparable exit pathComplaints and legal exposure
Key compliance obligations by lifecycle moment

Failed payments, dunning and involuntary churn

Failed payments are the largest operational risk in recurring billing because each decline can end a customer relationship that the customer did not intend to end. This loss is called involuntary churn, and it is distinct from voluntary churn, where the customer deliberately cancels.

Declines fall into two groups. Hard declines, such as a closed account or a card reported stolen, will not succeed on retry. Soft declines, such as insufficient funds or a temporary issuer outage, often succeed later. A good dunning strategy retries soft declines at spaced intervals, avoids retrying hard declines, and asks the customer to update the payment method.

The following decision table pairs typical decline situations with a recommended response.

SituationRecommended responseReason
Insufficient fundsRetry after several days, ideally near paydayBalance often recovers
Expired cardUse account updater, then ask customerIssuer may supply new details
Lost or stolen cardStop retries and request a new methodRetries cannot succeed
Authentication requiredSend customer a link to authenticateIssuer demands an on-session step
Processor timeoutRetry shortly with idempotency keyAvoids double charging
Decline handling in recurring billing

Two tools reduce failures before they happen. Card account updater services let networks push new expiry dates and numbers to merchants, and network tokens update automatically when a card is reissued. Together they typically recover a meaningful share of charges that would otherwise fail, although results vary by region, card mix and issuer participation.

Designing recurring billing at checkout

Recurring billing succeeds or fails largely at the checkout step, where trust and clarity determine whether the customer accepts an ongoing charge. The checkout must state the amount, frequency, start date and renewal terms in plain view, not hidden in fine print.

  • Show the next charge date and amount on the confirmation page and in the receipt email.
  • Support digital wallets such as Apple Pay and Google Pay, which provide recurring payment tokens and reduce typing errors.
  • Offer a self-service portal for upgrades, pauses and cancellation, which lowers support load and dispute rates.
  • Avoid forcing account creation when guest checkout is possible, but link the subscription to a verified email address.
  • Send pre-renewal notices for annual plans, which reduce surprise charges and chargebacks.

A common mistake is treating recurring billing as a simple scheduled job. In practice it is a stateful financial system that must handle time zones, currency changes, tax recalculation, refunds, credits and partial periods consistently, and errors in any of these surface quickly as disputes.

In everyday language

Recurring billing means you agree to pay once, and the shop then charges you automatically on a regular schedule until you stop. It works like a standing arrangement with a milk delivery service: you set it up one time, and the deliveries and bills keep coming each week without a new order.

For the shop, it brings predictable income. For you, it saves effort, but it also means you should keep track of what you have signed up for and know how to cancel. Good services make the price, the date of the next charge and the way out easy to see.

Seen in the real world

An online store selling specialty coffee offers a subscription that ships 500 grams of beans every four weeks for 18 euros. At checkout, a customer in Germany enters a card, completes 3D Secure authentication once, and accepts terms that state the price, the shipping interval and how to pause or cancel.

Every four weeks, the store’s billing engine submits a merchant-initiated charge that references the original transaction, so no further authentication is needed. In month seven, the customer’s card expires; the account updater supplies the new expiry date and the charge goes through without interruption.

In month nine, a charge fails for insufficient funds. The system retries three days later and succeeds, and the customer never notices. Over a year, the store tracks that automated retries and card updates kept roughly one in ten at-risk subscriptions active, a result it uses to justify further investment in its dunning settings.