Why a payment processor and a payment orchestration platform are not the same thing — and why the gap between them is where recurring revenue leaks out.
Most businesses believe they've solved payments the moment they've signed with a PSP.
The processor is live, cards are being charged, money is landing in the account. Payments feel done.
And for a single one-off transaction, they are. But recurring revenue isn't a single transaction. It's the same relationship, billed again and again, across methods and markets and edge cases the PSP was never designed to manage.
That's the missing layer. And most businesses don't notice it's missing until churn shows up.
A payment service provider does one thing extremely well: it moves a payment from A to B.
A customer pays, the PSP authorises, captures, and settles. It's the plumbing — essential, reliable, and largely invisible when it works.
But notice what that definition assumes: a payment already exists, ready to be processed.
The PSP doesn't decide how to get a hesitant customer to sign up. It doesn't decide what to do when a mandate fails, or a card expires, or a direct debit bounces. It doesn't switch a customer from one method to another. It processes what it's handed.
A PSP answers "can this payment go through?" It doesn't answer "how do we keep this customer paying?"
The problems that kill recurring revenue almost never happen at the processing step. They happen around it.
None of these are processing failures. They're orchestration failures. And a PSP, by design, doesn't own any of them.
That's why "we have a PSP" and "we've solved recurring payments" are two very different statements.
Payment orchestration is the layer that sits above processing and manages everything the PSP leaves untouched.
It owns the parts that actually determine whether recurring revenue holds:
Processing is a component inside that. Orchestration is the system that makes the component useful for a recurring business.
As businesses add markets, methods, and channels, the gap between processing and orchestration gets wider — and more expensive.
Bolt a second PSP on for a second market and you've now got two integrations, two sets of exceptions, two reconciliation flows, and no single view of the customer. Scale that across the Nordics and the complexity compounds faster than the revenue.
The orchestration layer is what collapses that back down: one API across Autogiro, AvtaleGiro, Betalingsservice, SEPA Direct Debit, card, and invoice, with a single place to manage the exceptions.
PSPs let you take a payment. Orchestration lets you keep the customer.
If churn is creeping up, exceptions are eating your support team's time, or every new market feels like starting over — the problem usually isn't your processor.
It's the layer above it that was never there.
Recurring businesses need both. Most have only noticed the first.
Stop asking whether your payments go through. Start asking whether your customers keep paying.
That's the layer worth owning.
That's how you #killbill.