Policy administration systems are the operational heart of insurance carriers and MGAs. They underwrite, rate, bind, endorse, renew, cancel, and adjudicate claims. They issue the invoices for premium and they record the disbursements on claims. What they generally do not do is execute the underlying money movement.
Premium collection happens through a separate billing portal, a separate IVR, a separate cards-on-file system or a separate direct debit bureau. Claims disbursement happens through the carrier's treasury workflow, a separate ACH/Bacs file, sometimes a third-party prepaid card vendor. The PAS sits at the centre of the policy lifecycle but cedes the moment of money movement to a perimeter of point solutions.
That perimeter is increasingly the bottleneck. New product launches stall on payment configuration. Cross-border programmes hit acquirer constraints. MGA delegated authority programmes need flexible per-MGA routing that the carrier's central infrastructure was never designed to support. And the customer-experience expectation, driven by personal lines disruption and embedded insurance, is for premium and claims flows that feel native, not bolted on.
This guide is for PAS vendors, MGA platforms, carrier platform teams and the technology partners that serve them, and how Shuttle's Payment Layer fits into the PAS workflow as a single embedded payment layer.
Why PAS Platforms Don't Execute Payments
PAS vendors built deep expertise in policy administration. Payment execution is a separate discipline with separate certifications.
PCI scope. Card data inside a PAS environment triggers PCI DSS scope across the policy, claims and customer master systems. That's a multi-year compliance project layered on a platform that was certified for other things.
Acquirer relationships are carrier-specific. A regional carrier has Worldpay. A national carrier has Adyen. A specialty MGA has Chase. A direct-to-consumer brand uses Stripe. The PAS serves all of them. Forcing a single processor through the platform is commercially impossible: the carriers already have their merchant pricing negotiated.
Multi-jurisdictional payment methods. Premium collection in the UK leans on direct debit (Bacs). The US uses ACH for recurring and card for one-off. Continental Europe needs SEPA. Latin America wants local debit and instalments. Each method has different mandate, dispute and reconciliation rules. The PAS team isn't staffed to maintain that breadth.
Claims disbursement is regulated. Paying a claim is a regulated activity in most jurisdictions: anti-money-laundering checks, beneficiary verification, sometimes tax withholding. PAS vendors aren't licensed money-services businesses and don't want to be.
The result: the PAS handles every part of the policy except the moment money changes hands.
What "Carrier-Side" Payments Look Like
Carrier and MGA payment flows differ structurally from broker-side or distribution-side payments. A useful distinction.
Premium collection. Recurring, mandate-driven, often multi-instalment, often net of premium financing. Payment frequency tied to policy cadence (monthly, annual, mid-term endorsements). Direct debit dominant in some markets, card dominant in others. First-payment-on-bind is often card while ongoing collection switches to direct debit.
Mid-term adjustments. Endorsement-driven pro-rata charges and refunds. Often the friction point: refunds in particular are slow and manual in most legacy stacks. Modern PAS deployments expect these to be near-instant from the customer's perspective.
Renewal collection. Annual or semi-annual cycle, often the moment of churn. Friction at renewal (declined cards, expired mandates, payment-method changes) is a leading cause of involuntary lapse. Smart retry and proactive mandate maintenance materially reduce lapse rate.
Claims disbursement. Outbound payments to policyholders, repair networks, healthcare providers, replacement vendors. Faster Payments / RTP / instant payouts increasingly expected in personal lines. Bulk-file ACH/Bacs still the default in commercial and specialty.
Premium financing reconciliation. Where the policy is financed (especially commercial lines and high-premium personal), the PAS reconciles between the financing provider and the underwriter. Payment infrastructure has to settle correctly to two counterparties.
MGA delegated authority programmes. The carrier's PAS may host multiple MGAs with delegated underwriting authority, each with its own brand, its own premium collection, its own bank account, sometimes its own acquirer relationship. The platform needs per-MGA routing without per-MGA engineering.
A payment layer that supports the collection side of these (card, direct debit, ACH/Bacs, SEPA, multiple acquirers and multi-MGA segregation) is the unlock. Most PAS vendors haven't built one because it's a different platform underneath.
Where Shuttle Fits Inside a PAS
Shuttle integrates with the PAS as the payment layer behind the policy and billing modules.
Inbound premium collection. At bind, at endorsement, at renewal, the PAS calls Shuttle to capture or charge. Hosted payment pages, mandate capture, card-on-file collection: all branded for the carrier or MGA, all routed to that entity's chosen PSP. Webhooks reconcile to the policy record in real-time.
Direct debit / ACH / SEPA mandates. Mandate capture and schedule execution. The PAS owns the policy schedule; Shuttle executes it. Failed payments surface back as exceptions on the policy record, and any chasing is yours to build, for example with payment links plus Zapier or Make.com, or through the API.
Voice channel premium collection. Call centres handling renewal calls, hardship cases and mid-term endorsements often capture payment on the call. Shuttle's Voice Checkout runs on Twilio Pay today (voice requires being a Twilio customer), capturing the card in a secure PCI DSS Level 1 flow so card data never enters the carrier's contact centre. There is no native CCaaS integration: the carrier builds the agent-side trigger against Shuttle's APIs. One honest caveat: full-call presence is not available today; returning the caller to the same agent after payment works today when the carrier builds the return route in Twilio and passes a conversation ID. Shuttle works with Twilio today, and any carrier coming soon.
Multi-MGA routing. Each MGA configured on the PAS has its own brand, its own acquirer, its own settlement account. Each MGA is configured against their own gateway and settles per the MGA's commercial agreement. The PAS doesn't carry MGA-specific integration code.
AI voice agent collection. Carriers running AI voice agents in their contact centres can capture payment securely at the point of payment rather than escalating to a human. The carrier builds its own agent interface against Shuttle's APIs. See PCI-compliant payments for AI voice agents for the architecture pattern.
How This Differs From The Insurance Core Platform Guide
This guide deliberately separates carrier and MGA platform patterns from the broader insurance core platform pattern and the broker / distribution-platform pattern. The audiences and the workflows are different.
A broker platform is distributing policies sold by underwriters. The payment flow on a broker platform is typically a first-money collection at the point of sale and a hand-off to the underwriter's collection cycle thereafter.
A carrier / MGA platform (what most PAS vendors serve) is the underwriter. Premium collection is the full lifecycle, claims disbursement is core, regulatory and treasury obligations attach to the carrier rather than the distributor. Payment infrastructure has to support the full set, not just the point-of-sale moment.
The PAS vendors building modern carrier and MGA infrastructure are the platforms this guide is written for.
Why Carriers Want Their PAS to Handle Payments
Carrier teams have a particular set of incentives that drive demand for native PAS payment execution.
Renewal retention. Mandates that survive renewal cycles. Carriers can quantify the basis-point impact of involuntary lapse reduction on retained premium.
Cycle time on launching new products. A carrier launching a new product line (a new commercial line, a new personal lines proposition, a new MGA programme) moves faster when payment configuration is a setting, not an engineering project. PAS vendors who can ship payment-ready new programmes win deals.
Customer experience parity with personal lines disruptors. Embedded insurance and digital-native personal lines brands have set a customer-experience bar around instant claims payout, frictionless renewal and smooth mid-term changes. Traditional carrier stacks that cede payment execution to legacy systems can't match that bar without modernising the payment layer.
Premium financing flexibility. Commercial lines and high-premium personal lines depend on premium financing arrangements. Payment infrastructure that reconciles cleanly to financing partners removes friction from the most material part of the commercial book.
Multi-MGA scaling. Carriers running multiple MGA programmes on a single PAS need payment routing flexibility. PAS vendors who can offer that out of the box win the MGA-platform deals.
PAS vendors who embed Shuttle can address the collection side of these without becoming a payments company.
Build vs Integrate
The build-vs-integrate question for PAS platforms is sharper than for most B2B software, because the regulatory overlay is real.
Building multi-PSP, multi-method, multi-jurisdiction payment infrastructure inside a PAS would require:
PCI DSS Level 1 certification
Money-services regulatory registration in each operating jurisdiction (where holding funds is contemplated)
ACH, Bacs, SEPA and Faster Payments / RTP scheme participation or sponsor arrangements
AML and KYC infrastructure for outbound claims payment
Per-PSP integration and maintenance across the global PSP landscape
Mandate management infrastructure for recurring direct debit across jurisdictions
That's not a feature. That's a separate company.
The alternative: integrate once with The Payment Layer. 40+ PSPs supported. Premium collection across cards, direct debit and bank payments in one integration, with card data kept out of the PAS, which limits its PCI scope. Per-carrier and per-MGA configuration without per-deployment engineering.
For the broader build-vs-integrate framework, see Build vs Buy: Payment Infrastructure for Platforms.
Related Reading
Payments for Insurance Core Platforms: the broader insurance platform guide covering broker and distribution patterns
PCI-Compliant Payment Architecture for Insurance Platforms: the technical deep dive on limited-scope architecture
AI Voice Payments for Insurance: the AI voice agent collection pattern for insurance
Embedded Payments Without Becoming a PayFac: why most platforms shouldn't own the payment relationship
Enterprise PSP Mandates: Why Customers Need Multiple Gateways, the constraint that drives PSP-neutral architecture
Insurance Payment Solutions: Alternatives Compared, the buying-side comparison of insurance payment vendors
Shuttle is The Payment Layer for insurance carriers, MGAs and PAS vendors. One integration powers premium collection, recurring mandates, and voice and AI agent capture, routed to each carrier's or MGA's own acquirer and branded per carrier or MGA. PCI DSS Level 1, ISO 27001, and SOC 2 certified. See how it works for platforms or book a discovery call.