The payment reality of SaaS and subscriptions
Involuntary churn is the quiet kind: a subscriber who wants to stay loses access because a renewal didn't authorize, not because they cancelled. It looks like churn in a dashboard, but it's a payments problem, and it's usually fixable at the routing layer rather than the product layer where teams instinctively go looking first.
Global subscribers add a second failure point — a card-only checkout excludes subscribers in markets where cards aren't the default way to pay. And plan changes, upgrades, downgrades and proration are where billing logic quietly breaks: a mid-cycle change that's billed wrong shows up as a support ticket or a dispute, not as a clean adjustment nobody has to think about twice.
Most churn dashboards can't tell you a renewal simply failed to authorize. Ours can.
How CyberPay helps
Four capabilities, built around where subscription revenue actually leaks: a renewal that didn't authorize, a subscriber a card-only checkout excludes, or a plan change billed wrong. Each capability targets a specific point where subscription revenue actually leaks, rather than a generic billing feature list.
Renewal authorization routing
Each renewal routed to the acquirer best placed to authorize it, reducing the share of churn that's actually a failed payment rather than a genuine cancellation. That routing runs quietly in the background on every billing cycle, without product or support teams having to intervene.
Local methods for global subscribers
The methods each subscriber's market uses, added alongside cards, so signup isn't gated by card ownership in markets that bank differently.
Upgrades, downgrades and proration
Plan changes billed correctly mid-cycle, handled on the same platform as regular renewals rather than a separate billing workaround. A downgrade mid-cycle is credited correctly rather than left for a subscriber to notice and dispute later.
Multi-currency pricing
Subscriptions priced and billed in the subscriber's own currency where supported, instead of a single global price that converts awkwardly.
Methods and markets
Subscription billing needs to authorize reliably on every renewal, across whichever methods a subscriber base actually uses:
- Cards, Apple Pay and Google Pay — for the majority of subscription billing, routed for authorization.
- Local bank methods and Open Banking — for subscribers in markets where a card isn't the default.
- Multi-currency billing — subscriptions priced and charged in local currency where supported.
- Renewal authorization routing — each renewal sent to the acquirer that performs best for it.
CyberPay covers 73 markets across 6 regions — see the full coverage map.
Renewals, upgrades, downgrades and refunds all reconcile on one platform, so finance sees one clean picture of recurring revenue rather than several partial ones.
Integration
A SaaS platform can bill through the Hosted Cashier for the fastest path to launch, or call the Direct API to keep billing inside its own product. Renewals, upgrades, downgrades and refunds run on the same integration, with Query-Transactions for reconciliation. Test renewal and proration logic against the sandbox before going live.
Use cases
Three ways subscription businesses use CyberPay to reduce involuntary churn and bill correctly across markets and plan changes as the subscriber base grows. Each business bills differently, but all three depend on the same reliable renewal routing underneath.
A B2B SaaS expanding to new regions
A B2B platform signing customers in new regions adds the local payment methods and currencies each region expects, without building a separate billing system per market from scratch.
A consumer app with monthly plans
A consumer subscription app routes every renewal for the highest chance of authorization, reducing the share of monthly churn caused by a payment that simply didn't clear rather than a subscriber choosing to leave.
A usage-billed platform
A platform billing by usage rather than a flat plan handles variable charge amounts and proration through the same integration used for standard renewals, without a second billing system bolted on.
Frequently asked questions
How does recurring billing work?
Every renewal is routed to the acquirer best suited to clear it, and failed renewals are visible in reconciliation immediately. Retry and routing logic runs automatically on every renewal attempt, with no manual configuration per subscriber.
What happens when a renewal fails?
A failed renewal shows up in reconciliation right away, distinct from a genuine cancellation, so it can be addressed before it's counted as churn.
What currencies can we bill in?
Subscriptions can be priced and billed in the subscriber's own currency across served markets — see the full coverage map.
How are plan changes and proration handled?
Upgrades, downgrades and mid-cycle proration are billed on the same platform as regular renewals, not through separate logic. Proration is calculated at the time of the plan change, not estimated after the fact.
We're migrating from another processor — what does that involve?
Talk to us about your current billing setup; migration is scoped around your existing subscriber base and renewal cycles.
Ready to stop losing subscribers to failed renewals?
One integration for renewal authorization routing, local payment methods and clean proration.