An embedded banking API with a stablecoin on-ramp is one integration that gives a neobank named accounts, conversion of deposits to a dollar stablecoin and payouts over local rails, with identity checks built in. The licence sits with whoever issues the account, so ask who holds it, and who runs each leg, before comparing features.
This guide is for a team choosing the account and money-movement layer. For the whole product, read how to build a neobank. For a regional ranking, see stablecoin infrastructure for Latin American neobanks. For a dollar balance that is not a deposit, see what stablecoin banking is.
Why one provider rarely covers the whole stack
A neobank asks a provider for five things: accounts in the customer's name, a way in from fiat to stablecoin, a way out, verification of every customer and, if the product has one, a card. Each provider type started with one of the five and has been reaching for its neighbours since.
Banking-as-a-service (BaaS) providers started with accounts, and some of them now sell stablecoin on-ramps and off-ramps as another payment rail next to ACH and wires. Stablecoin infrastructure APIs started with conversion and have added local accounts and cards. Wallet and embedded wallet SDKs started with keys and screens. Card issuers started with the card and have added on-ramps and compliance checks. That overlap is why a search for a banking-as-a-service stablecoin API and one for a stablecoin on-ramp with fiat bank accounts return the same pages, and why a feature list says little about who does the work.
The useful question is narrower: for each leg of a customer's money, which company holds the licence and which one executes it. On Lumx, one API covers accounts and the two ramps, plus wallets and verification, and a card issuer stays a separate part of the stack.
How do the four provider types compare for a neobank?
They differ less on features than on who stands behind each leg.
Four provider types compared on what a neobank buys from each, from public product and documentation pages read on November 19, 2026
Provider type | Fiat accounts | Stablecoin on-ramp | Rails | KYC and KYB | Who holds the licence | Who operates each leg |
Sponsor-bank BaaS (a bank selling its own API, or middleware connected to partner banks) | The core product: deposit accounts, pooled or per customer | A newer add-on at some providers, USDC in and out of the account | ACH, wires and real-time payments, with stablecoins as another rail where offered | The bank, or the middleware under the bank's program rules, with the neobank collecting the data | The bank. Middleware holds none | The bank holds the money and runs the rails. Middleware keeps its own ledger. The neobank owns the app |
Stablecoin infrastructure API | Named virtual accounts in a set of currencies, which varies by provider | The core product, fiat in and stablecoin out | Local rails per currency, plus stablecoin transfers | The provider, sometimes with reuse of a check the neobank already ran | The provider, its banking partners or both, depending on the market | Banking partners hold fiat and run rails. The provider converts and orchestrates, and custodies the wallet |
Wallet and embedded wallet SDK | Usually a separate module or a partner | Card or bank-transfer top-ups, often from a third party | Blockchain transfers, with fiat by add-on | The vendor or its partners, or the neobank | Varies. Some vendors sell their own licensed infrastructure | The SDK vendor handles keys and screens. Partners handle fiat |
Card issuer with stablecoin funding | None of its own, the card spends from a balance held elsewhere | An optional module at some issuers | Card networks, funded from a wallet or an account | The issuer checks cardholders, consumers or businesses | The issuer, under its card program | The issuer runs authorization and settlement. The balance comes from another provider |
No row is a ranking. Most neobanks end up combining two of them, or choose a stablecoin infrastructure API that already issues the accounts. The wallet row has its own comparison in wallet API vs SDK vs white-label.
On Lumx, the answer sits in the second row. A named virtual account (a local account number issued in the customer's own name) is issued by a banking partner, the conversion and the wallet are Lumx, and the card, if the product has one, is the issuer's.
Who holds the licence and who keeps the ledger
Start with the licence, because it decides what happens when something stops. With a bank that sells its own API, one company holds the deposits, keeps the ledger and answers to its regulator. Where middleware sits in between, a second company keeps a ledger that has to match the bank's balance, and a customer's claim runs through both.
US regulators have flagged the risk of that arrangement. On July 25, 2024, the Federal Reserve, the FDIC and the OCC issued a joint statement on third-party deposit arrangements reminding banks of the safety and compliance risks in them, and the risks to consumers. The statement says it sets no new expectations. Its questions still apply to the first row: who keeps the record of who owns what, and how often is it reconciled?
A stablecoin balance changes the question. It is not a deposit, so it sits in a wallet and not in an account at a bank, and the provider that custodies it needs its own answer on custody and segregation. The three places a neobank can hold customer funds are compared in where neobanks hold customer funds.
On Lumx, banking partners hold the funds and execute the fiat rails behind each account, and Lumx runs verification, the conversion and the wallets, and orchestrates the rails. The custodial wallets hold the assets with BitGo, and each customer's balance is segregated from other customers' and from Lumx's own. Lumx is not a bank, and the balance is stablecoin, not a deposit. Who operates a leg changes by market: Mexican SPEI (Mexico's interbank transfer system, run by Banxico) payments run through a partner licensed as an IFPE (Institución de Fondos de Pago Electrónico), under the partner's licence.
The account, the on-ramp and the wallet are one flow
The money runs in a loop. A payer sends money to the customer's account details. The deposit converts to a stablecoin and is credited to the customer's wallet. Later the customer sends money out, the wallet is debited, the stablecoin converts to local currency and a payout leaves over a local rail. The app shows one balance in dollars and a feed of events.
There are two ways to run the way in. A standing conversion rule on the account converts every deposit that arrives through its details, with no call per deposit, and suits a savings or salary account. A single on-ramp is created for one known amount, such as a checkout, and can settle at a locked rate. For the integration steps, read integrating a stablecoin on-ramp API or hand the on-ramp prompt to a coding agent.
Two details change the economics. A floating rate is a live reference with no lock, good for an estimate, and a locked rate fixes the conversion for a short window. The neobank earns by adding its own fee on top of the provider's, so the screen should show the amount received, not only the rate.
On Lumx, a customer is created with the currencies it needs, and an account is provisioned for each. BRL, MXN, EUR and GBP accounts activate right after the customer is approved, and a USD account takes up to one business day. A standing rule per account returns the deposit details to show for each rail, and a partner fee is the neobank's own charge, applied only when the request carries it. Webhooks report every status change.
Settlement by currency on Lumx, from the payment rail cut-off page of the docs, read November 19, 2026
Currency | Rail | Settlement |
BRL | Pix (Brazil's instant payment system, run by the Central Bank) | Every day, around the clock |
MXN | SPEI | Every day, around the clock |
GBP | Faster Payments (the UK's real-time bank transfer network) | Every day, up to 1 million pounds per payment |
EUR | SEPA | Routed by Lumx per payment: same day or next business day for large amounts after hours |
USD | ACH | 1 to 2 business days |
USD | FEDWIRE (the Federal Reserve's same-day wire system) | Same business day |
USD | SWIFT | 1 to 5 business days, with a UETR on every SWIFT payout and the MT103 on request |
The rails and their cut-off times are listed on the coverage page.
KYC, KYB and the one-customer-per-user rule
Whatever the provider type, someone verifies every customer before money moves. For an individual that is KYC (know your customer, the verification of an individual), and for a company KYB (know your business, the verification of a company and its owners). Ask whether the check is the provider's or yours, and what a customer sees when a document is missing. A hold that asks for a document before a transaction clears is an RFI (request for information), and the app needs a screen for it.
The second rule is structural. Each end user has to be a customer of their own, because a provider cannot screen a person it cannot see. Pooling several users behind one customer is what the docs call nesting, and it is the reason a neobank cannot run a single omnibus account for its whole base. What KYB is covers the business side.
On Lumx, each app user is one customer, with its own terms acceptance, KYC or KYB and status. An individual already verified on the neobank's own Sumsub account can be onboarded with a share token, which saves the document upload and the liveness check and still needs the questionnaire; companies always go through KYB. Lumx handles compliance and conversion inside the API, with identity checks through Sumsub and monitoring of blockchain addresses through Chainalysis.
Where wallets and cards fit
A wallet SDK puts keys on the user's side and a wallet API keeps them on the provider's. Both produce a stablecoin balance, and neither produces account details, so the accounts layer still has to come from the same provider or another one.
A card adds the issuer as a fourth party. A stablecoin card spends from a balance, so the question for the neobank is where that balance lives and how it is topped up and cashed out. On Lumx, the Rain card spends from the customer's Lumx wallet: the customer approves how much the card may spend, and only the value of each purchase moves at authorization. The top-up is a local-currency deposit that converts to stablecoin in the wallet, and cash-out is an off-ramp started through the API. Rain stays part of the neobank's own stack. The stablecoin card program guide covers the issuer side.
The order I would shortlist in
I recommend that a neobank start its shortlist from the leg it cannot build, which is nearly always the licence behind the account, and compare API quality only after that. Ask each provider who issues the account, who runs each rail and who answers when a payment is held. A clean API does nothing for a customer whose payout is stuck and nobody owns the answer.
When an embedded banking API with stablecoins is the wrong stack
It is the wrong stack when the product promise is insured deposits. A stablecoin balance is not a deposit, so a neobank that wants to say "your savings are insured" needs a bank account holder behind the balance, and a sponsor-bank program is the route.
It is also the wrong stack when customers will only ever hold one local currency and spend it at home. Conversion to a stablecoin then adds a leg and a quote that the product does not need. Lending is a third case: loans and credit lines need a bank partner that lends. And the customer base has to sit in countries the provider onboards, which each provider publishes as a list; check it before the integration, not after.
What this looks like on Lumx for a neobank
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 neobank, that means one customer per app user, with named virtual accounts in the currencies the user picked and a custodial wallet on the networks Lumx supports. On every rail with a named account, the recipient's bank statement shows the customer as the sender, and POBO and COBO let the neobank pay and collect for its customers in their own name without nesting. Lumx does not sell a white-label app: the neobank builds its own screens on the API, and the neobank prompt gives a coding agent the endpoints for onboarding, accounts, balance, add money and send money.
Methodology and sources
Provider types were compared from the public product and documentation pages of providers in each of the four types, read on November 19, 2026. Those pages are marketing and documentation, so the table says "varies" where a page did not say. The regulatory reference is the joint statement of July 25, 2024, read on the Federal Reserve's press release. Every Lumx capability comes from the Lumx documentation, read on November 19, 2026.
Verified on November 19, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Tran Mau Tri Tam ✪ on Unsplash.
Which embedded banking API with a stablecoin on-ramp works for neobanks?
It depends on which leg you cannot build. A sponsor-bank BaaS provider fits a neobank that needs insured deposit accounts, a stablecoin infrastructure API fits one that needs conversion and named accounts in several currencies, and a wallet SDK or card issuer covers the keys or the card. Most neobanks combine two. On Lumx, one API covers accounts and the two ramps, plus wallets and verification, and the card issuer stays separate.
Can a banking-as-a-service provider also offer a stablecoin on-ramp?
Some do. Sponsor-bank providers have started to add stablecoin on-ramps and off-ramps to their account platforms, so a customer can fund a balance in dollars and hold it as USDC. Coverage, currencies and countries vary, so ask what is live. On Lumx, the on-ramp is the core product: a deposit on a named account converts to stablecoin and lands in the customer's wallet.
Who holds the licence in an embedded banking program with stablecoins?
The company that issues the account holds the licence for it. With a bank API that is the bank, with middleware it is a partner bank behind the middleware, and with a stablecoin API it is the provider's banking partners, which differ by market. On Lumx, banking partners hold the funds and execute the fiat rails, Lumx is not a bank, and the balance is stablecoin, not a deposit.
Can a neobank give each customer a named account and a stablecoin balance together?
Yes, when the provider issues accounts in the customer's name and credits conversions to a wallet. The customer sees account details to receive money and one balance in dollars. Each customer has to be verified on its own. On Lumx, each user is one customer with a wallet and the accounts requested, and BRL, MXN, EUR and GBP accounts activate right after approval.
What does a neobank still have to build itself?
The app, the ledger that matches the provider's records, the pricing and the support flows for holds and rejections. The provider supplies the accounts and the conversion, with wallets and verification, not the product. On Lumx, the neobank builds its own screens on the API, since Lumx does not offer a white-label app.





