What is the difference between a BIN sponsor and an issuer processor?

A BIN sponsor provides the regulatory and scheme infrastructure that makes card issuance legally possible: principal membership of a card scheme, a licensed BIN, and accountability to Visa or Mastercard for scheme compliance. An issuer processor provides the technology infrastructure that makes transactions work in real time: authorisation, clearing, settlement messaging, card lifecycle management, and spend control enforcement. The two roles are structurally distinct and governed by separate contractual relationships – but they are frequently provided by the same entity, which has significant implications for programme flexibility and negotiating leverage.

On this page:

• What does a BIN sponsor do?
• What does an issuer processor do?
• Who is accountable for regulatory compliance in a card programme?
• What happens when one provider offers both roles?
• What is a programme manager, and how does it relate to these two roles?
• Can you switch issuer processor without changing BIN sponsor?
• Can you switch BIN sponsor without changing issuer processor?

Answer

A BIN sponsor provides the regulatory and scheme-level infrastructure that makes card issuance possible. Specifically: they hold principal membership of a card scheme, own or control the BINs used by client programmes, register client programmes as affiliate members of the scheme, bear accountability to Visa or Mastercard for compliance across all cards issued under their BINs, and provide the settlement infrastructure through which card transactions are cleared and funds move.

The regulatory dimension

A BIN sponsor must hold a regulatory licence – typically an Electronic Money Institution (EMI) licence or banking licence – issued by a recognised financial regulator. In Europe, this is a prerequisite for principal scheme membership and for operating any card issuance activity. The sponsor is the regulated entity in the programme: it is accountable to the regulator and to the card scheme for the conduct of all cards issued under its BINs, regardless of how many client programmes are running beneath it.

This is not a passive role. The sponsor must maintain active oversight of the compliance standards of all affiliated programmes, approve programme design and marketing materials, and ensure that AML and KYC standards are met consistently across all clients. A sponsor that takes a light-touch approach to these obligations is a compliance risk for client programmes – not just for itself.

The scheme dimension

The BIN sponsor’s scheme membership determines what the client programme can access: which networks (Visa, Mastercard or both), which geographies, which card product types, and which programme features. The sponsor negotiates directly with the schemes on fees, programme parameters, and product access. Clients benefit from the sponsor’s commercial relationships with the schemes but do not have a direct voice in those negotiations.

What to watch for

• Confirm the sponsor holds principal membership – not affiliate membership – of the relevant scheme. Only principal members can legitimately sponsor client programmes.
• Ask specifically about the sponsor’s oversight model: how do they monitor the compliance of client programmes on an ongoing basis? A sponsor with weak oversight processes creates scheme compliance exposure for all programmes under its BINs.

Answer

An issuer processor provides the transaction technology infrastructure that connects the card programme to the scheme network and handles the real-time mechanics of every card transaction. This includes authorisation processing, clearing and settlement messaging, card lifecycle management (issuance, activation, blocking, replacement), spend control enforcement, and the data feeds that drive programme reporting and reconciliation.

The authorisation function

When a cardholder presents a card, the transaction request arrives at the issuer processor’s authorisation platform within milliseconds. The platform applies the programme’s configured rules – spend controls, fraud logic, account status checks – and returns an approval or decline to the card scheme’s network before the cardholder’s card reader has finished processing. The speed, reliability and configurability of this function directly determines the cardholder experience and the programme’s operational performance.

Card lifecycle and scheme connectivity

Beyond real-time authorisation, the issuer processor manages the full card lifecycle: issuing card numbers and PINs, managing tokenisation for mobile wallets (Apple Pay, Google Pay), processing card replacements and blocks, and handling dispute and chargeback workflows in line with scheme rules. They also maintain the technical connectivity to the scheme’s network infrastructure and are responsible for implementing scheme rule changes and technical updates as they are released by Visa and Mastercard.

Key European issuer processors

The European issuer processing market is served by a relatively small number of specialist providers. Thredd (formerly GPS) is one of the largest and most widely used. Others operating in this space include Marqeta, Nuvei, and various providers that have expanded into processing from adjacent positions in the payments stack. The processor a programme runs on matters commercially as well as technically – fee structures, transaction volume thresholds, and product capability vary materially between providers.

What to watch for

• Processor capability is programme-specific, not generic. A processor that works well for a high-volume consumer prepaid programme may not be the right fit for a low-volume B2B virtual card programme with complex spend control requirements. Evaluate fit for your specific use case.
• Ask about the processor’s scheme certification status. Processors must be certified by Visa and Mastercard to process on their networks, and certifications have scope limits. Confirm the processor is certified for the card types and geographies your programme requires.

Answer

The BIN sponsor – as the regulated entity and scheme principal member – holds ultimate accountability for regulatory compliance in a card programme. The issuer processor operates a compliant technical environment (PCI DSS, scheme technical rules) but regulatory accountability under frameworks such as PSD2 and AML legislation rests with the licensed entity, which is the sponsor.

The compliance division in practice

The regulatory compliance picture in a card programme involves three overlapping layers, and the distinction between them matters:

• Scheme compliance – adherence to Visa and Mastercard’s operating rules. Accountability sits with the principal member (the BIN sponsor). The processor supports this by implementing scheme rule updates in their technical platform, but the sponsor is accountable to the scheme.
• Regulatory compliance – adherence to financial regulation (PSD2, AML Directives, data protection). Accountability sits with the licensed entity – again the sponsor, as the EMI or bank. The processor is not regulated as a financial institution and does not carry this accountability.
• Technical compliance – PCI DSS and scheme technical standards for data security and transaction processing. This is primarily the processor’s domain: they operate the environment in which card data is handled and are responsible for maintaining the certifications that cover that environment.

A card programme therefore has two separately accountable compliance parties: the sponsor for regulatory and scheme-rule accountability, and the processor for technical security compliance. This distinction matters when reviewing programme agreements – the allocation of compliance obligations, indemnities, and incident response responsibilities should reflect this division explicitly.

What to watch for

• Do not assume that because a processor operates a PCI DSS-certified environment, the programme is fully covered from a regulatory compliance standpoint. PCI DSS is a data security standard, not a regulatory compliance framework.
• In the programme agreement with your BIN sponsor, check how compliance obligations are allocated between the sponsor, the processor and your own business. Ambiguity in this allocation creates risk that will only become visible when something goes wrong.

Answer

When a single provider acts as both BIN sponsor and issuer processor – often described as a fully integrated or turnkey card programme platform – the client has one commercial relationship, one contract, and one point of accountability. This simplifies launch and reduces integration complexity. The trade-off is reduced flexibility: switching either the sponsor or the processor relationship means switching both, because they are contractually and technically bundled.

The case for integrated providers

For most businesses launching their first card programme, an integrated provider offering both BIN sponsorship and issuer processing is a sensible starting point. The integration between the two functions is already built, scheme and regulatory compliance is coordinated by one team, and time to market is faster than assembling separate relationships. The operational burden of managing two vendor relationships is also reduced.

DiPocket provides both BIN sponsorship and processing infrastructure, working with multiple issuer processors – including Thredd – to give clients flexibility in their processing arrangement while maintaining a single point of accountability for scheme compliance and regulatory oversight.

The processor flexibility question

The critical question with any integrated provider is not whether they bundle both roles, but whether their processing arrangement is fixed or flexible. Some integrated providers are tied to a single processor: the BIN sponsorship and the processing are offered as a single indivisible product, and the client has no ability to use a different processor. Others, like DiPocket, operate with multiple processors and allow the processing component to be selected or changed based on the client’s requirements.

Processor lock-in has operational consequences that only become visible as a programme grows. If the bundled processor cannot support a new geography, a higher transaction volume, or a specific technical requirement, the client has no recourse short of migrating the entire programme to a new provider – including re-issuing cards to existing cardholders.

What to watch for

• When evaluating an integrated provider, ask explicitly: are the BIN sponsorship and processing components separable? Can you change the processor without changing the BIN sponsor? The answer to these questions determines your long-term flexibility.
• Ask which processors the sponsor works with and whether you can specify or influence the choice. A sponsor who works with multiple processors and is transparent about the options is materially better positioned to support a growing programme than one who cannot answer the question.

Answer

A programme manager is an entity that takes operational responsibility for running a card programme on behalf of the client – coordinating between the BIN sponsor, the issuer processor, the card bureau, and other service providers. A programme manager does not need to hold a regulatory licence or scheme membership themselves. They act as the operational layer above the infrastructure, not as part of it.

Where the programme manager sits

In a card programme with all roles separated, the structure typically looks like this: the BIN sponsor provides regulatory and scheme access; the issuer processor handles transaction technology; and the programme manager coordinates the operational delivery – onboarding, card management, dispute handling, reporting, and day-to-day scheme rule compliance on behalf of the client. The client sits above all of these.

In an integrated provider model, the sponsor often also acts as the programme manager, handling operational coordination as part of the service. This is the model DiPocket operates: the BIN sponsorship, operational oversight, and programme support functions are provided by the same entity.

Why the distinction matters

Some providers in the market describe themselves as programme managers or card programme platforms without being the BIN sponsor themselves – they are sitting above a sponsor and a processor without holding the scheme membership or regulatory licence that underpins the whole arrangement. This creates a longer chain of dependency and an additional potential failure point. If the provider’s relationship with the underlying sponsor breaks down, every programme running on the platform is affected.

What to watch for

• If a provider describes themselves as a programme manager, ask directly: who is the BIN sponsor, and do they hold principal scheme membership? The answer tells you where the regulatory and scheme accountability actually sits.
• The longer the chain between your programme and the regulated entity, the more dependency risk you carry. Ideally the BIN sponsor, the regulatory licence holder, and the scheme principal member are the same entity.

Answer

In principle yes, but in practice it depends entirely on the contractual and technical architecture of your current arrangement. If the BIN sponsor and issuer processor are separate providers with separate agreements, processor migration is technically possible without changing the sponsor relationship. If the two are contractually bundled, changing the processor means changing the sponsor – and everything that entails.

What processor migration actually involves

Even where processor and sponsor relationships are technically separable, migrating an issuer processor is a significant technical project. The new processor needs to be integrated with the sponsor’s settlement infrastructure, scheme registrations need to be updated to reflect the new processor, and the card programme’s transaction processing logic needs to be re-implemented and tested on the new platform. Active cardholders are typically not affected – card numbers and PANs do not change when a processor changes, because the PAN is associated with the BIN and the account, not with the processor.

When processor migration is worth considering

Processor migration becomes relevant when the current processor cannot support a new requirement – a new geography, a higher transaction volume tier, a specific spend control feature, or better pricing at scale. It is also relevant when a programme migrates to a new BIN sponsor who uses a different processor. In either case, the commercial benefits need to outweigh the migration cost and operational disruption, which is non-trivial for active programmes.

What to watch for

• Before signing with any BIN sponsor, confirm in writing whether you have the contractual right to change issuer processor independently of the sponsor relationship. If the agreement is silent or ambiguous on this point, assume it is not permitted.
• Processor migration for an active programme with cardholders takes months, not weeks. If your programme is growing and you anticipate needing to change processor, plan the migration well before the need becomes urgent.

Answer

Switching BIN sponsor is operationally more disruptive than switching issuer processor. A sponsor change typically requires re-registration of the programme with the card scheme under the new sponsor’s BINs, which means issuing new card numbers to existing cardholders – because the BIN prefix changes. This is the most operationally significant aspect of any programme migration.

What a sponsor migration actually involves

When a programme moves to a new BIN sponsor, the cards in existing cardholders’ hands carry the old sponsor’s BIN. Those cards cannot simply be reassigned to a new BIN – the card number incorporates the BIN prefix and cannot be changed without physical or virtual card replacement. This means all active cardholders need to be re-issued new cards, all card-on-file registrations (subscriptions, saved payment methods) need to be updated, and the programme needs to operate on both old and new BINs simultaneously during a transition period.

This is the most frequently cited reason why businesses stay with a sub-optimal BIN sponsor longer than they should – the cost and complexity of migration is significant, and underestimated at the time the original sponsor relationship was established.

Whether the existing processor can be retained

In some cases, the new BIN sponsor will work with the same issuer processor as the old one, allowing the programme to migrate the sponsor relationship without also migrating the processing infrastructure. Whether this is possible depends on the new sponsor’s processing relationships and the technical architecture of the existing programme. Where it is possible, it materially reduces migration complexity.

What to watch for

• When selecting a BIN sponsor, think explicitly about the migration scenario. How would you exit this relationship if needed, and what would the cardholder impact be? A sponsor who has managed client migrations – and who can describe how they approach them – understands the risk they are asking you to accept.
• Build a cardholder re-issuance cost estimate into any programme migration business case. For programmes with tens of thousands of active cardholders, card replacement logistics alone represent a material cost and operational project.

Answer

The core questions to ask a provider that offers both BIN sponsorship and issuer processing are: whether the two components are contractually separable, which processors they work with and whether you can specify or change the processor, what their authorisation performance and uptime data looks like, how they handle a client that needs to migrate to a different processor or direct scheme membership, and what their financial standing and regulatory compliance track record is.

The separation question

Ask directly: if I need to change processors in two years because my volume has grown or my requirements have changed, can I do that without changing BIN sponsor? A provider who cannot answer this question clearly, or who answers it with a commercial deflection rather than a structural explanation, is signalling that the two components are effectively locked together.

Performance and stability

For the processing component, ask for authorisation uptime SLA data and historical authorisation rate performance across programmes comparable to yours. Uptime SLAs below 99.9% for the authorisation platform are a concern for any programme where card acceptance reliability matters to the cardholder experience. Authorisation rate performance tells you how effectively the platform converts legitimate transaction attempts into approvals.

For the sponsorship component, ask about the provider’s financial standing, regulatory audit history, and how they have handled compliance incidents or scheme rule changes across their client portfolio. A sponsor who has been operating for a decade and has navigated multiple regulatory changes is materially more credible than one who cannot speak to their history.

BIN sponsor vs issuer processor: roles at a glance

What to watch for

• Ask for the provider’s authorisation uptime SLA in writing, and ask for historical performance data. Claims of high uptime without supporting data should not be taken on trust for a function this operationally critical.
• Ask how the provider has handled clients that outgrew the bundled arrangement and needed to move to direct scheme membership or a different processor. Their answer tells you whether they see themselves as a long-term partner or a fixed-term infrastructure contract.

DiPocket provides BIN sponsorship with processor flexibility – working with multiple issuer processors including Thredd so that clients are not locked into a single processing arrangement as their programme grows. Explore our BIN sponsorship service.