The Payment Orchestration Guide
Search the guide: retries, failover, 3D Secure…
FIND YOUR WAY
Start with your role
Four ways in, depending on what you need to know.
FREE TOOL
Work out what it is worth
Authorization lift calculator
Enter your own numbers to see what a better authorization rate and lower fees could be worth to your subscription business. It takes a minute.
Try the calculator ->
Extra revenue per year (example)
£120,000
20,000 renewals a month, £25 each, 88% authorized, 2 points better.
Payment orchestration, explained properly
For the people who run payments at scale.
Payments at scale are messy: different processors, cards, countries and rules, and a decline that could be a blip or a permanent no. For a subscription business the stakes are higher, because every renewal is a payment that can fail. Payment orchestration is the layer that makes sense of it, deciding where each payment goes and what happens when it fails.
This guide starts with the first definition and runs all the way to failover architecture. Read it in order, or search for the exact question you have. Every term is explained in plain English, and the glossary covers 91 of them.
FOR SUBSCRIPTION BUSINESSES
The benefits of payment orchestration for subscription businesses
Orchestration puts one layer between your subscription billing and your payment providers. Here is what that gives you.
Higher authorization rates
Each payment goes to the processor most likely to approve it, based on card type, currency or region. If a payment fails, it is retried through a backup, so fewer renewals are lost.
Lower processing costs
Payments take the lowest-cost route, and you are no longer tied to a single provider, which gives you leverage to negotiate better rates.
Global expansion
Reach new markets through one integration, and offer the local cards, bank transfers and wallets your customers prefer.
Resilience
If a provider has an outage, payments move to another automatically. One integration and one dashboard replace a patchwork of connections.
Compliance and risk
Keep pace with standards such as PCI DSS, PSD2 and GDPR, and add fraud checks to the payment flow before authorization.
PART 1 · FOUNDATIONS
What payment orchestration is, and why it exists
Start here. The core idea, the problems it solves and where it sits in your payment stack.
What is Payment Orchestration?
A clear, practical definition of payment orchestration
Read the guide ->
The Problems Payment Orchestration Solves
The operational and technical issues orchestration is designed to fix
Read the guide ->
Where Payment Orchestration Sits in the Payment Stack
Understanding how orchestration fits alongside billing, PSPs and gateways
Read the guide ->
PART 2 · CAPABILITIES
What an orchestration layer actually does
Routing, retries and failover, and how they work together to keep payments flowing.
Core Capabilities of Payment Orchestration
The functional building blocks of a payment orchestration layer
Read the guide ->
Designing Payment Recovery at Scale: Retries, Cascading, and Revenue Stability
Most failed subscription payments are recoverable. The difference between fragile and resilient SaaS businesses lies in how recovery logic is designed, governed, and observed.
Read the guide ->
Failover: designing resilient execution at scale
At enterprise scale, routing stops being a configuration detail and becomes a resilience strategy.
Read the guide ->
PART 3 · FIT & RELEVANCE
Is payment orchestration right for you?
Who benefits most, and how orchestration differs from gateways, PSPs and billing systems.
PART 4 · OUTCOMES
What to expect, and what to watch out for
The benefits and return, alongside the misconceptions and pitfalls.
PART 5 · IMPLEMENTATION
Choosing a platform and building for resilience
How to evaluate platforms, and what resilient failover looks like in practice.
How to Choose a Payment Orchestration platform
What to look for when evaluating orchestration platforms
Read the guide ->
Payment Processor Failover Architecture: The Engineering Guide to 99.99% Uptime for SaaS Billing
Build redundancy into your payment infrastructure to eliminate revenue loss from processor outages
Read the guide ->
PART 6 · ADVANCED
Recovery and retries at scale
Why retries fail at scale, and how to design dunning that recovers revenue.
Why Payment Retries Fail at Scale (And What Actually Works)
Why retries, dunning and single-PSP setups stop working — and what scalable SaaS teams do differently
Read the guide ->
The SaaS Dunning Strategy Playbook: A Framework for Recovering Failed Payments
How to structure your retry logic, timing, and communications to maximise payment recovery — without damaging customer relationships
Read the guide ->
PART 7 · PLAYBOOKS & BENCHMARKS
Benchmarks, playbooks and how-tos
Numbers to measure yourself against, and practical playbooks for cutting failures and churn.
SaaS Payment Failure Rate Benchmark: What's Normal, What's a Problem, and How to Diagnose Yours
What a healthy payment failure rate looks like at scale — and a step-by-step diagnostic for finding out where yours is leaking
Read the guide ->
SaaS Chargeback Rate Benchmark and Reduction Checklist
What a healthy chargeback rate looks like for SaaS — and the 12 operational steps to stay well clear of the danger zone
Read the guide ->
How to Reduce Payment Failure Rate in SaaS: The Operational Approach
Why payment failures are a structural problem at scale — and the operational interventions that actually move the number
Read the guide ->
How High-Growth SaaS Companies Reduce Payment Failures at Scale
Why retries, dunning and single-PSP setups stop working and what scalable SaaS teams do instead.
Read the guide ->
How to Reduce Involuntary Churn in SaaS: The Operational Playbook
Involuntary churn is recoverable revenue — but only if your operational layer is built to catch it before it becomes a cancellation
Read the guide ->
Involuntary vs. Voluntary Churn in SaaS: Definitions, Benchmarks, and Measurement Framework
A clear reference guide for understanding, separating, and measuring the two types of SaaS churn — and why the distinction changes everything operationally
Read the guide ->
REFERENCE
The A–Z glossary
Every term you’ll meet in payment orchestration and SaaS billing, explained in plain English. From 3D Secure to zero-amount authorisation: 91 terms, one page.
3D Secure (3DS)
An extra authentication step for card payments.
Acceptance rate
The share of payment attempts that banks approve.
Cascading
Retrying a declined payment through another provider.
Dunning
Retrying failed payments while keeping customers informed.
Idempotency
Making sure a repeated request never double-charges.
Soft decline
A temporary failure that may succeed on retry.
Frequently asked questions
What is payment orchestration?
Is payment orchestration the same as a payment gateway or PSP?
Who needs payment orchestration?
What are the main benefits?
How do I choose a payment orchestration platform?
