Insurance core platforms make money from licensing, implementation, and support. The business model is well-understood. Annual contracts. Per-policy or per-user pricing. Professional services for deployment and customisation.
What most platform companies don't realise is that they're sitting on a revenue line that requires zero additional engineering headcount, compounds with every new carrier, and generates margin from day one.
Payment execution.
The Math
Every insurance premium — new business, renewal, overdue collection — is a transaction. When that transaction flows through the platform, the platform participates in the payment economics.
The mechanics are straightforward: the platform earns a revenue share on each transaction processed through its embedded payment capability. The share varies by PSP, by volume, and by negotiation — but the principle is constant. Money moves through the platform. The platform takes a cut.
Consider a mid-size insurance core platform:
50 carriers on the platform
Average 10,000 policies per carrier with annual premiums
Average premium: £600/year collected in monthly installments
That's £300M in annual premium volume flowing through the platform
Even a modest revenue share on that volume generates millions in annual recurring revenue — with no additional engineering, no additional sales, and no additional support burden beyond the initial integration.
Why This Revenue Line Doesn't Exist Today
Most insurance platforms don't capture payment revenue because they don't execute payments. The billing module manages what's owed. The carrier collects the money separately — through a portal, a phone call, a paper process. The platform has no visibility into the transaction and no participation in the economics.
This isn't a deliberate decision. It's a structural gap. The infrastructure to embed multi-PSP, multi-channel payment execution into a platform — while handling PCI compliance, carrier onboarding, and per-carrier PSP routing — didn't exist until recently.
The result: billions in insurance premiums flow around the platform every year. Not through it.
What Changes With Native Payment Execution
When premium collection flows through the platform, three things happen:
1. Revenue share activates. Every renewal, every overdue collection, every new policy inception that processes through the platform generates margin. This is not project revenue. It's recurring, volume-based, and grows with the platform's carrier base.
2. Carrier stickiness increases. A carrier whose premium collection is embedded in the platform has a deeper integration than one whose billing is managed but payments happen elsewhere. Switching costs rise. Contract renewals become easier. Expansion conversations start from a stronger position.
3. Competitive differentiation sharpens. When two insurance core platforms compete for a carrier, the platform that offers native payment execution — voice, links, embedded checkout, any PSP — has a structural advantage over the one that says "you'll need to figure out payments separately."
The Competitive Angle
Insurance core platforms compete on depth of functionality. Policy administration is table stakes. Billing is table stakes. Claims management is expected.
Payment execution is not yet table stakes. It's a differentiator.
The platform that adds it first in a given segment — P&C, life, specialty, or commercial — captures an advantage that compounds over time. Every carrier that onboards with native payment execution is a carrier that's unlikely to switch.
And as AI voice agents become standard in insurance contact centres — handling renewals, collections, and claim payments autonomously — payment execution becomes inseparable from the platform. The AI agent lives inside the platform. The payment must live there too.
Why Not Build It?
Some platform teams consider building payment execution in-house. The thinking: "We already have billing. Adding payment capture is just one more module."
The reality is different:
PCI DSS Level 1 certification costs $2M+ to achieve and maintain annually
Multi-PSP integrations require building and maintaining connections to every PSP each carrier uses — 10 carriers might mean 8 different processors
Voice payment infrastructure requires DTMF capture, audio segmentation, and telephony integration — a separate engineering discipline
Ongoing maintenance across API version changes, certification renewals, and incident response consumes engineering capacity indefinitely
The build cost diverts 12+ months of engineering from core platform development. The ongoing cost never goes away.
The alternative: integrate once with The Payment Layer. 40+ PSPs supported. Voice, links, embedded checkout. PCI DSS Level 1 handled by the layer. New carriers onboard in days. Average savings: $360K annually, $2M in PCI costs eliminated, 12 months of development time recovered.
For the full analysis of how platforms monetise embedded payments, see How Platforms Monetise Payments Without PSP Lock-In.
One Platform's Experience
An anonymised insurance core platform — one of the leading policy administration systems in the market — embedded Shuttle's Payment Layer into their platform. The integration took weeks. Within months:
Premium collection was live across multiple carriers, each using their own PSP
Voice payments were active in carrier contact centres
Payment links reduced overdue premium delinquency rates
Payment revenue became a new line item in the platform's P&L
No new hires. No PCI audit. No multi-quarter engineering project.
The premium volume that had been flowing around the platform started flowing through it. The revenue followed.
*Shuttle is The Payment Layer for insurance platforms. One integration. Any carrier's PSP. Voice, links, and embedded checkout. See how it works for platforms or book a discovery call.*