The three roles behind every card program, stablecoin cards included: what each one does, who carries liability, and what to ask a provider.
Reading time: about 8 minutes.
Summary: A BIN sponsor is the licensed bank that legally issues the card. An issuer-processor is the technology that authorizes and processes each transaction. A program manager designs the card product and owns the customer. Stablecoin cards use the same three roles; only the funding and settlement layer changes.
Key takeaways
If you are planning a program, the three roles decide your contracts, your compliance load, and who you call at 2 a.m. when cards decline. This guide defines each one, shows who carries liability, and lists the questions to ask a provider. For the full build, see the guide to issuing cards with stablecoins.
A BIN sponsor is the bank that owns the card numbers. It lends its license and network membership to your program and stays the legal issuer of every card.
A BIN (Bank Identification Number, now often called an IIN) is the first six to eight digits of a card number. Networks assign BIN ranges to member institutions. A BIN sponsor is a member bank that lets a non-bank program issue cards from its range. The bank approves the program, sets its limits, reviews its compliance, and answers to regulators for it.
A concrete example from a stablecoin program: Bridge's learn page says its prepaid debit Visa card "is issued by Lead Bank and managed by Bridge Ventures, LLC." Lead Bank is the sponsor and legal issuer. Bridge also states plainly that "Bridge is not a bank."
An issuer-processor is the system that answers the network when a card is used. It receives the authorization request, runs controls, gets a decision, and produces the records that clearing and settlement need.
When a cardholder taps, the network routes the authorization request (the real-time approve or decline question) to the issuer's processor. The processor checks card status, limits, and merchant category rules, and in most modern programs forwards the request to the program for a final decision. Stripe Issuing works this way: per Stripe's docs, if it does not receive your approve or decline within 2 seconds, the authorization is approved or declined based on your timeout settings.
The processor also stores card numbers, which puts it in PCI DSS scope. PCI DSS v4.0.1 is the active version of the card data security standard.
The program manager is the company the cardholder thinks of as "the card." It designs the product and runs the customer relationship, under the sponsor bank's rules.
The program manager decides who gets a card, what limits and rewards look like, how the app works, and how support runs. It usually performs first-line compliance: cardholder KYC (Know Your Customer identity checks), sanctions screening, and transaction monitoring, all under policies the sponsor bank approves. In the Bridge example above, Bridge Ventures, LLC is named as the manager of the card.
If you are a fintech launching a card, you are often a program manager yourself, or a sub-program under a provider that is.
The sponsor carries regulatory responsibility, the processor carries technical responsibility, and the program manager carries product and first-line compliance responsibility.
| BIN sponsor | Issuer-processor | Program manager | |
|---|---|---|---|
| Who it usually is | A licensed bank with network membership | A processing company, sometimes the card provider itself | The fintech or card provider that runs the product |
| Core job | Legal issuer; owns the BIN; approves the program | Authorization, card data, clearing and settlement files | Product design, cardholder relationship, operations |
| Regulatory responsibility | Primary: answers to bank regulators for every card | Indirect, through contracts and PCI DSS | Delegated: runs the compliance program the sponsor approves |
| Typical liability by contract | Retains regulatory risk; pushes losses down | Outages and processing errors | Fraud losses, unrecovered chargebacks, onboarding failures |
| Touches money | Holds program funds or settlement accounts | Calculates positions; usually does not hold funds | Funds the program; in stablecoin models, the stablecoin balance |
| What changes with stablecoins | May settle with the network in USDC where supported | Reads balances from a ledger or on-chain approval | Holds or pulls USDC or USDT instead of a bank balance |
Liability allocation is contractual and varies. Treat the last two rows as the common pattern, not a rule.
Most card platforms bundle the processor and program manager roles and partner with a sponsor bank. A few hold network membership directly.
Three published examples:
Combining roles is not good or bad by itself. It changes who you negotiate with and who you escalate to. A deeper provider comparison is in stablecoin card issuing platforms compared.
Each role acts once per transaction, in order. Here is one stablecoin card purchase:
The full sequence with timing is in what stablecoin card issuing is.
Ask which roles it holds itself, which it subcontracts, and who you deal with when each one fails.
Question 9 is the one teams skip. Sponsor banks do exit programs. Know the migration plan before you sign. A fuller list is in the platform comparison and buyer checklist.
BlindPay sits beside these three roles as the money movement layer. The sponsor, processor, and program manager run the card; BlindPay moves money into and out of the stablecoin balance behind it.
On the funding side, BlindPay virtual accounts give each verified customer a US bank account in their own name. ACH, wire, and SWIFT deposits convert into USDC or USDT and arrive in the wallet linked to the account. Pix, SPEI, Transfers 3.0, and PSE payins do the same from Latin American bank accounts.
On the payout side, BlindPay converts USDC or USDT to local currency over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO/COBO), with UETR tracking and MT103 confirmations on SWIFT. Every payment flows through a customer that passed KYC or KYB, and BlindPay is registered with FinCEN as a Money Services Business.
Read the payouts docs or talk to the team.
This article is for general information only and is not legal, tax, or financial advice.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.
A 10-point checklist and a side-by-side of BlindPay, Wise Platform, Airwallex, Thunes, Bridge, and Circle for real-time, low-fee cross-border settlement.