A stablecoin card program is launched by buying the issuing stack and the money legs, and building the product and the ledger. The issuing stack is a bank that sponsors the BIN (the card's bank identification number), a program manager and a processor. The money legs fund the balance and cash it out. Decide custody first.
Build vs buy, layer by layer
A card program is six layers, each with its own build-or-buy answer. Visa describes its stablecoin programs as arrangements between Visa and card issuers or program managers. It counted more than 130 of them in more than 50 countries in its March 31, 2026 update, so the market is real. The issuing side is a bank partnership, not software: Rain's cards are Visa debit cards issued by Cross River Bank, with Rain Products, Inc. as program manager.
The six layers of a card program and the default call on each (industry roles, with Visa and Rain as the worked example, November 1, 2026).
Layer | What it does | Default | Why |
Network membership and BIN sponsor | The bank that holds the issuing licence and whose BIN the card carries | Buy | Licences and bank contracts |
Program manager | Runs the program under the issuer's rules | Buy first | Platforms such as Rain act as program manager |
Processor | Approves or declines each authorization in real time | Buy | It must read a stablecoin balance while the terminal waits |
Wallet and custody | Holds the balance the card spends from | Decide first | It sets who holds funds |
Funding and cash-out legs | Turns local money into the balance and the balance back into local money | Buy | Each country needs bank partners and rails, such as BRL to USDC |
Product and ledger | The app, balance and limits view, reconciliation | Build | Your users touch it |
Rain's own comparison puts its time to market at 8 to 12 weeks, against 6 to 18 months for traditional issuers, on its card issuing page. Buy the first five rows and build the last.
Lumx sits in the funding and cash-out row and, through its wallet, in the custody row. It does not issue cards.
Who is the BIN sponsor, the issuer processor and the program manager?
They are three jobs a platform often bundles into one contract. Write down who holds each before you sign.
Who does what in a card program (industry roles, with Visa and Rain as the worked example, November 1, 2026).
Role | Usually held by | What it owns | What it means for your launch |
Card network | Visa or Mastercard | Acceptance, program rules, dispute rules | Sets the rules every other role follows |
BIN sponsor (the issuer) | A bank that is a network member | The issuing licence, the BIN, the compliance program | Reviews your business and users before cards ship |
Program manager | A fintech or card platform, or you | Onboarding, limits, support | Decides what the cardholder experiences |
Issuer processor | The platform or a processor it uses | Authorization decisions, card controls, card data | Checks the stablecoin balance for each purchase |
Balance holder | A custodian, the platform or the user's own smart account | The stablecoin the card spends from | Decides who bears the loss if it fails |
Rain's page shows the split: Cross River Bank issues, and Rain Products, Inc. says it is a technology company, not a bank, and serves as program manager.
Lumx holds none of these roles. For the balance and money-movement side, see how to choose an infrastructure provider.
The architecture: one ledger, two money legs and the card
A purchase touches five steps, and only one of them is the card.
The cardholder is onboarded and verified.
Local money comes in through a funding leg and becomes stablecoin.
The balance sits in a wallet the card can spend from.
At each purchase the processor checks the balance, the program manager's rules apply, and the network settles later.
The cardholder cashes out to a bank for everything a card cannot pay.
Visa describes the middle step: on a tap, the program manager verifies the user's wallet balance through a smart contract or an API, and the amount is reserved and converted as needed. Settlement runs one of two ways: the program manager converts to fiat before settling with Visa, or, for Visa Principal Members, issuers settle in USDC. Mastercard has started settling card transactions in stablecoins too.
Skip the last step and the card becomes a one-way door.
Your app owns the ledger: available balance is credits minus debits minus open authorizations, which the card platform's events supply.
On Lumx, each cardholder is a customer with a wallet on every supported network once approved. The webhooks onramp.success, offramp.success and transfer.success report each balance change, so the app mirrors the balance without polling a chain. Your app caps cash-out at the wallet balance minus open authorizations, using the card platform's events. A withdrawal above the wallet balance fails with an insufficient balance error.
Funding and cash-out in Brazil, Mexico and the US
The legs meet local banks, so they differ by country. Brazil runs on Pix (Brazil's instant payment system, run by the Central Bank) and Mexico on SPEI (Mexico's interbank transfer system, run by Banxico), paid to a CLABE (the 18-digit Mexican bank account number). The US runs on ACH and wires. Rails for other countries are on the coverage page.
Funding and cash-out rails for three corridors (Lumx docs, November 1, 2026).
Country | Top-up rail and what the payer uses | Cash-out rail | Timing |
Brazil | Pix, paid with a static code that carries the reference. See BRL to USDC | Pix, see USDC to BRL | Instant, 24/7/365, no cut-off |
Mexico | SPEI, paid to a CLABE with a memo reference. See MXN to USDC | SPEI | Instant, 24/7/365, no cut-off |
United States | ACH or FEDWIRE to an account and routing number. See USD to USDC | ACH, FEDWIRE or SWIFT in USD | ACH 1 to 2 business days, cut-off 2:00 PM ET. FEDWIRE same business day, cut-off 3:00 PM ET. SWIFT 1 to 5 business days |
A Pix or SPEI top-up is instant at any hour, so there is no banking-hours queue. A US top-up is not: a transfer sent after the cut-off, on a weekend or on a bank holiday waits for the next business day, so show the cut-off before the cardholder sends.
Lumx gives each cardholder a named virtual account (a local account number in the customer's own name) in the currency they earn in. BRL, MXN, EUR and GBP accounts go active right after approval, and a USD account takes up to one business day. An autoconversion rule converts each deposit to USDC or USDT on the network you pick, and each deposit must be worth at least 50 USD in the account's currency. Cash-out is an off-ramp to a destination registered under the same customer. See named virtual accounts and global payments.
Custody and settlement are the two choices to settle early
They come before the vendor shortlist. Custody: a provider holds the balance, or the user controls a self-custodial smart account. Settlement: fiat over bank rails or USDC with the network, converted just in time at authorization or from a prefunded balance. A provider can change a fee, but changing the custody model means moving funds and rewriting flows.
Ask your sponsor bank which model is open to you. The mechanics are in how stablecoin card transactions settle.
Lumx wallets are custodial and the balance persists, so the model is prefunded. For on-ramp, off-ramp and transfer, USDC runs on Ethereum, Polygon and Base, and USDT on Ethereum, Polygon and Tron, plus Stellar USDC for BRL on-ramp only, per the Coverage page. Set the autoconversion network to the one the card platform reads.
Start with the money legs, not the card
I would build the top-up and cash-out legs in the same week the sponsor bank review starts, not after the card works. The review runs on the bank's calendar, so the legs are the only part of the launch you can test while it runs. A card users can load but not drain is the version that fills the support queue, so I would refuse a launch date that has a funding screen and no cash-out screen.
Write the role table with a name in every row, then open the sponsor review.
Build both money legs in a sandbox while the review runs.
Pilot with staff on real purchases: a partial capture, a refund, a dispute, and a cash-out while an authorization is still open.
Open to users in stages, with spending limits.
Lumx has a sandbox with simulated deposits, so step 2 needs no real money, and an API integration takes 2 to 3 weeks.
What does a launch cost and how long does it take?
A card program has five cost lines, each in a different contract. Nobody can quote them without a named sponsor bank and platform, so this gives the lines, not numbers.
Cost lines and who earns on them in a card program (industry roles, November 1, 2026).
Line | Who charges it | Where it shows up |
Platform and program management | The card platform | Monthly, per-card or per-transaction fees |
Sponsor bank | The BIN sponsor | Program fee or minimums, usually passed through |
Processor | The issuer processor | Per authorization, often bundled |
Interchange | Paid by the merchant side, shared under contract | Revenue on card spend, not a cost |
Money-leg fees | The funding and cash-out provider | Per top-up, per payout and FX |
The calendar splits the same way: sponsor review runs on the bank's schedule, the money legs on yours. Rain's 8 to 12 weeks to market is a vendor claim, not a measurement, so get any platform's timeline in writing.
Lumx prices the money legs as a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans. The standard agreement has a monthly minimum with a ramp-up period. The card platform's fees are a separate contract, so ask for its schedule line by line.
Compliance: who verifies whom
The card platform verifies the cardholder, and the money legs need their own verification. Agree in writing who runs KYC (know your customer, verifying an individual), KYB (know your business, verifying a company and its owners), sanctions screening and monitoring for each leg, because a gap between the two is where a compliance hold appears. Every payment must belong to an onboarded party acting on its own funds, because a pooled account hides counterparties from screening.
Lumx onboards each cardholder as its own customer with KYC through Sumsub, and a business with KYB verification, targeting one business day. Its nested payments rule forbids the pooled structure. The onboarding questionnaire has a business activity value for crypto cards, and the docs' high-risk list names prepaid or gift cards and managing client funds, stablecoins or wallets. High-risk activities get enhanced due diligence, which takes longer than Standard verification, so disclose the program up front and plan for a longer verification. A compliance hold arrives by webhook as an RFI (request for information, a hold that asks for a document before a transaction clears), and a transaction hold needs an answer within 24 hours or it may be refunded.
When a card program is the wrong tool. Cardholders who mostly need money in a bank account do not need a card: rent and salaries are bank payments, which a local payout from a stablecoin balance can make. The stablecoin card vs local payout comparison covers that choice.
It is also wrong when the money is not the cardholder's: a platform holding many users' funds in one account runs a pooled account, which Lumx does not allow.
What a card program looks like with Lumx underneath
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.
For a card program, Lumx supplies two legs: local-currency top-up in and cash-out to a local bank. It does not issue cards. The issuer is a separate company you contract yourself. Rain is one example, and the Lumx and Rain comparison shows how the layers fit.
You create each cardholder as a customer with the currencies they need, and the accounts go active after KYC approval. The top-up is a stablecoin on-ramp or an autoconversion rule on that account. The card spends from the wallet; the cash-out is a stablecoin off-ramp to a registered destination that your platform starts through the API. Pricing for these legs is in the cost section above.
Next step: name the company in every row of the role table, then start the two money legs in the sandbox while the sponsor bank reviews you.
Methodology and sources
We read the Lumx docs, the Visa pages and Rain's card issuing page on November 1, 2026. Rain statements come from its public site, and Visa figures are Visa's own, with dates.
Lumx docs: Coverage, Accounts, Wallets, Autoconversion rules, Cut-off times, Nested payments, Prohibited activities, RFI
Rain's card issuing page, read November 1, 2026, for the program manager statement and the time-to-market comparison (a vendor claim); see Lumx vs Rain
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Laura Ockel on Unsplash.
How do you launch a stablecoin card program?
Pick the market, choose a platform that bundles bank, program manager and processor, decide custody and settlement, split compliance duties in writing, build the money legs while the sponsor bank reviews you, and pilot with staff. Lumx supplies those two legs: local-currency top-up into a custodial wallet and cash-out to a registered bank account, and it does not issue cards.
Should you build or buy a stablecoin card program?
Buy the sponsor bank relationship, the program management and the processor, and build the product and the ledger. On the money legs, Lumx is the buy option: one API for top-up through named virtual accounts and cash-out over Pix, SPEI, ACH, FEDWIRE or SWIFT in USD.
What is the difference between a BIN sponsor, an issuer processor and a program manager?
The BIN sponsor is the bank whose number the card carries, the legal issuer. The program manager runs the program under its rules. The issuer processor decides each authorization in real time. Lumx holds none of these roles: it handles the wallet, the top-up and the cash-out around them.
How do cardholders get money into and out of the program?
They pay a local account in their own name, such as a Pix code or a CLABE, and the deposit becomes stablecoin in the wallet the card spends from. Cash-out pays a registered bank account. On Lumx, the top-up is an on-ramp or an autoconversion rule and the cash-out is an off-ramp your platform starts through the API.
Do you need a banking licence to launch a stablecoin card program?
In the structure Rain describes, no: its cards are issued by Cross River Bank under a Visa licence, and Rain is not a bank and serves as program manager. You still answer for onboarding and how user funds are held, and whether you need your own authorization depends on that and on where your users live, which is a question for counsel. Lumx puts prepaid cards and managing client funds or stablecoins on its high-risk list, which means disclosure and enhanced due diligence, so state the program when you onboard.
