What is PayFac-as-a-Service?

PayFac-as-a-Service (PaaS) is a vendor-hosted platform that handles the card-rail PayFac machinery — sponsor-bank relationships, registrations, compliance, settlement — so you can launch a sub-merchant program without building the full stack yourself. PayRam is the self-hosted, non-custodial, stablecoin-native alternative.

Do I need a sponsor bank to be a Payment Facilitator?

For card rails, yes — a sponsor bank provides the BIN and acquiring relationship. For crypto rails with PayRam, no. Settlements happen on-chain directly to merchant-controlled wallets, so there is no card network and no sponsor bank in the loop.

How is a PayFac different from a Payment ISO?

An ISO resells a processor’s service and earns residual commission on volume; the merchant has a direct contract with the processor. A PayFac onboards sub-merchants under its own master merchant account; the sub-merchant contracts with the PayFac, not the processor. A crypto-native PayRam deployment sits outside both models — you own the infrastructure outright.

Is sub-merchant KYC required?

Card-rail PayFacs are obligated to KYC every sub-merchant above Visa / Mastercard volume thresholds. PayRam is infrastructure you run — what KYC you apply to sub-merchants is your decision based on your jurisdiction, not a network mandate.

PayFac · Reimagined

The Payment Facilitator model. Without the sponsor bank.

Q: What is a Payment Facilitator (PayFac)?

A Payment Facilitator is a master merchant that onboards sub-merchants under its own acquiring relationship, removing the need for each sub-merchant to sign their own processor contract. PayFacs own the master MID, the sponsor-bank relationship, and the underwriting decision — sub-merchants simply register and start transacting.

Q: What does it cost to become a Payment Facilitator?

Traditional card-rail PayFac certification typically costs $500k–$5M in Visa / Mastercard registration fees, compliance audits, MTL state licensing, underwriting infrastructure, and staff — plus 12–18 months of setup. Launching a crypto-native PayFac with PayRam costs a VPS (~$20–$150/month), a domain, and a hardware wallet. Setup takes about 10 minutes.

PayRam gives you the master-merchant / sub-merchant architecture a PayFac provides — on stablecoin rails. No sponsor bank, no MTL registration in most jurisdictions, no card-network gatekeeper. Deploy once, onboard sub-merchants in seconds, settle directly to their own cold wallets.

Book a call Deploy your instance Operator playbook

The crypto PayFac patternNo sponsor bank·No KYB for operators·No card-network dependency·Non-custodial settlement

The model

What is a Payment Facilitator?

A Payment Facilitator (PayFac) is a master merchant that onboards sub-merchants under its own acquiring relationship. Instead of every small merchant signing their own processor contract and going through bank underwriting, they register under the PayFac in minutes.

The PayFac carries the sponsor-bank relationship, the BIN, the underwriting policy, the sub-merchant roster, and the liability. The sub-merchant signs up for the PayFac — not for Visa, not for Stripe, not for a processor they've never heard of. It's the pattern behind Stripe, Square, Toast, Mindbody, Shopify Payments, and every modern SaaS that ships an embedded checkout.

The problem: setting up a card-rail PayFac costs $500K–$5Min registrations, licenses, compliance audits, and underwriting infrastructure, and takes 12–18 months. It's a moat — which is exactly why hosted PayFac vendors (PayFac-as-a-Service) charge what they do.

PayRam: the crypto PayFac

Same pattern. Different rails.

PayRam delivers the operational shape of a Payment Facilitator — master merchant, sub-merchants, one instance serving many — on stablecoin infrastructure. The value prop survives the rail change. The bank dependency doesn't.

Master-merchant architecture

One PayRam instance is the master. Each sub-merchant is a tenant with their own deposit wallet, API keys, webhook URL, and reference namespace. Reconciliation is automatic — every payment arrives tagged with the sub-merchant it belongs to.

Sub-merchant onboarding in seconds

Create a merchant in the operator dashboard, they designate a cold wallet, you hand them their API key. No KYB queue, no underwriting, no sponsor-bank review. You decide what KYC to apply based on your jurisdiction — not Visa’s.

Non-custodial settlement

Funds flow from the customer wallet (or card, via PayRam’s card-to-crypto onramp) directly to the sub-merchant’s cold wallet via smart-contract sweeps. PayRam never touches their money. You never touch their money. There is no third-party custodian who can freeze the flow.

No sponsor bank, no card network

Card-rail PayFacs depend on a BIN and an acquiring relationship — that’s why 3% of revenue goes to Visa / Mastercard. A crypto PayFac on PayRam settles on-chain with a typical fee of less than $0.01 per transaction on Tron USDT or Base USDC. No middleman, no commission, no single point of failure.

Multi-tenant by design

A single instance on a modest VPS comfortably serves 50+ sub-merchants. Per-merchant API keys, per-merchant webhooks, per-merchant wallets, per-merchant references. Scale is a database concern, not a bank-approval concern.

Your brand, not PayRam’s

Deploy on your own domain. Style the checkout to match your product. Your sub-merchants see your brand, your support, your terms of service — not PayRam's. Full white-label details here.

Side-by-side

Card-rail PayFac. PaaS vendor. PayRam.

The three realistic paths to running sub-merchants under one operator. Numbers are directional — vendor pricing varies and deployment scope shifts with jurisdiction.

Feature	Card-rail PayFac	PayFac-as-a-Service	PayRam (crypto)
Setup cost	$500k–$5M	$50k–$250k + rev share	~$20–$150 VPS/mo
Setup time	12–18 months	3–6 months	~10 minutes
Sponsor bank required	Yes	Yes (vendor’s)	No
Visa/MC registration	Required	Required (vendor)	Not applicable
MTL licensing	State-by-state	Varies by vendor	Depends on jurisdiction
Sub-merchant onboarding time	Hours to days	Minutes	Under 30 seconds
Fund custody	PayFac (pooled)	Vendor	Merchant-controlled wallet
Rolling reserve	5–10% of GMV	Varies	Zero
Chargeback liability	PayFac	Shared with vendor	None (on-chain is final)
Take rate on volume	2.5–3.5%	1–2%	Whatever you charge
Deplatform risk	Visa / MC / sponsor bank	Vendor ToS	Zero (you own the stack)

Use cases

Who runs a crypto PayFac?

SaaS platform

Every customer takes payments through your checkout. You keep the integration, the sub-merchants settle to their own wallets. No processor in the middle.

Marketplace

Buyers pay, sellers get paid. Each seller is a sub-merchant with their own wallet and reference namespace. Reconciliation is automatic per seller.

Agency

Deploy once, onboard dozens of clients under your brand. Charge setup + monthly + volume margin. Your clients never see PayRam.

Cross-border payout service

Collect USDC in one jurisdiction, pay out to a sub-merchant’s wallet in another. Spread between traditional remittance (6–8%) and crypto fees (<$0.01) is the margin.

Creator / platform economy

Every creator is a sub-merchant. Fans pay directly to the creator’s wallet. You take a flat platform fee without touching funds.

Vertical-specific PSP

iGaming, adult, high-risk — categories the card-rail PayFacs won’t touch. Stablecoin rails don’t discriminate by vertical.

Economics

PayFac cost, disaggregated.

Here's roughly what a traditional card-rail PayFac program costs to stand up, and why PayFac-as-a-Service exists. Numbers vary by jurisdiction — order of magnitude is what matters.

Visa / Mastercard PayFac registration$75k–$100k + annual

Sponsor bank setup + integration$50k–$250k + ongoing

MTL licensing (per US state)$50k–$250k each, 50 states

Compliance + BSA/AML infrastructure$100k–$500k + staff

Underwriting software + manual review$50k–$200k + ongoing

Settlement + reconciliation systems$100k–$500k

Time to first sub-merchant live12–18 months

PayRam (crypto PayFac)~$20–$150/mo VPS

Supported Chains & Tokens

20+ tokens across 6 networks. Stablecoin-native — USDT and USDC on every supported chain.

Bitcoin

BTC

Variable · ~10 min

Ethereum

ETH

~$1–5 · ~15 sec

Tron

TRX

~$0.01 · ~3 sec

Base

BASE

~$0.01 · ~2 sec

Polygon

POL

~$0.01 · ~5 sec

Soon

Solana

SOL

~$0.001 · ~0.4 sec

Primary stablecoins:

USDT

USDC

+ BTC, ETH, TRX, and 15 more

Payment Facilitator questions.

What is a Payment Facilitator (PayFac)?+

A Payment Facilitator is a master merchant that onboards sub-merchants under its own acquiring relationship, so each sub-merchant doesn’t need to sign their own contract with the processor. The PayFac owns the master MID, the sponsor-bank relationship, and the underwriting decision — sub-merchants simply register and start transacting. It’s how Stripe, Square, and modern SaaS platforms onboard millions of merchants quickly without asking each one to go through a bank approval.

What’s the difference between PayFac and PayFac-as-a-Service (PaaS)?+

A full PayFac runs the entire stack — certifications, sponsor-bank relationship, underwriting, settlement. PayFac-as-a-Service vendors handle that machinery for you, letting your brand sit on top. PayRam is the self-hosted version of PaaS on crypto rails: you own the stack outright without any vendor dependency, no sponsor bank, no third-party in the settlement path.

Do I need a sponsor bank to operate like a PayFac?+

For card rails, yes — the sponsor bank provides your BIN and the acquiring relationship. For crypto rails with PayRam, no. Settlements flow on-chain directly to merchant-controlled wallets. There is no card network, no acquirer, and no sponsor — and no one in the middle who can cut off your operation.

What does sub-merchant onboarding look like?+

On a traditional PayFac: collect KYC, run underwriting, provision a sub-merchant ID under your master MID, wait for the network. On PayRam: the operator creates the merchant in the dashboard, the merchant designates their cold wallet, the operator issues an API key, and the merchant is live. Typical time: under 30 seconds.

How does a crypto PayFac make money?+

Three common shapes: (1) a setup fee per merchant for operator-managed deployment, (2) a monthly retainer for ongoing operations, or (3) a volume margin you negotiate directly with each sub-merchant. Because PayRam is non-custodial, your revenue flows outside the payment stack — you never need to touch merchant funds. See the operator playbook for the four business models.

What does it cost to become a Payment Facilitator?+

Traditional card-rail PayFac certification runs $500k–$5M in Visa / Mastercard registration fees, compliance audits, MTL state licensing, underwriting infrastructure, and operations staff — plus 12–18 months of setup. Launching a crypto-native PayFac with PayRam costs a VPS (~$20–$150/month), a domain, and a hardware wallet. Deploy takes about 10 minutes.

How is this different from a Payment ISO?+

A Payment ISO resells a processor's service and earns residual commission; the merchant contracts directly with the processor. A PayFac onboards sub-merchants under its own master account; the sub-merchant contracts with the PayFac. PayRam sits outside both — you own the infrastructure, your merchants contract with you on your terms, no external processor in the chain. Full ISO comparison.

Is a crypto PayFac legal?+

PayRam is self-hosted software. Any jurisdictional obligations — MTL licensing, KYC/AML where required, tax reporting, consumer-protection rules — are the operator’s responsibility. PayRam does not hold funds, is not a payment service provider, and carries no liability for how operators use the software. Always consult local counsel before launching commercially.

Skip the sponsor bank. Launch this quarter.

You don't need a year, a lawyer, or a Visa sponsor to start running a payment service for your clients. You need a VPS, a cold wallet, and an operator mindset.

Book a call Full operator playbook Deploy your instance Docs