---
title: "BIN sponsor vs. issuer-processor vs. program manager: who does what in a card program"
seoTitle: "BIN sponsor vs. issuer-processor vs. program manager"
description: "The three roles behind every card program, stablecoin cards included: what each one does, who carries liability, and what to ask a provider."
date: "2026-10-02"
updated: "2026-10-02"
category: "payments"
author: "BlindPay Team"
faq:
  - q: "What is a BIN sponsor?"
    a: "A BIN sponsor is the licensed bank that owns the Bank Identification Number range a card is issued from and lends its regulatory license and card network membership to a program. The sponsor bank is the legal issuer, approves the program, oversees its compliance, and carries the regulatory responsibility for every card on its BIN. Bridge's prepaid Visa card, for example, is issued by Lead Bank."
  - q: "What does an issuer-processor do?"
    a: "An issuer-processor runs the technology that makes a card work: it receives authorization requests from the network, applies controls, asks the program for an approve or decline decision, stores card data under PCI DSS, and produces clearing and settlement files. It is the real-time engine between the network and the program, and its uptime decides whether a card works at the terminal."
  - q: "What is a program manager in card issuing?"
    a: "A program manager designs and runs the card product: who gets cards, limits, rewards, the app, support, and the customer relationship. It usually runs first-line compliance such as cardholder KYC under the sponsor bank's oversight. Bridge describes its prepaid Visa card as managed by Bridge Ventures, LLC, which is the program manager role in that structure."
  - q: "Who is liable when something goes wrong in a card program?"
    a: "Regulatory responsibility sits with the BIN sponsor, because the bank is the legal issuer. Contracts then push operational liability down: the program manager usually owns fraud losses, chargebacks it cannot win, and compliance failures in its own onboarding, while the issuer-processor owns outages and processing errors. Read the program agreement, because liability allocation varies by contract."
  - q: "Can one company be BIN sponsor, processor, and program manager?"
    a: "A bank can hold all three, but most fintech programs split them. Many card providers bundle the processor and program manager roles and partner with a sponsor bank. Some go further: Rain says it holds principal memberships with Visa and Mastercard, which means it connects to the networks directly. Ask each provider which roles it holds itself and which it subcontracts."
  - q: "What should I ask a card provider about its roles?"
    a: "Ask who the sponsor bank is and whether you can name it publicly, whether the provider holds network membership directly or through the sponsor, who processes authorizations and where, who owns PCI scope, who approves your program and changes to it, and how fraud losses and chargebacks are allocated. The answers tell you where your program can break."
---

*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**

- Every Visa or Mastercard program has a BIN sponsor, an issuer-processor, and a program manager, even when one company bundles two of them.
- The BIN sponsor carries regulatory responsibility for every card on its BIN. That is why it approves your program.
- The issuer-processor is the real-time engine: authorization, card data, clearing files.
- The program manager owns the product, the cardholder, and usually first-line compliance.
- Stablecoins change where the money comes from and how it settles, not who holds these roles.


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](/resources/more/how-to-issue-stablecoin-cards-api).

## What is a BIN sponsor?

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."

## What is an issuer-processor?

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.

## What is a program manager?

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.

## Who does what: responsibilities and liability

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.

## How do providers combine these roles?

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:

- **Bridge.** Card issued by Lead Bank, managed by Bridge Ventures, LLC, per Bridge's learn page. Through Bridge's partnership with Lead Bank, Visa says these transactions can be settled on-chain with Visa.
- **Rain.** Rain says it is a Visa Principal Member and a Mastercard Principal Member. **Principal membership** means connecting to the network as a member, rather than reaching it only through a sponsor's membership. Rain also says it settles card transactions with the networks daily using stablecoins.
- **Stripe Issuing with Bridge.** Stripe's docs say an implementation expert manages requirements "across our BIN sponsor, networks, and other partners." Cards and spend webhooks run on Stripe's API; customers, KYC, and the cards endorsement run on Bridge.

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](/resources/more/stablecoin-card-issuing-platforms-compared).

## How does a single swipe touch each role?

Each role acts once per transaction, in order. Here is one stablecoin card purchase:

1. The cardholder taps at a merchant. The merchant's acquirer sends the request over Visa or Mastercard.
2. The network routes it to the issuer-processor for the BIN.
3. The processor checks card status and controls, then asks the program manager's system for a decision.
4. The program manager checks the cardholder's USDC balance in its ledger, or the on-chain approval in a non-custodial model, and places a hold.
5. The processor returns the approval to the network. No money has moved yet.
6. At clearing, the processor produces the final amounts. At settlement, the BIN sponsor's side pays the network, in fiat or in USDC where the network supports it.
7. The program manager funds that settlement from the stablecoin balance and posts it to its ledger.

The full sequence with timing is in [what stablecoin card issuing is](/resources/more/what-is-stablecoin-card-issuing).

## Which questions should you ask a card provider?

Ask which roles it holds itself, which it subcontracts, and who you deal with when each one fails.

1. Who is the BIN sponsor, and can we name the bank on our cards and in our terms?
2. Do you hold network membership directly, or through the sponsor?
3. Who runs authorization processing, and what is the timeout behavior?
4. Who is in PCI DSS scope for card numbers, and how are card details shown to cardholders?
5. Who approves our program, and who approves changes like new countries or card types?
6. Which compliance checks do you run, and which must we run?
7. How are fraud losses, chargebacks, and negative balances allocated?
8. How does settlement work: fiat, stablecoins, or both, and how often?
9. What happens to our cards if the sponsor relationship ends?

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](/resources/more/stablecoin-card-issuing-platforms-compared).

## Where does BlindPay fit?

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](/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](/docs/payouts) or [talk to the team](/contact).

## What to read next

- [What is stablecoin card issuing?](/resources/more/what-is-stablecoin-card-issuing)
- [How to issue stablecoin-funded cards through an API](/resources/more/how-to-issue-stablecoin-cards-api)
- [Stablecoin card issuing platforms compared](/resources/more/stablecoin-card-issuing-platforms-compared)
- [Compliance for stablecoin card issuing](/resources/more/stablecoin-card-issuing-compliance)

## Sources

- [Bridge: global card issuance with stablecoins explained](https://bridge.xyz/learn/stablecoin-payments-global-card-issuance)
- [Visa: Bridge-enabled stablecoin-linked cards live in 18 countries (March 3, 2026)](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.22206.html)
- [Rain: homepage, network membership and daily stablecoin settlement](https://www.rain.xyz)
- [Stripe docs: issue stablecoin-backed cards with Bridge](https://docs.stripe.com/issuing/bridge-stablecoin-cards)
- [Stripe docs: real-time authorizations](https://docs.stripe.com/issuing/controls/real-time-authorizations)
- [PCI Security Standards Council: PCI DSS v4.0.1](https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1)

*This article is for general information only and is not legal, tax, or financial advice.*