Choose a stablecoin card issuing provider by getting nine answers in writing: where cardholders can live and on which network, who the issuer of record is, how the program settles, who holds the balance, what happens if it fails, who owns compliance, what it costs, how users fund and withdraw, and how long launch takes.
What the issuer does, and what you still need around it
A stablecoin card issuing provider puts a Visa or Mastercard card in your users' hands that spends from a stablecoin balance. It bundles four jobs: the issuer of record (the licensed bank or institution whose BIN, the number range the card runs on, carries the regulatory duty), the program manager that runs the program under the issuer's rules, the processor that approves or declines each purchase in real time, and the connection to the card network. What stablecoin card issuing is covers the product itself.
Two jobs sit outside that bundle: getting money into the program and getting it back out to a bank account. A card pays merchants, not rent or payroll. The infrastructure provider guide covers choosing for those legs.
Visa said, in a page last updated March 31, 2026, that it operates more than 130 stablecoin-funded card programs across more than 50 countries and expects the number to roughly double in 2026 (Visa).
Here the split is simple: the issuer you pick runs the card, and Lumx runs the money in and out around it: a wallet that holds the stablecoin and local rails on both sides.
Which nine questions separate one issuer from another?
Send every issuer the same nine questions and ask for the answers in the program agreement.
Nine questions for a stablecoin card issuing provider, with the answer to look for and the red flag
# | Question | Answer worth having | Red flag | Type |
1 | Where can cardholders live, and on which network and card types? | A country list of what is live today, apart from what is planned, with network and card type per country | "Global" with no country list | Pass or fail |
2 | Who is the issuer of record, and who is the program manager? | A named licensed party and a named manager, with the split of duties in the contract | Nobody can name the licensed party | Pass or fail |
3 | How does the program settle with the network? | Fiat or stablecoin, which blockchains, and who funds any fiat buffer | The model can change without a new agreement | Hard to reverse |
4 | Who holds the balance the card spends from? | Custodial or self-custodial, the named custodian, and how each purchase pulls funds | A custody claim with no named custodian or contract | Hard to reverse |
5 | What happens to balances if the provider or a shared contract fails, and who bears fraud losses? | Balances kept apart per program, an incident process, who reimburses cardholders and by when, who funds fraud losses and runs chargebacks, and by when a disputed purchase is credited | Programs share one contract, or liability for fraud and disputes is not stated in the agreement | Scored |
6 | Who runs KYC, KYB, sanctions screening and monitoring, and what card controls exist? | A written split of what the issuer, you and your payments layer each check, plus controls such as freeze, spend limits, 3DS and tokenization | "We handle compliance" with no split | Scored |
7 | What do you pay? | Interchange share, per-card fee and conversion spread, each as a number | A "no fee" claim with no spread disclosed | Scored |
8 | How do users fund the card in local currency and withdraw to a bank account? | Named rails for both legs, settlement times, and the sender shown on the bank statement | Funding by card or US bank transfer only, no local cash-out | Scored |
9 | What decides the time to the first live card? | Gates named, such as sponsor bank approval, each with an owner and a duration | "Weeks" with no gates named | Scored |
Questions 1 and 2 are pass or fail: an issuer that cannot serve your main market or name its licensed party is out before price matters. We treat questions 3 and 4 as hard to reverse, because both are written into the program agreement and every card already issued. Questions 5 to 9 are scored, and the weights depend on who your users are. The issuer answers questions 1 to 7 and 9. Question 8 is answered by the layer around it.
Reading the settlement and custody answers
In the older settlement model the program converts stablecoin to fiat and settles with the network over bank rails. In the newer one the issuer settles in USDC. Visa launched USDC settlement for U.S. issuer and acquirer partners on December 16, 2025, with Cross River Bank and Lead Bank settling over Solana, according to its press release. The Mastercard settlement post covers the other network.
Settlement says little about the cardholder's balance, so read custody separately. In a custodial program a provider or custodian holds the balance. In a self-custodial one the user's own wallet or smart account holds it and approves each spend. They fail differently, which is why question 5 exists. Ask also who bears fraud and chargeback losses and who runs disputes, since the agreement, not the network, decides that. Ask whether program balances sit in separate contracts or one shared contract, how upgrades reach every program, and who reimburses cardholders after an incident and by when.
The table quotes two issuers. We did not test the claims, and it is not a ranking.
How two issuers describe themselves on their own pages (Bridge's cards page and Rain's site, read November 1, 2026)
Issuer | Settlement and networks, as declared | Funding and issuing, as declared |
Bridge (a Stripe company) | Programs "settle in fiat or stablecoin"; virtual cards with Apple and Google Pay, plus physical cards | Spend is funded from "a custodial wallet, noncustodial wallet, or Stripe financial account"; programs keep 100% of interchange |
Rain (compared with Lumx in Lumx vs Rain) | Settles card transactions with the networks daily using stablecoins; lists itself as Visa Principal Member and Mastercard Principal Member | "Cards are issued through partners licensed in their respective jurisdictions" |
Around a card, Lumx keeps the balance in a custodial wallet under the customer who owns it, in USDC on Ethereum, Polygon or Base, or USDT on Ethereum, Polygon or Tron, so the first thing to match with an issuer is which chain and stablecoin pairs it accepts.
Who owns compliance when two companies touch the money
The issuer's bank typically verifies the cardholder for the card. Your payments layer has to verify who funds the program and who receives the cash-out. A gap between the two is the risk, so ask for the split in writing.
On the Lumx side, KYB (know your business, the verification of a company and its owners) for the platform targets one business day, individuals go through KYC (know your customer, the verification of an individual) with Sumsub, which can be reused through Sumsub token sharing, and monitoring runs on Chainalysis. Each bank destination is verified before its first payout. A company that runs a card program discloses it at onboarding, and the business activity list has a CRYPTO_CARDS value. Prepaid and gift cards sit on the high-risk list, which triggers Enhanced Due Diligence, so plan for a longer verification window. A transaction flagged by monitoring is held as an RFI (request for information, a compliance hold that asks for a document before a transaction clears). The KYB explainer covers what the company submits.
Lumx also needs to see every payer and payee. A platform that pools its cardholders' balances in one wallet is nesting under the docs' Nested Payments policy, so each balance sits in a wallet under the customer who owns it.
Test the cash-out before you sign
Pilots cover the swipe. Add the exit, because cash-out is the leg a card cannot make.
I recommend running the pilot all the way through a withdrawal, not only a swipe: issue a card to a colleague, fund it in local currency, spend a small amount, then withdraw the rest to a bank account and watch the status until the money lands. I would also try a withdrawal larger than the balance, because the issuer and your payments layer each keep their own view of the balance, and the withdrawal is where the two views meet.
For the exit, a Lumx withdrawal is an off-ramp from the wallet to a destination registered under the customer, and one larger than the balance fails with an insufficient balance error. Before the platform starts a withdrawal, it sets aside the card's open authorizations from the wallet balance and withdraws the rest. A Pix (Brazil's instant payment system, run by the Central Bank) cash-out shows the customer as payer, not Lumx.
How do users top up and cash out in local currency?
A local top-up is a deposit on a bank rail that lands as stablecoin. A cash-out is the reverse, to a bank destination. Each country needs its own pair of rails. Pix and SPEI (Mexico's interbank transfer system, run by Banxico) both settle 24/7/365. Bre-B (Colombia's instant payment system) is listed as instant in the docs, and PSE (Colombia's online bank-transfer network) collects only, because the payer authorizes a debit.
Local rails for card top-up and cash-out, with settlement times (Lumx docs on coverage and cut-off times, read November 1, 2026)
Country and currency | Top-up | Cash-out | Settlement |
Brazil, BRL (BRL to USDC) | Pix | Pix | Instant, 24/7/365 |
Mexico, MXN (MXN to USDC) | SPEI to a CLABE (18-digit account number) with a memo | SPEI | Instant, 24/7/365 |
Colombia, COP | Bre-B key or PSE | Bre-B or ACH Colombia | Bre-B is instant, capped at COP 12,110,000 per payment in 2026 |
United States, USD | ACH, FEDWIRE or SWIFT | ACH, FEDWIRE or SWIFT | ACH 1 to 2 business days, FEDWIRE same business day, SWIFT 1 to 5 business days |
The Bre-B cap is a Banco de la República rule for every provider. ACH Colombia has no per-payment limit, so it is the rail above the cap. The stablecoin card funding guide walks through the top-up.
For local funding, a Lumx BRL or MXN account is a named virtual account (a local account number issued in the customer's own name), so the deposit is a normal local transfer. An autoconversion rule turns each deposit into stablecoin at market, with no call per transaction, and a per-transaction stablecoin on-ramp with a locked quote is the route for an exact amount. The cash-out is a stablecoin off-ramp. For rails and countries, see global payments and the coverage page.
When this checklist is the wrong starting point
When your users need to be paid, not to spend. A Pix or SPEI payout does that without a card, and the card versus local payout comparison shows where each fits.
When cards are your core product and you already hold a sponsor bank and a processor. Your question is the build itself, which launching a stablecoin card program covers.
When one vendor for the card and the accounts matters more than the best answer on each leg. An issuer that bundles both is simpler to run than an issuer plus Lumx when every cardholder lives in a market it covers end to end.
What this looks like around a card program on Lumx
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
Lumx supplies the wallet and both money legs, local-currency top-up and cash-out to a bank account.
With Rain as the issuer, the card spends straight from the Lumx wallet through Rain's real-time funding. The user connects the wallet and approves how much the card may spend, and can revoke the approval. At each purchase only that purchase's amount moves to the collateral contract, and the rest stays in the wallet. There is no card-loading step: the top-up is the local deposit that becomes stablecoin in the wallet, and the withdrawal is an off-ramp the platform starts through the Lumx API. Rain is part of the client's stack, not a Lumx partner.
Webhooks report each leg: onramp.success when the wallet is credited, destinations.approved when a bank destination can receive funds, then offramp.success or offramp.failed. A locked quote returns the Lumx fee, the partner fee and the total before any money moves, which answers question 7 for the money layer. Lumx pricing is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans.
The named virtual accounts page shows the account side.
Methodology and sources
Product statements come from the Lumx docs for coverage, cut-off times, wallets, destinations, autoconversion rules, webhooks, nested payments, high-risk activities, company types and the exchange rate reference, read on November 1, 2026.
Issuer statements are the issuers' own, from Bridge's cards page and Rain's website, read on November 1, 2026. Visa figures come from its page on stablecoin-linked cards, last updated March 31, 2026, and its press release of December 16, 2025. The Bre-B cap is Circular Reglamentaria Externa DSP-465 of the Banco de la República.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Tim Mossholder on Unsplash.
How to choose a stablecoin card issuing provider?
Send every provider the same nine questions and get the answers in the program agreement, covering markets and network, issuer of record, settlement, custody, failure, compliance, cost, local funding and withdrawal, and what gates the first card. Treat the first two as pass or fail. Lumx does not issue the card: the issuer runs it, and Lumx supplies the wallet, local-currency top-up and cash-out around it.
What should a card issuer put in writing before you sign?
The licensed party and the program manager by name, the settlement model and who funds any fiat buffer, the custodian, the compliance split, every fee as a number including the conversion spread, and the gates to the first live card. A marketing line is not a commitment until it is a clause. At the Lumx layer, fees show on a locked quote before funds move.
Do you need a separate provider for local-currency top-up and cash-out?
Usually yes, if your cardholders live in Latin America and the issuer funds only by card or US bank transfer. A withdrawal to a bank account needs its own rail. Lumx handles this with a Pix, SPEI, Bre-B or PSE deposit that becomes stablecoin in the wallet, and the cash-out is an off-ramp to a verified bank destination over Pix, SPEI, Bre-B or ACH Colombia.
Is a stablecoin card custodial or self-custodial?
It depends on the issuer: some spend from a provider-held balance, some from the user's own wallet or smart account, and some offer both. Custodial puts the failure question on the provider, self-custodial on the user. Lumx wallets are custodial, held per customer in USDC on Ethereum, Polygon or Base, or USDT on Ethereum, Polygon or Tron, and a card can spend from the wallet once the user approves an amount.
What decides how fast the first card goes live?
Usually gates outside the API, such as sponsor bank approval, program review and your own compliance onboarding. Ask each issuer to list them with an owner and a duration. At Lumx, a customer reaches an active account after KYB, which targets one business day, and a card business discloses its activity at onboarding, so allow more time if Enhanced Due Diligence applies.
