Skip to content

Recurring card payments explained: card-on-file, MIT vs CIT, and account updater for subscriptions

How recurring card payments work: stored card consent, customer vs merchant-initiated charges, account updater, and a 7-step failed payment recovery plan.

Recurring card payments start with a customer-initiated transaction, where the customer agrees to store the card and to be charged later. Every later charge is a merchant-initiated transaction that relies on that consent. Network tokens and account updater services keep stored cards working when they expire or are reissued.

This guide covers how the first and later charges differ, how to store cards safely, how to recover failed payments, why subscriptions attract disputes, and what to disclose. It reflects Visa and Mastercard documentation as of November 2026. Rules on renewals and cancellation differ by country and state, so check the current rules for each market you sell in.

Key takeaways

  • The first charge sets up everything. The customer is present, gives consent, and can be authenticated.
  • Later charges are merchant-initiated. They must be flagged that way so the issuer reads them correctly.
  • Store tokens, not card numbers. A token keeps card data out of your systems.
  • Cards change constantly. Account updater services and network tokens refresh stored details before a renewal fails.
  • Subscriptions drive disputes. Mastercard data cited by PayPal in 2026 ties a quarter of Mastercard chargebacks to recurring transactions.

How do recurring card payments work?

A recurring card payment is a series of charges to the same card under one agreement. The customer agrees once, and the merchant charges on a schedule or when an agreed event happens.

  1. The customer signs up. The checkout shows the price, the billing schedule, and how to cancel.
  2. The customer consents to storing the card. Visa's stored credential framework says merchants must "obtain cardholder consent for initial storage of credentials."
  3. The first transaction runs with the customer present. It is a customer-initiated transaction, and it can be authenticated with 3-D Secure.
  4. The card is stored as a token. The merchant keeps a reference, not the card number.
  5. Each renewal runs as a merchant-initiated transaction. The merchant sends the charge with indicators that mark it as a stored credential payment under an existing agreement.
  6. The issuer approves or declines each charge. Every renewal is a fresh authorization, as described in how card payments work.

The agreement is the anchor. The card details can change over the life of a subscription. The consent and its terms should not, unless the customer agrees to new ones.

What is the difference between customer-initiated and merchant-initiated transactions?

Visa's stored credential framework splits card payments by who starts them. A cardholder-initiated transaction (CIT) is "any transaction where the cardholder is actively participating in the transaction," in a store, at an online checkout, or with a stored credential. A merchant-initiated transaction (MIT) happens "without the active participation of the cardholder." The framework is published in a Visa business bulletin.

Customer-initiated (CIT)Merchant-initiated (MIT)
Who starts itThe cardholderThe merchant
Is the cardholder present?Yes, in person or onlineNo
Can it be authenticated?Yes, for example with 3-D SecureNo, the cardholder is not there
Basis for the chargeThe cardholder's action at that momentAn earlier CIT or a standing instruction
ExamplesSignup payment, one-click reorderRenewal, installment, usage-based billing

The label matters to the issuer. An MIT that arrives without the right indicators looks like a customer payment with no customer and no authentication, which is a common reason for declines. Your payment provider sets these indicators for you if you tell it which kind of payment you are sending.

Authentication happens on the first payment. In markets that require strong customer authentication, the signup payment goes through 3DS, and the renewals rely on that first authenticated payment. 3D Secure 2 explained covers the protocol.

How do you store cards safely?

Store a token and let a specialist hold the card number. A token is a substitute value that maps back to the card only inside the system that issued it.

There are two kinds. A gateway token is issued by your payment provider and works only with that provider. A network token is issued by the card network and is designed to work across processors. Network tokens also update when the card behind them changes. Card tokenization explained compares them in detail.

Two rules hold for any setup. Collect the card in a hosted page or hosted fields, so the number never reaches your servers. And never keep the card security code after authorization. The PCI Security Standards Council publishes the standard that sets these limits.

How do you recover a failed recurring payment?

Treat a failed renewal as a process, not a single retry. The response code tells you which path to take. Why card payments get declined explains the codes, using the list in Stripe's network decline codes reference.

  1. Read the response code. Sort the failure into soft, such as insufficient funds, or hard, such as an invalid card number.
  2. Check for updated card details. Query your account updater or token service before you retry. A reissued card is often the whole problem.
  3. Retry soft declines on a spaced schedule. Try again after a few days, for example after a typical payday. Stay inside your network's and processor's retry limits.
  4. Tell the customer. Send a short message with a secure link to update the card. Do not ask for card details by email.
  5. Offer a second payment method. A backup card or a bank payment recovers customers whose card will not come back.
  6. Apply a grace period, then pause. Keep the service on for a defined period while you retry, then pause it. Do not keep charging.
  7. Stop and record the outcome. After the final attempt, or on any hard decline, end the retries, cancel or suspend the subscription, and log what happened.

Never retry a hard decline with the same details. It will fail again, and repeated attempts can look like an attack on the card.

How do you keep stored cards current?

Cards expire, get lost, and get replaced. Two services keep stored credentials valid without asking the customer.

Account updaterNetwork token
What it doesSupplies new card numbers and expiry dates for stored cardsKeeps one token linked to the current card
Who runs itThe card network, fed by issuersThe card network
How the merchant uses itQueries or receives updates, usually through its providerCharges the token; the network resolves the card
What changes in your recordsThe stored card detailsNothing. The token stays the same

Visa describes Visa Account Updater as "a service that enables issuers, acquirers, and qualified merchants to exchange updated account information" for recurring and credential-on-file payments. Its updates cover account numbers, expiration dates, closed accounts, and cardholder advices.

Mastercard's Automatic Billing Updater "provides access to updated payment account credentials including PAN and expiry date updates." Issuers report account changes to the service, and merchants can query it or subscribe to notifications.

Neither service fixes a closed account or an empty one. They remove one cause of failure: stale details.

Why do subscriptions attract disputes?

Recurring charges arrive when the customer is not thinking about the purchase. That gap produces disputes. PayPal, citing Mastercard, reports that "a quarter of Mastercard chargebacks are linked to recurring transactions" (PayPal, September 3, 2026).

The usual triggers are easy to name.

  • Forgotten renewals. Annual plans are the classic case.
  • Trials that convert. The customer did not notice when the free period ended.
  • Unclear descriptors. The name on the statement does not match the brand the customer knows.
  • Hard cancellation. A customer who cannot find the cancel button calls the bank.
  • Price changes. The amount went up and the customer was not told.

A dispute costs more than a refund, and too many of them put a merchant in a network monitoring program. Chargebacks explained covers the process, and friendly fraud covers disputes over purchases the customer did make.

What do you need to disclose, and how should cancellation work?

Clear terms prevent many subscription disputes. Card network rules and consumer protection laws both cover recurring billing, and they change. Check the current rules for each market you sell in, and ask a specialist where the rules are unclear.

These basics hold up in most markets.

  • State the terms before the customer pays. Show the price, the billing frequency, the trial length, and what happens when the trial ends.
  • Get explicit consent. Record when and how the customer agreed, and keep that record.
  • Confirm in writing. Send the terms and the cancellation steps by email after signup.
  • Remind before you charge. Send a notice before a trial converts, before an annual renewal, and before a price change.
  • Make cancellation as easy as signup. Offer it in the same channel the customer used to subscribe.
  • Use a descriptor customers recognize. Include the brand name and a support contact where your provider allows.
  • Refund fast when asked. A quick refund is cheaper than a dispute.

Keep the consent record, the reminders, and the usage history together. They are your evidence if a dispute arrives.

Sources

What to do next

Review your signup page against the disclosure list, then map your failed-payment process to the seven steps above. For the stages behind each renewal, read how card payments work. If your business also pays people on a schedule, BlindPay handles that side: see how to schedule recurring payouts with live quotes. BlindPay does not issue cards.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.