Bridge and BlindPay: stablecoin cards plus local-currency payouts in one stack

Reading time: about 8 minutes.

Summary: Bridge and BlindPay fit together at different layers of a stablecoin card program. Bridge issues stablecoin-linked Visa cards and runs wallets and card settlement. BlindPay funds those wallets from bank transfers and pays stablecoins out as local currency over Pix, SPEI, ACH, SEPA, and SWIFT (POBO/COBO). The wallet connects them.

Key takeaways

• Bridge covers the card layer: issuance, wallets, and settlement with Visa. Its card is issued by Lead Bank and managed by Bridge Ventures, LLC, per Bridge.
• BlindPay is an end-to-end stablecoin-to-local-currency payout API, plus US virtual accounts that turn bank deposits into USDC or USDT.
• The two providers never need to call each other. Both touch the same cardholder wallet.
• Your ledger is the glue: one available balance per cardholder, minus open card holds.
• The same split works with any card provider that spends from a wallet.

The head-to-head view, rails and custody side by side, is in BlindPay vs. Bridge. This page answers a different question: you already picked Bridge for cards, so how do you wire in bank funding and local payouts without building them yourself? For the wider program decisions, start with how to issue cards with stablecoins.

What does each provider handle?

Bridge handles the card and the stablecoin wallet it spends from. BlindPay handles the bank legs: money in from a bank account and money out to one. Neither has to replace the other.

Bridge's reach keeps growing. Visa reported Bridge-enabled cards live in 18 countries on March 3, 2026. Bridge reported 30 countries through its Stripe Issuing integration on April 29, 2026, with a goal of 100+ by the end of the year. Check the live list for your markets.

How does the architecture look end to end?

Picture five boxes in a row, with the cardholder wallet in the middle. Money enters on the left through BlindPay, sits in the wallet, leaves through the card in the middle, and leaves through BlindPay on the right when it goes to a bank account.

[Bank account] --ACH/wire/SWIFT--> [BlindPay virtual account]
                                          |
                                   USDC or USDT
                                          v
[Card terminal] <--Visa-- [Bridge card] <-- [Cardholder wallet] --> [BlindPay payout] --Pix/SPEI/ACH/SEPA/SWIFT--> [Bank account]
                                          ^
                                   [Your ledger]
                    (payin, authorization, capture, refund, payout events)

Three design choices follow from this picture.

The wallet is the contract between providers. Per Stripe's docs for Bridge-backed cards, a card can spend from "a Bridge custodial wallet, a Privy non-custodial wallet, or any other non-custodial wallet". If you use a non-custodial wallet, BlindPay can settle virtual account deposits straight into it.

The network has to match. BlindPay settles on Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Stellar, Solana, and Tron, with USDC or USDT depending on the network. Confirm which network and token your Bridge card spends from, then link that same wallet on the BlindPay side.

Your ledger owns the available balance. The card authorization deadline is short, so your systems decide from a ledger, not from a live chain query. The same ledger tells you how much a cardholder can send to a bank account.

How does one cardholder's month run, step by step?

Take a freelancer in Brazil paid by a US client. They spend part of the money on a card and send the rest to their bank account in reais.

1. Onboard. The cardholder passes KYC once on each side: BlindPay for the virtual account and payouts, Bridge for the card. On the Stripe Issuing path, Stripe's docs say the cards endorsement needs KYC within the past 24 hours, so create the card in the same session.
2. Get account details. BlindPay issues a US virtual account in the cardholder's name with its own routing and account number. It goes through compliance and bank review before the virtualAccount.complete webhook fires.
3. Get paid. The US client sends an ACH payment. BlindPay creates a payin, converts the deposit, and delivers USDC to the linked wallet. Your ledger credits the balance on payin.complete.
4. Spend. The cardholder buys something abroad. Bridge receives the authorization and, for a non-custodial wallet, pulls the funds onchain at authorization. Your ledger places a hold.
5. Settle the card. Captures, partial captures, and refunds arrive as card events. Stripe's docs say refunds are pushed back onchain and can be batched. Your ledger adjusts the hold to the final amount.
6. Cash out. The cardholder sends BRL 2,000 to their own bank account. You create a BlindPay payout quote, which shows the fee breakdown and the exact amount they receive, valid for 5 minutes. The cardholder authorizes the exact token amount, and the payout goes out over Pix, typically within minutes.
7. Reconcile. At month end, every movement on the wallet matches a BlindPay payin or payout event or a card event. Anything else is an exception to investigate.

What can go wrong between the two providers?

Most failures come from timing, not from either API. Plan for these four.

The overcapture behavior is documented by Stripe: Bridge "might also proactively pull an additional amount at the time of authorization based on the MCC". Treat the pulled amount as the hold, not the purchase amount.

When a BlindPay payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set. On Pix and other non-USD local rails the refund is automatic. USD payouts, and payouts whose review times out, are refunded after an operator review. Route those refunds back into the same ledger balance.

Does the same pattern work with BVNK or other card providers?

Yes. The pattern depends on a wallet the card spends from, not on Bridge specifically. Rain and Stripe Issuing with Bridge slot into the same card box. If your card or account layer is BVNK, which Mastercard finished acquiring on August 3, 2026, split by job the same way: the card and account stay there, and the local payout leg runs through BlindPay. The BlindPay vs. BVNK comparison covers that pairing.

Where does BlindPay fit?

BlindPay is an end-to-end stablecoin-to-local-currency payout API, and in this stack it owns both bank legs. Bridge runs the card. BlindPay moves money into and out of the wallet behind it.

Into the wallet: a US virtual account per cardholder, in their own name, converts ACH, wire, and SWIFT deposits to USDC or USDT. In Latin America, payins over Pix, SPEI, Transfers 3.0, and PSE do the same. Out of the wallet: payouts over Pix, SPEI, ACH Colombia, Transfers 3.0, ACH, RTP, Domestic Wire, SEPA, and SWIFT (POBO/COBO), funded at send time with no pre-funding per country.

Fees come from a monthly plan plus per-transaction fees that each quote discloses before you execute. KYC and KYB run in the same API, and every payin and payout fires a signed webhook your ledger can consume.

Read the payout quotes docs or talk to the team.

What to read next

• Stablecoin card issuing platforms compared
• How to issue stablecoin-funded cards through an API
• What is stablecoin card issuing?
• How to on-ramp BRL, MXN, ARS, and COP into stablecoins

Sources

• Bridge, Stablecoin-backed cards are now integrated with Stripe Issuing (April 29, 2026)
• Bridge, Global card issuance with stablecoins explained (March 16, 2026)
• Stripe, Issue stablecoin-backed cards with Bridge
• Visa, Bridge-enabled stablecoin-linked cards live in 18 countries (March 3, 2026)
• Mastercard, Mastercard completes acquisition of BVNK (August 3, 2026)

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