An 8-point framework for choosing a stablecoin card issuing provider, a neutral look at Bridge, Rain, BVNK, and Gnosis Pay, and the payout layer beside it.
Choose a stablecoin card issuing provider on eight criteria: market coverage, card network, settlement model, custody model, compliance ownership, fee transparency, SDK quality, and time to launch. Bridge, Rain, BVNK, and Gnosis Pay package these differently. The issuer runs the card. A separate payout layer, such as BlindPay, can handle funding and local cash-out.
That split matters because a card only covers one job: paying merchants that accept Visa or Mastercard. The money still has to arrive in the program, and users still need to reach a bank account for rent, payroll, and invoices. This guide covers how to evaluate the card side honestly, and where the other legs go.
Key takeaways
For the basics of the product itself, start with what stablecoin card issuing is.
A stablecoin card issuing provider lets you put a Visa or Mastercard card in your users' hands that spends from a stablecoin balance. It bundles the licensed issuer, the processor, and the program tooling into one integration.
A few terms come up in every vendor call:
The step-by-step flow of a single purchase is covered in how stablecoin card transactions settle.
Buy, unless cards are your core product and you already have a sponsor bank, a processor contract, and a compliance team. Building the stack yourself takes months of negotiation and certification before the first card ships.
The market has moved toward platforms. Visa reported more than 130 stablecoin-linked card programs across more than 50 countries, and expects the number of programs to roughly double in 2026. A platform that bundles issuer, processor, and program tooling is the shorter path to joining them.
Building makes sense when you need control that no platform offers, such as a custom authorization rule set or a settlement arrangement only your bank partner supports. The developer guide to issuing stablecoin cards through an API lists what a card issuing API has to expose if you go that way.
Use the same eight criteria for every provider and score each one against your own markets and users. A provider that is strong in Latin America can be the wrong pick for an EEA consumer card.
| Criterion | What to ask | Why it matters |
|---|---|---|
| Market coverage | Which countries can cardholders live in today, and which are planned? | A card you can't offer in your main market is a non-starter |
| Card network | Visa, Mastercard, or both? Physical and virtual cards? | Network rules and acceptance follow from this |
| Settlement model | Does the program settle with the network in fiat, or in USDC? | Changes your liquidity needs and conversion timing |
| Custody model | Custodial ledger or self-custodial smart account? | Decides who holds funds and what fails if the provider fails |
| Compliance ownership | Who runs KYC, KYB, sanctions screening, and monitoring? | You need a clear split before a bank partner signs off |
| Fee transparency | Interchange share, per-card fees, FX and conversion spread | "No fee" claims often sit in the spread |
| SDK and API quality | Sandbox, webhooks, card controls, dispute endpoints | Sets your engineering cost for years |
| Time to launch | Weeks or months to first live card, and what blocks it | Usually gated by the sponsor bank, not the API |
Two of these are hard to reverse. Moving from custodial to self-custodial balances, or from fiat to USDC settlement, usually means a new program, new contracts, and reissued cards. Decide those first. Custodial vs self-custodial stablecoin cards walks through the custody trade-off in detail.
The cleanest stack uses the issuer for cards and BlindPay for funding and local payouts. The card provider handles authorization and merchant spend. BlindPay handles money coming into the program and money leaving it for a bank account.
On the funding side, BlindPay virtual accounts give each customer a US account with its own routing and account number. Each ACH, wire, or SWIFT deposit converts to USDC or USDT and lands in the wallet linked to the account, which can be the wallet the card spends from.
On the payout side, 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 the stablecoins move, there is no pre-funding, and plans are published with no volume floor. That covers the payments a card can't make: rent, salaries, supplier invoices, and transfers to a user's own bank.
Each of the four describes its card offering differently, and each has had notable news in 2025 and 2026. The table sticks to what each company says publicly and what has been reported, with links in the sources list.
| Provider | How it describes the card offering | Notable public fact |
|---|---|---|
| Bridge (a Stripe company) | "Launch a compliant consumer or commercial card program to users in multiple markets with a single integration," with users spending stablecoin balances | Visa partnership announced April 30, 2025, starting with Argentina, Colombia, Ecuador, Mexico, Peru, and Chile |
| Rain | "Stablecoin payments platform for enterprise," covering card programs, wallets, and scoped cards for agentic payments | August 28, 2026 vulnerability in an outdated version of its Solana contracts affecting a small number of programs; affected users reported repaid |
| BVNK | Enterprise stablecoin payments, including linking virtual cards to stablecoin balances and rewards on balances | Mastercard completed its acquisition of BVNK on August 3, 2026 |
| Gnosis Pay | Card programs on Safe smart accounts with self-custody and spending allowances | June 1, 2026 exploit of its Delay and Roles modules; its post-mortem says Gnosis absorbed the losses and restored all user funds |
Read the table as a starting point, not a ranking. Bridge's Visa partnership signals strength in Latin America. BVNK now sits inside a card network. Rain positions around enterprise programs and agent use cases. Gnosis Pay is the reference design for self-custodial spend. For how BlindPay compares on the payout job, see the Bridge and BVNK comparison pages.
Ask whether the program settles with the card network in fiat or directly in USDC, and who converts. The answer decides how much fiat liquidity the program has to hold and when stablecoins are sold.
In the traditional model, the program converts stablecoins to fiat and settles with the network over bank rails. In the newer model, the issuer settles with the network in USDC. Visa launched USDC settlement in the United States on December 16, 2025, with Cross River Bank and Lead Bank as initial banking participants, settling over Solana. By April 29, 2026, Visa's settlement pilot supported nine blockchains and a $7 billion annualized settlement run rate. That is settlement activity, not card spend.
Questions for the provider:
Ask how the provider isolates one program from another on shared smart contracts and shared ledgers. A flaw in shared infrastructure can hit many programs at once, even when each program is run well.
The Rain incident shows the pattern. On August 28, 2026, unauthorized withdrawals hit card balances held in a Rain-managed Solana contract. Rain described "a vulnerability impacting a small number of programs using an outdated version of our Solana contracts." Tria reported 636 affected users and $431,945, with every affected user being refunded in full. Avici reported $500,859 across 1,685 users, refunded in full plus 10% cashback. Self-custodial wallets were reported unaffected.
The useful questions are about process, not blame:
Are stablecoin cards safe? covers the full risk list for users.
Run a short, structured process: write requirements, shortlist on hard constraints, score on the eight criteria, then pilot. Most teams can do this in four to six weeks.
Match the stack to the job your users actually need done. A card alone rarely covers it.
Shortlist two or three card providers on the eight criteria, then design the funding and payout legs before you sign. Create a free BlindPay development instance to test virtual account deposits and Pix, SPEI, ACH, or SEPA payouts with test stablecoins while your card pilot runs.
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.
The three roles behind every card program, stablecoin cards included: what each one does, who carries liability, and what to ask a provider.