- Adding Stripe to your SaaS platform is not embedded payments. It is a referral. Your sub-merchants are Stripe’s customers, not yours.
- True embedded payments require you to decide how much risk, compliance, and revenue you want to own. Each step up the stack adds margin and adds liability.
- The four models are referral, PSP integration, PayFac, and PayFac-as-a-Service. Most B2B SaaS platforms land in the wrong one because they choose on speed, not fit.
- Stripe, Adyen, Finix, Stripe Connect, WePay, Payrix, Stax Connect, NMI, Payroc, and ConnexPay each serve a different point on that spectrum.
- Merchant onboarding speed, revenue share structure, and underwriting ownership are the three variables that actually differentiate providers at scale.
The best embedded payments providers for B2B SaaS platforms are Stripe Connect, Adyen for Platforms, Finix, Payrix, Stax Connect, WePay (a JPMorgan Chase company), NMI, ConnexPay, Payroc, and PayPal Braintree. The right choice depends on whether your platform wants to act as a referral agent, a PSP reseller, a registered payment facilitator, or a full PayFac-as-a-Service operator. Each model shifts different amounts of compliance burden, underwriting liability, and payment revenue between the provider and your platform.
Why Most B2B SaaS Platforms Are Not Actually Doing Embedded Payments
Most SaaS founders believe they have embedded payments the moment their app can collect a credit card. They have not. Dropping a Stripe Checkout link or redirecting users to a PayPal flow means Stripe or PayPal owns the merchant relationship. Your customer is their customer. You earn a referral fee at best.
Real embedded payments means your platform controls the payment experience end to end: onboarding sub-merchants under your master merchant ID, setting pricing, managing disputes, and keeping a share of interchange. That requires either becoming a registered payment facilitator yourself or working with a PayFac-as-a-Service provider that handles the infrastructure while you keep the economics.
This distinction matters because the revenue gap is significant. A platform processing $50 million annually in sub-merchant volume at a 0.3% net revenue share earns $150,000 per year. The same platform operating as a full PayFac, keeping 60 basis points after provider fees, earns $300,000 from the same volume. The compliance and risk investment is real, but so is the delta. Understanding the hidden costs in your fintech SaaS margin stack is worth doing before committing to a model.
What Is the PayFac Decision Tree for B2B SaaS Platforms?
Before evaluating any specific provider, your team needs a structural decision. FintechSpecs calls this the Platform Payments Ladder: four rungs that differ in control, revenue, and compliance burden. Most platforms belong on rung two or three but default to rung one because it is the fastest to ship.
Rung 1: Referral
You link out to or redirect users to a third-party processor. You earn nothing or a small referral bounty. The processor owns KYC, underwriting, disputes, and the customer relationship. Best for pre-product-market-fit platforms that cannot afford compliance overhead. Examples: direct Stripe links, PayPal buttons not integrated via API.
Rung 2: PSP Integration
You integrate a payment API directly and collect payments on behalf of your customers under your own merchant account. You handle the UX, the processor handles risk. You earn no interchange but you own the customer experience. Best for SaaS tools where payments are incidental, not the core feature. Examples: Stripe Payments (not Connect), Braintree standard integration.
Rung 3: Payment Facilitation (PayFac)
You become a registered payment facilitator under a card network sponsor. You onboard sub-merchants, set pricing, and own disputes within the limits of your sponsor bank agreement. You earn meaningful revenue on every transaction. This requires registration with Visa and Mastercard, a sponsor bank relationship, and an underwriting program. Examples: building on Finix, Payrix, or Stax Connect.
Rung 4: PayFac-as-a-Service
A provider handles PayFac registration, sponsor bank, underwriting technology, and compliance infrastructure while you white-label the experience and keep most of the economics. Lower compliance burden than full PayFac, higher revenue than PSP. This is where most vertical SaaS platforms processing above roughly $5 million in annual payment volume should operate. Examples: WePay, Payrix Pro, NMI’s PayFac program, Payroc.
How Do These Four Models Compare on Revenue, Risk, and Speed?
| Model | Time to Launch | Revenue Potential | Compliance Burden | Merchant Ownership | Best For |
|---|---|---|---|---|---|
| Referral | Days | Minimal | None | None | Early-stage, incidental payments |
| PSP Integration | 1-4 weeks | Low | PCI scope only | Partial | SaaS with payments as a side feature |
| Full PayFac | 6-18 months | High | High (registration, underwriting, monitoring) | Full | High-volume vertical SaaS, fintech |
| PayFac-as-a-Service | 4-12 weeks | Medium-High | Medium (shared with provider) | Substantial | Scaling vertical SaaS, $5M+ annual volume |
Top 10 Embedded Payments Providers for B2B SaaS Platforms
1. Stripe Connect
Stripe Connect is the most widely deployed platform payments product in North America. It supports three account types: Standard (sub-merchants manage their own Stripe accounts), Express (a faster onboarding flow Stripe controls), and Custom (your platform controls the full UX). Custom accounts are the only configuration that puts your platform on the PayFac path with Stripe as the infrastructure.
Stripe’s public pricing page lists a 0.25% + $0.25 per payout fee for Custom accounts on top of standard processing fees. The trade-off is that Stripe retains underwriting and risk decisions even in Custom mode. You do not own the merchant relationship in the same way a registered PayFac does. For platforms that want fast time-to-market and Stripe’s fraud tooling without PayFac complexity, Connect Custom is the practical default. If you want to compare Stripe’s architecture against a more enterprise-grade stack, the Stripe vs Adyen breakdown for B2B SaaS is worth reviewing before committing.
2. Adyen for Platforms
Adyen for Platforms targets enterprise-grade marketplaces and SaaS companies with global payment volume. The product handles sub-merchant onboarding, split payments, and payouts under Adyen’s acquiring license. Adyen processes in over 40 countries and supports local payment methods in most of them, which makes it the strongest option for B2B SaaS platforms with international sub-merchants.
Adyen does not publish standard platform pricing publicly. Pricing is negotiated, typically based on monthly volume, and the minimum commercial relationship usually requires substantial processing commitments. The onboarding timeline for Adyen for Platforms is longer than Stripe Connect. The payoff is deeper acquiring relationships, better authorization rates in non-US markets, and more control over settlement timing.
3. Finix
Finix is purpose-built for SaaS companies that want to become payment facilitators without registering directly with card networks. Finix acts as the payment facilitator of record while giving platforms deep API access to onboarding, underwriting, disputes, and transaction data. Platforms keep meaningful revenue on transaction volume and set their own pricing for sub-merchants.
Finix is explicit that it targets platforms processing at least $5 million in annual payment volume. Below that threshold, the economics of the PayFac-as-a-Service model do not justify the integration investment. Above it, Finix gives B2B SaaS platforms more control over the payments stack than Stripe Connect without the 12-to-18-month timeline of full PayFac registration. Their pricing is not publicly listed and requires direct negotiation.
4. Payrix (now part of Worldpay)
Payrix is a PayFac-as-a-Service provider focused exclusively on software platforms. Following its acquisition by Worldpay, Payrix has access to Worldpay’s acquiring network and international processing capacity. The product includes automated sub-merchant onboarding with customizable KYC flows, a revenue-sharing model where platforms earn on interchange, and a white-label dashboard for sub-merchant reporting.
Payrix’s primary differentiator is its vertical SaaS specialization. The company has built documented go-to-market playbooks for legal tech, healthcare, field services, property management, and adjacent verticals including home services, fitness, and professional services. If your platform serves any of those verticals, Payrix’s existing sub-merchant risk models and approval logic will be calibrated closer to your user base than a generalist provider’s.
5. Stax Connect
Stax Connect offers a PayFac-as-a-Service product with a subscription-based pricing model rather than a percentage-of-transaction approach. Platforms pay a monthly fee and pass interchange-plus pricing through to sub-merchants, which can make the total cost of payments significantly lower for B2B SaaS platforms with high average transaction values. Stax publishes pricing for its direct merchant products but Stax Connect pricing is negotiated per platform.
The subscription model is genuinely differentiated. Most PayFac-as-a-Service providers clip a percentage of every transaction processed. Stax Connect’s flat-rate structure means a platform’s per-transaction cost drops as volume grows, which is the inverse of the typical embedded payments economics. For B2B SaaS platforms with large invoice-based transactions (over $1,000 average ticket), this structure is worth modeling carefully before defaulting to Stripe.
6. WePay (JPMorgan Chase)
WePay is JPMorgan Chase’s platform payments product, targeted at software companies that want PayFac economics backed by a top-tier bank. WePay’s integration with Chase’s acquiring infrastructure gives it strong approval rates and access to Chase’s fraud intelligence network. The product is white-labeled, so sub-merchants see the platform’s branding rather than WePay or Chase.
WePay’s key advantage for enterprise-facing SaaS is bank credibility. Platforms selling to CFOs and finance teams at mid-market companies often find that a payments product backed by JPMorgan Chase has a shorter trust curve than one backed by a standalone fintech. WePay is not the right choice for international platforms or for those that need deep API customization. It is a strong option for US-focused B2B SaaS platforms serving regulated industries where counterparty trust matters.
7. NMI
NMI (Network Merchants Inc.) positions itself as a payment facilitation gateway for ISVs and SaaS providers. Its PayFac enablement product lets software platforms onboard sub-merchants, set pricing, and manage transactions through a single API. NMI supports connections to multiple backend processors, which gives platforms more redundancy and rate negotiation leverage than single-processor solutions.
NMI’s multi-processor routing is its standout feature. A platform can route transactions to different acquirers based on card type, merchant category, or risk profile, which can meaningfully improve authorization rates and reduce interchange costs. NMI does not publish platform-tier pricing, but its architecture suits established software companies that want processor optionality without building their own switching layer.
8. ConnexPay
ConnexPay is differentiated by linking payment acceptance and payment issuance in a single platform. For B2B SaaS businesses where the platform both collects from buyers and pays out to suppliers, ConnexPay’s ability to fund virtual card issuance directly from incoming payment flows eliminates float risk and simplifies treasury operations. According to ConnexPay’s public product pages, platforms can launch embedded payment capabilities within days.
This combined acceptance-and-issuance model is most relevant to procurement SaaS, travel tech, and marketplace platforms where the platform sits in the middle of a money flow. For platforms where payment acceptance and supplier disbursement are separate problems, ConnexPay’s combined structure adds integration complexity without meaningful benefit.
9. Payroc
Payroc is a payment facilitator and ISO that has built a dedicated software partner program for SaaS companies. Its platform product includes sub-merchant onboarding, revenue sharing, and access to Payroc’s acquiring relationships. Payroc is less visible in venture-backed SaaS circles than Finix or Stripe Connect, but it has a substantial existing merchant base and deep relationships in certain verticals like hospitality and retail.
Payroc is worth evaluating for B2B SaaS platforms that serve industries where Payroc already has merchant density. Existing acquirer relationships in your target vertical translate to faster sub-merchant approvals and better risk calibration for your merchant category code mix.
10. PayPal Braintree
PayPal Braintree sits in an awkward position for B2B SaaS. Its core API is well-documented, and Braintree for Platforms enables split payments and sub-merchant onboarding. The inclusion of PayPal and Venmo as native payment methods makes Braintree relevant for consumer-facing platforms or platforms serving small businesses where PayPal wallet acceptance improves conversion.
For pure B2B SaaS platforms with business-to-business transaction flows, Braintree is rarely the top choice. Authorization rates for commercial card types and ACH debit are competitive, but the PayFac infrastructure is less developer-centric than Finix or Stripe Connect, and the revenue-sharing economics are less transparent. Braintree is a reasonable fallback if PayPal wallet acceptance is a specific commercial requirement, not a general-purpose recommendation for embedded B2B payments.
How Do These Providers Stack Up on the Criteria That Actually Matter?
| Provider | Model | Sub-Merchant Onboarding | Revenue Share | International | Best Fit |
|---|---|---|---|---|---|
| Stripe Connect | PSP / Near-PayFac | Fast (Express/Custom) | Low-Medium | Strong | Early to mid-stage, global |
| Adyen for Platforms | PayFac infrastructure | Moderate | Negotiated | Strongest for multi-currency | Enterprise, multi-currency |
| Finix | PayFac-as-a-Service | Customizable via API | High | US-focused | Series A-C vertical SaaS |
| Payrix | PayFac-as-a-Service | Automated, white-label | High | Moderate | Vertical SaaS (specific industries) |
| Stax Connect | PayFac-as-a-Service | Platform-controlled | Subscription model | US-focused | High-ticket B2B transactions |
| WePay | PayFac-as-a-Service | Guided onboarding | Negotiated | US-focused | Enterprise SaaS, regulated industries |
| NMI | PayFac gateway | Platform-managed | Negotiated | Moderate | Multi-processor ISV/SaaS |
| ConnexPay | Accept + Issue | Fast | Model-dependent | Moderate | Marketplaces, procurement SaaS |
| Payroc | PayFac / ISO | Partner-assisted | Revenue share | US-focused | Vertical SaaS with existing merchant base |
| PayPal Braintree | PSP / Near-PayFac | Moderate | Low-Medium | Strong | Consumer-adjacent B2B, PayPal wallet users |
What Should B2B SaaS Platforms Evaluate Before Choosing a Provider?
Provider selection for embedded payments comes down to five variables. Processing volume determines which economics are available. Merchant risk profile determines which underwriting models will approve your sub-merchant base without excessive friction or false declines. The degree of experience your engineering team has with payments compliance determines whether a fully managed PayFac-as-a-Service or a lower-level API is the right layer to integrate at.
Consider a hypothetical Series B vertical SaaS platform serving 400 small landscaping companies, processing roughly $8 million in annual payment volume at an average ticket of $350. On Stripe Connect Custom, this platform earns referral-level economics from Stripe, owns zero merchant data, and cannot adjust pricing per sub-merchant. On Finix or Payrix, the same platform functions as a payment facilitator, keeps a revenue share on every transaction, and owns the KYC and onboarding flow. The annual revenue difference on $8 million can exceed $150,000 once you account for the difference in net economics between the two models.
Merchant onboarding approval rates are often ignored at the evaluation stage. A provider whose automated underwriting rejects 20% of your target merchant category because the risk models were calibrated for a different vertical will create support tickets, churn, and trust damage. Ask prospective providers for approval rates in your specific merchant category codes before signing. This is a more useful number than their headline processing volume. The analysis of KYC provider performance by approval rate applies directly here.
What Does the Implementation Process Actually Look Like for Embedded Payments in SaaS?
A PayFac-as-a-Service integration has five phases regardless of which provider you choose. First, commercial negotiation: revenue share, volume minimums, reserve requirements, and dispute liability thresholds. Second, technical integration: API authentication, sub-merchant onboarding webhooks, transaction reporting, and dispute management flows. Third, compliance alignment: confirming your platform’s Terms of Service, AML/KYC policies, and acceptable use policy meet the provider’s program requirements.
Fourth is merchant onboarding design. The UX decisions here have direct revenue consequences. An onboarding flow that asks for 14 fields before a merchant can accept their first payment will produce high abandonment. Most PayFac-as-a-Service providers offer a tiered onboarding approach: collect minimal information to allow low-volume processing, then trigger enhanced due diligence as the merchant’s monthly volume crosses defined thresholds. Building this logic correctly from day one avoids the more painful retroactive verification scramble later. The research on why fintech users drop off during onboarding documents exactly how quickly friction compounds.
Fifth is ongoing monitoring. Payment facilitators are responsible for their sub-merchants’ compliance. That means transaction monitoring, chargeback ratio tracking, and periodic account reviews. Providers like Finix and Payrix include merchant monitoring dashboards. NMI’s multi-processor architecture adds a routing intelligence layer. Whatever you build or buy, a chargeback ratio above 1% across your sub-merchant portfolio will trigger acquirer intervention. Building risk monitoring from the start, not after the first acquirer warning, is the difference between a sustainable payments program and an expensive remediation project. The most expensive risk mistakes fintech founders make consistently trace back to underestimating the ongoing monitoring requirements of the PayFac model.
What Is the Difference Between a PayFac and an ISV?
An ISV (Independent Software Vendor) integrates with a payment processor and refers merchants to that processor. The ISV earns a residual or referral fee. The processor owns the merchant relationship, the underwriting, and the risk liability. An ISV can be live in days. A PayFac (Payment Facilitator) is registered with Visa and Mastercard, sponsors its own sub-merchants, and owns the underwriting and risk for those merchants. The PayFac earns interchange revenue and sets its own pricing. The registration process takes months and requires a sponsoring bank.
PayFac-as-a-Service blurs this line. The platform looks and earns like a PayFac but uses the provider’s registration and bank sponsorship. The platform takes on meaningful compliance obligations but avoids the direct card network registration burden. Most B2B SaaS platforms processing between $5 million and $50 million annually land here.
How Does Embedded Payments Revenue Work in Practice?
When your platform processes a $1,000 invoice payment on a business credit card, the total interchange and network fees might be 2.4% ($24). The acquiring bank takes a cut, the card network takes its assessment, and what remains is split between your provider and your platform. In a PayFac-as-a-Service arrangement, a platform might net 0.3% to 0.8% of the transaction ($3 to $8 on a $1,000 payment) after all fees. At scale, this compounds. A platform with 500 active sub-merchants each processing $120,000 per year has $60 million in annual payment volume. At a 0.5% net take rate, that is $300,000 in annual payment revenue from a product the platform does not operate directly.
Pricing your platform’s payment service is a separate decision from choosing the provider. You can choose to pass through costs at near-zero markup to increase adoption, or charge a premium to sub-merchants who would pay more than market rate for a fully integrated experience. The ways fintech companies monetize payments without degrading the user experience covers the strategic options here in detail.
Frequently Asked Questions
What is the difference between embedded payments and payment facilitation?
Embedded payments is a broader term for integrating payment acceptance directly into a software platform’s product experience rather than redirecting to a third-party checkout. Payment facilitation is a specific regulatory and commercial model where a company (the PayFac) sponsors sub-merchants under its own master merchant account and accepts liability for their transactions. You can have embedded payments without being a PayFac, but you cannot be a PayFac without embedding payments into your platform.
What is the PayFac-as-a-Service model and how does it differ from full PayFac registration?
PayFac-as-a-Service means a provider handles card network registration, sponsor bank relationships, and core underwriting technology while a platform white-labels the merchant-facing experience and keeps a revenue share. Full PayFac registration means the platform registers directly with Visa and Mastercard, sources its own sponsor bank agreement, and owns the underwriting and compliance program entirely. PayFac-as-a-Service trades some revenue upside for significantly lower compliance overhead and a faster path to market.
At what payment volume does it make sense to move from Stripe Connect to a PayFac-as-a-Service provider?
The threshold is not fixed, but most PayFac-as-a-Service providers target platforms processing at least $5 million in annual sub-merchant volume. Below that level, the integration investment and compliance overhead typically do not generate enough incremental revenue over Stripe Connect to justify the switch. Above $10 million, the economics of a more capable PayFac-as-a-Service arrangement almost always outperform Stripe Connect Custom from a net payment revenue standpoint.
Who is responsible for KYC and AML when a SaaS platform uses PayFac-as-a-Service?
Responsibility is shared. The PayFac-as-a-Service provider owns the underlying compliance program and sets minimum KYC requirements. The platform is responsible for collecting required merchant information during onboarding, implementing the provider’s verification flows, and maintaining acceptable use policies that align with the program. If a sub-merchant violates AML rules and the platform failed to collect required documentation, the platform bears liability for that gap. This is why onboarding flow design is a compliance decision, not just a UX one.
Can a B2B SaaS platform use embedded payments for ACH and not just card transactions?
Most PayFac-as-a-Service providers support ACH in addition to card acceptance. Stripe Connect, Finix, Payrix, and NMI all support ACH debit and credit flows through their platform products. ACH carries different risk profiles and dispute mechanics than card transactions: the return window is longer and chargebacks work differently. Platforms should confirm their provider’s ACH return monitoring and handling process before enabling it for sub-merchants, particularly in high-risk B2B verticals where invoice disputes are common.
What are examples of companies that use a PayFac model?
Square is the most cited example: it onboards small businesses as sub-merchants under its own PayFac registration rather than making them apply for individual merchant accounts. Toast in restaurant SaaS, Mindbody in fitness software, and Shopify Payments operate on similar structures. These are full PayFac builds, not PayFac-as-a-Service arrangements. They each took years and significant capital investment to build. PayFac-as-a-Service providers like Finix and Payrix allow B2B SaaS companies to replicate the commercial model without the same investment.
How long does embedded payments implementation take for a B2B SaaS platform?
A Stripe Connect integration can go live in two to four weeks for a developer-ready team. A PayFac-as-a-Service integration with customized merchant onboarding, revenue share configuration, and dispute handling typically takes eight to twelve weeks. Full PayFac registration with a sponsor bank takes six to eighteen months depending on the bank’s onboarding process and the platform’s compliance readiness. The implementation timeline is almost always the deciding factor for early-stage platforms, which is why most start on Stripe Connect and migrate later.
Does adding embedded payments affect a SaaS platform’s compliance obligations?
Significantly. A platform operating as a payment facilitator or PayFac-as-a-Service participant takes on PCI DSS scope, AML monitoring obligations, and in many states money transmission considerations depending on how funds flow. The specific obligations depend on the provider’s program structure, the platform’s role in the transaction, and the transaction types processed. Any platform moving beyond simple PSP integration should review compliance obligations before going live. The fintech product and compliance readiness checklist covers the key areas to audit before launch.
The Most Important Variable Nobody Mentions at the Start
Every provider comparison eventually comes down to authorization rates and sub-merchant approval rates, not features. A PayFac-as-a-Service provider with a 95% sub-merchant approval rate in your merchant category and a 90% card authorization rate will outperform a provider with better pricing and worse approval rates. Payment revenue that never processes is worth nothing.
Before signing with any provider, request the following: sub-merchant approval rates for your target MCCs, card authorization rates for domestic commercial card transactions, average chargeback ratios across their platform portfolio in your vertical, and the settlement timing for sub-merchant payouts. These four numbers tell you more about fit than any feature comparison table.
The platform that ships embedded payments fastest is rarely the platform with the best payment economics at scale. The decision is not whether to embed payments. The decision is which rung of the Platform Payments Ladder to target at your current volume, and which provider’s infrastructure gets you there with acceptable compliance overhead. Most teams get this wrong once, migrate 18 months later, and spend the intervening time leaving revenue on the table.
