The Line Visa Draws Between a Referral Agent and a Registered ISO
An unregistered referral partner can generate leads in a registered ISO's name. The moment they discuss pricing or draft a contract, that line is crossed.

- Visa's own Third Party Agent Registration Program draws a specific, bright line between a referral entity and a registered ISO. A referral partner may generate leads and market in the registered ISO's name, but the moment they discuss pricing, fees, or contract terms, or submit an application themselves, they have crossed into activity only a registered ISO may legally perform.
- Visa Core Rules Section 1.9.8.6 requires registration to be completed before the performance of any contracted services or transaction activity, and Section 1.9.8.7 makes that registration specific to each acquirer, meaning the same agent needs a separate registration for every acquirer relationship they actually work under.
- Effective October 24, 2026, Members in the Canada and US regions must additionally disclose a Third Party Agent's numeric IDs, issuing and acquiring identifiers, BINs, and account ranges to Visa, and review that information annually. This is a new, specific recordkeeping obligation layered on top of the registration requirement itself.
- The 25 percent affiliate exemption from registration does not apply to Payment Facilitators, Marketplaces, Business or Consumer Bill Payment Service Providers, or Digital Wallet Operators running Staged Digital Wallets, regardless of how closely affiliated they are with the registering Member.
The line Visa draws between a referral agent and a registered ISO is specific and nameable. A referral partner may generate leads and market in a registered ISO’s name. The instant they discuss pricing, fees, contract terms, or submit an application themselves, they have stepped into activity Visa’s own rules reserve for a registered ISO alone. That line is not a gray area or a matter of internal company policy. It is written into Visa’s Third Party Agent Registration Program, and it explains a specific, recurring friction point in how ISOs actually staff their sales organizations.
What actually separates a referral entity from an ISO
Visa’s Third Party Agent Registration Program FAQ defines an ISO as any entity that solicits merchant or cardholder accounts, discusses pricing, fees, or rates, processes merchant or cardholder accounts, discusses terms and agreements, manages or drafts contracts, or submits contracts to the registering acquirer or issuer. A registered ISO is permitted to use referral entities or sales representatives to solicit on its behalf, but those referral entities may only solicit and market in the name of the registered ISO itself. They may not provide ISO services independently.
The FAQ draws the practical consequence out explicitly. A referral entity or sales representative marketing in its own name may only generate leads for a registered ISO. It may not discuss pricing, fees, or rates, process accounts, discuss terms, draft or manage contracts, or submit contracts to an acquirer or issuer. An acquirer is barred from processing applications submitted by any entity it has not itself registered as an ISO. The line is not about how senior or experienced the referral partner is. It is about which specific activities that partner is performing, measured against a fixed list.
Why this line actually matters day to day
This distinction shows up constantly in how an ISO’s sales organization actually operates, often without anyone framing it in these exact terms. A sales rep who has built real relationships with prospective merchants, and who understands pricing well enough to answer a question accurately, is still not permitted to discuss that pricing directly with a merchant unless they are registered, or unless they are strictly relaying a quote the registered ISO itself produced and approved. A rep who starts negotiating terms, or who drafts language into a contract before sending it up the chain, has moved from generating a lead into performing registered ISO services, regardless of whether their business card says “agent,” “representative,” or something else entirely.
This is precisely why a competent, well-intentioned sales rep can end up personally handling a surprising amount of back-office-adjacent work: not because the work is inherently theirs to do, but because nobody built a clean handoff point where the rep’s job legitimately ends and a registered entity’s job legitimately begins. A rep who is told to “just get the paperwork moving” with a merchant, without a clear boundary on what they can and cannot discuss or submit themselves, is being set up to cross this line without necessarily realizing it.
When registration actually has to be in place
Visa Core Rules and Visa Product and Service Rules, Section 1.9.8.6, states plainly that a Member must register a Third Party Agent with Visa, using the Program Request Management application and completing the appropriate regional forms, and that registration must be completed before the performance of any contracted services or transaction activity. The timing is not flexible. An agent beginning to perform services before registration clears is not in a gray period. They are operating outside what the rule permits, from the first transaction forward.
Section 1.9.8.7 adds a layer that is easy to miss: registration of a Third Party Agent is specific to each acquirer. An agent working relationships under two different acquirers does not get to rely on a single registration covering both. Each acquirer has to register that same agent separately, which means an ISO’s back office is not managing one registration per agent. It is managing one registration per agent per acquirer relationship that agent actually touches, a multiplier that grows quickly for any ISO working with more than one sponsor.
The new disclosure requirement that just took effect
Visa’s rules add a specific, dated obligation that applies directly to the US and Canada regions. Effective October 24, 2026, as part of the Third Party Agent registration process, Members in the Canada and US regions must disclose to Visa the numeric IDs associated with their Third Party Agent, along with the issuing identifiers, acquiring identifiers, all BINs, and any applicable account ranges that agent uses to perform contracted services or transaction activity on the Member’s behalf, including in connection with end-consumer or merchant-facing programs. The Member is responsible for maintaining accurate, complete, and current information for each Third Party Agent, and for reviewing and updating that information annually, following any change, or upon Visa’s request.
This is not a restatement of the original registration requirement. It is a new, specific recordkeeping obligation layered on top of it, and it adds a dimension most ISO back offices were not tracking before this effective date: not just whether an agent is registered, but whether every numeric ID, BIN, and account range that agent actually touches is currently and accurately disclosed, with an annual review cycle to keep it that way.
The affiliate exemption, and who it actually excludes
Visa’s rules do carve out a narrow exemption from registration. A Third Party Agent is exempt if it only provides services on behalf of affiliates, including parents and subsidiaries, that are Members owning and controlling at least 25 percent of that agent. On its face, this sounds like it could cover a broad range of closely held referral arrangements.
The rule immediately narrows that exemption back down. It explicitly does not apply to Business Payment Service Providers, Consumer Bill Payment Service Providers, Marketplaces, Payment Facilitators, or Digital Wallet Operators that operate Staged Digital Wallets, regardless of how the 25 percent ownership test comes out. An ISO or a platform assuming an affiliated entity is automatically exempt from registration because of a clean ownership structure needs to check which specific category that entity actually falls into first. The exemption exists, but it was written narrowly enough that most of the entity types doing meaningful payments work do not qualify for it at all.
Why the acquirer, not the ISO alone, enforces this line
The rule also puts an obligation on the acquirer specifically, not just on the ISO managing its own sales force. The FAQ states that an acquirer must not process applications from any entity it has not itself registered as an ISO with Visa. That means an acquirer receiving a merchant application has its own independent reason to check who actually submitted it, separate from whatever internal process the ISO running the sales relationship has in place.
This matters because it removes any assumption that the ISO alone decides how strictly to enforce the referral-versus-ISO line. An acquirer that discovers an application came from an unregistered entity submitting on its own behalf, rather than being passed through a registered ISO’s own process, has grounds to reject that application regardless of how strong the underlying merchant looks. The ISO’s own sales practices do not just create internal risk. They create a second point of failure at the acquirer’s desk, where a file can get bounced for a reason that has nothing to do with the merchant itself.
A concrete example: the rep who thought referring was the same as closing
Picture an ISO that brought on an independent sales rep to generate leads in a new vertical, with the understanding that the rep would simply pass promising merchants along to the ISO’s own team to close. Eight months in, the rep, confident and capable, starts fielding pricing questions directly from merchants during the initial conversation, because waiting to loop in someone else felt like it was costing deals. The rep begins drafting a simplified term sheet to send prospects before formally handing them off, to speed up what had become a slow internal process.
None of this was malicious, and the rep had no idea they had crossed into territory Visa’s rules reserve for a registered ISO. The ISO’s compliance team only discovers the pattern during a routine review of marketing materials, when a prospect forwards along a term sheet with pricing language the registered ISO never actually approved or reviewed. The fix is not disciplinary. It is structural: building a process where the rep’s job stops cleanly at the lead, with pricing and contract language handled only by people and systems operating under the actual registration, rather than leaving that boundary to the rep’s own judgment about where a reasonable shortcut ends.
What this means for building the handoff correctly
The fix for this is not asking sales reps to memorize Visa’s rulebook. It is building a back-office process with a clean, enforced handoff point: the rep generates and qualifies the lead, and from the moment pricing, terms, or contract language enters the conversation, a registered entity takes over, every time, without exception carved out for a rep who seems experienced enough to handle it themselves. That handoff has to be paired with the registration tracking Section 1.9.8.7 actually requires, one registration per agent per acquirer, and the disclosure and annual review obligation that took effect this October, so the paperwork side of the relationship is never the part that quietly falls behind.
Building that clean handoff, and the registration tracking behind it, so a growing sales organization does not accidentally push unregistered reps into registered-ISO territory, is exactly the discipline behind Midcore’s ISO back office support. Getting the agent relationship itself structured correctly before the first rep is ever brought on, including which activities they are and are not authorized to perform, is the work behind ISO agent setup consulting. And once a lead actually becomes an application, merchant onboarding and underwriting support is where that handoff continues cleanly into the file itself.
Frequently Asked Questions
Can an unregistered referral partner discuss pricing with a prospective merchant?
No. Visa’s Third Party Agent Registration Program defines an ISO as any entity that solicits merchant or cardholder accounts, discusses pricing, fees, or rates, processes applications, discusses terms and agreements, drafts or manages contracts, or submits contracts to the acquirer. A referral entity or sales representative that has not registered as an ISO may only generate leads and market in the name of an already-registered ISO. The moment they do any of the activities in that list themselves, they are performing ISO services without the registration Visa requires for them.
When does a Third Party Agent actually need to be registered with Visa?
Before the agent performs any contracted services or transaction activity at all. Visa Core Rules Section 1.9.8.6 states registration must be completed before that activity begins, not sometime after the relationship is already operating. Section 1.9.8.7 adds that this registration is specific to each acquirer, so an agent working under two different acquirer relationships needs two separate registrations, not one that covers both.
Is there an exemption from Third Party Agent registration for an affiliated company?
A narrow one. An agent is exempt if it only provides services on behalf of affiliates, including parents and subsidiaries, that are Members owning and controlling at least 25 percent of that agent. The exemption does not apply at all to Payment Facilitators, Marketplaces, Business Payment Service Providers, Consumer Bill Payment Service Providers, or Digital Wallet Operators that operate Staged Digital Wallets, even when the 25 percent ownership condition is otherwise met.
Sources: Visa Core Rules and Visa Product and Service Rules, Sections 1.9.8.6 and 1.9.8.7, and Visa Third Party Agent Registration Program FAQs.