How Do Recurring Card Payments Work?
Recurring card payments let a business charge a customer's stored card on a schedule — monthly for a subscription, per instalment for a payment plan, or whenever a usage bill falls due — without the customer entering their card details each time.
They are the card-rail equivalent of a debit order: the customer authorises future charges once, and the business initiates each subsequent payment. The mechanics, however, are quite different, and getting them right affects approval rates and dispute outcomes.
How is the card stored?
Card numbers are never stored as-is. When the customer first pays or saves their card:
- The card is tokenised: the card number is replaced with a token that can only be used by the merchant or platform that created it.
- The token, not the card number, is stored and used for future charges.
- Network tokens, issued by the card schemes, can update automatically when a card is reissued, which reduces failures over time.
See card tokenisation and network tokens for how this works in detail.
What is the difference between CIT and MIT?
Card scheme rules distinguish who initiates a payment:
| Customer-initiated (CIT) | Merchant-initiated (MIT) | |
|---|---|---|
| Who starts it | The cardholder, in session | The merchant, without the cardholder present |
| 3-D Secure | Applied, and used to establish the agreement | Not required; the charge references the original agreement |
| Example | First payment at sign-up | Each monthly billing charge |
The first payment in a recurring series is a CIT, usually authenticated with 3-D Secure, and it establishes the recurring agreement. Every later charge is an MIT that references that agreement. Flagging recurring charges correctly as MITs matters: issuers approve properly flagged recurring transactions more readily, and the reference to the original consent supports you if a charge is disputed. See recurring card payments, CIT and MIT.
What does the customer agree to?
Before storing a card for recurring billing, the customer should explicitly agree to:
- The amount, or how a variable amount will be calculated
- The billing frequency and the date charges will be made
- How they can cancel, and how much notice is required
- The name that will appear on their card statement
Keep a record of this consent. It is the card equivalent of a debit order mandate and is central to defending disputes.
Why do recurring card payments fail?
Common causes of failed recurring charges:
- Insufficient funds — the most common cause, and often temporary.
- Expired or reissued cards — the stored details no longer match a valid card.
- Lost or stolen cards — the card has been blocked and replaced.
- Issuer declines — risk rules or account status at the customer's bank.
Insufficient-funds declines are usually recovered by retrying at a better time — in South Africa that means around salary dates, typically the 25th to the 1st. Expired and reissued cards are better solved by account updater services and backup cards than by retrying. See dunning and payment recovery and backup cards and account updaters.
Recurring cards or debit orders — which should you use?
Cards give immediate authorisation responses and work well for digital services. Debit orders, especially DebiCheck, are widely used for essential services in South Africa and offer bank-confirmed mandates and built-in tracking as a recovery mechanism. Many businesses offer both and let the customer choose; Kwik supports card-on-file billing alongside EFT and DebiCheck debit orders on the same subscription. For the comparison, see how subscription payments work.
Related topics
Subscription Payments
How subscription billing works, from sign-up and mandate or card capture to recurring collections, failed payment handling and cancellations.
Instalments and Usage Billing
How instalment plans and usage-based billing work, how variable amounts interact with debit order and DebiCheck mandates, and how to notify customers.