Should a software platform become a payment facilitator itself or use a provider's embedded payments?

Default: use a provider’s embedded-payments offering first. Become your own registered payment facilitator only when payments are strategically central and you’re ready to own the extra risk, operations, and regulatory work.

A PayFac can contractually onboard sub-merchants and receive settlement for them, which brings more control—but also significant responsibility for merchant oversight, disputes, fraud, and compliance. The precise division of work and liability depends on the provider, acquirer, and contract; using an embedded-payments provider does not necessarily eliminate the platform’s responsibilities. (usa.visa.com)

A practical path: start with a provider, but negotiate for the things you may want to retain—your branded experience, control over pricing, access to transaction data, and a viable migration path. Measure the actual economics and operational burden. Revisit becoming a PayFac only when the additional control and margin clearly outweigh the costs and risk. Provider models vary: some offer a more managed marketplace setup, while others support platforms that take on more payment-facilitator responsibilities. (docs.adyen.com)

Before choosing, model net payment margin, not headline processing revenue: include provider and network fees, fraud and chargeback losses, onboarding and support costs, compliance, reserves, and engineering. Then compare providers on merchant approval rates, payout control, dispute handling, data portability, geographic coverage, and contract terms.

Rule of thumb: if your main goal is to make payments feel native in your software, use a provider. If payments themselves are a major competitive advantage and you’re prepared to run a payments operation, investigate becoming a PayFac. Get payments counsel to review the proposed structure and contracts before launch.

Short answer: For most software platforms, start with an embedded payments provider that offers payfac-as-a-service. Become a registered payment facilitator only when payments are central to your business and you have the scale and capital to run the compliance stack.

Why most platforms start with a provider

• The provider carries the heaviest burden. Under payfac-as-a-service, the platform still controls the user experience and often earns revenue share, but the provider handles the regulatory and risk heavy lifting.
• Launch timing differs a lot. One provider's comparison puts a days to weeks launch with a provider against 12–18 months to become a fully registered PayFac. Treat vendor-published figures with caution, since these sources sell embedded payments.
• Costs are the other big gap. Vendor estimates for building your own stack run from roughly $600,000+ in engineering alone, to a full card-rail budget of $2.5M–$7M upfront. Estimates vary widely, but the fixed cost is large.
• Most of the economics are still available. A provider model still lets you get better economics and UX control than pure referral, without taking on everything a registered facilitator does.

When becoming a payfac makes sense

• Payments are your core product, not a feature. If you're building a payments company, not a platform that needs payments, then owning the stack makes strategic sense.
• You have enough volume to absorb fixed costs. Full registration brings maximum control over pricing, payout timing, and experience; highest revenue potential, but also significant time, capital, and expertise required.
• You're willing to carry risk directly. You take on financial liability for merchant fraud and chargebacks, plus KYC, AML, and sponsor-bank relationships. Registration requires a sponsor bank to underwrite you with Visa, Mastercard, and the card networks.

Questions to settle before deciding

1. Who needs to own underwriting and monitoring? Decide how risk decisions get made, audited, and adjusted.
2. How much pricing and payout control do you need? This usually decides between referral, payfac-as-a-service, and full registration.
3. How much merchant fragmentation can you tolerate? Letting every customer bring its own processor keeps you hands-off, but it creates fragmented data, slow onboarding, and a heavy support burden.
4. What is your revenue model? Payments as a second revenue line only pays off if transaction volume is large enough to justify the cost of owning the compliance stack.

Practical path: Launch with a provider's embedded payments to validate demand and volume. Negotiate contract terms that preserve your pricing and data access. Revisit full registration once volume is large enough that the margin gain exceeds the fixed compliance and staffing costs. Also check whether your provider's terms make a later migration hard, since that affects how reversible the decision is.

Deciding between becoming a Payment Facilitator (PayFac) and using embedded payments via a provider is a strategic crossroads that hinges on your platform’s scale, appetite for risk, and long-term business goals.

The Core Distinction

• Becoming a PayFac means you become the "master merchant." You take on full responsibility for onboarding sub-merchants, managing risk, handling chargebacks, and ensuring compliance with card network rules.
• Embedded Payments (via a partner) means you integrate a third-party's payment infrastructure into your software. You gain the benefits of a native payment experience—where users never leave your platform—but the partner handles the heavy lifting of compliance, underwriting, and risk.

Comparison at a Glance

When to Consider Becoming a PayFac

Becoming a registered PayFac is a significant undertaking, essentially turning you into a fintech company. You should only consider this path if:

• You have immense scale: You process enough payment volume (GPV) to justify the high fixed costs of compliance, audits, and dedicated risk teams.
• You require total control: Your business model depends on highly specific underwriting or payout structures that off-the-shelf embedded solutions cannot support.
• Payments are a core pillar: Your company’s valuation and growth are fundamentally tied to owning the entire financial infrastructure.

When to Choose Embedded Payments (Partnered Model)

For most software platforms, partnering with an embedded payments provider (often called PayFac-as-a-Service) is the more pragmatic choice. This approach allows you to:

• Focus on your product: You keep your engineering and leadership teams focused on your core software rather than payment operations.
• Accelerate time-to-market: You can launch integrated payments in weeks rather than spending years navigating regulatory approvals.
• Mitigate liability: By using a partner, you offload the complex burden of KYC, AML, and PCI-DSS compliance, protecting your platform from the financial risks of sub-merchant fraud or bankruptcy.
• Scale economically: Modern providers offer "PayFac-like" economics, allowing you to monetize payments through revenue-sharing or configurable fee arrangements without the startup costs of becoming a registered entity.

Recommendation

If you are a growing SaaS or vertical platform, start with an embedded payments partner.

Many platforms mistakenly believe they must become a PayFac to "own" the revenue or the experience. However, modern embedded finance providers can deliver the same white-labeled, seamless experience and significant revenue upside without the massive operational and regulatory overhead. You can always "graduate" to a full PayFac model in the future if your payment volume and strategic needs eventually demand it.

For most software platforms, start with a provider’s embedded-payments offering. Consider becoming a payment facilitator (PayFac) yourself only when payments are strategically central and the added control and potential margin justify the ongoing operational, financial, and regulatory burden.

Important: “Embedded payments” does not mean your platform has no responsibilities. Confirm in writing who handles merchant verification, ongoing monitoring, disputes, losses, reserves, payouts, and regulatory obligations in each market. Responsibilities can be shared, and the provider’s contract and product model matter. ¹²

A practical approach is to launch with a provider, measure payment volume, contribution margin, support and risk costs, and merchant needs, then revisit the PayFac decision using your actual data. Compare providers on total cost—not just the headline processing rate—including revenue share, minimums, reserves, payout terms, portability, and the controls you retain. ⁴

Bottom line: Choose a provider unless you have a clear, quantified case for taking on PayFac responsibilities. A provider can offer a branded, integrated experience, but “more control” should be weighed against what it costs to operate and manage risk—not assumed to mean better economics. ¹³

¹ Adyen: PayFac-as-a-Service
² Stripe: Marketplace compliance responsibilities
³ Adyen: What is a payment facilitator and should you become one?
⁴ Adyen: Understand the economics of embedded payments