The question lands on every vertical SaaS founder's desk eventually: should we become a payment facilitator?
The answer matters more than most teams realize. The wrong call costs anywhere from $300K to $2M in capital and 12 to 18 months of focus. The right call captures 30 to 60 basis points of net margin on every dollar of merchant payment volume your platform carries, compounding for years.
This is a strategic decision that gets framed as a technical one. The technical pieces (card network registration, sponsor bank relationships, KYC infrastructure) are well-documented. The strategic pieces (when the financial case actually works, what the compliance burden really looks like, where the hidden costs hide) are what decide whether the move pays off or quietly drags on the business for years.
Here's the framework.
The Four Ways to Participate in Payments Economics
Before answering "should we become a PayFac," ground the conversation in what's available. There are four arrangements, each with different economics and different operational obligations. For the definitional version of each, see What Is a Payment Facilitator?
ISV Referral. You refer merchants to a processor. The processor handles boarding, underwriting, and settlement. You collect a residual of 5 to 15 basis points. Implementation is measured in weeks. No infrastructure investment, no compliance burden. The ceiling is low because the economics are.
ISV Enhanced Residuals. A variant of the referral model with negotiated improvements. You retain a larger share of the spread (15 to 30 basis points) and sometimes influence merchant pricing, but you're still not the merchant of record. Implementation is similar to ISV Referral.
PayFac-as-a-Service (Managed PayFac). You operate as a payment facilitator under another registered PayFac's umbrella. You own the merchant experience, set pricing, handle support. The provider handles the regulatory layer: card network registration, sponsor bank relationships, compliance frameworks. Net economics typically run 30 to 60 basis points. See PayFac-as-a-Service for the full mechanics.
Full Payment Facilitator. You register directly with Visa and Mastercard as a PayFac. You build the compliance infrastructure, hire the risk and operations staff, and take full responsibility for the merchant relationship and the card network obligations. Net economics run 60 to 100+ basis points.
The decision isn't binary. Most platforms that ultimately become full PayFacs go through ISV Referral first, then PFaaS. The question for any given platform is which arrangement is right for the current stage, and which is the right end state.
When Each Model Actually Makes Sense
The financial case for each model is volume-driven. Below a certain processing volume, the infrastructure investment doesn't pay back. Above it, the marginal economics of the more sophisticated arrangement materially outpace the simpler one.
ISV Referral works for platforms under $25M in annual processing volume. At this scale, the absolute dollar amount of residuals is modest but real (5 to 15 basis points on $25M is $12K to $37K per year). The operational cost is essentially zero. There's no reason to build infrastructure that won't pay for itself.
PayFac-as-a-Service starts making sense around $30M to $50M in volume. At $50M with a 40 basis point net take rate, you're earning $200K per year, enough to justify the staff and integration investment. PFaaS gives you 80 to 90% of the economics of being a full PayFac at 10 to 20% of the cost. For most platforms in the $30M to $200M range, PFaaS is the right answer.
Full PayFac registration starts making sense at $100M+ in processing volume, and the case strengthens at $200M+. The 25 to 30 basis point uplift over PFaaS (going from, say, 50 bps to 80 bps) needs to exceed the $300K to $800K annual operating cost of running the compliance and risk infrastructure yourself. At $100M, that's $250K to $300K of additional economic surplus before operating costs. At $200M, it's $500K to $600K. Above $300M, the case becomes obvious.
The transition from PFaaS to Full PayFac is also harder to reverse than the transition from ISV Referral to PFaaS. Going back means giving up control, returning to a provider relationship, and potentially restructuring contracts with sponsor banks. Get the timing right. The framework for evaluating provider transitions in general is in When to Switch Embedded Payments Providers.
What It Actually Costs
The financial case has to clear both the implementation cost and the ongoing operating cost. Both are larger than the back-of-envelope estimates that most platforms start with.
Full PayFac Registration
Implementation: $500K to $2M. This covers card network registrations with Visa and Mastercard ($25K to $75K each), sponsor bank setup and integration ($100K to $300K), KYC and underwriting infrastructure ($150K to $500K, build or buy), fraud and risk monitoring platforms ($100K to $300K), settlement and reserve management systems ($100K to $300K), and initial PCI DSS Level 1 certification ($50K to $200K). The range is wide because complexity scales with merchant count, vertical risk profile, and how much you build versus buy.
Annual operating cost: $300K to $800K. The biggest driver is staffing, 2 to 5 FTEs across risk, compliance, and operations, typically $150K to $220K loaded per head depending on geography. Beyond staff, expect $50K to $150K per year for continuous monitoring tools (transaction fraud scoring, watchlist screening, chargeback management), $30K to $80K for annual audits and PCI assessment, and card network fees that scale with volume.
Time to launch: 12 to 18 months. The card network registration alone is a 6 to 12 month process. Building or integrating the operational infrastructure typically adds 6 to 9 months on top.
PayFac-as-a-Service
Implementation: $50K to $200K. Mostly engineering integration with the PFaaS provider's APIs: boarding flow, settlement, reporting, and webhooks. There may be a one-time setup fee from the provider, typically $20K to $50K.
Annual operating cost: $100K to $300K. The biggest cost is merchant operations staff, typically 0.5 to 1.5 FTEs handling boarding support, chargeback response, and tier-1 merchant inquiries. Beyond staff, expect $20K to $50K per year for monitoring tools and integration maintenance.
Plus a structural cost the operating budget doesn't capture: the provider's spread share. PFaaS providers take 5 to 15 basis points of net spread in exchange for handling the regulatory layer. This doesn't show up as a line-item expense, but it's a real economic cost that scales with volume. On $50M of volume at a 10 basis point provider share, that's $50K per year flowing out of your net economics before you pay your own ops staff. On $200M, it's $200K.
Time to launch: 3 to 6 months. Most of the timeline is engineering integration. No card network registration delay because you operate under the provider's existing registration.
The Break-Even Comparison
At $100M of volume, the rough comparison looks like this. PFaaS implementation $100K, annual operating $200K, provider spread share $100K (10 bps), total Year 1 cost roughly $400K, ongoing $300K. Full PayFac implementation $1M, annual operating $500K, total Year 1 cost $1.5M, ongoing $500K. The Full PayFac model becomes positive-economic versus PFaaS only when the additional take rate captured (typically 20 to 30 bps over PFaaS) exceeds the additional cost. On $100M of volume, 25 bps captures $250K of additional gross economics, which barely covers the additional $200K of operating cost.
That's why $200M+ in volume is where Full PayFac starts to feel like the right call. Below that, the marginal economics don't justify the marginal complexity.
The Compliance Burden (Usually Underestimated)
Cost numbers capture about 60% of what makes the Full PayFac decision hard. The other 40% is operational and compliance burden that most teams underestimate at decision time.
Merchant underwriting. As a Full PayFac, you board every merchant under your own MID, which means you carry direct underwriting responsibility. You set the rules, you accept the merchants who meet them, and you carry the risk if a merchant defrauds the system or generates chargebacks beyond network thresholds. PFaaS providers handle much of this work for you within their published frameworks.
Transaction monitoring. Card networks expect continuous monitoring for fraud, money laundering, and high-risk merchant activity. As a Full PayFac, you need either a built or bought transaction monitoring platform, plus the analysts to investigate alerts. As a PFaaS, the provider handles the platform and most of the alerting; you handle merchant-facing follow-ups.
Chargeback management. Every dispute requires a response within network-defined windows. As a Full PayFac, you're the merchant of record from the network's perspective, which means you carry the first-loss exposure and the operational responsibility. PFaaS providers typically handle the network-side response and pass operational tickets to you for merchant communication.
PCI compliance. Full PayFacs are subject to PCI DSS Level 1, which means an annual on-site Qualified Security Assessor (QSA) audit. Depending on your environment, the audit alone costs $50K to $150K and consumes 2 to 4 months of engineering and operations focus. For deeper context on PCI levels and how the burden scales by model, see PCI Compliance for SaaS Platforms.
Regulatory reporting. Full PayFacs file quarterly and annual reports with card networks and sponsor banks, including transaction volumes, chargeback ratios, fraud rates, and merchant counts by category. These reports drive whether you remain in compliance with network thresholds.
The operational burden of Full PayFac is what trips up most platforms that pursued the model too early. The financial case might justify the move on volume, but the team isn't structured to handle the compliance discipline. Six months in, the leadership team is spending a third of its time on payments operations questions instead of product.
Common Decision-Making Mistakes
The wrong call usually comes from one of these patterns.
Optimizing for the wrong horizon. Full PayFac captures more economics over a 5 to 10 year horizon, but the cash investment is upfront. Platforms in growth mode that need capital for product or sales often make the right strategic call (move to PFaaS) for the right reason (preserve capital for higher-ROI investments). Don't confuse "right end state" with "right next step."
Underestimating the compliance overhead. The dollar cost of staffing and audits is visible. The CEO time, board time, and audit fire drills that come with Full PayFac are not. Most platforms that ultimately stay in PFaaS do so because they realize the leadership-attention cost is bigger than the basis-point gain.
Confusing the decision with vendor selection. "Should we become a PayFac?" is a strategic question about your business model. "Which PFaaS provider should we use?" is a vendor selection question. They get bundled in early-stage planning, which clouds both decisions.
Pursuing Full PayFac to "control our own destiny." Sometimes a real motivation, often a rationalization. Going Full PayFac doesn't give you more strategic flexibility, it gives you more compliance obligations. The destiny you control is mostly the boring back-office one.
Not modeling the PFaaS-to-PayFac transition explicitly. The economics of staying in PFaaS for 2 to 3 more years and then transitioning to Full PayFac are very different from the economics of going Full PayFac today. Run both scenarios. The right strategic answer is often "PFaaS now, Full PayFac at $200M."
A Three-Question Decision Test
If you take nothing else from this article, take the three-question test.
- What's your annual processing volume? Under $30M: ISV Referral. $30M to $200M: PayFac-as-a-Service. Above $200M: evaluate Full PayFac seriously.
- What's your strategic time horizon? If you're building toward a 3 to 5 year exit and payments revenue is a major value driver, PFaaS captures most of the economics with much less execution risk. If you're building toward 10+ year value creation and you have the capital and team to absorb the compliance burden, Full PayFac is a legitimate option above the volume threshold.
- How prepared is your team for the compliance load? If you have or can hire experienced payments compliance and risk leaders, Full PayFac is operationally feasible. If you're still figuring out who handles chargebacks, the answer is PFaaS for at least another year.
If all three answers point to Full PayFac, the decision is straightforward. If even one points to PFaaS, that's where you should land.
Becoming a payment facilitator is a strategic decision that gets framed as a technical one. The technical pieces are well-documented. The strategic pieces, when the financial case actually works, what the compliance burden really looks like, where the hidden costs hide, are what decide whether the move pays off.
The decision isn't urgent for most platforms. The wrong call costs years of focus and capital. The right call captures structural margin on every dollar of merchant volume your platform carries. Take the time to get it right.
For the financial modeling, the Margin Multiplier shows revenue under each model at your specific volume. For the strategic conversation about your platform's specific situation, see the advisory engagement.