1. Home
  2. ConvesioPay
  3. Subscriptions & Recurring Revenue
  4. Subscription Payment Processing: The Complete Guide for Recurring Businesses
  1. Home
  2. ConvesioPay
  3. Subscription Payment Processing: The Complete Guide for Recurring Businesses

Subscription Payment Processing: The Complete Guide for Recurring Businesses

Subscription payment processing is fundamentally different from one-time transactions. Recurring billing requires tokenized payment storage, merchant-initiated transaction flagging, smart retry logic, and involuntary churn management — all of which standard payment setups don’t handle automatically. This guide covers what subscription businesses need from their payment infrastructure and how to build it right.

ConvesioPay supports subscription payment processing for WooCommerce — stored credentials, MIT flagging, Account Updater, and dunning tools built in through Adyen’s infrastructure. Get started →


1. How Subscription Payment Processing Works

A subscription payment flow has two distinct phases:

Initial Transaction (Customer-Initiated)

The customer enters their payment details and authorizes the first charge and all future recurring charges. This transaction must include explicit stored credential consent — a declaration to the card network that the customer is authorizing future charges. Technically, this is a “Customer-Initiated Transaction with stored credential establishment” (CIT-SC).

Subsequent Transactions (Merchant-Initiated)

Every renewal after the first is a “Merchant-Initiated Transaction” (MIT) — the merchant charges the stored token without the customer actively participating. These must be flagged correctly in the authorization request, referencing the original CIT transaction ID. Processors that don’t implement this correctly see higher decline rates on renewals because issuers treat unrecognized MITs as potentially unauthorized charges.


2. Payment Tokenization for Subscriptions

The gateway stores a secure token — not the actual card number — representing the customer’s payment method. This token is used to authorize future charges without re-entering card details.

Token types matter for subscription performance:

  • Gateway tokens — stored by your payment processor; work only with that processor
  • Network tokens — issued by Visa or Mastercard; survive card replacement (if the customer’s card is reissued after loss/theft, the network token remains valid). Network tokens significantly reduce involuntary churn caused by card changes

ConvesioPay through Adyen supports network tokenization — a key advantage for subscription businesses where card reissuance is a major churn driver.


3. Billing Cycles and Proration

Common billing cycle configurations:

  • Fixed date billing — all subscribers billed on the same date (e.g., 1st of the month). Simplifies cash flow forecasting; requires proration when subscribers join mid-cycle
  • Anniversary billing — each subscriber billed on the date they originally signed up. No proration needed; billing distributed across the month
  • Usage-based — billing calculated based on actual usage metrics; charged at end of billing period

Proration handles the billing adjustment when a subscriber upgrades, downgrades, or joins mid-cycle. WooCommerce Subscriptions supports immediate proration (charge/credit the difference now) or next-renewal adjustment.


4. Dunning Management

Dunning is the process of recovering revenue from failed recurring payments. Industry data suggests 20–40% of subscription churn is “involuntary” — the subscriber didn’t intend to cancel, but their payment failed and the subscription lapsed. Effective dunning recovers a significant portion of this revenue.

Smart Retry Logic

Don’t retry failed payments immediately or on a fixed schedule. Optimize retry timing based on failure reason:

  • Insufficient funds (soft decline) — retry 3–5 days later (near end of billing period when funds are more likely available)
  • Do not honor (generic soft decline) — retry after 24 hours, then again at 3 days
  • Card expired — email the subscriber to update payment details; retry is unlikely to succeed without a new card
  • Card stolen/blocked (hard decline) — don’t retry; email subscriber immediately to update payment method

Subscriber Communication

  • Email immediately after first failure — many subscribers update payment details when notified promptly
  • Send reminder before automatic cancellation — give subscribers a clear deadline and a direct link to update payment info
  • Consider SMS for high-value subscriptions — higher open rates than email

Account Updater

Adyen’s Account Updater automatically receives updated card details from Visa and Mastercard when a cardholder’s card is reissued (new number, new expiry). This prevents failures caused by card replacement — one of the most common involuntary churn causes — without any subscriber action required.


5. SCA and Subscription Billing in Europe

EU merchants must comply with PSD2 Strong Customer Authentication (SCA). For subscriptions, the rules are:

  • Initial transaction — must be SCA-authenticated (3DS2 challenge or frictionless)
  • Subsequent recurring transactions — exempt from SCA if properly established as MIT during the initial checkout. The key is that the initial transaction must correctly flag the stored credential establishment

Gateways that don’t implement MIT flagging correctly may face SCA challenges on renewals — causing failed payments for EU subscribers even when the subscription was properly authorized.


6. Key Metrics for Subscription Payment Health

  • Authorization rate — percentage of renewal charges that succeed on first attempt; target above 90%
  • Recovery rate — percentage of initially failed charges recovered through dunning retries
  • Involuntary churn rate — percentage of subscribers lost due to payment failure vs. active cancellations
  • Average retries to recover — how many retry attempts are needed to recover a failed payment

For authorization rate optimization tactics, see Authorization Rate Optimization: How to Reduce Declined Payments.

ConvesioPay’s subscription billing infrastructure handles MIT flagging, network tokenization, and Account Updater automatically — so your WooCommerce subscription business recovers more revenue and retains more subscribers. Get started →

Updated on June 17, 2026

Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? we’re here to help!
Contact Support