How to launch a stablecoin card program: a 9-step plan and who does what

A 9-step plan to launch a stablecoin card program: market, program manager, sponsor bank and BIN, processor, custody, compliance, funding, and payouts.

To launch a stablecoin card program, choose your market, pick an issuing platform, secure a sponsor bank and BIN, connect a processor, decide the custody model, split compliance duties, then set up funding, payouts, and a staff pilot. The card platform runs the card. Funding and local payouts are separate legs you plan alongside it.

Most launch plans stop at the card. Then the first user asks how to pay rent, and the second asks how to top up from a bank. This guide is the business plan: the roles, the order of decisions, and the two money legs a card program can't skip. For the developer view of the card API itself, see how to issue stablecoin cards through an API.

Key takeaways

  • A stablecoin card program has five card roles: network, issuer or BIN sponsor, program manager, processor, and the stablecoin provider.
  • Visa reported more than 130 stablecoin-linked card programs in more than 50 countries as of March 31, 2026.
  • Custody and settlement are the two decisions that are expensive to reverse. Make them first.
  • Card platforms run merchant spend. Funding and cash-out to bank accounts need their own provider.
  • Sponsor bank review usually sets the launch timeline, not engineering.

New to the product? Start with what stablecoin card issuing is.

What does it take to launch a stablecoin card program?

It takes a licensed issuer, a program manager, a processor, a stablecoin balance the card can spend from, and a compliance program that covers both the card and the stablecoin. Most companies get the first three from one platform.

Definitions you will hear in every partner call:

  • Issuer or BIN sponsor: the licensed bank or e-money institution whose bank identification number the card carries. It holds the issuing license.
  • Program manager: the company that designs and operates the program under the issuer's rules.
  • Processor: the system that approves or declines each authorization in real time.
  • Just-in-time funding: stablecoins stay in the balance until a purchase, then convert at authorization.
  • Custodial vs self-custodial: whether a provider holds the balance or the user's own smart account does.

Visa reported more than 130 stablecoin-linked card programs in more than 50 countries, and expects that number of programs to roughly double in 2026. Platforms that bundle the issuer, program manager, and processor are the usual route to launch.

Where does BlindPay fit in the launch plan?

Use a card issuer for cards and BlindPay for funding and local payouts. The issuer handles authorization and merchant spend. BlindPay handles money entering the program from bank accounts and money leaving it for bank accounts.

On the funding leg, BlindPay virtual accounts give each customer a US account with its own routing and account number. ACH, wire, and SWIFT deposits convert to USDC or USDT and land in the linked wallet, which can be the balance the card spends from. BlindPay also collects Pix, SPEI, PSE, and Transfers 3.0 payins and delivers them as stablecoins.

On the payout leg, BlindPay converts USDC and USDT into local currency over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO/COBO) with UETR tracking and MT103 confirmations. A live quote locks the rate and fees before stablecoins move, there is no pre-funding, and plans are published with no volume floor. KYC, KYB, and sanctions screening run in the same API flow.

Who does what in a stablecoin card program?

Each role has a different owner and a different regulator. Write the split down before you sign anything, because the sponsor bank will ask for it.

RoleWhat it doesTypical owner
Card networkRoutes transactions, sets program and dispute rulesVisa or Mastercard
Issuer / BIN sponsorLegal issuer, owns the compliance programBank or e-money institution, usually via the platform
Program managerOnboarding, limits, support, reportingCard platform or you
ProcessorAuthorizations, card controls, disputesCard platform
Stablecoin providerHolds, converts, or settles the stablecoinCard platform, custodian, or user's smart account
Your companyProduct, users, brand, first-line supportYou

Bridge, Rain, and BVNK are examples of platforms that cover several of these roles. Bridge describes its offer as launching "a compliant consumer or commercial card program to users in multiple markets with a single integration." Rain calls itself a stablecoin payments platform for enterprise, with card programs, wallets, and scoped cards for agentic payments. BVNK, part of Mastercard since August 3, 2026, describes linking virtual cards to stablecoin balances. How to choose a stablecoin card issuing provider has a scoring framework.

What are the nine launch steps?

Work through them in order. Each step depends on decisions from the one before.

  1. Choose your market and users. List the countries where cardholders live, consumer or corporate cards, and the payments users make most. A remote team in Brazil has different needs from travelers in the EEA.
  2. Choose an issuing platform or program manager. Shortlist on coverage, network, settlement model, custody model, compliance split, fees, SDKs, and time to launch.
  3. Secure a sponsor bank and BIN. The platform usually brings one. Expect a detailed onboarding review of your business, users, and controls.
  4. Connect the processor. Configure authorization against stablecoin balances, card controls, and dispute flows. Test partial captures, such as hotel and fuel holds where the final amount changes.
  5. Decide the wallet and custody model. Custodial ledger or self-custodial smart accounts, and just-in-time or prefunded conversion. Just-in-time vs prefunded stablecoin cards compares the funding models.
  6. Split compliance responsibilities. Agree who runs KYC, KYB, sanctions screening, monitoring, and reporting. Stablecoin card issuing compliance lists each party's duties, and the US and EU guides cover regional rules.
  7. Set up funding and liquidity. Decide how money enters: stablecoin transfers, bank deposits through virtual accounts, or both. Confirm how settlement with the network is funded.
  8. Set up payouts and cash-out. Give users and your company a way to reach local bank accounts for rent, salaries, and supplier invoices.
  9. Pilot and go live. Issue cards to staff, run real purchases, refunds, and a dispute, then open to users in stages with spending limits.

Which decisions are hardest to change later?

Custody and settlement. Both shape your contracts, your user flows, and your liquidity, so changing either usually means a new program.

DecisionOptionsWhat it drives
Custody modelCustodial ledger or self-custodial smart accountWho holds funds, recovery, failure modes
Settlement modelFiat over bank rails or USDC with the networkFiat buffer, conversion timing, bank partner fit
Conversion timingJust-in-time or prefundedUser experience, exposure, load fees
Stablecoins supportedUSDC, USDT, euro stablecoinsCard support, chains, sponsor bank comfort

Settlement is moving fast. Visa launched US USDC settlement on December 16, 2025, and by April 29, 2026 reported a $7 billion annualized stablecoin settlement run rate across nine blockchains. Ask your platform which model your program uses and whether it can change.

What does the money flow look like for a user?

A user funds the card from a bank or a wallet, spends at merchants with the card, and cashes out to a bank for everything else. Three legs, often three providers.

Take a design studio in Mexico that pays contractors in Brazil and Colombia:

  1. Funding. A US client pays the studio's invoice by ACH into a virtual account. The deposit converts to USDC in the studio's wallet.
  2. Spending. Staff use stablecoin cards for software, travel, and equipment. The card platform authorizes each purchase against the USDC balance.
  3. Cash-out. Contractor invoices go out as local payouts: Pix in Brazil, ACH Colombia in Colombia. Salaries in Mexico go out over SPEI.

The card covers step 2 only. Steps 1 and 3 are where most of the money moves.

What goes wrong at launch?

The common failures are operational, not technical. Plan for them before the first card ships.

  • Bank review takes longer than expected. Start the sponsor bank's onboarding questionnaire early.
  • No cash-out path. Users load money, then can't pay rent. Build the payout leg before launch.
  • Shared infrastructure risk. On August 28, 2026, a vulnerability in an outdated version of Rain's Solana contracts hit a small number of programs. Tria reported 636 affected users and $431,945, with every affected user being refunded in full. Ask how your platform isolates programs and handles upgrades.
  • Unclear disclosures. State who holds funds, which fees apply, and that stablecoin balances are not bank deposits.

What is the next step?

Write the role table above for your own program, with a name in every row. Then test the funding and payout legs on a free BlindPay development instance with test stablecoins while your card platform runs its review.

Sources

FAQ