A sponsor bank is a fully licenced deposit-taking institution that grants non-bank entities — fintechs, programme managers, corporates, marketplaces — access to regulated payment infrastructure: card scheme BIN ranges, IBAN issuance, clearing and settlement systems, and central-bank access. The sponsor assumes ultimate regulatory responsibility for the programme, while the non-bank party operates under the sponsor's regulatory umbrella. This arrangement is the foundational mechanism behind Banking-as-a-Service, embedded finance, and the majority of white-label card programmes operating in the EU, UK, and US today.
A sponsor bank (also called a banking sponsor, BIN sponsor, or in card-scheme parlance a principal member acting in a sponsoring capacity) is a regulated credit institution that holds direct membership of one or more payment rails — Visa, Mastercard, SWIFT, SEPA, Faster Payments, ACH — and contractually extends access to those rails to a third-party programme manager that itself lacks the necessary licence or membership.
The term does not appear verbatim in European primary legislation, but the underlying concept is fully recognised in regulatory instruments. Under the EU's revised Payment Services Directive (PSD2, Directive 2015/2366/EU), access to payment systems is restricted to regulated payment service providers; sponsor banking is the practical mechanism by which unlicensed or partially licenced entities participate via an agent or distributor relationship with a fully authorised institution. Similarly, in card-scheme rules, Visa and Mastercard permit principal members to sponsor associate members or affiliate members — a direct analogue of the sponsor-bank model at the scheme level.
It is important to distinguish the sponsor bank from two adjacent concepts. First, an Electronic Money Institution (EMI): an EMI holds its own regulatory licence (under the Electronic Money Directive 2009/110/EC, EMD2) and does not require a sponsor bank for e-money issuance, though an EMI may still rely on a sponsor bank for card-scheme connectivity or central-bank settlement access it does not hold directly. Second, a Banking-as-a-Service (BaaS) provider: BaaS is the commercial and technical packaging of sponsor-bank capabilities into developer-friendly APIs; the sponsor bank may be the BaaS provider itself, or the BaaS layer may sit between a programme manager and an underlying sponsor. See the BaaS glossary entry for that distinction in full.
The sponsor bank is not merely a pass-through: it is the entity of record with the card scheme, the central bank, and the financial intelligence unit. It bears full anti-money-laundering (AML) and counter-terrorism-financing (CTF) liability for activity conducted under its umbrella, it holds the settlement account, and it absorbs operational risk if the programme manager fails. This asymmetry of regulatory exposure is why sponsor-bank relationships are contractually complex and why selecting the right sponsor is a critical commercial decision.
The mechanics of a sponsor-bank arrangement follow a well-defined lifecycle that spans commercial agreement, technical integration, scheme registration, and ongoing programme governance.
1. Agreement and due diligence. The programme manager (the "client" or "distributor") approaches a sponsor bank with a programme proposal — typically a card programme, IBAN-based account product, or payment wallet. The sponsor conducts an onboarding due-diligence review covering the programme manager's corporate structure, beneficial ownership, proposed use-case, customer base, and AML/KYC framework. This mirrors the sponsor bank's own regulatory obligations: it is, in effect, applying its customer-due-diligence standards to a business customer that will originate regulated activity.
2. Scheme registration. For card programmes, the sponsor bank notifies the relevant card scheme (Visa or Mastercard) of the new programme and the proposed programme manager. The scheme issues a BIN (Bank Identification Number) range — a block of card numbers — to the sponsor bank, which sub-allocates it to the programme. All cards issued carry the sponsor's BIN, making it the entity of record at the scheme level. This is covered in detail in the BIN sponsorship glossary entry.
3. Technical integration. The programme manager integrates with the sponsor bank's APIs (or with a BaaS/card-processor layer the sponsor has certified). Capabilities provisioned typically include: card issuance and lifecycle management, transaction authorisation routing, IBAN generation, SEPA/SWIFT payment initiation, and real-time balance management. The sponsor bank's core banking or card-processing infrastructure sits underneath; the programme manager's product is the consumer-facing layer.
4. KYC/AML delegation. The sponsor bank delegates customer identification and verification (KYC) to the programme manager under a formal agent or distributor agreement, but retains ultimate AML accountability. The programme manager must implement transaction monitoring, suspicious-activity reporting, and sanctions screening to standards approved by the sponsor. The sponsor audits these controls periodically — typically quarterly or annually — and may conduct mystery-shopping or file reviews.
5. Settlement and float. Customer funds may be held in a pooled safeguarding account at the sponsor bank (for e-money products) or in individual deposit accounts. Settlement of card transactions flows through the scheme's clearing infrastructure to the sponsor's settlement account; the sponsor then reconciles and distributes funds to the programme manager's ledger. The sponsor bank controls the settlement float and bears intraday liquidity risk.
6. Ongoing governance. The programme manager operates within a set of scheme rules and sponsor policies that govern permissible merchant category codes, transaction velocity limits, geographic scope, and customer eligibility. Any material change to the programme — new product features, new geographies, new customer segments — requires sponsor-bank approval and potentially re-notification to the scheme.
European Union. The primary legislative framework is PSD2 (2015/2366/EU), which establishes a closed list of entities permitted to provide payment services — credit institutions, EMIs, and payment institutions. A non-licenced entity may provide payment services only as an agent of a licenced PSP, registered with the relevant national competent authority (NCA). The sponsor bank is therefore either the principal PSP itself, or it appoints the programme manager as a registered agent. Under the Capital Requirements Regulation (CRR, Regulation 575/2013) and CRD IV/V, the sponsor bank also carries credit and operational risk capital requirements for the programme.
For card programmes, EMD2 (2009/110/EC) governs e-money issuance. If the programme involves issuing e-money (prepaid balances), the sponsor must be a credit institution or authorised EMI, and customer funds must be safeguarded under Article 7 of EMD2 — either segregated in a credit institution or covered by an insurance policy.
AML/CFT. The EU's Sixth Anti-Money Laundering Directive (6AMLD, 2018/1673/EU) and the forthcoming AML Regulation (AMLR, expected 2025–2026) impose customer due-diligence, transaction monitoring, and suspicious-transaction reporting obligations on all obliged entities — including credit institutions acting as sponsors. The sponsor bank cannot outsource its AML liability; it must satisfy itself that the programme manager's AML framework is equivalent to its own standards and must implement escalation procedures for high-risk transactions.
United Kingdom. Post-Brexit, the UK operates under the Payment Services Regulations 2017 (PSRs 2017, implementing PSD2 into UK law) and the Electronic Money Regulations 2011 (EMRs 2011), supervised by the Financial Conduct Authority (FCA). The FCA has issued specific guidance on principal–agent models (FCA PS21/3 and subsequent Dear CEO letters on safeguarding) and has increased scrutiny of sponsor banks' oversight of their programme managers.
United States. US sponsor banking operates under a distinct "bank charter" model: non-bank fintechs partner with FDIC-insured state or national banks, which hold the charter required for FDIC deposit insurance and access to ACH/Fedwire. The Office of the Comptroller of the Currency (OCC) and state banking regulators have issued guidance (OCC Bulletin 2020-10 on third-party relationships) requiring banks to conduct robust due diligence of fintech partners.
Cost structure. Sponsor-bank fees fall into three layers. First, a setup and onboarding fee covering due diligence, legal agreement drafting, scheme registration, and technical integration — typically €10,000–€100,000 depending on programme complexity. Second, per-transaction or per-account fees: card interchange is shared between scheme, issuer (sponsor), and processor, with the programme manager receiving a negotiated portion; IBAN and SEPA transaction fees are charged at cost plus margin. Third, a programme management fee or monthly minimum, reflecting the ongoing compliance overhead the sponsor assumes.
Selection criteria. When evaluating a sponsor bank, programme managers should assess: (i) scheme membership — does the sponsor hold Visa and/or Mastercard principal membership and in which geographies?; (ii) IBAN issuance capability — can the sponsor issue native EU IBANs in the programme's target markets, with full SEPA Instant support?; (iii) regulatory geography — does the sponsor hold passporting rights across the EU/EEA, or only in its home jurisdiction?; (iv) technology maturity — are APIs modern (REST/JSON), well-documented, and supported by a sandbox environment?; (v) time to launch — what is the realistic end-to-end timeline from signed agreement to first live transaction?; (vi) compliance culture — is the sponsor's AML framework proportionate and pragmatic, or will it impose restrictions that make product-market fit impossible?
Alternatives to sponsor banking. Programme managers have three principal structural alternatives. Sponsored access via an EMI: rather than a full credit institution, a licenced EMI acts as the regulatory principal — suitable for e-money programmes but limited in deposit-taking and lending capability. Principal scheme membership: a programme manager can apply directly for Visa or Mastercard associate/principal membership, eliminating the scheme-level sponsor but still requiring a banking partner for settlement and IBAN issuance; this is slower (12–18 months), more capital-intensive, and requires significant compliance infrastructure. Full bank licence: obtaining a credit institution or EMI licence directly — the highest-control, highest-cost path, typically 2–4 years and €2M+ in regulatory capital and project cost. Sponsor banking remains the dominant entry route because it compresses time-to-market to weeks rather than years while the programme manager builds regulatory maturity.
For card issuing specifically, the sponsor bank's BIN sponsorship is often the single most commercially sensitive element: BIN availability, interchange economics, and scheme rule flexibility vary significantly between sponsors and should be pressure-tested before contract execution.
Codego operates as a European Banking-as-a-Service infrastructure provider, combining its NBB electronic-money distribution licence with Codego Europe SIA's ongoing EMI authorisation to offer programme managers a single access point to regulated rails across 12 EU/EEA countries — without requiring a separate sponsor-bank relationship for each jurisdiction.
On the card side, Codego holds Visa and Mastercard BIN sponsorship, enabling programme managers to launch branded cards under either scheme through the card-issuing platform or the white-label card programme. Virtual cards are live on day one; physical cards ship within 15 days. Apple Pay and Google Pay provisioning completes within 24 hours of card activation. For a full explanation of the BIN layer, see the BIN sponsorship glossary entry.
For account infrastructure, Codego provides native EU IBAN issuance across six countries with full SEPA Credit Transfer, SEPA Direct Debit, SEPA Instant, and SWIFT connectivity — removing the need for a separate correspondent-banking arrangement. The BaaS platform and core banking layer expose these capabilities via REST APIs, with a self-service programme-configuration portal that allows programme managers to define product parameters, fee structures, and compliance rules without bespoke engineering for each change.
Codego also supports crypto-native programmes through its white-label crypto offering, including stablecoin- and crypto-funded card spending with on-the-fly conversion — an architecture increasingly demanded by Web3 programme managers who still require fiat settlement rails. For corporates, the expense card and white-label bank products demonstrate the same sponsor infrastructure applied to different programme types. Programme managers can begin the assessment process via the programme questionnaire.