Resources

Recurring Payment Mandates: Permission to Charge

Every recurring charge rests on a permission: the subscriber agreed, at some point, that you may charge their payment method on a schedule, for an amount or a kind of amount, until they say stop. That permission — formally a mandate, in everyday terms the stored-credential consent behind the subscription — is invisible when everything works. It surfaces only when it breaks: a charge rejected because authentication is required, a subscriber disputing a renewal they forgot they authorised, a processor asking you to evidence consent you recorded badly years ago. Mandate hygiene is unglamorous, but sloppy consent records quietly convert into failed payments, and failed payments convert into churn. This article covers what a mandate is, why charges fail when the record behind them is weak, and the hygiene practices that keep permission solid — at principle level, as general information rather than legal advice.

What a recurring payment mandate actually is

A mandate is the subscriber's authorisation for recurring charges, captured when the subscription begins and relied on for every charge after. Strip away the formal vocabulary and it has four components, each of which should be answerable from your records at any time:

• Who agreed. The identity of the subscriber and, where it differs, the cardholder who authorised the payment method.
• What they agreed to. The product, the billing frequency, the amount or how the amount is determined, and that charges will recur without them approving each one.
• When and how they agreed. The timestamp and the mechanism — a checkout checkbox, a signed order form, a recorded confirmation — plus the terms version in force at that moment.
• How it ends. How the subscriber can revoke the permission, and what happens to future charges when they do.

Different payment methods and regions formalise this differently — card-based recurring billing, direct debit schemes, and wallet-based subscriptions each have their own structures and terminology — but the underlying shape is universal: a stored permission, relied on repeatedly, that must be genuine, specific, and demonstrable. If any of the four components cannot be produced from your records, the mandate is weaker than you think it is, regardless of how confident everyone feels.

Why charges fail when consent records are sloppy

Authentication-required declines

Some issuers respond to a recurring charge by deciding they want the cardholder involved — an authentication-required decline. This happens more readily when the charge looks different from what was authorised: a changed amount, an unusual gap since the last charge, a first charge long after signup, or a subscription whose stored-credential indicators are missing or inconsistent. A clean mandate trail — the original agreement, the expected amount pattern, correct recurring indicators on the transaction — gives the issuer a coherent story. A sloppy one gives it reasons to ask questions the charge cannot survive unattended. The operational responses to this decline family are detailed in our guide to authentication-required declines; mandate hygiene is how you get fewer of them in the first place.

The trial-to-paid conversion moment

The highest-risk charge in any subscription is the first full-price one after a trial, because it is often the first charge that matches the mandate's real amount, sometimes weeks after consent was captured. If the trial terms did not state the post-trial price, the first charge date, and how to cancel before it, the subscriber experiences the charge as unauthorised even when it technically was not — and disputes and authentication challenges follow. This failure mode is common enough that we treat the whole pattern separately in why trial first charges fail; the mandate lesson is that consent captured vaguely at trial is consent you do not fully have at conversion.

Amount and schedule drift

Subscriptions evolve: prices rise, plans change, add-ons attach, billing dates shift. Each change moves the actual charges further from the original permission. Some changes sit comfortably inside what the subscriber agreed to; others materially change the deal and need fresh, explicit agreement. Operators get into trouble when drift accumulates silently — three small changes, none re-consented, until the charge on the statement bears little resemblance to the checkout the subscriber remembers. The mandate no longer matches the money.

Revocation and record mismatches

When a subscriber cancels, the mandate ends — but records do not always keep up. A cancellation recorded in the subscription platform but not reflected in a legacy billing list, a winback offer accepted without fresh consent on file, or a paused account resumed after its original authorisation context is lost can all produce charges that are operationally easy and evidentially indefensible. These are the charges subscribers dispute successfully, and they are entirely self-inflicted.

Mandate hygiene: the practices that hold up

• Capture consent explicitly at signup. The recurring nature, amount or amount logic, frequency, first charge timing, and cancellation route should be visible at the moment of agreement — not only in linked terms the subscriber never opened. Save the evidence with the account: timestamp, terms version, and the payment method authorised.
• Keep the charge pattern faithful to the permission. Consistent amounts, expected intervals, and correct recurring indicators on every transaction. Where the pattern must change, treat it as a consent event, not an administrative one.
• Re-consent on material change. Price increases, plan restructuring, or a change in what is charged should come with clear notice and, where the change is significant, explicit fresh agreement before the new pattern starts. Notice alone and agreement are different things; know which one your change needs.
• Send the pre-charge reminders subscribers rely on. Reminders before first post-trial charges, before annual renewals, and before resumed charges after long pauses are both good service and mandate maintenance — they give the subscriber the chance to revoke before the charge, which is exactly what a healthy mandate contemplates.
• End mandates cleanly. Cancellation should stop future charges everywhere the subscriber exists — every system, every list, every legacy schedule — and the record of that cancellation should be retained and retrievable.
• Audit the record, not just the revenue. Periodically sample old subscriptions and check that each can still produce its four components: who agreed, what, when and how, and how it ends. Long-tenured bases accumulate the oldest, weakest records. A structured pass against the dunning compliance checklist keeps that audit from depending on memory.

How hygiene shows up in recovery numbers

Mandate quality is upstream of dunning. A recovery sequence can retry a soft decline and request a card update, but it cannot retroactively create consent that was never captured, and it should never be used to keep charging on a mandate the subscriber has revoked. Where hygiene is good, the failure mix shifts toward the tractable problems — insufficient funds and expired cards — and away from authentication demands and disputes, which are the failures that cost the most and recover the least. In a well-run stack the roles are clear: clean mandates and honest signup flows prevent the consent-shaped failures, and recovery tooling such as Swipe Again — decline-code-aware retries up to 6 attempts over ~16 days with hard declines never retried, branded card-update pages, and a 90-day backfill on connect across Stripe, Recharge, Seal Subscriptions, Skio, Loop Subscriptions, Chargebee, Recurly, Braintree, and Paddle — handles the payment-shaped ones, at $179/mo flat with no percentage of recovered revenue.

The bottom line

A recurring payment mandate is not paperwork behind the subscription; in a real sense it is the subscription — the standing permission every renewal spends. Keep it explicit at capture, faithful in the charge pattern, refreshed on material change, honoured at cancellation, and auditable on demand, and a whole category of mysterious failures and unwinnable disputes simply stops occurring. Let the records rot, and you will meet the consequences one declined or disputed charge at a time.

Frequently asked questions

What is a recurring payment mandate?

It is the subscriber's standing authorisation for you to charge their payment method repeatedly on an agreed schedule, for an agreed amount or amount structure, without separate approval of each charge. A complete mandate record shows who agreed, what they agreed to, when and how they agreed, and how the permission can be revoked.

Why would a legitimate subscription charge fail over consent?

Issuers can require the cardholder to authenticate when a charge does not match the expected pattern of the stored permission — a changed amount, a long gap, a first real charge well after signup, or missing recurring indicators. Weak or inconsistent consent records make those challenges more likely and harder to resolve, even where the subscriber genuinely intended to pay.

What should be captured when a subscriber signs up?

The recurring nature of the billing, the amount or how the amount is set, the frequency, when the first charge will occur — especially after a trial — and how to cancel, all visible at the point of agreement. Store the evidence with the account, including the timestamp and the version of the terms in force, so the permission can be demonstrated later.

Do price increases or plan changes affect the mandate?

They can. Any change that moves actual charges materially away from what the subscriber originally agreed to should be treated as a consent event: clear notice at minimum, and explicit fresh agreement where the change is significant. Silent drift — several small changes, none re-agreed — is how charges end up looking unauthorised to both subscribers and issuers.

How does mandate hygiene affect failed payment recovery?

Good hygiene prevents the consent-shaped failures — authentication demands, disputes over unrecognised charges, charges after cancellation — that recovery sequences cannot fix, because no retry creates permission. That leaves dunning to handle the failures it is good at, like insufficient funds and expired cards, and keeps the overall failure mix cheaper and more recoverable.