Launching a card program means becoming fluent in a value chain most software PMs never touch: a BIN sponsor bank that lends its regulatory charter, an issuer processor that runs the technical rails, a program manager who owns the product, and a network (Visa, Mastercard, or a domestic scheme) that clears and settles. Get the partner stack and the authorization flow wrong, and the card doesn't work at the point of sale — literally.

Quick Answer: A card issuing product requires four partners working in concert — a BIN sponsor bank, an issuer processor, a program manager (often you), and a card network. Success depends on getting the authorization flow, funding model, spend controls, and compliance obligations right before you ever ship a physical or virtual card.

Most PMs arrive at card issuing from either payments infrastructure or a neobank/fintech product background, and the gap between "I understand payments conceptually" and "I can spec a card program" is wider than it looks. This is the map.

The Issuing Value Chain: Who Actually Does What

The card issuing value chain has four roles, and conflating any two of them is the single most common rookie mistake. A BIN sponsor is a bank that owns a Bank Identification Number range and takes on regulatory liability; an issuer processor operates the ledger, authorization engine, and card management systems; a program manager designs the product and owns the customer relationship; and the network routes transactions and enforces scheme rules.

BIN sponsor (the bank). This is a chartered, regulated bank — think Sutton Bank, Cross River, Column, or Evolve — that agrees to "sponsor" your program by issuing cards under its own BIN. You are not a bank, and in the overwhelming majority of fintech card launches you never become one; you rent regulatory standing from an entity that already has it. The sponsor bank is on the hook with regulators and the network for your program's compliance, which is why they underwrite you as a partner, not just a vendor.

Issuer processor (the plumbing). Companies like Marqeta, Galileo, i2c, or Lithic run the technical infrastructure: card issuance, PIN management, authorization decisioning, ledger posting, and dispute tooling. Some processors also offer "program management as a service," blurring the next role, but the processor's core job is moving and recording transactions correctly and fast — typically sub-second, end to end.

Program manager (often you). This is the entity that designs the card product: spend controls, rewards, fee structure, onboarding, and support. If you're a fintech PM reading this, you are very likely building the program manager function, even if you outsource pieces of it to a processor's managed-service tier.

Network (the rails). Visa, Mastercard, or a domestic network like RuPay or Interac sets interchange rates, dispute rules, and technical standards, and provides the switch that routes an authorization from a merchant's acquirer to your issuer processor. You don't choose "no network" — you choose which one, and that choice locks in interchange economics and geographic reach for the life of the program.

How the Four Roles Actually Interact

RoleOwnsTypical Partner ExamplesYour Relationship
BIN sponsorRegulatory charter, ultimate liabilitySutton Bank, Cross River, Column, EvolveContractual partner, compliance oversight
Issuer processorLedger, authorization engine, card productionMarqeta, Galileo, i2c, LithicTechnical integration, API contract
Program managerProduct design, spend rules, UX, supportYou (the fintech)This is your seat
NetworkInterchange rates, dispute rules, routingVisa, Mastercard, RuPayCertification and scheme compliance

The table understates one thing: these relationships aren't independent. Your processor choice constrains which sponsor banks will work with you (not every processor-sponsor pair is pre-integrated), and your sponsor's risk appetite constrains what spend controls and credit products you can even propose. Sequencing matters — most programs pick a processor first, then a sponsor the processor already has a working relationship with, which shortens integration time considerably.

Authorization Flow: What Happens in the 200 Milliseconds After a Swipe

An authorization request travels from the merchant's terminal through an acquirer, across the network, to your issuer processor, which checks the ledger and spend rules and returns an approve or decline — all in roughly 100-300 milliseconds. Understanding this loop is non-negotiable for a PM designing spend controls, because every rule you write executes inside that window.

Here's the sequence a PM needs to internalize, step by step:

  1. Cardholder swipes, taps, or enters card details at a merchant terminal or checkout page.
  2. Merchant's acquiring bank captures the transaction and forwards it to the network.
  3. Network routes the authorization request to your issuer processor using the BIN.
  4. Issuer processor evaluates the request against available balance or credit line, velocity limits, MCC (merchant category code) restrictions, and fraud rules — this is where your program's spend controls live.
  5. Processor returns approve/decline back through the network to the acquirer to the merchant, typically in under half a second.
  6. Settlement happens later, often next business day, when funds actually move between banks.

The gap between authorization and settlement is where a lot of product complexity hides — an authorization "holds" funds against a customer's balance but the actual money movement lags, which is exactly the kind of timing mismatch covered in depth in a double-entry ledger data model for PMs. If you're designing spend controls, you're really designing rules that execute at step 4, and you need your processor's decisioning API to expose every lever you want to control — real-time balance checks, category blocks, geographic restrictions, single-transaction caps — before you promise them to stakeholders.

Interchange: The Upside That Makes Issuing Worth It

Interchange is the fee a merchant's bank pays to the cardholder's bank (you, via your sponsor) every time your card is used, typically ranging from 0.05% to over 2% of transaction value depending on card type, network, and region. This is the revenue engine that makes issuing programs financially viable, and it's why program managers care intensely about transaction mix — a debit card used for high-frequency, low-value purchases behaves very differently, economically, than a credit card used for large, infrequent ones.

In the US, the Durbin Amendment caps debit interchange for large banks (roughly 21-24 cents plus a small percentage per transaction), but exempts banks under $10 billion in assets — which is exactly why so many fintech debit programs are built on smaller, "exempt" sponsor banks that can pass through unregulated (higher) interchange. Credit interchange isn't capped the same way and varies more by network tier and card rewards level. A PM modeling unit economics needs the sponsor's actual interchange schedule, not a network's published rate card, because negotiated splits between sponsor, processor, and program manager determine what you actually keep.

Funding Models: Prefunded, Direct Debit, or Credit Line

A card program's funding model determines where money sits before a transaction settles, and it fundamentally shapes your risk exposure, cash-flow timing, and regulatory obligations. The three common models are prefunded (pooled) accounts, direct-debit-per-transaction, and revolving credit lines, each with distinct tradeoffs.

Prefunded/pooled model. Your program maintains a funding account (often an FBO — "for benefit of" — account at the sponsor bank) that covers settlement obligations across all cardholders. This is the dominant model for debit and prepaid programs because it's simplest to reason about: you can never authorize more spend than what's actually funded, which caps your credit risk near zero.

Direct debit per transaction. Less common for card issuing specifically, this model pulls funds from a linked bank account at time of settlement rather than pre-loading a pool. It reduces float requirements but introduces settlement risk if the underlying account lacks funds — you've authorized a transaction the customer can't actually cover.

Revolving credit line. For credit card programs, you (or a partner bank) extend a line of credit, authorize against available credit rather than cash balance, and collect through statement billing. This model carries real credit risk and typically requires either your own lending license, a partner bank willing to hold the receivables, or a purchased-receivables arrangement — a materially heavier compliance lift than prefunded debit.

The funding model you choose early is expensive to change later — it's baked into your sponsor bank agreement, your ledger architecture, and your customer disclosures.

Spend Controls and the Closed-Loop vs. Open-Loop Decision

Spend controls are the rules — velocity limits, MCC restrictions, geographic locks, single-transaction caps — that your issuer processor evaluates at authorization time, and they're the primary lever a PM has for shaping product behavior without touching the core ledger. Designing them well requires understanding a foundational architecture choice: closed-loop versus open-loop.

A closed-loop card only works within a specific merchant or network of merchants — a store gift card, or an employee card restricted to office-supply vendors. An open-loop card runs on a full network (Visa, Mastercard) and works anywhere that network is accepted. This decision shapes nearly everything downstream: compliance scope, partner requirements, user experience, and revenue model.

DimensionClosed-LoopOpen-Loop
Where it's acceptedSingle merchant or curated networkAnywhere the network is accepted
Regulatory complexityLower — often exempt from some card-network rulesHigher — full network certification, Reg E, EFTA
BIN sponsor requiredSometimes not required at allAlmost always required
Interchange revenueNone or minimalMeaningful revenue stream
Typical use caseCorporate expense cards, gift cards, campus cardsConsumer debit/credit, general-purpose spend cards
Time to launchFaster, fewer partner dependenciesSlower, multi-partner underwriting and certification

The decision point most PMs underestimate: open-loop unlocks real interchange revenue and broad utility, but it drags in a sponsor bank, network certification, and the full weight of consumer protection regulation (Regulation E for electronic funds transfers, Regulation Z if any credit feature exists). Closed-loop lets you launch faster and sidestep much of that, but caps your product's usefulness and revenue ceiling. Most programs that start closed-loop as an MVP — an expense card for a single vendor category, say — do it explicitly to validate demand before taking on open-loop's compliance burden.

Compliance Obligations Issuing Creates

Becoming a program manager makes you responsible for downstream compliance even though your sponsor bank holds the regulatory charter — the obligation doesn't disappear just because you outsourced the license. Expect obligations across KYC/AML (customer identity verification and suspicious activity monitoring), Regulation E (electronic fund transfer error resolution and liability limits), network scheme rules (Visa/Mastercard operating regulations that go well beyond federal law), and data security (PCI DSS for anywhere card data touches your systems).

Your sponsor bank will conduct ongoing oversight of your program — not a one-time approval — including periodic audits of your marketing materials, dispute handling, and fraud metrics. The Consumer Financial Protection Bureau has repeatedly signaled, including in guidance following its 2021-2023 fintech partnership inquiries, that banking-as-a-service arrangements don't shield program managers from consumer protection scrutiny; regulators increasingly look through the sponsor relationship to the underlying product experience.

This is also where fraud stops being an abstract risk line and becomes an operational discipline — dispute rates, chargeback ratios, and Regulation E error-resolution timelines all become metrics you're measured against by your sponsor, which is exactly the territory covered in fraud as a product problem. Build your dispute-handling workflow and fraud monitoring before launch, not after your first chargeback spike forces the issue.

Reconciliation Becomes a Daily Discipline

Every authorization, settlement, and interchange payment needs to reconcile across your ledger, your processor's records, and your sponsor bank's records — and discrepancies here are a compliance red flag, not just an accounting nuisance. The mechanics of matching these three sources of truth, and what to do when they drift, are covered in depth in payment reconciliation systems for PMs; treat reconciliation tooling as launch-critical infrastructure, not a post-launch nice-to-have.

Keeping the Partner Stack Aligned Through Launch

A card program is unusual among fintech products in how many external, contractually-bound partners sit on the critical path — your sponsor bank, processor, and network all have their own compliance calendars, release cycles, and escalation paths, and a delay in any one blocks the whole launch. This is fundamentally a stakeholder-management problem wearing a technical-integration costume.

Prodinja's Stakeholders CRM is built for exactly this shape of problem: it lets you track each partner relationship — sponsor bank compliance officer, processor integration lead, network certification contact — with a computed alignment-debt score that flags relationships drifting out of sync before they become launch blockers. Rather than discovering three weeks before go-live that your sponsor's risk team never signed off on a spend-control change your processor already built, the alignment-debt view is designed to surface that gap while there's still time to close it.

Key Takeaways

  • Four distinct roles run every card program: BIN sponsor (regulatory charter), issuer processor (technical rails), program manager (product), and network (routing and scheme rules) — conflating any two causes launch delays.
  • Authorization happens in under a second, evaluating balance, velocity limits, and MCC restrictions against rules your program manager function defines — this is where spend controls actually live.
  • Interchange is the revenue engine of issuing, typically 0.05-2%+ per transaction, with US debit interchange capped under Durbin for large banks but exempt for smaller sponsor banks.
  • Funding model (prefunded, direct debit, or credit line) shapes your risk exposure and is expensive to change post-launch — decide it early and deliberately.
  • Closed-loop versus open-loop is the highest-leverage early decision: closed-loop launches faster with less compliance weight; open-loop unlocks real revenue and utility but drags in full network certification and consumer protection law.
  • Compliance obligations don't transfer away just because a sponsor bank holds the charter — KYC/AML, Reg E, PCI DSS, and reconciliation discipline are all yours to operationalize.
  • The partner stack itself is a stakeholder-management challenge, and tools that surface misalignment early — before it becomes a launch blocker — are as important as the technical integration.

Frequently Asked Questions

What is a BIN sponsor bank in card issuing?

A BIN sponsor is a chartered, regulated bank that issues cards under its own Bank Identification Number range on your behalf, taking on the regulatory liability so your fintech doesn't need its own banking charter. You partner with them contractually and operate under their ongoing compliance oversight.

Do I need my own banking license to launch a card program?

No — the overwhelming majority of fintech card programs launch through a BIN sponsor bank rather than obtaining their own charter, which is faster and dramatically less capital-intensive. You still take on real compliance responsibility as the program manager, even without holding the license yourself.

What's the difference between an issuer processor and a program manager?

An issuer processor (like Marqeta, Galileo, or i2c) runs the technical infrastructure — authorization, ledger, card production — while the program manager designs the product: spend rules, onboarding, rewards, and customer experience. Some processors offer managed-service tiers that blur this line, but the roles are conceptually distinct.

Is a closed-loop or open-loop card better for a first launch?

Closed-loop typically launches faster with fewer partner dependencies and lighter compliance scope, making it a common MVP choice to validate demand. Open-loop unlocks real interchange revenue and broad merchant acceptance but requires a sponsor bank, network certification, and full consumer protection compliance from day one.

How much revenue can interchange actually generate for a card program?

Interchange typically ranges from roughly 0.05% to over 2% of each transaction, varying by card type, network, and whether Durbin Amendment caps apply to your sponsor bank's size. Actual take-home revenue depends heavily on the negotiated split between your sponsor, processor, and program manager, so model against your specific agreement rather than published network rate cards.

Understanding this value chain deeply connects to the broader responsibilities fintech PMs carry across their careers — for a fuller picture of the role, see the complete guide to the fintech PM role, and for a framework on validating what your cardholders actually need before you lock in program design, jobs-to-be-done and mapping the customer journey both pay off before, not after, you sign a sponsor bank agreement.