Payments · Guide17 min readUpdated November 2, 2026

Subscription Payment Processing: From First Charge to Every Renewal

How subscription payment processing works: the first charge, stored-credential renewals, Visa rules, SCA, card updates, retries and choosing a processor.

Article summary

TL;DR

Subscription payment processing charges a customer again and again on one agreement. The first payment is made by the customer, with consent, and the card is stored. Each renewal is then charged by the merchant on that stored credential, flagged as recurring. Card updates, retries within network limits and a processor that accepts your model keep renewals going.

  • The first payment is customer-initiated. Every renewal after it is merchant-initiated, on a stored credential, and must be flagged that way.
  • Visa requires a written agreement before you store the card, and an approved authorization or account check. If the check is declined, you can't store the card.
  • In Europe, authenticate the first payment or the card setup. Renewals are merchant-initiated and outside SCA, but the issuer can still ask for authentication.
  • Card account updaters and network tokens keep stored cards working after a reissue. Lost, stolen, closed and revoked cards must never be retried.
  • Choose a processor on its subscription rules, MIT support, card updates, retry tools and token portability, not only on the rate.
Want to go further? AskChatGPTClaudePerplexityGrok
On this page

Subscription payment processing is how you charge the same customer again and again on one agreement, without them typing their card each time. Behind every renewal sits a chain of rules: the consent you collected at sign-up, the way you store the card, the flag on each charge, and what you're allowed to do when the bank says no. This guide follows a card subscription from the first charge to the tenth renewal, with the Visa rules, the European SCA rules and the processor checks that decide whether renewals keep going through. For supplement and skincare brands: subscriptions for supplement brands and subscriptions for skincare brands.

What is subscription payment processing?

It's the part of your stack that turns a subscription agreement into payments: it stores the customer's payment details, charges them on schedule, and handles the renewals that fail. The billing system decides what to charge and when. The processor sends each charge through the card network to the customer's bank, which approves or declines.

Card networks don't use the word "subscription". They classify payments on a stored card by how they're scheduled, and each type has its own flag and its own rules.1Visa Core Rules and Visa Product and Service Rules, April 18, 2026

Visa transaction typeWhat it isTypical use
Recurring transactionA series on a stored credential, at fixed regular intervals, no more than one year apartMonthly box, yearly membership, software plan
Unscheduled credential-on-fileFixed or variable amount on a stored credential, not on a schedule, triggered by an agreed eventAutomatic top-up when a balance runs low
Installment transactionOne purchase split into a set number of paymentsPay in 3 or 4
Cardholder-initiated with a stored cardThe customer pays with a card you saved, while presentOne-click reorder, upsell

Bank debits like ACH and SEPA work on mandates instead of card rules. They're covered further down.

How a recurring card payment works, step by step

  1. The customer agrees to the terms. Price, frequency, trial length, how to cancel, shown at checkout and separate from your general terms.
  2. The first payment runs, customer-initiated. You authorize the first charge, or a zero-amount account check if nothing is due yet (a free trial). In Europe, this is where strong customer authentication happens.
  3. The card is stored as a token. The processor keeps the card number in its vault and gives you a token. It also returns the network's reference for this first transaction: keep it.
  4. The billing system triggers the renewal. On the billing date, it charges the token without the customer, flagged as a recurring merchant-initiated transaction, with the original reference.
  5. The issuer decides. It checks the card status, the funds, its fraud signals and the link to the original agreement.
  6. You handle the outcome. Approved: the subscription stays active. Declined: the decline code tells you whether to retry later, update the card or stop.

Steps 1 to 3 happen once. Steps 4 to 6 repeat on every billing date.

The order matters. Visa says that after the agreement is in place and before the first transaction, you must either authorize the amount due or send an account verification. If that first request isn't approved, you must not store the card.1Visa Core Rules and Visa Product and Service Rules, April 18, 2026

Customer-initiated vs merchant-initiated transactions

Every subscription has two kinds of payments. The customer-initiated transaction (CIT) is the one the customer makes at sign-up. The merchant-initiated transactions (MIT) are the renewals you charge afterwards, on the strength of that first agreement.

Fig. 1Two kinds of payments in one subscription

Sign-up: customer-initiated

  1. CheckoutCustomer enters the card and accepts the terms
  2. AuthorizationWith 3-D Secure where requiredApproved
  3. Token and reference savedFor every renewal to comeApproved

Customer present, can authenticate, card gets stored

Renewal: merchant-initiated

  1. Billing dateYour system starts the charge
  2. Stored tokenFlagged recurring, original reference attached
  3. Issuer decisionApprove, or decline with a code

Customer absent, can't authenticate, charge rests on the agreement

same card, different flags

Based on Adyen's PSD2 business models documentation and Stripe's off-session payment flow.

Each processor exposes the flags differently, but they map to the same network framework:

StepStripeAdyen
First payment, card savedsetup_future_usage=off_session on the paymentshopperInteraction: Ecommerce with recurringProcessingModel: Subscription
Renewaloff_session=true on a new payment with the saved payment methodshopperInteraction: ContAuth with recurringProcessingModel: Subscription
Original referenceHandled by StripeStore networkTxReference and send it with each renewal

Sources: Stripe3Stripe Docs, Save a customer's payment method when they use it for a payment and Adyen.7Adyen Docs, PSD2 SCA business models overview15Adyen Help Center, How can I choose the Recurring Processing Model? Adyen is explicit about the risk: if you don't send the scheme transaction identifier with later payments, issuers can return soft declines. If you store cards in your own vault or a third-party one, Adyen tells you to use the card schemes' MIT framework so the payment is classified correctly.7Adyen Docs, PSD2 SCA business models overview

What Visa requires before you store a card

Visa's rules for stored credentials start before the first charge. Before you store a card for future payments, you need the cardholder's express, informed consent to an agreement that covers, among other things:1Visa Core Rules and Visa Product and Service Rules, April 18, 2026

  1. The transaction

    What you sell, the total price, and the cancellation and refund policy, with the date cancellation rights expire.

  2. Who you are

    Your merchant location, plus the address, email and phone number customers should use for these payments.

  3. How the card will be used

    Last four digits of the card, amount or how it's set, currency, timing and frequency, how you'll notify changes, and when the agreement ends.

  4. Trials and promos

    The length of any trial period, introductory offer or promotional period.

These terms must be shown when the customer gives consent, and separately from your general terms and conditions. You keep them for the length of the agreement and hand them over if the customer or the issuer asks in writing. A recurring or unscheduled credential-on-file charge can't include finance charges or interest. And if you don't respect your own terms, Visa says you refund the full amount paid.1Visa Core Rules and Visa Product and Service Rules, April 18, 2026

In Europe, two extra steps

Visa asks European merchants to confirm the recurring agreement to the customer within 2 business days. For unscheduled credential-on-file charges, any change of amount or terms must be notified at least 2 working days before it applies.1Visa Core Rules and Visa Product and Service Rules, April 18, 2026

On each charge, Visa also has processing rules: a transaction with a stored credential uses POS entry mode 10 and the recurring, installment or unscheduled indicator; the authorization can't exceed the amount of that payment; and before a customer pays with a card you saved, you validate who they are, for example with a login.1Visa Core Rules and Visa Product and Service Rules, April 18, 2026 Your processor sets the technical fields. Your job is to tell it which kind of payment it is.

Visa rules for recurring transactions

On top of the stored-credential agreement, recurring transactions have their own requirements. Here is what they mean for a subscription business.1Visa Core Rules and Visa Product and Service Rules, April 18, 2026

RuleWhat to doWhere in the Visa rules
Simple cancellationOffer an easy way to cancel, online if the customer signed up onlineTable 5-21, p. 461
Fixed datesState the fixed dates or intervals of the chargesTable 5-21, p. 461
End of a trial or promoAt least 7 days before the charge, email the amount, the date of the next charges and a simple way to cancel online or by text messageTable 5-21, p. 461-462
Europe: long gap or changed termsSend the same notice if more than 6 months passed since the last charge, or if the amount, the date or other terms changedTable 5-21, p. 462
Europe: checkout displayShow merchant name, product, trial length, amount due today (even zero), recurring amount and interval, last four digits, cancellation policy on the card-entry page and the checkoutTable 5-21, p. 462
A renewal is declinedTell the customer in writing and give them at least 7 calendar days to pay another wayTable 5-22, p. 464

Trials and "until cancelled" offers carry more rules, from the FTC and US states as well as Visa. They're covered in our guide to negative option billing.

If an Authorization Request for a Merchant-initiated Transaction with a Stored Credential is declined, the Merchant must notify the Cardholder in writing and allow the Cardholder at least 7 calendar days to pay by other means.

Visa Core Rules and Visa Product and Service Rules, April 18, 2026, Table 5-22, p. 464

That last rule is easy to miss. A declined renewal isn't only a retry problem: it starts a 7-day window in which the customer must be told and offered another way to pay. Plan your dunning emails around it.

SCA and subscriptions in Europe

In the EEA and the UK, strong customer authentication applies to online payments the customer initiates. A subscription fits that rule in two parts.

Fig. 2The authentication path of a European subscription

approved declined or closed routing step

  1. Sign-up3-D Secure on the first payment or card setupApproved
  2. thenRenewalsMerchant-initiated, no challenge
  3. sometimesIssuer asks to authenticateRenewal declinedDeclined
  4. dunningCustomer authenticates onceThrough a payment link, renewals resumeApproved
Based on Delegated Regulation 2018/389, EBA Q&A 2018_4031 and Stripe's SCA documentation.

Merchant-initiated renewals also skip the liability shift: a fraud dispute on a renewal stays with you. The detail of exemptions and liability is in our guide to payment authentication.

Keeping stored cards alive: account updater and network tokens

Cards expire, get reissued after a loss, or get replaced by a new number. A subscription stored on the old details fails at the next renewal unless something updates them. Two tools do that job.

A card account updater lets the processor fetch new card details from the network. Visa requires issuers in most regions, including the US, Canada and Europe (except Hungary and Türkiye), to enroll their BINs in Visa Account Updater; prepaid BINs are excluded, and commercial BINs in several regions. Issuers must send a new number and expiry within 2 business days of activating the account.1Visa Core Rules and Visa Product and Service Rules, April 18, 2026 A network token goes further: it's a substitute for the card number, issued by the network, that keeps working when the underlying card changes. Stripe uses both on saved cards, and Adyen offers both, requesting network tokens automatically for stored cards where possible.6Stripe Docs, Payments optimization (Authorization Boost)8Adyen Docs, Tokenization

The updater doesn't always return a new card. Visa defines the answers an issuer can send, and each calls for a different move:1Visa Core Rules and Visa Product and Service Rules, April 18, 2026

  1. New number or expiry dateThe card was reissued and the new one is activeCharge the renewal on the updated card
  2. Closed accountPermanently closed, the number can never be reopenedStop charging it. Ask the customer for a new payment method
  3. Contact cardholderThe issuer won't share the new details, for risk reasons or at the customer's requestEmail the customer with a link to update their card
  4. Opt-outThe customer asked the bank not to share new detailsAsk the customer directly. Don't try to guess

Two limits to know. Updater coverage is wide in the US, but Stripe says international support varies by country and that you can't tell in advance which cards support it.5Stripe Docs, How cards work (automatic card updates) And keeping stale cards costs money: Stripe notes that Mastercard charges a Credential Continuity Program fee when a payment is attempted with outdated card details, and that network tokens can avoid it.6Stripe Docs, Payments optimization (Authorization Boost) If you route renewals across several processors, check that each one runs the updater and network tokens on the cards it charges.

When a renewal is declined: retries and network limits

Most failed renewals can be recovered, but not all of them, and not without limits. The card networks set how often you may try again, and the limit counts per card across all your processors.

Visa decline categoryExamples relevant to subscriptionsRetry the same card?
1. Issuer will never approve14 invalid account, 41 lost, 43 stolen, 46 closed account, 57 not permitted, R0 stop payment order, R1 revocation of authorization, R3 revocation of all authorizationsNoNever, on any processor
2. Issuer can't approve now51 not sufficient funds, 61 exceeds amount limit, 9G blocked by cardholder, 91 issuer inoperativeYesUp to 20 attempts in 30 days
3. Data quality54 expired card, N7 CVV2 failure, 1A additional authentication required (Europe)YesUp to 20 attempts in 30 days, once the data is fixed
4. GenericAll other codes, including 05 do not honorYesUp to 20 attempts in 30 days

Source: Visa Core Rules, Table 7-2, p. 538-541.1Visa Core Rules and Visa Product and Service Rules, April 18, 2026 R0, R1 and R3 deserve attention in a subscription business: they mean the customer told the bank to stop paying you. Retrying them is a breach, and a dispute waiting to happen.

20

Visa's cap on attempts for the same card in 30 days, outside Category 1

7 days

Minimum Visa window to let the customer pay another way after a declined renewal

8

Tries within 2 weeks, Stripe Billing's recommended Smart Retries default

Billing tools apply their own limits inside the network's. Stripe Billing's Smart Retries picks retry times from signals like the time of day and how the card was recently used; you set a number of attempts over 1 week to 2 months, with 8 tries within 2 weeks as the recommended default. Stripe won't retry after hard declines such as lost_card, stolen_card, revocation_of_authorization or authentication_required until a new payment method is added. When retries run out, the subscription is canceled, marked unpaid, left past due or paused, depending on your setting.4Stripe Docs, Automate payment retries

Practical rule

Read the decline before you retry. Insufficient funds: retry later, on a schedule. Expired card: update the card first. Lost, stolen, closed or revoked: stop on every processor and ask for a new payment method. In every case, email the customer within the 7-day window.

What causes failed renewals and how to prevent them is covered in subscription payment failures. The retry rules across several processors are in dynamic payment routing, and how to measure them in payment acceptance rate.

Cards, ACH or SEPA for subscriptions

Cards aren't the only way to bill on a schedule. In the US, ACH debit pulls from a bank account; in the euro area, SEPA Direct Debit does. Both work on a mandate the customer accepts, and both behave very differently from cards when something goes wrong.

CardsACH Direct Debit (US)SEPA Direct Debit (EU)
AuthorizationAgreement plus stored credential, network rulesMandate; at least 7 calendar days' notice if you change the timing of recurring debitsMandate; notify the customer before each debit
Result knownIn secondsUp to 4 business days at StripeWait at least 6 business days at Stripe
Customer dispute windowCard network rulesUp to 60 calendar days for a personal account, 2 business days for a business account8 weeks with no questions asked, up to 13 months if unauthorized
Can you contest a dispute?YesWith evidenceNoDisputes are final (except late returns)NoDisputes are final
Stripe automatic retriesSmart Retries, within network limitsInsufficient funds only, 2 retries within 40 daysInsufficient funds only, 2 retries within 30 days
Card updatesAccount updater, network tokensNone: a new account means a new mandateNone: a new account means a new mandate

Sources: Stripe's ACH and SEPA documentation13Stripe Docs, ACH Direct Debit payments12Stripe Docs, SEPA Direct Debit payments and retry settings.4Stripe Docs, Automate payment retries A disputed ACH payment invalidates the mandate, and a SEPA dispute can deactivate it: you need a new mandate before charging again.13Stripe Docs, ACH Direct Debit payments12Stripe Docs, SEPA Direct Debit payments Bank debits cost less to run and never expire like cards, but the customer holds stronger dispute rights. They fit best as a second method you offer, not a replacement. More in ACH payment processing and alternative payment methods.

Do processors accept subscription businesses?

Most do. Recurring billing is a standard feature at Stripe, Adyen and most acquirers. What they review is how you sell it.

What processors generally accept

  • Plans with a clear price, interval and cancellation path
  • Trials whose end date, price and cancellation are disclosed at sign-up
  • Renewal reminders and easy online cancellation, as Visa requires

What they restrict or refuse

  • Stripe's prohibited list names marketing and membership clubs that bill until cancellation, and discounted trials with hidden or unclear charges14Stripe, Prohibited and restricted businesses
  • Offers where the recurring charge is buried in the terms
  • Physical goods sold on subscription through direct marketing, which Visa classifies apart

That last point is about your merchant category code. Visa's MCC 5968, Direct Marketing, Continuity and Subscription Merchants, covers goods like books, cosmetics, food, clothing or nutraceuticals sold on subscription through direct marketing. A merchant that simply offers recurring billing without direct marketing keeps the code of its main business; streaming uses 4899 and digital subscriptions 5815 to 5818.2Visa, Merchant Data Standards Manual, April 2026 Visa lists 5968 among its high-risk codes for card-absent sales.2Visa, Merchant Data Standards Manual, April 2026 If your offer fits it, expect a closer review and plan for it. See MCC 5968 and our guide to high-risk MCC codes.

Your dispute rate is the real test

Subscription disputes often come from customers who don't recognize a renewal or couldn't cancel. A processor that accepted you can still review or close the account if disputes pile up. The prevention side is in chargeback prevention.

How to choose a payment processor for subscriptions

The rate is the easiest thing to compare and the least specific to subscriptions. These questions tell you more about how renewals will go.

Question to askWhy it matters for subscriptionsA good answer
Does your policy accept my offer as I sell it?Trials, "until cancelled" offers and MCC 5968 are reviewed closelyA written answer on your exact offer and the MCC you'll get
How do you flag renewals as merchant-initiated?Wrong or missing flags and references cause soft declinesSeparate CIT and MIT flags, network transaction reference stored and sent
Do you run the card account updater and network tokens? On which networks and countries?Reissued cards are the most avoidable failed renewalsBoth, with coverage where your customers' cards come from
What retry tools do you have, and do they respect network limits?Over-retrying costs fees and declinesRetries by decline code, blocks after Category 1, attempts counted per card
Can I export my stored cards?Without the cards, switching processor means asking every subscriber for their card againExport to another PCI-compliant vault, with a stated process
Which recurring methods do you support?Some customers prefer to pay by bank debitCards plus ACH or SEPA where you sell
What happens to my funds if disputes rise?Subscription disputes arrive in waves after renewalsReserve and review terms written in the contract

Verdict

For subscriptions, the processor's job is to keep renewals going: correct MIT flags, fresh cards and retries inside the rules. And make sure you can leave with your cards.

If you already run more than one processor, the same questions apply to the layer that sits above them: where the cards are stored, and who keeps the reference of each customer's first payment. That's covered in what payment orchestration is.

Running subscriptions across several processors

A second processor protects you if the first one reviews or closes your account. It only works for subscriptions if the stored cards can follow. A card stored in one processor's vault can't be charged through another without migrating it.

Fig. 3One card vault, several merchant accounts

Your card vaultOne stored card per subscriber, outside any single processor
  1. StripeMain account for renewals
  2. NMISecond account, same subscribers
  3. TagadaPayTakes over if an account is paused

the card stays put, the route changes

Illustrative example.

Before you move renewals to a new account, check with that processor how it handles a card first authenticated elsewhere, and send the original transaction reference where it accepts one. The retry count stays per card, whichever account charges it.

By industry

IndustryWhat changesGuide
SupplementsAuto-ship plans, claims and trial history decide whether a processor accepts the fileHow to sell supplements on subscription
SkincareRefill cycles per product and past "risk-free" trial cases shape the processor reviewHow to sell skincare products on subscription
Online pharmacyEvery refill needs a valid prescription: authorize at checkout, capture on approval, charge each refill when it shipsHow to sell prescription drugs on subscription
TelehealthCare plans and memberships are accepted with clear terms; the risk is billing a plan before a clinician reviews the caseHow to sell telehealth services on subscription
FitnessProtein, pre-workout and programs, not equipment; hidden trial terms are what close accountsHow to sell fitness products on subscription
Info productsCourse memberships, communities and monthly coaching; a fixed payment plan follows its own rulesHow to sell info products and online courses on subscription

How Tagada helps

Subscriptions that keep charging when you change processor

Tagada runs subscriptions with trials and automatic renewals. A declined renewal isn't cancelled at once: it's retried up to five times, then the subscription is cancelled (subscriptions in the Tagada docs). Cards are tokenized once in a vault that isn't tied to one processor, and each renewal is charged through the processor your payment flow selects, with a fallback when one declines (multi-processor routing in the Tagada docs). The checkout runs native 3DS2 for the first payment. TagadaPay underwrites every account and refuses deceptive trial and subscription marketing.

  • A vault you own: your PCI-tokenized cards, customer profiles and subscription data stay portable. Switch processors without re-onboarding customers. No vendor lock-in.
  • Approval routing: TagadaPay reports a +18% approval uplift from sending each payment to the processor most likely to approve it.
  • Live in 24h: one KYC, one signed package, and most merchants are live in under 24 hours.
  • From 2.9% + $0.29, no setup fees, no monthly minimums. High-risk verticals and edge cases are priced case by case.

Tagada follows Visa and Mastercard rules and the laws that apply to payments.

Apply today · Go live in under 24 hours

Nick Bonnassies

CMO at Tagada

CMO at Tagada. Before Tagada, Nick built direct-to-consumer brands that generated over $115M in sales, raised over $25M in crowdfunding and sold two of them. He also works as a fractional CMO on marketing operations and AI systems.

Frequently asked questions

How does subscription payment processing work?

The customer signs up, accepts the terms and pays the first charge, which you authorize and use to store the card as a token. On each billing date, your billing system charges that token without the customer present, flagged as a recurring merchant-initiated transaction. If the issuer declines, you retry within network limits, update the card or ask the customer to pay another way.

What is the difference between recurring payments and subscription payments?

In practice the terms overlap. Visa defines a recurring transaction as one in a series on a stored credential, at fixed regular intervals no more than a year apart. A subscription is the commercial offer behind it. Charges on a stored card at irregular times, like automatic top-ups, are unscheduled credential-on-file transactions, with their own flag.

Do subscription renewals need 3D Secure?

In the EEA and UK, the first payment or the card setup needs strong customer authentication. Renewals you charge on that mandate without the customer present are merchant-initiated and outside SCA. The issuer can still decline a renewal and ask for authentication, so keep a way to bring the customer back. Outside Europe, 3D Secure is optional.

How many times can you retry a failed subscription payment?

Visa allows up to 20 attempts in 30 days on the same card for most declines, across all your processors, and none after a Category 1 decline such as lost, stolen, closed account or revoked authorization. Stripe Billing's recommended default is 8 tries within 2 weeks. After a declined renewal, Visa also requires you to tell the customer and give them 7 days to pay another way.

What is a continuity subscription merchant?

It's Visa's merchant category 5968, Direct Marketing, Continuity and Subscription Merchants: physical goods like cosmetics, food or nutraceuticals sold on subscription through direct marketing. A merchant that simply offers recurring billing without direct marketing keeps the code of its main business. Visa lists 5968 among its high-risk codes, and processors review it closely.

Can I move my subscribers to another payment processor?

Only if you can move the stored cards. If the cards sit in one processor's vault, ask whether it exports card data to another PCI-compliant vault, and how long that takes. Keep each card's original transaction reference too: renewals sent without it can be declined. A vault you control lets you route renewals to another account without asking customers for their cards again.

Sources

Checked November 2, 2026
  1. Visa Core Rules and Visa Product and Service Rules, April 18, 2026
  2. Visa, Merchant Data Standards Manual, April 2026
  3. Stripe Docs, Save a customer's payment method when they use it for a payment
  4. Stripe Docs, Automate payment retries
  5. Stripe Docs, How cards work (automatic card updates)
  6. Stripe Docs, Payments optimization (Authorization Boost)
  7. Adyen Docs, PSD2 SCA business models overview
  8. Adyen Docs, Tokenization
  9. Commission Delegated Regulation (EU) 2018/389, RTS on strong customer authentication
  10. EBA Single Rulebook Q&A 2018_4031, payee-initiated card payments
  11. Stripe Docs, Strong Customer Authentication readiness
  12. Stripe Docs, SEPA Direct Debit payments
  13. Stripe Docs, ACH Direct Debit payments
  14. Stripe, Prohibited and restricted businesses
  15. Adyen Help Center, How can I choose the Recurring Processing Model?

TagadaPay

Selling subscriptions? Keep renewals charging on more than one processor

Tell us what you sell and how you sell it. Each application is underwritten, and approval is not guaranteed.

  1. 01Tell us what you sell and how
  2. 02Underwriting reviews your business
  3. 03Process through TagadaPay alongside your other processors