Adding debit cards to a neobank means picking a program model (debit, prepaid or stablecoin-backed, which the issuer may structure as debit, prepaid or credit), signing a card issuing provider that brings the BIN sponsor and the processor, and making your own ledger the source of the spendable balance. Then you build funding and cash-out around the card.
What card program models can a US neobank choose?
Three models cover most programs, and they differ in where the money sits when the customer taps the card. That decides who holds the funds, which US rules attach and what the neobank has to build. The rule set for the third model depends on how the issuer structures the card, so ask before you assume it is debit.
Three card program models for a US neobank, compared by where the balance sits. Rules and provider terms read on November 1, 2026.
Model | Who issues | Where the balance sits | Who funds it | Lumx role |
Debit on a deposit account | A sponsor bank, through a card provider | A deposit account at the sponsor bank | Direct deposit and transfers | None in the card path |
Prepaid | A sponsor bank, through a card provider | A prepaid balance held for the program | Loads from a funding source | None in the card path |
Stablecoin-backed (debit, prepaid or credit, depending on the issuer) | A card provider with a BIN sponsor | A stablecoin wallet the card spends from | USDC or USDT in that wallet | Funds the wallet and cashes out the balance |
A US neobank is not a bank, so the first two models need a sponsor bank behind the product.
One swipe touches the card network, the BIN sponsor that owns the card range, an issuer-processor that answers authorizations and a program manager, and providers bundle these roles differently. Our guide to choosing a card issuing provider lists the questions to put to two or three candidates.
On Lumx, the card comes from the issuer you sign, and Lumx sits outside the authorization path, so it never approves or declines a purchase. A stablecoin-backed card pairs with Lumx for funding and cash-out, and the other two models need no Lumx in the card path.
Is a stablecoin-backed card a debit card?
Not always, and the answer changes the rules. Rain's card-issuing page lists credit and prepaid products, and its real-time funding post says that at each purchase only that purchase's amount is committed to a collateral contract, where it stays until it is liquidated to repay Rain's extension of credit to the user. That is credit secured by stablecoin, not a card that debits a bank account.
For a neobank this is the point to settle with the issuer in writing before the product is named. If the card is debit or prepaid, the Regulation E and Regulation II sections below apply. If it is credit secured by collateral, they do not apply the same way, and which consumer-credit rules attach is a question for counsel and the issuer. Stablecoin card vs crypto debit card lays out the four types side by side.
On Lumx, the wallet is custodial and it holds the stablecoin the card spends from. For a Rain-issued card, the cardholder connects the wallet and approves a spend limit, and the Lumx off-ramp does not see open card authorizations.
How long does it take and what does it cost to add debit cards?
Timelines depend on the issuer, the sponsor bank and your own build. The card figures come from Rain's card-issuing page, read on November 1, 2026, and are the issuer's own claims.
Launch timelines as one stablecoin card issuer states them on its own page, with the Lumx integration for the money legs.
Source | Figure | What it measures |
Rain, comparison table | 8-12 weeks | Speed to market for a Rain program |
Rain, FAQ | Under two weeks | Some programs, per Rain, depending on scope and the customer's own resourcing |
Lumx API integration | 2 to 3 weeks to go-live | The funding and cash-out legs only, not the card |
On cost, the card side is priced by the issuer under your contract, and Rain's page lists no prices, so get a written quote that separates per-card, per-transaction and program fees, and ask how interchange is shared. On Lumx, pricing is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, and no published plans. There is no pre-funding: no capital sits in settlement accounts before a transaction. That covers the funding and cash-out legs, not the card.
Virtual cards, physical cards and wallets
Rain's page lists virtual and physical cards and Apple Pay and Google Pay provisioning. A virtual card skips printing and shipping, so it is the usual first release, and a wallet token lets the customer tap to pay before any plastic arrives. Cardholder identity is checked once for the card and once for the money legs, so ask whether the issuer relies on your onboarding. On Lumx, each cardholder is created as a customer and completes KYC (know your customer, the verification of an individual) before the USD account and wallet exist, and that KYC can be reused through Sumsub token sharing.
How a card meets the neobank's ledger
The ledger decides the available balance. A card authorization needs an answer in milliseconds, so it cannot wait on a live query to a funding provider. A deposit credits the available balance, an authorization moves the amount from available to held, a capture debits the held amount, a cash-out debits available, and a refund credits it back.
I recommend building the cash-out leg before the card goes live, and I would let the neobank's own ledger, not the issuer's balance view, decide what a customer can withdraw. A card on a balance with no way out becomes a support ticket the first time a customer wants the money back.
On Lumx, the funding and cash-out legs report through webhooks (onramp.success, offramp.success and transfer.success), so the ledger posts each credit and debit without polling a blockchain. A withdrawal larger than the wallet balance fails with an insufficient balance error. The cash-out does not see open card authorizations, so capping the withdrawable amount at the wallet balance minus what open authorizations commit is the app's job.
Funding the card and cashing out, with US cut-offs
Funding is where timing surprises a neobank: a customer who pays by ACH sees the balance after the deposit settles, not when the transfer is sent. ACH on Lumx is credit (push) only, so the customer sends the payment and Lumx never pulls it by debit.
USD card-funding rails on a Lumx account, from the Lumx docs read on November 1, 2026.
Rail | Cut-off (ET) | Settlement | Operating days |
ACH | 2:00 PM | 1 to 2 business days | US business days |
FEDWIRE | 3:00 PM | Same business day, typically within hours | US business days |
Requests after a cut-off, on a weekend or on a bank holiday are processed the next business day.
On Lumx, each cardholder is a customer who completes KYC and gets a USD named virtual account (a local account number issued in the customer's own name), open to any individual or company in a supported country. It supports ACH, Fedwire and SWIFT on the same account and goes active up to one business day after approval. An autoconversion rule converts every deposit to USDC or USDT on the network you pick, with no call per deposit, and a customer can have one active rule per USD account. Each deposit that converts is a stablecoin on-ramp that credits the wallet, and the onramp.success event is the moment to credit the ledger.
Cash-out is the reverse. The neobank's app starts a stablecoin off-ramp from the cardholder's wallet to a destination the cardholder registered as their own, and the stablecoin converts to dollars on a rail from the coverage page. Every deposit must be worth at least 50 USD, and a smaller one is not converted. Limits are set per transaction type, so the on-ramp has its own: at standard KYC the default is $7,500 per transaction and $15,000 per day, and the off-ramp has the same default of its own, and the limits may change. A deposit above the on-ramp limit is held as a balance on the account, and a cash-out above the off-ramp limit is rejected with the code TRANSACTION_LIMIT_EXCEEDED. Show the 50 USD floor and the remaining headroom on the add-money screen. Where no on-ramp or rule is active, a USD deposit stays as fiat in the account.
The US rules that shape a card program
Three federal rules decide most of the product work on a debit or prepaid program, and counsel confirms what binds a given product.
Federal rules that touch a US debit or prepaid card program, with what each does to the build.
Rule | What it says | What it does to the program |
12 CFR 1005.6 (Regulation E) | A consumer who reports a lost or stolen card within two business days is liable for the lesser of $50 or the unauthorized transfers before notice. | Freeze and report flows must work on day one |
12 CFR 1005.18 (Regulation E) | A financial institution complies with Regulation E for prepaid accounts, with pre-acquisition disclosures given before the consumer acquires the account | A prepaid model needs the disclosures built into onboarding, not added after |
12 CFR 235.5 (Regulation II) | The debit interchange fee limits do not apply to an issuer that holds the debited account and has under $10 billion in assets with its affiliates | The sponsor bank's asset size changes how much interchange the program can share |
Regulation II also sets the fee limit in 12 CFR 235.3 and requires two unaffiliated networks in 12 CFR 235.7, so ask the issuer how routing is set up. How US neobanks earn on remittances puts interchange beside the other revenue lines.
On Lumx, these rules sit on the card side, with the issuer and the sponsor bank. The Lumx side has its own rule: every payment must belong to a customer Lumx has onboarded. A third party may pay in (COBO), and an unusual payer can trigger a compliance hold and a return. A shared funding account hides who is paying from sanctions screening, which is why named accounts are one per cardholder (see nested payments). A transaction held for review is cleared through an RFI (request for information, a compliance hold that asks for a document), and the answer is due within 24 hours or the transaction may be refunded.
What breaks after launch
Common failure points between deposit, card spend and cash-out, with the fix.
What breaks | What happens | The fix |
ACH deposit sent after 2:00 PM ET | It is processed the next business day | Show the cut-off on the add-money screen |
Deposit under 50 USD | The minimum applies to every deposit, so it is not converted | Show the 50 USD minimum on the add-money screen and route small top-ups to support |
Deposit above the on-ramp limit | The balance is held on the account | Read the remaining on-ramp headroom from the customer's limits and show it before the deposit |
Withdrawal above the wallet balance | The off-ramp fails with an insufficient balance error | Cap the field at the withdrawable amount |
Cash-out ignores an open authorization | The off-ramp does not see card authorizations, so the account ends short at settlement | Subtract open holds in your ledger before showing the withdrawable amount |
When a stablecoin-backed card is the wrong choice
A stablecoin-backed card is the wrong choice when the customers are US residents who already hold dollars at the sponsor bank. A debit card on a deposit account is simpler: a conversion adds a step, a spread and a second set of limits. It is also the wrong shape when the card must be debit or prepaid and the issuer's card is credit secured by collateral, or when the neobank wants to pool customers' funds in one account, because Lumx requires every payer to be an onboarded customer.
For customers who earn in another currency, the Rain card top-up and cash-out guide covers that build, and Lumx vs Rain compares the two companies.
What the Lumx side of a US card program looks like
Lumx supplies the money legs of a stablecoin-backed card program, and the card issuer is signed separately, as in Mastercard's stablecoin settlement.
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 US neobank, each cardholder is a customer with a USD account and a wallet. The named virtual account takes the deposit, an autoconversion rule turns it into USDC or USDT, the issuer's card spends from that wallet, and the cash-out is an off-ramp. For the wider picture, see what stablecoin banking is.
The first move is a written question to the issuer: is the card debit, prepaid or credit, and where does it expose open authorizations? Then test the deposit, the conversion and the off-ramp in the sandbox, where POST /autoconversion-rules/simulate-deposit triggers the flow, before any real money moves.
Methodology and sources
The Lumx statements come from the docs read on November 1, 2026: Coverage, Accounts, Autoconversion rules, Exchange rates, Cut-off times, Transaction limits, Nested payments and RFI.
The Rain statements come from its public card-issuing and real-time funding pages, read the same day, and the federal rules from the CFR text at law.cornell.edu: 12 CFR 1005.6, 1005.18, 235.3, 235.5 and 235.7.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Wilhelm Gunkel on Unsplash.
How do you add debit cards to a neobank?
Pick a program model, sign a card issuing provider, and connect card events to your ledger. Then fund the balance and give customers a way to cash out. On Lumx, a stablecoin-backed program funds the cardholder's wallet through a USD named virtual account over ACH or FEDWIRE and cashes it out through an off-ramp.
Who issues the cards in a neobank card program?
A sponsor bank issues them under a card network membership, and a card provider usually bundles the BIN sponsor, the issuer-processor and program management in one contract. Lumx does not issue cards or approve purchases: it funds the wallet a stablecoin-backed card spends from and cashes out the unspent balance.
How do cards affect a neobank's revenue?
Cards add interchange, which the issuer shares with the program under the contract, and Regulation II limits it for issuers with $10 billion or more in assets. On Lumx, pricing is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, and no published plans. Those fees are a cost on the funding and cash-out legs.
How long does it take to add debit cards to a neobank?
It depends on the issuer, the sponsor bank and your own build. Rain's page claims 8-12 weeks to market and says some programs launched in under two weeks, both vendor claims. On Lumx, the API integration for the funding and cash-out legs takes 2 to 3 weeks to go-live.
How does a stablecoin-backed card get funded and cashed out?
The cardholder pays dollars to a USD account in their own name, the deposit converts to USDC or USDT in a wallet, and the card spends from it within a limit the cardholder approves. To cash out, the app starts an off-ramp to a registered destination. On Lumx, ACH has a 2:00 PM ET cut-off and FEDWIRE a 3:00 PM ET one.
