Recurring billing
What is recurring billing?
Recurring billing is a payment model where a merchant charges a customer's stored payment method automatically at agreed intervals for ongoing goods or services. The authorizes the arrangement once at signup, and every charge after that runs on schedule without a new approval step.
Recurring billing names the arrangement: the schedule, the amount, the consent behind it, and the retry logic when a charge fails. names the individual charges that arrangement produces. The two get used interchangeably in everyday conversation, and the distinction only matters when you're describing which part of the system you mean.
The model covers subscription services such as streaming, software, and memberships, utilities billed by consumption, insurance and gym contracts, and consumables shipped on a cycle like meal kits or supplements. It runs on cards, , and , and the billing method is independent of the schedule.
Key facts
- Also known as: automatic billing, subscription billing, scheduled billing
- Billing models: fixed (same amount every period), variable (amount changes with tier or usage), metered (charged on consumption), quantity-based (priced per unit or seat)
- Common intervals: weekly, monthly, annual, or custom cycles
- Applies to: subscription services, utilities, memberships and contracts, consumables on a delivery cycle
- Transaction classification: the first charge is a , and each renewal after it is a (MIT). The classification isn't cosmetic - it determines which authentication rules and exemptions the issuer applies to the charge, which is why misflagged renewals get declined.
How it works
- Consent and initial charge. The cardholder agrees to the schedule and amount, then completes a first charge with authentication. In the EEA, applies to this initial charge; the renewals that follow are generally treated as out of scope, though exemption handling varies by issuer.
- Credential storage. The card details are replaced with a token through and stored against the customer record, flagged as a stored credential for future use.
- Scheduled charge. On each cycle date, the merchant submits a merchant initiated transaction against the stored token. No cardholder is present and no authentication prompt is shown.
- Authorization response. The approves the charge or returns a identifying the reason, such as expired card, insufficient funds, or a card the issuer has reissued.
- Recovery. Failed charges enter , where the merchant retries on a schedule and contacts the customer before the subscription lapses.
Recurring billing vs related terms
| Term | What it names | Where it applies |
| Recurring billing | The billing arrangement and its schedule | Merchant billing setup and product pricing |
| The individual charges the arrangement produces | Transaction records and settlement | |
| The scheme classification of a charge with no cardholder present | Authorization messages and authentication rules | |
| A consent model where silence counts as acceptance | Free trials, auto-renewals, and consumer protection rules |
Common issues
- Involuntary failures. Expired, reissued, or blocked cards break the stored credential, so the renewal declines even though the customer still wants the service. These declines drive most subscription churn that neither party intended.
- Unrecognized charges. When the on the statement doesn't match the brand the customer signed up with, the customer disputes the renewal and the merchant absorbs a instead of a support ticket.
- Contested consent. Arrangements that renew without a clear reminder, especially after a free trial, attract both disputes and consumer protection scrutiny.
- Schedule drift. Plan upgrades, proration, and pauses change the amount mid-cycle, and a charge that doesn't match what the customer expects to see gets treated as an error.
