Flow of Fundsby Fintech North

How recurring and subscription billing works

Recurring billing relies on a stored mandate or saved payment credential that lets a merchant pull an agreed amount on a schedule, with each pull running as its own authorization and settlement.

Smart non-experts new to payments: founders, ops, PMs, and BD building subscriptions who need to understand stored credentials, retries, and cancellation.

Subscriptions work because the customer gives the merchant standing permission to charge them on a schedule. That permission is stored either as a card-on-file credential or as a pre-authorized debit mandate against a bank account (ACH in the US, PAD in Canada). Each billing cycle the merchant triggers a fresh charge using that stored permission, and each charge authorizes and settles on its own. When a charge fails, the merchant retries and sends reminders (dunning); customers can cancel the mandate, and consumer rules govern how that works.

The flow at a glance

CustomerMerchantProcessor / gatew…Network or ACH/PADCustomer's bank1Mandate authorized2Trigger cycle charge3Submit charge4Authorize / debit5Funds settle6Retry on failure7Cancel or dispute
money (funds move) message (instructions) exception

Who’s involved

Customer
The subscriber who grants standing permission to be charged
Merchant
The business that stores the mandate and triggers each cycle's charge
Processor / gateway
Submits each scheduled charge into the right rail
Network or ACH/PAD rail
Routes the charge: card network for card-on-file, or the ACH/PAD system for bank debits
Customer's bank / issuer
Approves or declines and moves the money from the customer's account

How it moves, step by step

  1. 1
    messageCustomer

    At signup the customer authorizes recurring charges, creating a stored card-on-file credential or a pre-authorized debit (ACH/PAD) mandate. This permission is not a charge.

  2. 2
    messageMerchant

    When a billing cycle arrives, the merchant triggers a new charge using the stored credential or mandate.

  3. 3
    messageProcessor / gateway

    The processor submits the charge into the card network (card-on-file) or the ACH/PAD rail (bank debit).

  4. 4
    messageNetwork or ACH/PAD rail

    The rail routes the request to the customer's bank for authorization (cards) or as a debit entry (ACH/PAD).

  5. 5
    messageCustomer's bank / issuer

    For card-on-file, the issuer approves or declines in real time and places a hold on the funds. For ACH/PAD bank debits there is no upfront approval: the debit is presented and settles on schedule, and the merchant only learns of a failure (like insufficient funds) when a return comes back a few days later, or weeks later if the customer disputes the debit as unauthorized.

  6. 6
    moneyCustomer's bank / issuer

    On settlement the funds move from the customer's account toward the merchant; banks move the money, the rail just routes and nets.

  7. 7
    exceptionMerchant

    If a charge fails (expired card, insufficient funds), the merchant runs retries and dunning emails to recover the payment before the subscription lapses.

  8. 8
    exceptionCustomer

    The customer can cancel the mandate or dispute an unauthorized charge; consumer protection rules govern how cancellations and reversals must be handled.

money: funds actually move message: instructions, no money yet exception: reversal / dispute

When it’s final

Card-on-file charges typically authorize in seconds and settle in 1 to 2 business days. ACH or PAD bank debits clear over 1 to 3 business days and can fail or be returned several days after the pull, so confirmed receipt is slower than with cards.

Common misconceptions

  • Myth: Each subscription charge needs the customer to re-enter their details.

    Reality: The customer grants permission once. After that the merchant pulls on schedule using a stored credential or mandate, with no fresh customer action per cycle.

  • Myth: Authorizing a subscription is the same as being charged.

    Reality: The mandate or stored credential is standing permission. The actual money only moves when the merchant triggers each cycle's charge and it settles.

See it in the studio

Show a monthly card-on-file subscription charge, marking the authorization message and the settlement money leg separately.Card-on-file (card rail) example, to contrast with the bank-debit pull below.Map a Canadian pre-authorized debit (PAD) for a monthly membership, including a failed pull and retry.Shows the PAD mandate and exception/retry path.ACH debit (web-authorized)Audited template, loads instantlyPre-authorized debit (Canada)Audited template, loads instantlyVisa four-party modelAudited template, loads instantly

Terms in this guide

AuthorizationSettlementTokenizationODFI (Originating Depository Financial Institution)RDFI (Receiving Depository Financial Institution)ChargebackPayment Service Provider (PSP)Payment Gateway3-D Secure (3DS)

Sources

  • NACHA ↗ · NACHA. Rules for ACH pre-authorized debits and recurring entries (US).
  • Payments Canada ↗ · Payments Canada. Rules governing pre-authorized debit (PAD) in Canada.
  • Visa ↗ · Visa (operator). Network rules including the stored credential and card-on-file framework for recurring card payments.
  • Consumer Financial Protection Bureau ↗ · CFPB. Consumer rights around recurring charges and cancellation (US).

Educational, plain-English explainers. Not legal, compliance, tax, or financial advice. These cover fundamentals, not current fees, limits, or rates (which change). Rails and parties vary by program and country, so verify specifics against primary sources. Last reviewed June 2026.