How BIN sponsorship works in acquiring

In the first part of this series, we looked at where BIN sponsorship sits across issuing and acquiring. The next step is understanding how acquiring BIN sponsorship works in practice.

Acquiring BIN sponsorship is a practical way for a business to run an acquiring proposition without becoming a licensed acquirer. The BIN, or Bank Identification Number, identifies the acquirer to the card schemes.

The sponsored entity builds the merchant-facing proposition on top of it. The sponsor stays accountable to the schemes; the sponsored entity takes on the parts of the operation the sponsor is comfortable delegating. Everything in acquiring sponsorship flows from that balance: who is involved, what is delegated, and what the acquirer continues to own.

The parties involved

Every arrangement starts with the acquirer of record. This is the licensed entity that holds the scheme membership and owns the BIN. From the schemes’ point of view, this is the party responsible for compliance, settlement exposure, and how merchants are managed.

Working alongside the acquirer is the sponsored entity, often a payment service provider (PSP), payment facilitator (PayFac), aggregator, or independent sales organisation (ISO). They use the acquirer’s BIN to run their acquiring proposition. They handle most of the merchant-facing work, but always within the boundaries the sponsor sets.

And then there is the merchant. In many sponsorship models, merchants are typically onboarded as scheme-recognised merchants, not as sub-merchants (depending on the structure). They usually deal with the sponsored entity day-to-day, but the acquirer of record remains the formal counterparty in the schemes’ eyes.

Where responsibility sits

A recurring misunderstanding is that responsibility moves as the sponsored entity takes on more control. It doesn’t. The acquirer of record remains accountable until the sponsored entity becomes a principal member.

Delegation covers operations. Accountability stays with the sponsor.

A useful way to think about it is that the acquirer provides the licence and the rails, while the sponsored entity handles the driving. The sponsor stays in the background, monitoring how the journey is run and stepping in where scheme rules require it.

What the sponsored entity usually runs

Most sponsors allow the sponsored entity to manage the merchant relationship. That typically includes onboarding and underwriting within agreed criteria, shaping the commercial proposition, handling reporting and reconciliation, and supporting merchants day-to-day.

Sponsored entities often run transaction monitoring as well, applying controls such as velocity limits and escalating issues according to rules agreed in advance. From a merchant’s perspective, the sponsored entity often feels like the acquirer. The sponsor sits behind the scenes, focusing on oversight.

What the sponsor keeps

Certain responsibilities stay with the acquirer of record regardless of how much is delegated – the sponsor will set boundaries and step-in rights. Scheme reporting and scheme‑level compliance also remain with the sponsor. So do settlement exposure, liquidity management, and final accountability for disputes and chargebacks. These areas carry ongoing risk, so they stay with the licensed entity.

Why acquiring sponsorship feels less clear-cut than issuing

Issuing sponsorship tends to follow a more consistent pattern. Acquiring varies more because merchant profiles, transaction patterns, and settlement timing differ widely. Underwriting, monitoring, and dispute handling may be structured differently depending on the sponsor’s operating model and risk appetite. That variability is one of the reasons acquiring sponsorship is governed more tightly.

Common misconceptions

Several misconceptions surface regularly. One idea is that sponsorship allows companies to bypass regulation. All activity sits within the sponsor’s regulatory and scheme framework.

Another is the assumption that taking on more operational control automatically means taking on scheme‑level liability. Control and accountability are deliberately separated.

A further area that causes confusion is compliance. Some responsibilities sit in grey areas across the ecosystem, and customers sometimes assume partners cover more than they do. The acquirer remains responsible for scheme rules, credit risk, underwriting standards, and dispute handling, even when operational tasks are delegated.

Why this matters for operating teams

Clear boundaries make acquiring models easier to run. When each party knows what they own, merchant onboarding is cleaner, risk decisions are consistent, and growth doesn’t introduce surprises. It also gives both sides confidence that the model can scale without creating gaps in responsibility.

Understanding how acquiring BIN sponsorship operates in practice provides the foundation for comparing the different ways businesses approach acquiring.

Tribe provides the processing technology that supports these models, helping acquirers and payment companies keep responsibilities clear as they grow. If you’re exploring different approaches to acquiring, the Tribe team is always happy to share insights. Get in touch with us here.