Every PayFac-as-a-Service pitch sounds the same. We handle compliance. Merchants onboard in minutes. You keep more of the spread. None of that is wrong. PFaaS is the right model for a lot of vertical SaaS platforms, and if you have decided PFaaS is your route, you are pointed in a sensible direction.

But every PFaaS provider makes tradeoffs, and the ones that hurt do not show up in the demo. They show up twelve to eighteen months in, when a chunk of your merchants get frozen, or your margin quietly compresses, or your finance team cannot reconcile a month. This piece is the part that does not make the deck: where PFaaS providers are genuinely strong, where they are systematically weak, and what each tradeoff actually means for you. No provider named, because the point is to teach you to read any of them.

The pattern to hold in your head is simple. Every PFaaS strength has a paired tradeoff. The right provider is not the one with no weaknesses. It is the one whose weaknesses you can live with given your product and your merchant base.

1. Onboarding speed

Strength. Fast, self-serve merchant boarding. The best providers get a sub-merchant from sign-up to processing in minutes.
The catch. The providers that board fastest usually have the strictest, most automated downstream risk. Your merchant boards in minutes, then trips a rule weeks later and gets held or offboarded, and you eat the support call.

Speed at the front door is a real strength, but it is the wrong thing to weigh alone. What happens after boarding is where the cost actually lives: how often merchants get held, what triggers a review, who notifies the merchant and who fields the call when a merchant's funds are frozen. Boarding is a one-time event. Risk holds are a recurring cost, and they land on you, not the provider. The fastest boarding and the strictest downstream risk tend to travel together, and that pairing is the part the speed pitch leaves out.

2. The economics

Strength. You capture far more of the payment spread than an ISV referral model, often 50 to 80 basis points versus 5 to 15.
The catch. Blended pricing looks great at today's merchant mix and compresses as you add larger or lower-margin merchants. The residual that pencils out now may not at scale.

The headline take rate is the most quoted number and the least useful one. What actually sets your margin is the buy rate underneath the blended figure and how your merchant mix moves over time. A residual that pencils out on today's mix can compress meaningfully once larger or lower-margin merchants come on, and most platforms never model that second part. The number that matters is what you keep after cost-to-serve at scale, not the rate on the slide. For the full picture of what sits in that cost stack, see what embedded payments actually cost.

3. "We handle compliance and risk"

Strength. The provider owns PCI scope, underwriting and the sponsor-bank relationship. You do not stand up a compliance or risk team.
The catch. The more they own, the less you control. "We handle it" can mean you cannot price a specific merchant competitively, or override a decline, or move fast on an exception your sales team needs closed.

This is the central PFaaS tradeoff, and for most platforms it is genuinely a feature. Offloading risk and compliance is the whole point. What matters is understanding where the control line sits: who can override an underwriting decision, who can adjust pricing on a named merchant and how long an exception takes. For many providers the honest answer is that the provider decides, and that is fine, as long as you understood the constraint going in rather than meeting it the first time a deal needs an exception your sales team has already promised.

4. Funds flow and settlement

Strength. Clean, predictable settlement for the standard case: a charge settles to the merchant on a normal cycle.
The catch. Anything beyond charge-then-settle (split payments, delayed capture, escrow, hold-and-release, marketplace flows) varies enormously between providers and is exactly where integrations break.

If your product needs only simple payments, this dimension is easy and most providers handle it well. If your product needs to split a payment across parties, hold funds, delay capture, or move money in any non-trivial way, the variance between providers is wide and it is where integrations quietly break. A provider that is excellent at simple settlement can be painful at split-pay, and that gap almost never surfaces in a demo. It surfaces in your build, months later, when the workaround becomes the roadmap.

5. Support and dispute handling

Strength. "Dedicated support" and a partner team, as every provider will tell you.
The catch. Support quality is the single largest gap between the demo and the reality, and it is invisible until you need it. It is also where your cost-to-serve quietly lives.

Who actually handles the hard cases (a frozen merchant on a Friday afternoon, a chargeback that needs a representment, a merchant disputing a hold) is what separates the demo from the reality. When those route back to you instead of the provider, your team absorbs the load, and support is one of the biggest and most underestimated cost-to-serve drivers in a payments program. A current partner's lived experience tells you more about this dimension than anything in the pitch does.

6. Reporting and reconciliation

Strength. A clean dashboard and a payments API.
The catch. Sub-merchant-level reporting and reconciliation depth varies wildly, and a thin one is what your finance team will quietly hate for years.

A dashboard demos well. Reconciliation at the sub-merchant level, month after month, is the real test, and it is rarely the thing that gets shown. Whether you can tie every dollar of volume, fee and residual back to a specific merchant and period through the API is what your finance team lives with for as long as the program runs, and the depth of it is wildly variable between providers. A thin reporting layer is a cost you pay quietly, every single close.

7. Contract and exit terms

Strength. A standard agreement and a smooth onboarding.
The catch. Exclusivity, multi-year terms, change-of-control provisions and data-portability limits are what make leaving painful, and they are buried where nobody reads.

The terms that matter most are the ones nobody reads at signing: whether you can migrate to a different model or provider without penalty, who owns the sub-merchant data and underwriting history, what happens if you get acquired and whether exclusivity blocks a second processor. These rarely affect the launch and heavily shape the next three years, which is also when they show up in payments due diligence if you raise or sell. When you do get to the table, how to negotiate a processor agreement walks through the terms worth pushing on.

The right PFaaS provider is not the one with no weaknesses. It is the one whose weaknesses you can live with, given your product and your merchant base.

How to read all of it at once

Lay the seven dimensions next to your own situation and the picture usually resolves quickly. A platform with simple payments, small merchants and a light support appetite weights onboarding speed and economics, and can live with less control. A platform with complex funds flow, larger merchants or a regulated vertical weights control, settlement flexibility and support, and should be suspicious of the fastest-boarding, most-automated option. There is no best provider in the abstract. There is a best fit for a specific platform, and the fit is determined by which tradeoffs you can absorb.

For the full provider-agnostic evaluation checklist, the companion piece is how to choose an embedded payments provider, and the mechanics of choosing a payment processor for your SaaS sit one layer underneath that. And if you are still deciding between models before you get to providers at all, start with ISV Referral vs PayFac Lite.

So which provider is right for you? My honest answer is the same one I give every platform that asks: it depends. Not as a way to dodge the question, but because it genuinely does, on your volume, your merchant mix and what your product needs to do with money. The seven dimensions are the framework anyone can use. Which tradeoffs you can absorb, and which provider on your shortlist is strongest exactly where you are weakest, is the part that only resolves when someone who has done this looks at your actual situation. If you are weighing providers right now, that is the conversation worth having before you sign anything. Reach out and we will work through yours.