Everyone studies acquiring — taking the payment. Issuing is the mirror: who put the card in the cardholder’s hand, who carries the credit risk, who earns the interchange. Get the BIN, processor and program-manager stack right and a non-bank can launch a card; get it wrong and you are stranded mid-build.
Issuing is the business of putting payment cards into cardholders’ hands and standing behind them. The issuer — historically a bank — owns the cardholder relationship, holds the account or credit line, authorises or declines each transaction, funds the purchase, and earns the interchange that the acquirer pays on every sale. Where acquiring serves the merchant, issuing serves the cardholder.
The problem issuing solves for a fintech is structural: card schemes only deal with licensed members, and becoming a scheme principal is slow, capital-intensive and bank-only territory. A whole layer of infrastructure has grown up to let non-banks issue cards without becoming a bank — and understanding that layer is the point of this leaf.
A live card program needs three distinct things, often supplied by different parties:
| Role | What it provides | Who plays it |
|---|---|---|
| BIN sponsor | Scheme membership — rents its Bank Identification Number / principal licence so your cards are legitimate scheme cards | A licensed bank or e-money institution |
| Issuer-processor | The transaction switch — authorises, applies controls, runs the ledger, makes the card actually work | Marqeta, GPS/Thredd, Lithic, local processors |
| Program manager | Owns the end product — onboarding, KYC, the app, support, the commercial wrapper | The fintech, or a BaaS platform on its behalf |
BIN sponsorship (sometimes “BIN rental”) is the linchpin: a non-member rents a principal member’s BIN so it can issue under a scheme brand and settle through interchange. The sponsor makes you legitimate; the processor makes the cards function. Increasingly these are bundled — Marqeta’s 2025 acquisition of TransactPay, an EMI-licensed BIN sponsor in the UK/EEA, is a clear case of a processor absorbing the sponsorship layer to sell a one-stop programme.
Spends the cardholder’s own funds against a deposit account. Lower interchange, low credit risk, the workhorse of inclusion-focused programs.
Spends the issuer’s money on a revolving line. Highest interchange but real credit risk, capital and lending-licence implications.
Spends a pre-funded balance, no underlying bank account needed. The classic vehicle for fintech, payroll, gig and unbanked programs — and for fast launches.
Spend now, settle in full at cycle end. Common in commercial and expense-management programs.
The product choice cascades through the whole stack: credit drags in a lending licence and capital; prepaid is the lightest-touch and so the default for a fintech proving a concept; debit needs a deposit-account relationship. Interchange — the issuer’s core revenue — is regulated very differently across these and across regions, which is often the make-or-break of the business model.
The modern shape is issuing-as-an-API. A fintech calls an issuer-processor to create virtual cards instantly, set granular spend controls, and push the card straight into Apple or Google Pay — no plastic, no branch. Banking-as-a-Service (BaaS) platforms go further, bundling the BIN sponsor relationship, the processor and the program-management plumbing so a non-bank can launch a card without separately negotiating each layer.
This is genuinely how most new card programs ship today, but the BaaS middle has been under heavy regulatory scrutiny — the sponsor bank carries the compliance obligations for everything its BINs touch, and several high-profile failures have come from sponsor banks not actually overseeing the programs riding on them. The API is easy; the accountability behind it is not.
In markets with thin banking penetration, prepaid issuing is the inclusion workhorse — payroll cards, social-grant disbursement, gig-economy and unbanked wallets all ride prepaid BINs. Local BIN sponsorship is often the binding constraint: a fintech with a great product can stall for months waiting on a sponsor bank and scheme certification. The processor is rarely the bottleneck; the sponsorship and the regulator are.
Founders budget for the processor integration and forget the sponsor bank and scheme certification can take many months. The card cannot launch without it, regardless of how finished the app is.
The sponsor bank is the legal issuer and carries the compliance liability. A program manager that behaves as if it owns the risk — or a sponsor that does not actually supervise — is the exact pattern behind recent BaaS blow-ups.
Interchange is the revenue engine, but it is capped and structured very differently by region and product. A business model built on uncapped interchange assumptions can evaporate on contact with the local rules.
Credit earns more but brings lending licences, capital, collections and credit-loss risk. Many fintechs that “wanted a credit card” should have shipped prepaid or debit first.
A card that cannot push-provision cleanly into Apple/Google Pay feels broken to modern users. Wallet provisioning is part of issuing now, not an afterthought.
Use prepaid via a BaaS / issuer-processor to launch fast and prove the concept — it is the lightest licensing burden, needs no deposit-account or lending infrastructure, and gets a working card (often virtual-first into a wallet) into users’ hands in the shortest time. For most fintechs starting out, this is the correct first move, full stop.
Move to debit once you own or can access a deposit-account relationship and want lower-cost everyday spend. Reach for credit only when the lending economics, capital and licensing genuinely justify it — not merely to capture higher interchange. Negotiate the BIN sponsor relationship first and seriously, including who carries which compliance obligation in writing; the sponsor is your regulatory ceiling, not a commodity input.
Cost of being wrong: choose a sponsor or processor that cannot scale or exits a market and you are looking at a BIN migration — among the most painful projects in payments, touching every issued card. Treat the sponsor as a pass-through and you inherit its regulatory failures. And building for credit when prepaid would do burns months and capital before you have proven anyone wants the card at all.