SaaS
How to Choose an Embedded Payment Solution for SaaS
There's no single best embedded payments provider — there's the right category for your platform's GPV, geography, and business model. Here's how to find yours in under 10 minutes.
Your flat-rate processor is capturing most of your transaction margin. Subscription revenue is plateauing. And becoming a registered PayFac costs $500K+ and requires a 12–24-month build timeline.
PayFac as a Service (PFaaS) exists because the math doesn't work for platforms with under $500M in Gross Payment Volume (GPV). For most vertical SaaS companies, it's the rational default.
This guide covers the economics, your first 90 days, a five-part buyer's rubric, and where PFaaS is the wrong answer.
What PFaaS actually means for your platform
Skip the acquirer-side definition. From the ISV perspective, you integrate one API. The PFaaS partner provides the master merchant account, acquirer relationship, and compliance infrastructure — PCI DSS, Know Your Customer (KYC)/Anti-Money Laundering (AML), and card-network registration. You own the merchant relationship, onboarding UX, and pricing.
The result is interchange-plus economics. Your platform earns 60–100 basis points on processed volume instead of the 10–30 basis points referral arrangements pay.
What you own vs. what the partner owns:
| Your platform | PFaaS partner |
|---|---|
| Merchant relationship and sales | Master merchant account and acquirer relationship |
| Onboarding UX and approval workflows | KYC/AML verification and underwriting |
| Merchant pricing and rate cards | PCI DSS Level 1 certification |
| Product experience and support | Card network registration and compliance |
| Settlement reporting and reconciliation UI | Chargeback management and dispute resolution |
A few edge cases, like automated approval thresholds and merchant-level risk tiering, require explicit negotiation. But the core division is clean: you control the merchant experience, the partner handles regulatory and network infrastructure.
The economics: a monthly P&L walkthrough
This section changes your business case.
Model a SaaS platform processing $50M in annual GPV ($4.2M/month). US general-purpose card payments totaled $9.76T in 2022, per the Federal Reserve Payments Study. Even a thin slice of that volume compounds into meaningful platform revenue.
PFaaS interchange-plus model
| Line item | Rate | Monthly amount |
|---|---|---|
| Gross processing revenue | ~2.6% of volume | ~$109,000 |
| Interchange + assessments | ~1.8% of volume | ~$75,600 |
| PFaaS partner margin share | ~0.4% of volume | ~$16,800 |
| Platform take | ~0.4% of volume | $16,800/mo ($200K/yr) |
Interchange fees average 1.7%–1.9% for a standard card mix, per published network rate schedules. Card network assessments add 0.13%–0.15%, bringing all-in cost to 1.85%–2.05%.
Same volume on flat-rate
| Line item | Rate | Monthly amount | Annual amount |
|---|---|---|---|
| Platform revenue share | ~0.1% of volume | ~$4,200 | ~$50,000 |
The revenue gap
| Model | Annual platform revenue |
|---|---|
| PFaaS | ~$200,000 |
| Flat-rate | ~$50,000 |
| Delta | +$150K/yr |
The gap comes down to who keeps the margin between interchange cost and the rate charged to merchants. On flat-rate, your processor pockets most of it and pays you a thin referral cut (~0.1% of volume). On PFaaS interchange-plus, you price merchants directly and keep what's left after interchange, assessments, and your partner's share (~0.4% of volume).
At $50M GPV, that shift turns $50K in passive revenue into $200K you control.
How the delta scales
| Annual GPV | PFaaS platform take | Flat-rate take | Annual delta |
|---|---|---|---|
| $10M | ~$40K | ~$10K | ~$30K |
| $50M | ~$200K | ~$50K | ~$150K |
| $250M | ~$1M | ~$250K | ~$750K+ |
Vertical SaaS platforms on PFaaS report payments revenue that rivals or exceeds subscription revenue at scale. The embedded finance market is projected to exceed $320B in revenue by 2030, per BCG and QED Investors.
What happens in your first 90 days
Weeks 1–4: API integration and sandbox testing
Your engineering team integrates the PFaaS API, sets up webhook handlers, and tests transaction flows in sandbox. Plan for 2–4 weeks, depending on stack complexity.
Weeks 4–8: merchant onboarding design
Most platforms underestimate this phase. You decide which KYC fields to collect, how to tier merchants by risk, and which approval rules to automate. The PFaaS partner runs KYC/AML verification. Your UX determines merchant sign-up conversion.
Weeks 8–12: reconciliation, ledger setup, and go-live
Wire settlement records, chargeback routing, and reporting obligations — 1099-K, PCI — into your finance stack before pilot launch. Run a pilot cohort of 10–20 merchants before broader rollout.
Three pitfalls that burn platforms
Underestimating chargeback handling. Disputes require response workflows, evidence collection, and deadline tracking. If your PFaaS partner doesn't fully indemnify chargebacks, build a dedicated process from day one.
Treating settlement reconciliation as an afterthought. Mismatched ledger entries compound. Build reconciliation into finance workflows before go-live, not after.
Discovering late that certain MCCs aren't supported. PFaaS partners operate under their acquirer's risk appetite. Confirm your merchant category codes are approved before signing.
The five-part PFaaS buyer's rubric
Bring this to every sales call.
1. Economics
Does the partner publish interchange-plus pricing with a clear revenue share — or hide it behind a blended flat rate? Ask for the full rate card: chargeback fees, FX markups, payout fees. If they can't produce it, that's your answer.
2. Settlement model
T+2 remains the card default, yet innovations are shaping the future of modern payment systems. Same-day settlement is increasingly available. Instant settlement via stablecoin rails works for platforms that need liquidity now. Ask where your partner sits on that spectrum — and whether it can change as your needs evolve.
3. Geographic coverage
US-only, global pay-ins, or global pay-ins and payouts? Ask how many countries, which local payment methods are supported, and whether cross-border payouts require a separate integration. Coverage claims in marketing materials often don't match reality in practice.
4. Compliance handoff
What PCI scope does the partner reduce? What KYC/AML do they run? What compliance lives inside your product? The best partners reduce your PCI scope to SAQ-A and handle the full AML/KYC workflow. Anything less, and you're carrying compliance overhead you didn't budget for.
5. Support model
Dedicated account team with a payments expert, or a shared ticket queue? Ask for a service-level agreement and named contacts before signing. This is where partnerships succeed or fail post-launch — and it's the question most platforms forget to ask.
Evaluation template
Use the following categories to compare vendors side by side:
- Pricing model (interchange-plus vs. flat)
- Revenue share (bps)
- Settlement speet
- Country coverage (pay-ins)
- Country coverage (payouts)
- PCI scope reduction
- KYC/AML ownership
- Chargeback indemnification
- Support model
When PFaaS is the wrong answer
PFaaS isn't right for every platform. Naming the edges makes the model more credible where it fits.
Over $500M GPV with a dedicated payments team. Full PayFac registration — including state-by-state money transmitter licensing — captures more margin at this scale.
Under $10M GPV and pre-product-market-fit. Flat-rate is cheaper to operate. The $30K annual delta doesn't justify the integration lift yet.
High-risk merchant categories. If your merchants include categories a PFaaS acquirer won't sponsor, like adult content, CBD, and high-risk gaming, you need a specialized processor.
Merchant-of-Record requirements. If your platform requires the payments partner to hold the legal seller-of-record position for tax and regulatory obligations on every transaction, PFaaS is the wrong choice. You need a Merchant-of-Record structure.
The 2026 PFaaS landscape
The market has split into three categories.
US-focused PFaaS. Providers targeting vertical SaaS platforms that process domestically. Strong onboarding tools, US-only coverage. The right fit for platforms that don't need global reach yet.
Enterprise global acquiring with PFaaS-like flows. Large acquirers offering platform-style payment facilitation for enterprises needing global card acceptance. Long timelines, minimum volume commitments, built for $500M+ GPV.
Next-generation PFaaS with instant settlement and global coverage. Coinflow occupies this category — interchange-plus pricing delivering 3–4x the platform revenue share of flat-rate models. Instant settlement via USDC stablecoin rails. PCI DSS Level 1 and SOC 2 compliance. Embedded AML/KYC. Fully indemnified chargeback protection. Coverage across 170+ markets through a single API.
The right category depends on your GPV, geography, and how much of the payment experience you want to control. If you're evaluating where Coinflow sits relative to legacy processors, Coinflow vs. Stripe breaks down where the economics diverge.
Model your PFaaS economics
The $150K+ annual revenue delta at $50M GPV is real math — not a marketing estimate. For platforms seeking interchange-plus economics, instant settlement, and global coverage without vendor sprawl, PFaaS deserves serious consideration.
Schedule a call to model your PFaaS economics with Coinflow →
Getting started is easy
Whether you're running a marketplace, a gaming platform, a payroll product, or a cross-border fintech, the infrastructure is the same. The outcomes are specific to your model.
Talk to the Coinflow teamFAQs
What is PayFac as a service?
PFaaS lets SaaS platforms offer payment facilitation to merchants without registering as a PayFac. The PFaaS partner provides the master merchant account, acquirer relationship, and compliance infrastructure. Your platform owns the merchant experience and earns interchange-plus economics.
How long does it take to launch PFaaS?
Most platforms go live in 8–12 weeks. The timeline includes API integration (2–4 weeks), merchant onboarding design (4 weeks), and reconciliation setup before pilot launch.
How much revenue can a SaaS platform earn from PFaaS?
A platform processing $50M in annual GPV earns ~$200K/year under interchange-plus PFaaS, compared to ~$50K on flat-rate. The delta grows with volume.
What's the difference between PFaaS and becoming a registered PayFac?
Registered PayFac costs $500K+ to launch and takes 12–24 months. PFaaS delivers similar economics in 8–12 weeks with no registration cost. The trade-off: you share margin with your PFaaS partner rather than owning the full acquirer relationship.
How does instant settlement change the PFaaS equation?
Traditional PFaaS runs on T+2 — funds arrive two business days after the transaction. Instant settlement via stablecoin rails closes that gap within minutes, improving working capital and eliminating the cash-flow delay that affects high-velocity platforms. See real-time payment use cases for how platforms are applying this today.
This content is for informational purposes only and does not constitute financial, legal, or investment advice. Past performance is not indicative of future results.
