How to Become a Payment ISO in 2026: Registration, Costs, and the Self-Hosted Alternative

A Payment ISO (Independent Sales Organization) is a Visa/Mastercard-registered sales agent who brings merchants to a processor in exchange for residual commission on processed volume. It's a classic payments-industry business model: you build a portfolio of merchants, earn 10–40 basis points on every transaction they process, and collect residual income for years. This guide walks through the registration process, realistic costs, and a self-hosted alternative that lets you skip the ISO model entirely and own the gateway outright.

What a Payment ISO actually does

An ISO is a sales channel. You identify merchants, pitch them on a processor's services (rates, features, support), help them onboard, and earn a share of the processor's revenue from their processed volume. The merchant signs a contract with the processor — not with you. The processor handles settlement, chargebacks, and fund movement. You handle sales and relationship management.

For a deeper explainer on the model, see our Payment ISO pillar page.

Step 1: Find a sponsor bank and processor

You need two relationships:

Sponsor bank: provides the acquiring relationship through which your merchants process. Common sponsor banks for ISOs: Wells Fargo, Chesapeake, Esquire, Pathward, Fifth Third.
Processor / acquirer: provides the actual payment rails. Common choices: Fiserv (First Data), TSYS (Global Payments), Worldpay (FIS), Elavon, Chase Payment Solutions, Heartland.

Most ISOs pick one processor relationship and one sponsor bank. Some large ISOs maintain multiple processor relationships to shop rates.

Step 2: Register with Visa and Mastercard

Both card networks require ISO registration, typically through your sponsor bank. Costs:

Visa ISO registration: ~$5,000/year + setup fees
Mastercard ISO registration: ~$5,000/year + setup fees
Renewal audits and annual compliance attestations

Your sponsor bank typically handles the mechanics in exchange for a slice of your residual.

Step 3: Sign the ISO agreement

The ISO agreement with your processor covers:

Commission split (typically 10–40 bps of the discount rate, depending on volume tiers)
Residual payment terms (monthly payout, vesting schedule)
Exclusivity provisions (can you board merchants on other processors?)
Chargeback reserve requirements (you may be asked to fund a reserve)
Termination clauses (what happens to residuals if either side exits)

Read carefully. Residual terms are the difference between a good ISO book and a bad one.

Step 4: Compliance training

ISOs must complete PCI DSS training (at least attestation; Level 2–4 depending on handling of card data), BSA/AML orientation, and sponsor-bank specific compliance modules. Ongoing: annual re-certification, periodic audits.

Step 5: Build your sales motion

The operational job. You need a pipeline, a pitch, a set of rate cards, a boarding process, merchant statements you can read, and a way to handle merchant support. Many ISOs hire sub-agents (independent sales reps) and share residuals down the chain.

Step 6: Board your first merchant

Collect the merchant application, run underwriting through the processor, provision their MID, configure their gateway (if applicable), train them on chargeback response. First merchant live. Residuals start flowing 60–90 days after first processed transaction (processors hold back to confirm no chargebacks).

Realistic costs

Item	Typical cost
Visa + Mastercard ISO registration	$10k/year + setup
Sponsor bank onboarding + compliance	$5k–$25k
ISO agreement + legal review	$10k–$25k
PCI DSS attestation	$2k–$10k
Sales + CRM infrastructure	$5k–$50k
Reserve / collateral	Varies (processor call)
Total (realistic)	$30k–$100k upfront
Time to first merchant live	2–6 months

ISO residual economics

A realistic mid-size ISO book might look like this:

500 active merchants
$5M average monthly processing volume
2.5% average discount rate → $125k/month gross processor revenue from the book
25 bps residual → ~$12.5k/month to the ISO
Per-merchant residual split with sub-agents (if any): 50% → $6.25k/month

That's $75k/year of recurring income from a mid-size book, with ongoing sales effort to replace churn. Larger ISOs scale into the millions. The catch: you don't own any of it. Change of processor, change of sponsor bank, change of network policy — any of these can disrupt the residual stream.

The self-hosted alternative

If you're going to the trouble of building a merchant-facing sales motion, consider skipping the ISO model and running the gateway yourself. PayRam gives you the operator economics of owning the stack:

Deploy on a VPS in 10 minutes — no sponsor bank, no Visa registration
Onboard merchants directly on your infrastructure, under your brand
Set your own rates — you're not splitting with a processor
Non-custodial: settlement goes merchant-wallet-to-merchant-wallet, you never touch funds
No one can cut you off — the rails are on-chain, not in a processor's database

ISO vs. self-hosted economics, same book

Scenario	ISO path (25 bps residual)	PayRam path (50 bps margin)
$1M/mo portfolio	$2.5k/mo	$5k/mo
$5M/mo portfolio	$12.5k/mo	$25k/mo
$25M/mo portfolio	$62.5k/mo	$125k/mo
Revenue vulnerability	Processor can change terms or drop	None (you own it)

Rates above are directional. Your actual margin depends on what you negotiate with merchants. The point: on a portfolio of similar size, an owned-gateway operator keeps more of the spread and carries less counter-party risk than an ISO does.

When ISO is still the right choice

You have deep relationships with established B2C merchants whose customers must pay by card
You want minimal operational burden — the processor handles everything
You're scaling an existing ISO book and the residual stream is already material

When the self-hosted path makes sense

You're starting fresh and want to own the infrastructure
Your merchants are crypto-friendly or will accept the card-to-crypto onramp
You want to serve categories card-rail ISOs can't (iGaming, adult, high-risk e-commerce)
You want un-capped upside on margin instead of a fixed residual split