Cycles · tokens · retries · dunning

Subscription payment gateway built for renewals that survive.

Network tokens, scheme account updaters, R-code-aware retries and dunning that stops on success — on top of the same unified payments API used for one-off acceptance. One platform, one ledger, every cycle accounted for.

Book a subscription review Read the API docs
Cycles
weekly · monthly · quarterly · annual
Tokens
network-token-by-default for recurring card
Cascade
smart retries across the connected panel
1 ledger
renewals, retries, refunds in one feed

Key benefits

Why this subscription payment system pays back inside the first quarter

Four properties that move the operator's MRR retention rate the moment recurring traffic moves onto the platform.

  1. 01

    Renewals that survive re-issuance

    Network tokens via VTS and MDES plus scheme account updaters keep recurring card credentials alive across re-issuance, lost-and-stolen reissues and BIN-table changes. Subscriptions don't churn because of expired cards.

  2. 02

    Smart retries beat brute-force retries

    Failed renewals retry across the connected acquiring panel on a per-decline schedule — different acquirer, different time-of-day, different scheme path. R-code-aware retries handle bank-rail (ACH / SEPA SDD) returns specifically rather than retrying blindly.

  3. 03

    Card, ACH and SEPA on one engine

    Subscription billing runs the same renewal engine across card-on-file, recurring ACH and SEPA Direct Debit. The merchant doesn't fork billing per rail; finance reads one ledger across them.

  4. 04

    Dunning that stops the moment the renewal clears

    Recovery emails are templated per merchant, per plan and per invoice age — and stop the moment the renewal settles. Customer-facing inboxes don't get spammed past success.

How online subscription payment processing works

From plan setup to reconciled MRR in six steps

What happens between the operator defining a plan and the platform closing out the renewal cycle in the reconciliation ledger.

  1. 01

    Plan & cycle setup

    Plans, currencies, billing cycles, trial lengths and proration policy are configured in the dashboard or via API. Per-segment policies (consumer vs B2B, monthly vs annual) coexist on the same merchant record.

  2. 02

    First authorisation

    Card, ACH or SEPA SDD mandate captured through the hosted checkout, embedded fields or SDK. The vault provisions a network token (card) or stores the mandate ID (bank rail) for renewal.

  3. 03

    Cycle scheduler runs renewals

    On the cycle date the scheduler fires the renewal authorisation. The routing engine picks the best ranked provider for the BIN / scheme / currency at that moment.

  4. 04

    Smart retries on failure

    Failed renewals retry across the connected panel on a per-decline schedule. R-code-aware for ACH and SEPA SDD returns; scheme-decline-aware for card.

  5. 05

    Dunning emails (managed)

    If renewal hasn't cleared by the configured retry window, a dunning email goes to the customer with a hosted update-payment link. The cadence is per merchant / plan.

  6. 06

    Reconcile & report

    Settlements, refunds and chargebacks normalise into one reconciliation feed tagged by plan, customer, cycle and acquirer. MRR / ARR / churn reporting reads from the same source.

Main use cases

Where subscription payment solutions earn their compounding return

Six recurring merchant shapes that get more out of one subscription engine than running stitched-together billing per rail.

  • SaaS

    SaaS monthly and annual billing

    Monthly card billing on network tokens plus annual invoice or ACH for enterprise tier. Both ride the same engine; the operator doesn't run two billing systems.

  • Mbr

    Membership and community platforms

    Recurring memberships with trial periods, upgrades, downgrades and dunning sequences. Vault-based credentials make plan-change flows frictionless.

  • Med

    Media and streaming subscriptions

    High-volume monthly card renewals where every percentage point of churn matters. Network tokens plus account updaters lift renewal success per cycle.

  • Box

    Subscription box / DTC commerce

    Recurring physical-goods boxes on monthly or quarterly cycles. Pause / skip / cancel flows pre-baked into the API.

  • Edu

    Online education and courses

    Tuition payments on monthly card or recurring ACH; cohort-based start dates aligned to the cycle scheduler.

  • Util

    Utility-style and metered billing

    Metered consumption invoiced monthly, settled by recurring card or bank-rail debit; partial-payment reconciliation supported per customer.

Platform features

Capabilities behind subscription payment management on topropay

Twelve capabilities grouped into the cycle / plan engine, renewal / retry layer and reporting / finance layer. Every operator who runs subscriptions touches all three.

Cycle & plan engine

  • Plan and pricing model

    Tiers, add-ons, currencies, billing cycles and trial lengths defined per merchant; proration policy configurable.

  • Cycle scheduler

    Weekly, monthly, quarterly, annual and bespoke cycles; aligned to anniversary date or fixed billing day.

  • Trials & dunning windows

    Trial periods (auto-convert or opt-in), grace periods after failure, and dunning windows per plan.

  • Plan-change flows

    Upgrade, downgrade and proration handled in the API; vault token persists across plan changes.

Renewal & retry

  • Network tokens (VTS, MDES)

    Card credentials replaced by scheme tokens at first authorisation; the vault holds the token, not the PAN.

  • Account updaters

    Visa account updater and Mastercard ABU surfaced through the platform; recurring renewals follow updated credentials automatically.

  • Smart retries on decline

    Per-decline retry schedule across the connected acquirer panel; soft declines cascade inside the same auth too.

  • R-code-aware bank rail retries

    ACH and SEPA SDD returns parsed per R-code; NSF / R01 / R03 / R04 each retry with different policies.

Reporting & finance

  • MRR / ARR & churn views

    MRR, ARR, churn rate, involuntary churn (failed renewals) and recovery rate calculated from the same ledger.

  • Plan-tagged reconciliation

    Settlements tagged by plan, customer, cycle, acquirer and currency; daily exports as CSV or via API.

  • Webhook lifecycle events

    Signed webhooks on plan-created, customer-subscribed, cycle-renewed, renewal-failed, dunning-started, customer-cancelled.

  • Operator-side cancel controls

    Cancel flows configurable per merchant: immediate, end-of-cycle, win-back interstitial, with reason-code logging.

Industry relevance

subscription payment provider posture for licensed EU, UK, APAC and LATAM operators

topropay's subscription posture targets licensed merchants operating across Europe, the UK, APAC and LATAM — SaaS, membership platforms, streaming and media, subscription boxes and DTC commerce, online education, and metered utility-style billing. Licensed gaming subscriptions are supported only where current operating licences exist.

  • SaaS · monthly + annual
  • Membership · community
  • Streaming & media
  • Subscription boxes · DTC
  • Online education & cohorts
  • Utility-style metered billing
  • Licensed gaming · where licensed
  • Adult-content acceptance · out of scope
  • Unlicensed gambling · out of scope

Trust & compliance

Compliance posture across every subscription cycle

One audited environment for the orchestration layer; rail-specific mandate handling for ACH and SEPA Direct Debit; scheme-side stored-credential (CIT / MIT) tagging for card recurring.

PCI DSS Level 1
Card data captures into the platform vault before any acquirer sees it; sub-merchants inherit the posture across every subscription cycle.
Network tokens
PAN replaced by VTS / MDES tokens in the vault; renewals reference the token, not the underlying credential.
NACHA / SEPA mandate handling
Recurring ACH authorisations and SEPA Direct Debit mandates captured and retained per scheme rules; mandate IDs travel with each subscription.
SCA & PSD2 stored-credential rules
Recurring scheme-tagging (CIT / MIT) and PSD2 SCA exemption logic applied per renewal so subsequent cycles don't break European customers.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned per merchant vertical and recurring-volume profile.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope regardless of subscription cadence.

Ready to defend MRR

Lift renewal survival on the same platform you use for one-off acceptance.

A 30-minute subscription review covers the cycle engine, retry posture, dunning cadence and reporting that suit your plan mix — plus a sandbox you can test against before any commercial commitment.

Book a subscription review Read the API docs

Frequently asked

Operator questions about subscription payment gateway on topropay

Definitions, retry mechanics, dunning policy, multi-currency mechanics and the evaluation criteria buyers tend to weigh before choosing a subscription provider.

  1. 01

    What is a subscription payment gateway in topropay's terms?

    A subscription payment gateway in topropay's terms is the orchestration layer that handles cycle scheduling, network-token recurring credentials, smart retries across acquirers, dunning, plan-change flows and reconciliation — all on top of the same unified payments API used for one-off receipts. The gateway role and the subscription role aren't separate products; they're modes on the same platform.

  2. 02

    Which subscription payment services does the platform actually deliver?

    Subscription payment services delivered on the platform include the cycle scheduler, network-token vault, scheme account updaters, smart-retry engine, R-code-aware ACH / SEPA SDD retries, dunning email orchestration, plan-change and proration mechanics, cancel flows, MRR / ARR / churn reporting and the unified reconciliation feed.

  3. 03

    How does subscription payment processing differ from one-off processing on topropay?

    Subscription payment processing differs from one-off processing in three places: the cycle scheduler fires the authorisation (not the buyer), the credential is a vault / network token (not a card-entry surface), and the merchant uses smart-retry plus dunning instead of a hard fail-and-move-on. The underlying authorisation engine, routing and reconciliation are the same.

  4. 04

    Does topropay function as an online payment management system for subscriptions?

    Yes. The dashboard functions as an online payment management system for subscriptions — operators see active customers, plans, cycle history, retry attempts, dunning state, MRR and churn — and can act on each from the same surface. The same dashboard handles non-subscription receipts so finance reads one ledger across both.

  5. 05

    What does recurring payment management look like in practice?

    Recurring payment management in practice combines the cycle scheduler, retry engine and dunning orchestration. The operator sets policy per plan (cycle, retry window, dunning cadence, cancel policy); the platform runs the per-customer execution and surfaces failures only when they need attention rather than buried in raw logs.

  6. 06

    Is there a dedicated subscription payment platform separate from the wider product?

    No — there isn't a separate subscription payment platform. The same platform handles one-off, invoice, POS, recurring and subscription billing through one merchant record. What changes per use-case is dashboard configuration and API surface usage, not a different product the merchant has to onboard to.

  7. 07

    What about subscription payment software for finance and customer-success teams?

    The subscription payment software side — what finance and customer-success see — is the dashboard plus the API. Finance reads MRR / ARR, churn, recovery rate and tax-aware reconciliation; customer-success acts on individual customers (extend trial, refund cycle, override dunning, cancel reason capture). The same data feeds both.

  8. 08

    How does the subscription payment system handle dunning?

    The subscription payment system handles dunning via templated, merchant-branded emails sent on a per-merchant, per-plan, per-invoice-age cadence after a renewal fails. Each email contains a hosted update-payment link tied to the same vault token. Dunning stops the moment the renewal clears (whether automatically retried or manually updated).

  9. 09

    Does subscription payment management work across multiple currencies?

    Yes. Subscription payment management is multi-currency at the plan level — different customer cohorts can be billed in USD, EUR, GBP, AUD and other supported currencies. Reconciliation rolls up by currency and by plan; conversion-on-receipt is optional through partner FX routes.

  10. 10

    What does online subscription payment processing actually do at renewal time?

    Online subscription payment processing at renewal time fires an authorisation against the stored vault / network token, routes it through the connected acquirer panel via the scoring engine, and (on failure) executes the retry policy plus dunning. The customer experience is the existing service continuing to work; the operator experience is silent unless attention is required.

  11. 11

    How do I evaluate a subscription payment provider for my business?

    Evaluation criteria that matter most for a subscription payment provider are: network-token + account-updater support (renewal survival), retry-policy granularity (R-code-aware for bank rails), reconciliation tagging (plan + customer + cycle), dunning flexibility (no spam after success), and per-provider routing weights (cost / approval tuning). topropay's posture is built around exactly these dimensions.

  12. 12

    What's the difference between online subscription payment and one-off online payment?

    Online subscription payment differs from one-off online payment in that subsequent charges run without the customer at the keyboard. That distinction drives scheme-side rules (CIT / MIT tagging), the absence of step-up authentication on subsequent cycles, and the operator-side retry / dunning flow. The infrastructure for the first authorisation is identical between the two.

  13. 13

    Does the subscription payment model on topropay support hybrid one-off + recurring?

    Yes. The subscription payment model on topropay supports hybrid setups — base subscription with one-off add-ons (a usage-based overage charged in-cycle, a one-time setup fee, a one-off upgrade purchase). Vault tokens persist across both modes; the customer doesn't re-enter card details.

  14. 14

    What subscription payment solutions are best for a high-volume monthly billing operator?

    Subscription payment solutions for a high-volume monthly billing operator combine network-token recurring (card-side renewal survival), R-code-aware ACH or SEPA SDD as a lower-cost rail for repeat customers, scheme account updaters by default, and a dunning cadence tuned to each customer cohort's response window. topropay defaults to all four; per-segment customisation is dashboard-driven.

  15. 15

    How does monthly subscription payment processing compare to annual?

    Monthly subscription payment processing fires 12 renewals per year, so the marginal improvements from network tokens, account updaters and smart retries compound. Annual subscription payment processing has one renewal but a larger ticket per cycle, which makes the failure cost per attempt higher — so the retry / dunning posture matters more relative to volume even though absolute volume is lower.

Related

Related on the topropay platform