ISO vs PSP vs Acquirer: Who You Sign With

Most high-risk merchants who apply for a merchant account submit their application to an ISO, receive approval from an ISO, and receive support from an ISO. The ISO is the company they know, the relationship they manage, and the name on the emails they receive. The acquirer is often a name the merchant has never heard.

This matters because the ISO and the acquirer are different entities with different roles, different obligations, and different levels of authority over the merchant’s account. Understanding who each party is, what they control, and what happens when things go wrong requires understanding how the processing chain is actually structured.

The Acquirer: The Entity That Actually Holds Your Account

The acquiring bank, also called the acquirer or merchant acquirer, is the financial institution that underwrites the merchant account, issues the MID, assumes liability for chargebacks, settles funds to the merchant, and maintains the direct relationship with Visa and Mastercard on the merchant’s behalf.

The acquirer is the entity that reviewed the merchant’s file through underwriting, made the credit decision to approve the account, set the reserve requirements, and defined the processing limits in the contract. When a chargeback arrives, the acquirer is the party that absorbs the loss before recovering it from the merchant. When a merchant is terminated, the acquirer is the party that submits the MATCH listing if the termination is for cause.

Most acquirers do not deal directly with high-risk merchants at the individual account level. They manage portfolios and rely on ISOs and PSPs to handle merchant-facing sales, onboarding, and support. The merchant who applies through an ISO is getting access to an acquiring relationship that the ISO has negotiated and maintains with the bank.

Examples of acquiring banks active in high-risk portfolios include Worldpay, Elavon, Wells Fargo Merchant Services, Chesapeake Bank, and several offshore and European institutions. The acquiring bank behind any given ISO is material information for the merchant, because that bank’s risk appetite, reserve policies, processing category tolerances, and monitoring program responses are what govern the account in practice.

The ISO: The Front Door to the Acquiring Relationship

An ISO, or Independent Sales Organization, is a third-party company registered with Visa and Mastercard that is authorized to sell merchant account services on behalf of an acquiring bank. ISOs are the primary sales and service channel through which most high-risk merchants access dedicated merchant accounts.

The ISO handles the merchant-facing side of the relationship: marketing to prospective merchants, collecting applications, submitting files to the acquirer for underwriting, onboarding approved accounts, providing customer service, and managing the ongoing relationship. The ISO does not underwrite the account independently. It does not hold the merchant’s funds. It does not issue the MID. All of these functions belong to the acquiring bank behind the ISO.

Visa’s Global Registry of Service Providers, published at visa.com, confirms that ISOs must be registered with Visa before conducting merchant solicitation activities on behalf of acquiring banks. Visa maintains a specific ISO High Risk category for ISOs that contract with acquirers to provide merchant solicitation and sales in restricted verticals. The registration requirement confirms that the ISO is operating as an authorized agent of a member bank, not as an independent financial institution.

A high-risk ISO that specializes in a specific vertical, such as supplements, iGaming, or adult content, has typically negotiated underwriting parameters with its acquiring bank partners that accommodate those categories. The ISO’s specialty is in knowing which acquirers will take which categories and in packaging the merchant’s file in a way that those acquirers can evaluate efficiently. The ISO’s value is channel access and category knowledge, not independent underwriting authority.

The PSP: The Technology and Processing Layer

A PSP, or Payment Service Provider, is a company that provides the technology infrastructure for payment processing. This includes the payment gateway, transaction routing, fraud screening, reporting, and in many cases the connection to one or more acquiring banks. PSPs may or may not be acquirers themselves.

A non-acquirer PSP connects to one or more acquiring banks on behalf of merchants. The PSP handles the technical side of transaction processing while the acquirer handles the financial side, including funding the merchant account and assuming chargeback liability. Merchants who use a non-acquirer PSP have a processing relationship managed by the PSP and a funding relationship managed by the underlying acquirer.

A PSP that is also an acquirer handles both the technical and financial sides of the relationship. Adyen and Worldpay are examples of entities that function as both PSP and acquirer in many markets. In these arrangements, the merchant’s contract is with a single entity that controls the full processing stack.

The distinction matters for high-risk merchants because the PSP layer is where integration and routing decisions are made, while the acquirer layer is where underwriting and chargeback liability decisions are made. A merchant who is unhappy with their PSP’s gateway features but satisfied with their acquiring relationship may be able to change gateways without changing acquirers. A merchant who is unhappy with their acquirer’s reserve terms has a different problem that requires a different solution.

The PayFac: The Aggregator Model Revisited

A PayFac, or Payment Facilitator, is a PSP that holds a master merchant account with an acquirer and boards merchants as sub-merchants under that master MID. Stripe, Square, PayPal, and Shopify Payments are PayFacs. The PayFac aggregator model and its structural differences from a dedicated merchant account are covered in detail in the aggregator guide in this cluster.

The key distinction for this article’s purpose is that a merchant signing with a PayFac is not signing with an ISO. They are signing as a sub-merchant under the PayFac’s own acquiring relationship. There is no individual underwriting, no dedicated MID, and no direct acquirer relationship for the sub-merchant. The PayFac’s master MID is the only merchant account in the arrangement.

What the Structure Means for High-Risk Merchants

High-risk merchants who are applying for a dedicated merchant account are almost always dealing with an ISO as their primary contact. The ISO is who they call, who they email, and who they see at trade shows. But the decisions that matter most to the merchant’s account stability are made by the acquiring bank behind the ISO.

The reserve percentage is set by the acquirer, not the ISO. The processing limit is set by the acquirer. The MATCH listing, if the account is terminated for cause, is submitted by the acquirer. The monitoring program enrollment, when the chargeback ratio crosses the VAMP or ECM threshold, is the acquirer’s responsibility to manage.

This means that when evaluating an ISO, the most important question is not about the ISO’s features or customer service. It is about which acquirer or acquirers the ISO has relationships with, what those acquirers’ track records are with the specific merchant category, and what reserve and rate terms those acquirers typically offer for that vertical. An ISO that can answer these questions specifically, naming the acquiring bank and its category experience, is more valuable to a high-risk merchant than one that cannot.

The full picture of how merchant accounts work, what underwriting involves, and what the contract terms cover is in the high-risk merchant accounts hub. The acquirer and issuer roles in the transaction flow are covered in the payments 101 section of this site.

For merchants who need processing and cannot access a traditional ISO and acquiring relationship for their category, RiskPay operates on non-custodial rails that bypass the ISO and acquirer structure entirely. There is no acquiring bank in the chain, no ISO intermediary, and no reserve set by an underwriting committee. Settlement goes directly to the merchant’s own wallet in USDC on Polygon.

Frequently Asked Questions

What is the difference between an ISO and an acquirer?

An ISO is a third-party sales organization authorized to sell merchant account services on behalf of an acquiring bank. The acquirer is the bank that actually underwrites the account, issues the MID, holds the funds in transit, assumes chargeback liability, and submits MATCH listings on termination. A merchant who signs with an ISO has their account held at the acquiring bank behind the ISO, not at the ISO itself.

What does a PSP do that an acquirer does not?

A PSP provides the technology infrastructure for payment processing including the gateway, routing, and reporting. An acquirer provides the financial infrastructure including the merchant account, funding, and chargeback liability. A PSP that is not an acquirer connects to an acquiring bank on behalf of its merchants. A PSP that is also an acquirer handles both functions. Merchants may have separate PSP and acquirer relationships or a single entity handling both.

Why do most high-risk merchants deal with ISOs rather than acquirers directly?

Most acquiring banks do not maintain direct merchant-facing sales and support operations for individual high-risk merchants. They rely on ISOs to source, onboard, and manage merchant relationships. High-risk ISOs that specialize in specific verticals have established underwriting parameters with acquirers that accommodate those categories, giving merchants in restricted categories access to acquiring relationships that would not be available through a direct bank approach.

What should a high-risk merchant ask an ISO before signing?

The most important questions are: which acquiring bank or banks will hold the account, what is that acquirer’s experience with this specific merchant category, what reserve percentage and reserve period does the acquirer typically require for this vertical, and what are the processing limits at initial approval. An ISO that can answer these questions specifically is demonstrating that it has an actual underwriting relationship with a named acquirer, not a general marketing relationship.

---