How ISO Partnerships Work in Payment Processing
If you've ever gotten a call or email offering to set you up with credit card processing, there's a good chance the company on the other end wasn't the bank behind the transaction — it was an ISO. The term comes up constantly in payment processing but rarely gets explained clearly. This article breaks down what an Independent Sales Organization actually is, how the partnership structure works behind the scenes, and what it means for a merchant choosing between providers.
What an ISO Actually Is
ISO stands for Independent Sales Organization. It's a company that's been authorized by a card network — through a sponsoring bank — to sell and support merchant payment processing services, without being a bank itself. The ISO is the business you actually interact with: they sign you up, provide your equipment or software, and handle your day-to-day support. Behind that ISO sits a sponsoring bank (sometimes called an acquiring bank), which holds the actual banking relationship with the card networks and takes on the underlying financial risk of processing your transactions.
This structure exists because becoming a directly licensed acquiring bank is a heavy regulatory and financial undertaking that most processing-focused companies don't need to take on. Instead, an ISO partners with a bank that already has that infrastructure in place, and focuses its own resources on sales, service, technology, and merchant relationships.
It's worth noting that the term "ISO" is specific to card network terminology and is used somewhat differently across Visa, Mastercard, and other networks, though the underlying concept — a sponsored sales and service organization operating under a bank's authorization — is consistent across all of them. Most merchants never need to know which specific network relationship applies to their account; it's handled entirely on the back end.
How the Partnership Is Structured
In a typical ISO arrangement, the sponsoring bank underwrites the risk and maintains the network relationships required to move money between card networks, issuing banks, and the merchant's account. The ISO, in turn, handles merchant acquisition, onboarding, customer support, and often the technology layer — payment gateways, point-of-sale systems, reporting dashboards — that a merchant actually uses day to day.
Revenue in this relationship is typically split according to an agreement between the ISO and the sponsoring bank, based on the processing volume the ISO brings in and the services each party provides. The details of that split aren't usually visible to the merchant, but the structure is why an ISO can offer competitive processing rates and still operate profitably: they're distributing risk and infrastructure costs across a bank partnership rather than carrying them alone.
Why This Structure Matters to Merchants
For a merchant, the practical effect of the ISO model is that you get a single point of contact — the ISO — for sign-up, support, equipment, and software, while the underlying banking relationship is handled behind the scenes. This is generally a better experience than trying to deal directly with an acquiring bank's institutional processes, which are rarely built around small-business customer service.
It also means the quality of your experience depends heavily on which ISO you choose, since two ISOs sponsored by different banks can offer very different technology, support responsiveness, and contract terms even though the underlying card network processing is functionally similar. This is why comparing ISOs directly — rather than assuming they're interchangeable — is worth the time.
Questions Worth Asking an ISO Before You Sign
Because the ISO is your actual point of contact, it's worth asking direct questions before committing. Ask who the sponsoring bank is and how long the ISO has held that relationship, since a longer-standing sponsorship generally reflects more stability. Ask what happens to your account, your equipment, and your historical transaction data if the ISO's relationship with its sponsoring bank were ever to change. Ask how support requests are handled and what the actual response time looks like, rather than what's promised in marketing material. And ask for a clear breakdown of every fee in the contract, since rates quoted verbally don't always match what's itemized in the written agreement.
None of this is meant to suggest the ISO model is riskier than dealing with a bank directly — it isn't, and it's the standard structure behind the vast majority of small business card processing today. It's simply a relationship worth understanding so you know what you're actually signing up for.
ISO vs. Payment Facilitator: A Common Point of Confusion
Merchants researching this topic often run into a second term, "payment facilitator" or PayFac, and assume it's just another word for the same thing. It isn't. Under a traditional ISO model, each merchant is individually underwritten and gets its own dedicated merchant account with the sponsoring bank. Under a payment facilitator model, merchants are onboarded as sub-merchants under the payment facilitator's own master merchant account, with a faster, more automated sign-up process but generally less individual negotiating room on rates and terms.
Neither structure is universally better — a PayFac model tends to suit very small or fast-moving businesses that value quick onboarding over customization, while the ISO model tends to suit businesses that want a dedicated account, more tailored underwriting, and a direct relationship with a support team. It's worth knowing which structure a given provider is actually offering, since the marketing language often doesn't make the distinction obvious.
The Bigger Picture: ISO-in-a-Box and Banking Services
The ISO model also extends the other direction: some companies that want to build their own payment processing brand, rather than just accept payments, can become an ISO themselves through an ISO-in-a-box arrangement, which provides the banking sponsorship, infrastructure, and compliance framework needed to operate as an ISO without building that relationship from scratch. This is a different use case from typical merchant processing, but it's built on the exact same underlying structure described above, and it depends on the same kind of ISO banking services that sit behind any sponsored processing relationship.
How Expedio Payments Helps
Whether you're a merchant trying to understand who's actually behind your processing relationship, or a business exploring becoming an ISO yourself, Expedio Payments' ISO-in-a-box and ISO banking services provide the sponsorship, infrastructure, and support structure described in this article. Reach out to our team to talk through what the right setup looks like for your situation.
Frequently Asked Questions
Is an ISO the same thing as a payment processor?
They're closely related but not identical. An ISO sells and supports merchant processing services under a sponsoring bank's authorization, while "payment processor" more broadly can refer to the technology and infrastructure that actually moves transaction data — an ISO often provides or partners for that technology as part of its service.
Does working with an ISO instead of a bank directly cost more?
Not inherently. Rates depend on the specific agreement, merchant category, and processing volume rather than simply on whether the company is an ISO or a bank. Comparing itemized rate sheets directly is the only reliable way to know.
What happens to my merchant account if my ISO changes sponsoring banks?
This depends on the specific transition, but a well-run ISO change should be handled with advance notice and a clear transition plan for your account and equipment. This is worth asking about directly before signing with any ISO.
Can a business become an ISO itself?
Yes — this is typically done through an ISO-in-a-box style partnership, where an established banking and compliance infrastructure provider sponsors a new company to operate as an ISO, rather than that company building the banking relationship from scratch.