A sponsor bank model is an arrangement in which a chartered US bank holds the accounts and the funds and answers to its own regulators, while a fintech builds and runs the customer product on top. The company launches on the bank's charter instead of its own, and the bank stays accountable for what the program does.
How does a sponsor bank model work?
The joint statement of the Federal Reserve, the FDIC and the OCC, dated July 25, 2024 and announced by the Fed, describes the usual shape. A third party, rather than the bank, typically markets the deposit product and gives the end user access to it. The bank may also rely on third parties for the system of record and for payments. The statement says using them does not reduce the bank's responsibility to follow the law.
Who holds what in a sponsor bank program (industry roles, drawn from the July 25, 2024 joint statement and the author's reading, read November 6, 2026).
Layer | Sponsor bank | Fintech running the program |
Charter and deposit accounts | Holds both | Distributes the product |
Customer checks and monitoring | Stays responsible, even when the fintech does the work | Often does the work under contract |
System of record | Needs access to it | Often keeps it, or a subcontractor does |
Customer experience and support | Reviews it and can require changes | Owns the app, the marketing and first-line support |
Exit | Can end the program; the contract can set how accounts and data move | Needs a transfer plan before launch |
The sponsor bank is the chartered institution: it holds the accounts and answers to its regulators. The program manager runs the customer-facing program on the bank's behalf, from onboarding to support. A BaaS platform is, in common usage, middleware that connects several fintechs to banks; the joint statement calls that layer a middleware provider. One company can play two roles, but only the bank holds the charter.
Lumx works this way in the United States, on the program side: the USD account a customer receives is a virtual account issued by the sponsor bank, Lumx's banking partner. Per the accounts page of docs.lumx.io, read November 6, 2026, the banking partners hold the funds and run the underlying rails.
Sponsor bank, state licenses or a charter: how do the routes compare?
The US launch routes compared (FinCEN and CSBS pages read November 6, 2026).
Route | Who holds the authority | What it gives you | What it leaves to you |
Sponsor bank | The bank | Custody and deposit-taking under the bank's charter | Running a program the bank approves and keeps reviewing. Whether you are yourself a money transmitter still turns on who accepts and transmits the funds, and it can still need state licenses |
State money transmitter licenses | You, state by state | Permission to transmit money under each state's law | One application per state, with its own requirements |
FinCEN MSB registration | You, as a federal filing | A registration, not an authorization: Form 107 within 180 days of establishment, renewed every two years | The state licenses and the controls the registration assumes |
Own bank charter | You, as the bank | Deposits and the accounts themselves | The full supervisory load of a bank |
The state layer is large. The Conference of State Bank Supervisors (CSBS) says thirty-one states have enacted its model Money Transmission Modernization Act in full or in part, as of September 2026. The sponsor route moves custody and deposit-taking onto the bank's charter, so a company can launch without building that state layer first.
What it does not do is settle the licensing question. Whether the program manager is itself a money transmitter turns on who accepts and transmits the funds, and it can still need state licenses. We think the bank's risk appetite will set the edges of your product, because the bank answers to its regulators for everything the program does.
Lumx has chosen the sponsor route for its US start. The US entity is Lumx US OP LLC, registered with FinCEN as an MSB (money services business, the FinCEN registration category). Per its public terms, Lumx US OP LLC does not custody funds or perform money transmission; its payment providers do.
What registration and state licenses still add
A bank in the middle does not remove the definition question. FinCEN's rule at 31 CFR 1010.100(ff)(5) defines money transmission as the acceptance of currency, funds or other value that substitutes for currency from one person and its transmission to another location or person by any means. "Any means" includes transmission through a financial institution, and the answer depends on facts and circumstances.
FinCEN guidance FIN-2019-G001, issued May 9, 2019, applies that definition to convertible virtual currency. For a stablecoin company the point is that the asset does not matter: accepting dollars and transmitting a stablecoin is acceptance and transmission, and the guidance treats a person that does it as a money transmitter unless an exemption applies. A USD-to-USDC conversion step adds facts for counsel to weigh, and a bank holding the dollar leg does not remove them. On Lumx, that step is the autoconversion described below, and the payment providers hold custody and do the transmission, per its public terms.
Registration is a filing; the licenses are the permission, granted by each state. Whether a program manager needs its own (license vs partner) turns on who accepts and transmits the funds and each state's exemptions: a question for counsel.
The GENIUS Act regulates who may issue a payment stablecoin, not the company that moves it. Abroad, the FATF calls that company a virtual asset service provider.
What the bank still owns, and what stays with you
The bank cannot hand its legal duties to the program. The joint statement says that where a third party performs customer identification, sanctions screening or suspicious activity monitoring, the bank remains responsible for any failure. Payment disputes stay with the bank too, within the Regulation E timeframes.
For the fintech that means oversight, not relief: the bank audits you because it carries the exposure. What stays with you is the paper trail: who onboarded each customer, who watched each transaction, and whether the contract says you hand all of it over when the bank asks.
Lumx draws its own line. Per its nested payments page, read November 6, 2026, every transaction must tie to an onboarded customer acting for itself, so a platform that pays or collects for its clients onboards each of them. The reasoning is in named virtual accounts vs pooled accounts.
The risks inside the arrangement
The joint statement lists where these programs go wrong. Three examples matter most to a payments company.
A bank may lack access to the system of record that a third party keeps. The statement says this can impair its ability to determine its deposit obligations and delay end users' access to their funds.
A third party can grow to a large share of the bank's deposits or revenue, and the bank may then be reluctant to terminate it, so your program can depend on one bank's liquidity decisions.
End users can be confused about deposit insurance. FDIC insurance protects against the failure of an insured bank, not of the nonbank behind the product. Pass-through coverage needs conditions the program must meet (12 CFR 330.5 and 330.7).
What does a customer see when the bank freezes accounts? A balance that does not move. Payouts sit in pending, the app has nothing to show, and support has no answer, because the money is at the bank and the records may be in your database. We cite no named failed program: the joint statement is our primary source for how these programs fail.
On Lumx, a customer's account status changes arrive as webhooks, including one when the account becomes active and one when the review asks for more information. Your system of record does not depend on someone reading a bank portal.
How much does a sponsor bank program cost?
We found no public standard, and the joint statement sets no fees. In our reading, four contract terms drive the cost: fees, minimums, the revenue share the bank takes, and any reserve it requires you to hold. Ask for all four in writing.
Lumx does not publish plans. Its pricing model is a monthly platform fee plus usage-based per-transaction fees, with transparent FX on locked quotes and no pre-funding. The standard agreement has a monthly minimum, with a ramp-up period that waives it in the first months.
What to ask a sponsor bank before you sign
Each question maps to a risk in the joint statement. Ask for each answer in the contract text. The June 2023 interagency guidance (FIL-23-029) treats termination as one of five stages of managing a third-party relationship, so a bank should already have an answer on exit.
Six questions for a sponsor bank, drawn from the July 25, 2024 joint statement (read November 6, 2026).
Question | Why it matters |
Who keeps the system of record, and can the bank read it in real time? | Without records the bank cannot determine its deposit obligations |
What happens to funds and data if the bank ends the program or you fail? | The statement points to contract terms that move accounts, data or activities to another entity |
Who performs each control, and who gets audited? | The bank stays responsible even when you do the work |
How much of the bank's deposit base sits in programs like yours? | Concentration makes the bank reluctant to act |
Who answers complaints and error claims, and within what time? | Regulation E sets deadlines that stay with the bank |
Which customer types, countries or payment flows does the bank accept? | The bank's own risk appetite sets the edges of the program |
I would ask for the wind-down clause before I asked for the price. Pricing can move at renewal, but the clause on who moves the accounts, the data and the customer funds when the bank ends the program decides whether an exit is orderly or a freeze. I would also insist on reading it in the contract text rather than hearing it on a call.
On Lumx, the equivalent gate is onboarding. A customer goes through KYB (know your business, the verification of a company and its owners) or KYC (know your customer, the verification of an individual) before any account is provisioned, and an account can pause in an RFI (request for information, a compliance hold that asks for a document before a transaction clears) until the customer answers.
When a sponsor bank is the wrong route
Three situations point away from the sponsor route alone. The first is a product that pools customer money to pay out for people who are not onboarded; a bank does not change who transmits the funds. The second is a plan that depends on one bank for years; plan state licenses as the second leg, the order Lumx follows. The third is marketing that promises deposit insurance the records cannot support.
For a dollar account for users in Latin America, the product-side decisions are in launching a dollar account app. A virtual asset firm that needs its own bank account faces a different question, covered in bank accounts for virtual asset firms. The same trade-off in Latin America is in licensing routes in Latin America.
What this looks like on a USD account with 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.
For a US launch, the sponsor bank sits behind the USD side. You request USD in the accounts array when you create the customer. The account waits until the customer is approved, then moves through requested and provisioning to active. USD is the slowest currency to activate: the target is up to 1 business day after approval, because the banking partner reviews the account first. The account active event tells you when it can receive funds.
One USD account takes ACH, FEDWIRE (the Federal Reserve's same-day wire system) and SWIFT. A payment that rides SWIFT through correspondent banks passes through hands you cannot see, and each one takes a fee. Here an autoconversion rule on the account returns the bank details for each rail up front, and every matched deposit converts to USDC or USDT in the customer's custodial wallet.
The account is a named virtual account, issued in the customer's own name; the product page shows it across currencies, and the supported countries page lists where Lumx onboards. The bank's name and terms belong to the contract you sign with Lumx.
Methodology and sources
All sources were read on November 6, 2026 and are linked where used: the joint statement as the PDF, not only the press release, the FDIC guidance, 31 CFR 1010.100(ff)(5), FIN-2019-G001, the FinCEN registration page and the CSBS model law page.
Not researched: state-by-state exemptions, sponsor bank pricing and any named program failure. The Lumx statements come from Accounts, Coverage and Nested payments, all on docs.lumx.io.
Verified on November 6, 2026. Operational context, not legal, tax, or investment advice. The July 25, 2024 joint statement on bank third-party deposit arrangements checked against federalreserve.gov on November 6, 2026. 31 CFR 1010.100(ff)(5) checked against law.cornell.edu on November 6, 2026. FinCEN guidance FIN-2019-G001 checked against fincen.gov on November 6, 2026.
Cover photo: Sergej Kaldesić on Unsplash.
What is a sponsor bank model?
A sponsor bank model is an arrangement in which a chartered US bank holds the accounts and funds and stays answerable to its regulators, while a fintech builds and runs the customer product. The company launches on the bank's charter, not its own. Lumx launches in the United States this way: a customer's USD account is issued by a banking partner that holds the funds, and Lumx orchestrates the onboarding and the conversion and routes the payouts around it. Per its public terms, custody and money transmission sit with its payment providers.
Does a sponsor bank replace state money transmitter licenses?
Not automatically. FinCEN's definition reaches the acceptance and transmission of funds by any means, including through a bank, so a bank in the middle does not settle who needs a license; counsel decides that on the facts. Lumx launches with a sponsor bank, and Lumx US OP LLC is registered with FinCEN as an MSB; its payment providers hold custody and do the money transmission, per its public terms.
Are balances held through a sponsor bank FDIC insured?
Only if the pass-through conditions are met, and only against the failure of the bank, not of the fintech. The funds must sit at an insured bank, the records must disclose a basis such as a custodial relationship, and the owners and the relationship must be genuine and ascertainable. On Lumx the USD account is issued by a banking partner that holds the funds, so ask for the account records and the bank's written position before telling users anything about insurance.
How much does a sponsor bank program cost?
There is no public standard. The cost comes from the contract: fees, minimums, revenue share and any required reserve. On Lumx the pricing model is a monthly platform fee plus usage-based per-transaction fees, with no published plans, and a monthly minimum that a ramp-up period waives at first.
How long does it take to launch with a sponsor bank?
We found no published standard timeline. The bank's review sets the pace, so ask for each gate in writing, with an owner and a duration. On Lumx the documented time is narrower: once a customer is approved, a USD account takes up to 1 business day to become active, because the banking partner reviews it first.
