ISO vs ISV: what’s the difference?

An ISV (Independent Software Vendor) is a software company that integrates payments into their product — typically using a PayFac or a gateway behind the scenes. An ISO is primarily a payments sales channel. Modern SaaS companies increasingly act as their own PayFac (or embed a PaaS vendor) rather than partner with an ISO.

Can I run an ISO program without a sponsor bank?

Not on card rails — a sponsor bank is structurally required. On crypto rails with PayRam, you can operate the same resale / multi-merchant economics without a sponsor bank, without Visa registration, and without splitting residuals with a processor you don’t own.

ISO · Alternative path

Stop reselling. Start operating.

Q: What is a Payment ISO?

A Payment ISO (Independent Sales Organization) is a sales agent registered with Visa or Mastercard that resells a processor’s or acquirer’s services to merchants. ISOs don’t own the merchant contract — they bring merchants to the processor in exchange for residual commission on processed volume, typically 10–40 basis points.

Q: ISO vs PayFac: what’s the difference?

An ISO resells; the merchant contracts directly with the processor. A PayFac onboards sub-merchants under its own master merchant account; the sub-merchant contracts with the PayFac. ISOs earn residuals and carry no liability. PayFacs carry full liability and keep a larger share. Neither model is self-hosted.

Q: How do ISOs make money?

Residual commission on processed volume — typically 10–40 basis points of the discount rate charged to the merchant. A merchant processing $1M/month at a 2.5% rate generates ~$25k in processor revenue; the ISO takes a slice. Residual income accrues as long as the merchant keeps processing.

Q: How do I become a Payment ISO?

Register as a Visa / Mastercard ISO via a sponsor bank or acquirer (typically $5k–$10k annual fees each), sign an ISO agreement with a processor, complete compliance training, and start boarding merchants. Launching a crypto-native alternative with PayRam is instant by comparison — no registration, no sponsor, no residual split.

A Payment ISO resells a processor's service for residual commission — and the processor can pull the rug at any time. PayRam lets you skip the ISO model entirely and run the gateway yourself. No sponsor bank, no Visa registration, no residual split. Your infrastructure, your merchants, your margin.

Book a call Deploy your gateway Operator playbook

The ISO alternativeKeep 100% of the spread·No sponsor bank·No Visa / MC registration·No processor can drop you

The model

What is a Payment ISO?

An Independent Sales Organizationis a Visa / Mastercard-registered agent that resells a processor's or acquirer's payment services to merchants. The merchant signs a contract with the processor — not with the ISO. The ISO earns residual commission on the processed volume, typically 10–40 basis points of the discount rate.

It's a sales-channel model. Good ISOs build portfolios of thousands of merchants and collect residual income for years. The catch: you don't own the merchant relationship, the processor can change rates or residual splits on renewal, and if the processor cuts the merchant off, your residual stops.

The crypto-rails alternative is not to become an ISO — it's to skip the model. Run your own gateway, own your merchant contracts, keep the full spread.

Side-by-side

ISO. PayFac. Self-hosted.

Three models for operating a multi-merchant payment business. Only one lets you own the stack end-to-end.

Feature	Payment ISO	PayFac	PayRam
Who owns the merchant contract	Processor	PayFac	You
Visa / MC registration required	Yes	Yes	No
Sponsor bank required	Yes	Yes	No
Revenue model	Residual (10–40 bps)	Full rate minus costs	You set the rate
Take-rate ceiling	Fixed by processor	~0.5–1% margin	Uncapped
Liability for chargebacks	Merchant	PayFac	None (on-chain is final)
Processor can drop you	Yes	Yes (sponsor bank can)	No
Onboarding time (per merchant)	Days	Minutes–hours	Under 30 seconds
Setup cost	$5k–$25k	$500k–$5M	~$20–$150/mo VPS
Fund custody	Processor	PayFac (pooled)	Merchant wallet

The pivot

Own the stack. Skip the split.

ISO path

You sell someone else’s product

Register with Visa / Mastercard via a sponsor bank
Partner with a processor and sign their contract
Bring merchants — residuals flow back from the processor
Processor sets the discount rate; you take a slice
Residual stops when a merchant churns or gets deplatformed
No control over uptime, categories, or feature roadmap

PayRam path

You run the gateway yourself

Deploy PayRam on a VPS (10 minutes, $20–$150/mo)
Onboard merchants under your own brand
Set your own rates, your own fees, your own terms
Every merchant settles to their own cold wallet — you never custody
No processor, no sponsor bank, no third-party who can drop you
Keep 100% of whatever spread you negotiate

Economics

Residual vs. owned revenue.

Directional example on a $5M/month merchant portfolio — assumes 2.5% card discount rate, 30 bps ISO residual, or a 50 bps operator margin on crypto rails.

ISO path

~$15k/mo

30 bps residual on $5M/mo volume. Stops the moment the processor or merchant relationship ends.

PayRam path

~$25k/mo

50 bps operator margin on $5M/mo — your rate, your merchants, your infrastructure. Plus setup fees and monthly retainers on top.

Who switches from ISO to operator

The pivot profiles.

Ex-ISO operator

You built an ISO portfolio. Now you want to own the rails instead of reselling. PayRam is the migration path — invite your merchants onto your gateway instead of the processor’s.

Vertical niche

You have audience + expertise in one vertical (iGaming, adult, creator platforms). Card-rail ISOs won’t touch those categories. Crypto rails don’t discriminate.

Cross-border operator

Traditional ISOs are geographically constrained by sponsor banks. A PayRam deployment works globally from day one.

SaaS reseller program

Your SaaS already has a reseller channel. Layer payments on top: each reseller becomes an operator with their own sub-merchant portfolio on your gateway.

Payment consultant

You advise merchants on payment setups. Ship them on your PayRam instance instead of pushing them to a processor — you keep the client relationship.

Fractional CTO / fractional PSP

Offer "payments as a service" to startup clients. Deploy once, onboard a dozen clients, manage from one dashboard.

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 ISO questions.

What is a Payment ISO?+

A Payment ISO (Independent Sales Organization) is a Visa/Mastercard-registered sales agent that resells a processor’s or acquirer’s services to merchants. The ISO brings the merchant to the processor; the merchant signs directly with the processor. The ISO earns residual commission on processed volume — typically 10–40 basis points of the discount rate — for as long as the merchant keeps running.

ISO vs PayFac vs ISV: what’s the actual difference?+

An ISO resells — the merchant contracts with the processor, the ISO earns residuals. A PayFac onboards sub-merchants under its own master merchant account — the sub-merchant contracts with the PayFac, which carries the liability. An ISV (Independent Software Vendor) is a software company that integrates payments into its product, usually through a PayFac or a hosted gateway. See the PayFac explainer for the PayFac side.

How do ISOs make money?+

Residual commission on processed volume. A merchant doing $1M/month at a 2.5% discount rate generates ~$25k in processor revenue; the ISO takes 10–40 basis points as residual. Income accrues while the merchant keeps processing — the moment they churn or get deplatformed, the residual stops.

How do I become a Payment ISO?+

Register as a Visa / Mastercard ISO through a sponsor bank or acquirer (typically $5k–$10k annual fees per card brand), sign an ISO agreement with a processor, complete compliance training, and start boarding merchants. Setup is faster than becoming a PayFac but slower and more encumbered than simply operating your own gateway on crypto rails.

What does Payment ISO residual income look like?+

On a $5M/month portfolio at 2.5% discount with a 30 bps residual: ~$15k/month recurring. The catch: you don’t control the underlying processor contract. The processor can raise rates, change residual splits, or drop you. A PayRam-based model gives you the same multi-merchant economics but you own the infrastructure.

Can I skip the ISO model and run my own gateway instead?+

Yes — that's exactly what PayRam is for. Deploy a self-hosted instance, onboard merchants under your own brand, charge your own rates, keep 100% of the spread. No sponsor bank, no residual split, no processor in the middle. Full operator playbook.

What are the licensing requirements for a Payment ISO?+

Card-rail ISOs register with Visa / Mastercard, typically through a sponsor bank, and complete PCI DSS scope review. US state MTL requirements may apply depending on whether you touch merchant funds. Crypto rails with PayRam sidestep most of the network-specific registrations, though jurisdictional obligations (MTL, KYC/AML) remain the operator’s responsibility depending on where they operate.

How does PayRam compare to an ISO processor partnership?+

An ISO partnership gives you a sales territory and a residual slice — you’re essentially an affiliate for the processor. PayRam gives you the full stack: the checkout, the API, the sub-merchant management, the settlement engine. You’re not reselling; you’re the operator.

Don't rent the residual. Own the stack.

Every dollar a processor keeps is a dollar you're leaving on the table. Deploy your own gateway, onboard your merchants under your own brand, negotiate your own rates.

Book a call Operator playbook Deploy your instance Docs