April 22, 2026
How to Become a Payment Facilitator (PayFac) in 2026: The Realistic Guide
Becoming a Payment Facilitator sounds straightforward until you start adding up the line items. Visa and Mastercard registration. Sponsor bank setup. State MTL licensing. Compliance infrastructure. Underwriting software. Pre-launch this adds up to $500k–$5M and 12–18 months of work before you board your first sub-merchant. This guide walks through the card-rail path honestly, then introduces the alternative: launching a crypto-native PayFac-equivalent on self-hosted infrastructure in about 10 minutes for roughly $20–$150 per month.
What you're actually building
A PayFac is a master merchant that onboards sub-merchants under its own acquiring relationship. Your sub-merchants sign contracts with you, not with Visa or Mastercard directly. You carry the liability, you set the underwriting policy, you collect a share of the discount rate. Examples: Stripe, Square, Toast, Mindbody. It's how modern SaaS platforms and marketplaces onboard merchants in minutes instead of weeks.
See our PayFac pillar explainer for a full breakdown of the model.
Step 1: Pick a sponsor bank
Every card-rail PayFac needs a sponsor bank to provide the BIN and the acquiring relationship. Sponsor banks that work with PayFacs include Wells Fargo, Chesapeake, Fifth Third, Pathward, Esquire Bank, and several regional acquirers. You'll need:
- A business plan with projected transaction volume and merchant profile
- Financial statements demonstrating capital reserves (typically $250k–$2M minimum)
- A compliance plan covering KYC/AML, sanctions screening, and fraud monitoring
- Technical documentation of your payment stack
Sponsor banks are selective. Expect 3–6 months just on this step.
Step 2: Register with Visa and Mastercard
Both networks require PayFac registration. Costs run around $75k–$100k annually, plus setup fees. Mastercard also requires you to complete their Payment Facilitator registration program, which includes certification on their BRAM (Business Risk Assessment and Mitigation) program. Expect 2–3 months of process.
Step 3: MTL licensing (US state-by-state)
If you're touching merchant funds — even briefly, before settling to them — Money Transmitter Licensing applies in most US states. Costs range from $25k to $250k per state (NY is the worst), plus surety bonds and ongoing reporting. A nationwide US PayFac typically budgets $2M–$5M just on MTL.
You can avoid MTL by operating as a non-custodial payment facilitator — which is structurally what a crypto-rails PayFac on PayRam is.
Step 4: Compliance infrastructure
You need BSA/AML programs, KYC for sub-merchants above network volume thresholds, PCI DSS Level 1 compliance, sanctions screening, transaction monitoring, suspicious-activity reporting. That's typically a $100k–$500k/year build plus compliance staff.
Step 5: Underwriting + settlement
Build (or buy) software that underwrites sub-merchants, assigns sub-merchant IDs under your master MID, handles settlement to sub-merchant bank accounts, manages chargebacks, reconciles daily batches, and reports to the sponsor bank. Expect $100k–$500k.
Step 6: Go live
Certification testing with the sponsor bank and networks. First pilot merchants. Ongoing compliance audits. You're finally live — 12 to 18 months after you started.
Total card-rail PayFac cost
| Item | Typical cost |
|---|---|
| Visa / Mastercard registration + fees | $75k–$100k/year |
| Sponsor bank setup + integration | $50k–$250k + ongoing |
| MTL licensing (US nationwide) | $2M–$5M |
| Compliance / BSA / AML infrastructure | $100k–$500k + staff |
| Underwriting software | $50k–$200k |
| Settlement + reconciliation systems | $100k–$500k |
| Legal + consulting | $100k–$250k |
| Total (realistic, nationwide US) | $2.5M–$7M upfront + ongoing |
| Time to first merchant live | 12–18 months |
The crypto-rail alternative
Here's the same business shape — master merchant, sub-merchants, one operator serving many — on stablecoin rails with PayRam:
- VPS: $20–$150/month (Hetzner, DigitalOcean, OVH, Vultr)
- Domain: ~$15/year
- Hardware wallet (master key): $50–$150 one-time
- Smart-contract deployment gas: $5–$30 one-time on Base or Polygon
- Time to first sub-merchant live: about 10 minutes
Why this works: on crypto rails there's no sponsor bank (no BIN required), no Visa / Mastercard registration (no card network involved), and no MTL licensing if you're running non-custodial software that never touches merchant funds. Your jurisdictional obligations still apply — always consult local counsel — but you skip the card-network infrastructure entirely.
When does the crypto path make sense?
- You're a SaaS platform, marketplace, or vertical specialist that wants embedded payments fast
- Your customers are already crypto-native (or comfortable with the card-to-crypto onramp for end-users)
- You want to serve categories card-rail PayFacs won't touch (iGaming, adult, creator platforms)
- You want to own the infrastructure, not rent it from a PaaS vendor
- You want to start without eight-figure capital and eighteen-month runways
When the card-rail path still wins
- You have the capital and timeline for a traditional PayFac build
- Your target merchants' customers expect card-only checkout (though PayRam's card-to-crypto onramp narrows this gap)
- You need chargeback economics that only card networks provide
- You're competing head-on with Stripe / Square in a mainstream B2C category
Next steps
If the crypto PayFac path fits your business, start with the operator playbook, then follow the 10-minute deploy guide. Or book a call to talk through your specific use case. For more on how this compares to the ISO model, see PayFac vs. ISO vs. Self-Hosted Gateway.
