How to Pick a BIN Sponsor for a Corporate Card

A new guide explains how companies can choose a BIN sponsor to launch a custom corporate card brand and lists practical criteria for selecting the bank or issuer that owns a Bank Identification Number and connects cards to Visa or Mastercard.

The guide defines a BIN sponsor as the licensed bank or card issuer that provides access to card networks and takes legal responsibility for card issuance. It recommends that finance teams, product managers and founders assess sponsors on regulatory standing, commercial terms, technical integration, compliance support and contract terms before signing.

On licensing and regulatory risk, the guide says sponsors must be authorized in their home jurisdiction to issue cards and settle transactions. It recommends checking a sponsor’s track record on anti-money laundering controls, sanctions screening and transaction monitoring, and confirming how responsibilities for KYC, fraud detection and chargebacks will be divided between the sponsor and the client.

The guide separates the roles of sponsor, issuer processor and program manager. The sponsor supplies the BIN and regulatory cover. The issuer processor handles transaction routing, tokenization and settlement. The program manager coordinates product design, pricing and customer onboarding. Companies are advised to map which entity will perform each function and to test the proposed operating model before finalizing contracts.

On commercial terms, the guide recommends requesting clear schedules for setup fees, per-card costs, interchange passthrough or blended rates, monthly minimums and reserve or collateral requirements. It suggests negotiating support for pilot volumes, defined fee changes over time, and regular reporting on interchange and network fees. The guide also advises asking about minimum order quantities for physical cards and lead times for production and shipping.

Technical capabilities are covered in detail. Sponsors and processors should support APIs for card creation, virtual cards, real-time authorizations, reconciliation exports and webhooks for events. The guide recommends testing sample API calls, reviewing sandbox environments and confirming support for tokenization standards used by mobile wallets. It also suggests confirming uptime expectations, service-level agreements for disputes and chargebacks, and availability of test and production dashboards.

On data access and ownership, the guide tells companies to clarify which party retains transaction and cardholder data, how long data will be stored and what reporting formats will be available for finance and reconciliation. It recommends defining the frequency and granularity of statements, the format of settlement files and auditor access rights.

Geographic and product scope are also noted. Sponsors differ in accepted currencies, settlement rails, cross-border support and network reach. The guide asks companies to check whether a sponsor allows multi-currency settlement, supports corporate controls such as spend limits and merchant category filters, and has experience with virtual and single-use cards if those products are part of the plan.

Timing and exit terms are discussed. The guide states that straightforward programs can move from contract to pilot in weeks, while multi-jurisdictional programs or new regulatory approvals can take months. It suggests negotiating migration clauses, BIN portability and exit assistance to limit operational disruption if a partner becomes unsuitable.

The guide notes that BIN sponsorship is a common option for non-bank companies that want to offer payment products without taking on banking licenses. It recommends due diligence on references, running a small-scale pilot to validate the model and documenting operational processes before full rollout. The final chapter advises combining commercial, technical and compliance checks, building a short list of sponsors, conducting side-by-side tests of APIs and reporting, and including clear performance and termination terms in contracts.