Something broke in payments and nobody talks about it.
Every software platform that gets big enough eventually hits the same wall. A customer says "we need to take payments inside this." Could be a voice call. Could be an invoice workflow. Could be an AI agent having a conversation with a customer who's ready to pay.
And the platform team sits down and asks: how do we do this?
The answers they get are all bad.
The Three Bad Options
**Option one: pick a PSP and build the integration.** Stripe, usually. It works for the first customer. Then the second customer needs Adyen because that's their existing contract. The third needs Worldpay because their compliance team mandates it. By the fifth customer, payments are eating the product roadmap alive. Every new provider is a separate integration, a separate certification process, a separate maintenance burden. The engineering team that was supposed to be building the platform is now building payment plumbing.
**Option two: become a payment company yourself.** Get a PayFac licence. Build the compliance infrastructure. Hire a payments team. This takes 12-18 months and costs millions. And at the end of it, you're no longer a software company with payments. You're a payment company that happens to have software. The thing that made you valuable — the platform, the workflow, the customer relationship — is now secondary to the thing you were forced to build.
Option three: do nothing. Tell customers to figure it out themselves. This works until it doesn't. Until a competitor offers payments natively. Until the enterprise deal falls through because you can't support their PSP. Until the AI agent you spent two years building hits a dead end the moment money is involved.
Every platform team picks one of these three doors. Every one of them regrets it.
The Problem Isn't That Payments Are Hard
The problem is that the infrastructure doesn't exist.
Gateways process transactions. They're designed for merchants, not platforms. They don't handle multi-tenancy. They don't span channels. They lock you into one provider.
Orchestrators route between gateways. Better, but still merchant-facing. Still checkout-page-centric. Still require heavy integration. They optimise transaction routing — useful for a merchant with three gateways, irrelevant for a platform that needs to support whatever PSP each of its customers already uses.
PayFac models — Stripe Connect, Adyen for Platforms — make you the payment company. That's not a solution. That's a career change.
What's missing is a layer.
Three Shifts That Created the Gap
1. Software owns distribution
Vertical SaaS platforms control merchant workflows now. Talkdesk controls the contact centre. INSTANDA controls insurance operations. The merchant lives inside the software. Whoever controls the software controls the payment moment. But the payment industry still sells to merchants one by one — not through the software that already has them.
2. PSPs can't get inside software
PSPs have money and processing capability. Platforms have distribution and the customer relationship. The two sides need each other. But there's no clean way to connect them. Embedding a PSP inside a platform requires significant integration work. Supporting multiple PSPs requires multiples of that work. The math doesn't work.
3. Commerce is escaping checkout pages
Payments are moving into voice calls, AI agent conversations, messaging, field workflows, embedded finance flows. A customer calls a contact centre and wants to pay mid-conversation. An AI agent handles a collections call and needs to close the payment before the caller hangs up. None of these are checkout pages. None of them work with infrastructure designed for checkout pages.
The Payment Layer
What's missing is simple to describe: a thin piece of infrastructure that sits between software platforms and PSPs.
The platform integrates once. The layer handles PSP routing per customer, PCI compliance, merchant onboarding, and payment capture across every channel — voice, links, chat, embedded checkout, workflows.
The platform doesn't become a payment company. The PSP gets distribution inside software it couldn't reach before. The end customer uses whatever payment provider they already have.
This is The Payment Layer.
It's to payments what the CDN was to content delivery, or what Twilio was to communications. Portable, modular, usage-based infrastructure that software platforms plug into — not projects they build.
What Makes The Payment Layer Different
Gateway | Orchestrator | PayFac | Payment Layer | |
|---|---|---|---|---|
What it does | Processes transactions | Routes between PSPs | Makes you the PSP | Embeds payments inside software |
PSP relationship | Is the PSP | Sits above PSPs | Replaces the PSP | Distributes PSPs |
Who it serves | Merchants | Merchants | Platforms wanting to be PayFacs | Platforms wanting to NOT be PayFacs |
Channels | Checkout page | Checkout page | Checkout page | Voice, links, chat, embedded, workflows |
Time to live | Weeks | Months | 6-12 months | Days to weeks |
PCI scope | Merchant owns it | Merchant owns it | Platform owns it | Layer owns it |
The Payment Layer is not a better gateway. It's not a better orchestrator. It's a different thing — designed for a different problem.
For the full comparison, see our Gateway vs Orchestrator vs PayFac vs Payment Layer guide.
Why We Built It
We built Shuttle because we kept watching the same pattern repeat.
A platform would win an enterprise deal. The customer wanted embedded payments. The platform would start with Stripe Connect or build a direct PSP integration. It would work for three months. Then the next customer needed a different PSP. Then the contact centre team needed voice payments. Then the AI voice agent needed to take a card number mid-conversation.
Each of these moments was a separate project. A separate integration. A separate compliance exercise. By the time the platform had covered three PSPs and two channels, they'd spent a year and burned through engineering budget that was supposed to build their core product.
The Payment Layer collapses all of that into one integration. 40+ PSPs. Voice, links, chat, embedded checkout. PCI DSS Level 1 handled by the layer. White-label merchant onboarding and portals. The platform stays a platform.
We're live on Twilio's Marketplace. We power AI voice payments for PolyAI. We support platforms across CCaaS, insurance, field service, travel, and fintech. Every one of them integrated once and ships new payment capabilities without new projects.
What Happens Next
The category is forming whether any single company defines it or not. The market forces are too strong.
Software owns distribution. PSPs need access. Commerce is escaping checkout pages. Something has to sit in between.
Platforms that adopt The Payment Layer ship payments in weeks. They support any PSP their customers need. They expand into voice, links, AI agents — without new integration projects. They stay platforms.
Platforms that don't adopt it keep building. Keep hiring. Keep diverting engineering resources from their core product into payment infrastructure that someone else should own.
The only question is who builds the layer and who gets left building plumbing.
*Shuttle is The Payment Layer for software platforms. One integration. 40+ PSPs. Voice, links, chat, and embedded checkout. See how it works or book a discovery call.*