What is a good payments take rate for vertical SaaS?
A good payments take rate for vertical SaaS is best measured as net revenue in basis points on gross payment volume — after processing and vendor costs — not the gross fee you charge the merchant. As of June 2026, observed net take rates run from 0–20 bps on referral models to 100–120+ bps for registered payment facilitators, with most scaled platforms on PayFac-as-a-service or managed PayFac models earning 40–90 bps. What counts as 'good' depends on the vertical, the card-versus-ACH mix, and the operating model, because each keeps a different share of the economics.
Reviewed by Jane Podbelskaya · last reviewed 2026-07-24 · how we produce answers
Measure the right number
Most “take rate” confusion comes from comparing gross fees instead of net economics. Frame it consistently:
- Take rate (net) = (revenue from payments − processing and vendor costs) ÷ gross payment volume, expressed in basis points (bps).
A platform charging a high headline fee but keeping little after costs does not have a good take rate — it has a good-looking one.
What drives a healthy number
| Driver | Effect on net take rate |
|---|---|
| Monetization model | Referral < PayFac-as-a-service < full PayFac (gross), traded against cost and risk. |
| Card vs ACH mix | Card volume typically carries more monetizable spread than ACH. |
| Average transaction size | Interchange dynamics shift the economics between small and large tickets. |
| Vertical behavior | Chargebacks, seasonality, and B2B/B2C mix change achievable margin. |
The 2026 benchmark ranges by model and GMV
As of June 2026, these are the observed net take-rate ranges by operating model, and the GMV tier where each model typically fits:
| Operating model | Typical GMV tier | Net take rate |
|---|---|---|
| PSP referral / revenue share | Under $10M | 0–20 bps |
| Light PayFac-as-a-service | $10M–$50M | 20–40 bps |
| PFaaS / managed PayFac | $50M–$250M | 40–80 bps |
| Managed PayFac + orchestration | $250M–$1B | 65–90 bps |
| Full registered PayFac (optional) | $1B+ | 100–120+ bps |
These are observed market ranges, not guarantees: the same model can move ±10–30 bps depending on vertical and card-present mix, and $50M in annual GMV is the largest step-change on the curve — above it, graduating from referral economics to a full PFaaS model typically multiplies payment revenue on identical volume.
Two medians from the Rainforest 2026 benchmarking study of vertical SaaS platforms put those ranges in operating context. Platforms with a C-suite payments leader report a median net take rate of 98 bps; with a payments leader below the C-suite, 83 bps; with no dedicated payments leader, 53 bps. By maturity stage, “emerging” platforms report a 53 bps median while “scaling” and “optimized” platforms both report 98 bps — leadership and operating discipline, not tenure, separate the tiers.
When the benchmark is not worth chasing
A benchmark misleads when it is compared against the wrong tier. A $20M-GMV platform measuring itself against the 98 bps medians is comparing against operators on a different model with a different cost base — closing that gap would require taking on infrastructure and risk the volume does not yet justify. Compare against your own model and GMV tier first.
Use it as a diagnostic, not a target
The best use of a benchmark is to compare your net take rate to platforms at your stage and model, then ask why any gap exists — pricing, mix, or model. The take-rate calculator runs this on your own numbers, and the embedded payments hub covers the levers that move it.
FAQ
Gross take rate or net take rate?
Net. The number that matters is what you keep after processing costs, interchange, and your vendor's share. A high gross fee with thin net margin is not a good take rate.
Why does the model change the take rate?
Referral models keep the least of the economics, PayFac-as-a-service keeps more, and a full PayFac keeps the most gross margin but takes on the most cost, risk, and compliance. The right model depends on volume and appetite for operational burden.
Does vertical matter?
Yes. Average transaction size, card-versus-ACH mix, chargeback rates, and B2B-versus-B2C behavior all move the achievable net take rate significantly between verticals — the same model can move plus or minus 10–30 bps in observed results.
Sources
- Charge Forward, Embedded Payments Benchmarks 2026 (June 2026)
- Rainforest, 2026 Vertical SaaS Embedded Payments Benchmarking Study (Q1 2026 fielding) (2026)