Shuttle vs PayFac-as-a-Service (Payrix, Finix)

Two Approaches to Platform Payments

PayFac-as-a-Service (PFaaS) and Shuttle both solve the same problem: platforms want to embed payments. But they take fundamentally different paths to get there, and the path you choose determines how much compliance burden you carry, how fast you go to market, and what your payment operations look like in year three.

PayFac-as-a-Service (Payrix, Finix) lets platforms offer payment facilitation without building PayFac infrastructure from scratch. Depending on the tier, the platform takes on some or all of the PayFac role. Payrix, acquired by FIS in December 2021 and now part of Worldpay for Platforms, offers tiers from referral payments to PayFac-as-a-Service, where Worldpay handles underwriting and compliance, and full PayFac. Finix is VC-backed. Both give you more control over payment economics and the merchant relationship, in exchange for taking on more of the payment role.

Shuttle is a PSP-neutral payment layer. It lets platforms embed multi-PSP payments through a single integration, supporting 40+ gateways, multiple channels (checkout, voice, links, AI), and white-label merchant tooling. Platforms embed payments without becoming a PayFac, a sub-PayFac, or any variant in between.

The fundamental question: do you need to be a payment facilitator, or do you need payments to work inside your platform?

Side-by-Side Comparison

Where PayFac-as-a-Service Wins

Margin Control

This is the core argument for PFaaS. As a PayFac, you set the merchant's processing rate. You keep the spread between your rate and interchange-plus. For platforms with high transaction volume, that spread can add up. If payment revenue is your primary margin driver, that pricing power matters.

Ownership of the Merchant Relationship

When you're the PayFac, you own the full merchant relationship: underwriting, risk decisions, pricing, settlements, and disputes. You don't depend on an intermediary for any of these. For platforms that want total control over the merchant payment experience, PFaaS delivers that control.

Payment Economics Depth

PFaaS platforms give you access to interchange data, settlement mechanics, and acquiring economics that a payment layer abstracts away. If your business model depends on understanding and optimising payment economics at the interchange level (if you're building pricing strategies around BIN-level cost data), PFaaS gives you the levers.

Embedded Financial Services Path

Becoming a PayFac is often the first step toward embedded lending, embedded insurance, or embedded banking. If your long-term strategy involves becoming a financial services platform, PFaaS is a stepping stone toward that future. The compliance infrastructure you build for PayFac supports these adjacent products.

Where Shuttle Wins

No PayFac Compliance Burden

When you become a PayFac, you take on real obligations, and even through a PFaaS provider some of them stay with you, depending on the tier:

• Merchant underwriting: You evaluate and approve every sub-merchant

• KYC/AML: You perform identity verification and anti-money-laundering checks

• Risk monitoring: You monitor transactions for fraud, chargebacks, and suspicious activity

• Regulatory compliance: You comply with card network rules, state money transmitter laws (in the US), and evolving regulation

• Dispute management: You're in the chain for chargeback representment

These aren't one-time costs. They scale with your merchant count and compound with geographic expansion. A platform with 500 merchants has materially different compliance overhead than one with 50.

With Shuttle, your platform is not the PayFac. Underwriting, KYC and merchant agreements stay with each merchant's own PSP, and card data never touches your platform, which limits your PCI scope.

PSP Flexibility

PFaaS platforms typically route all transactions through their acquiring partner. If an enterprise customer says "we process through Worldpay" or "we have negotiated rates with Adyen," the PFaaS model can't accommodate that. The customer either processes through your PayFac's acquirer, or they don't use your platform.

Shuttle supports 40+ gateways. Enterprise customers can bring their existing PSP if it is one of them.

Multi-Channel Coverage

PFaaS providers cover online checkout, and some add payment links and in-person payments. Shuttle covers these channels through one integration:

• Voice payments: PCI-compliant DTMF capture, agent-assisted payments, AI voice agent payments

• Payment links: White-label links sent via SMS, email, or chat

• AI agent payments: Consumer card capture through AI voice and chat agents

• Chat payments: Secure payment capture within messaging interfaces

For platforms with contact centre operations, field service teams, or AI agent deployments, these channels are not optional, and building them on top of a PFaaS model means separate integrations with separate PCI implications.

Pre-Built Components

Going live as a PayFac takes time: sponsor bank approval, underwriting workflows, compliance documentation and risk monitoring. PFaaS providers take on some or all of this, depending on the tier.

Shuttle's onboarding, checkout and merchant portal are pre-built and white-label, so your team doesn't build those screens.

Enterprise PSP Mandates

Enterprise customers with existing PSP relationships will not abandon negotiated rates and established compliance certifications to process through your PayFac. This is the same lock-in problem that affects Stripe Connect and Adyen for Platforms, and it applies equally to PFaaS.

Shuttle removes the obstacle. If the enterprise customer's PSP is one of the 40+ Shuttle supports, it works within your platform's payment infrastructure.

The PayFac Question

Every platform that considers PFaaS needs to answer one question honestly: does your business need to be a payment facilitator, or does it need payments to work?

Becoming a PayFac makes sense when:

• Payment revenue is your primary business model, not a supplement to your SaaS revenue

• You have the resources to build and maintain a compliance function (legal, risk, operations)

• You process enough volume that interchange-level margin control meaningfully impacts your economics

• You plan to expand into embedded financial services (lending, banking, insurance)

• You're willing to accept the regulatory risk that comes with being in the payments chain of custody

For most SaaS platforms, payments are a feature, not the core business. The platform's differentiation is its software, its workflow, its industry expertise. Payments need to work reliably and support enterprise customers. They don't need to be a compliance operation.

The analogy: you wouldn't build your own cloud infrastructure to save on hosting margin (unless you're AWS). Most platforms shouldn't become payment facilitators to save on transaction margin, unless payments are genuinely the product.

PFaaS providers have done a good job lowering the barrier to becoming a PayFac. But "lower barrier" isn't "no barrier." The compliance obligations are real, they scale, and they don't go away. The question is whether the margin upside justifies the operational cost. For most platforms, it doesn't.

When to Choose PayFac-as-a-Service

• Payment revenue is your primary margin driver: you're building a payments business, not just embedding payments

• You want full control over merchant pricing: you set rates, you keep the spread

• You're prepared to build a compliance function: underwriting, KYC, risk monitoring, dispute management

• You have high transaction volume that justifies the fixed cost of PayFac operations

• You plan to expand into embedded financial services (lending, banking, insurance) and need the regulatory infrastructure

• You only need single-acquirer coverage

• You have time before payment capabilities are commercially critical

When to Choose Shuttle

• Payments are a feature of your SaaS, and you want them without becoming a financial institution

• Enterprise customers mandate their PSP (or you expect they will)

• You need multi-channel payments (voice, payment links, chat, AI agents), not just checkout

• You don't want PayFac compliance obligations: underwriting, KYC/AML, risk monitoring, regulatory reporting

• You operate across regions and need PSP coverage beyond a single acquiring partner

• You want PSP negotiating leverage, with more than one gateway connected and each merchant or payment method on the one that suits it

• You want pre-built, white-label merchant tools (onboarding, checkout, portal) without building them yourself

FAQ

Is PFaaS the same as being a full PayFac? Not exactly. PFaaS providers like Payrix and Finix run the processing platform and sponsor bank relationships. How much of underwriting, KYC and risk stays with the platform depends on the tier: Worldpay's PayFac-as-a-Service tier handles underwriting and compliance, while a full PayFac owns them. With a payment layer, your platform is not the PayFac at all.

Can I switch from PFaaS to Shuttle later? Yes, though it means moving your merchant base from your PayFac structure to Shuttle's model. Merchants are re-onboarded through Shuttle's white-label flow onto their own gateway, and you can move them in stages rather than all at once. Saved cards stay with the gateway that stored them.

Do I lose control over the merchant experience with Shuttle? No. Shuttle's checkout, onboarding, and merchant portal are white-labelled to your platform. Your merchants see your brand. You control the experience. You just don't carry the compliance burden of being the payment facilitator behind it.

Related Reading

• How to Get Payments Off Your Product Roadmap: why payments shouldn't consume your engineering bandwidth

• Shuttle vs Stripe Connect: how single-PSP lock-in limits your platform

• Shuttle vs Building In-House: the real cost of building payment infrastructure yourself

• PayFac Alternatives for Platforms: the full landscape of PayFac alternatives

• Embedded Payments Without Becoming a PayFac: why most platforms don't need to be a PayFac

Embed payments without becoming a PayFac. Shuttle gives your platform 40+ PSPs, multi-channel payments (including voice and AI) and white-label merchant tools through a single integration. Underwriting, KYC and merchant agreements stay with each merchant's own PSP.

Book a Demo | See Platforms