April 22, 2026
PayFac vs. ISO vs. Self-Hosted Gateway: Which Payment Model Is Right for You?
If you want to operate payments as a business — onboarding merchants, routing transactions, earning margin on volume — you have three main models to choose from: become a Payment Facilitator (PayFac), register as a Payment ISO, or run your own self-hosted gateway. Each has different economics, different compliance burdens, and different ceilings on what you can actually do. This guide breaks them down side-by-side so you can pick the one that fits your capital, timeline, and risk appetite.
Quick definitions
Payment Facilitator (PayFac): a master merchant that onboards sub-merchants under its own acquiring relationship. The PayFac owns the sponsor-bank relationship, the underwriting decision, and the merchant contract. Examples: Stripe, Square, Toast, Mindbody, Shopify Payments.
Payment ISO (Independent Sales Organization): a Visa/Mastercard-registered sales agent that resells a processor's or acquirer's services to merchants. The merchant contracts with the processor — not the ISO. The ISO earns residual commission on volume, typically 10–40 basis points.
Self-hosted payment gateway: you deploy payment infrastructure yourself (on a VPS, on crypto rails, non-custodial), onboard merchants under your own brand, set your own rates, and keep 100% of whatever spread you negotiate. PayRam is a self-hosted gateway built for this exact model.
Side-by-side comparison
| Dimension | Payment ISO | PayFac | Self-hosted gateway (PayRam) |
|---|---|---|---|
| Who owns the merchant contract | Processor | PayFac | You |
| Sponsor bank required | Yes | Yes | No |
| Visa / MC registration | Yes | Yes | Not applicable |
| Setup cost | $5k–$25k | $500k–$5M | ~$20–$150/month VPS |
| Time to launch | Weeks–months | 12–18 months | ~10 minutes |
| Revenue model | Residual (10–40 bps) | Full rate minus costs | You set it |
| Take-rate ceiling | Fixed by processor | ~0.5–1% margin after costs | Uncapped |
| Chargeback liability | Merchant | PayFac | None on crypto rails |
| Can be dropped | Yes (processor can revoke) | Yes (sponsor bank can revoke) | No |
| Category restrictions | Processor ToS | Sponsor bank ToS | You decide |
| Fund custody | Processor | PayFac (pooled) | Merchant-controlled wallet |
When to become an ISO
The ISO model works when you have an existing sales force or merchant-services network and want recurring residual income without owning the infrastructure. You bring merchants to a processor, earn a slice of their processing volume for years, and carry minimal operational burden. The trade-off: you don't control rates, you don't own the merchant relationship, and if the processor drops the merchant (or you), your residuals stop. Read our deeper explainer on what a Payment ISO is and how to become one.
When to become a PayFac
The PayFac model fits SaaS platforms, vertical specialists, and marketplaces that want to own the payment experience end-to-end and can absorb the $500k–$5M setup cost plus 12–18 months of certification. You get a much larger share of the discount rate (because you're taking on the acquiring risk) and you control the merchant relationship. The trade-off: massive upfront investment, ongoing compliance load, and full chargeback liability. Read the full breakdown on our Payment Facilitator explainer.
When to run a self-hosted gateway
The self-hosted model works when you want the operator economics of a PayFac (full control, full margin, owned merchant relationships) without the sponsor-bank dependency and without the eight-figure setup tab. PayRam delivers this on stablecoin rails: deploy once on a VPS, onboard sub-merchants in seconds, settle non-custodially to each merchant's own cold wallet.
You're not reselling — you're operating. There's no processor in the middle, no sponsor bank that can cut you off, no Visa or Mastercard ToS to navigate. You decide what rates to charge, what categories to serve, and what jurisdictions to operate in. Your merchants contract with you, settle to themselves, and get the economics of crypto rails (sub-cent fees, instant finality) with the familiarity of a branded checkout.
The honest trade-off on the self-hosted path
It's not a drop-in replacement for card-rail PayFacs. You're serving merchants whose customers pay in stablecoins (or use the card-to-crypto onramp). You're responsible for your own jurisdictional compliance — PayRam doesn't custody funds and isn't a payment service provider, so whatever MTL or KYC/AML obligations apply in your market are your call. And you're operating the software yourself (or paying a fractional team to operate it for you).
In exchange, you skip the bank queue, the Visa registration, and the vendor take-rate. For operators who want to own the rails instead of renting them, the math works.
Which should you pick?
- Want residual income, don't want to operate → Payment ISO
- Have $1M+ and 12 months, want card-rail acceptance at scale → Payment Facilitator
- Want operator economics without the bank queue, willing to build on stablecoin rails → self-hosted gateway (PayRam)
For a deeper look at each model, see our pillar pages on Payment Facilitators, Payment ISOs, and white-label payment gateways. Or if you're ready to deploy, jump straight to the setup guide.
