A US neobank launch checklist is a dated plan for taking a dollar account app live on a sponsor bank and vendors. Days 1 to 30 settle the regulatory route, the vendors and the scope. Days 31 to 60 build and test every money flow. Days 61 to 90 run a small pilot against criteria written in advance.
The 30, 60 and 90 split is a planning structure, not a vendor promise, and counsel decides which legal duties bind your product. This checklist adds the US legal clocks, read in the primary text, and treats the payout abroad as one workstream. The Latin American build is a different plan, in the Latin American neobank launch checklist.
Can you launch a US neobank in 90 days?
You can launch a pilot in 90 days if the route runs through a sponsor bank, the scope is one user type and one money loop, and vendors are chosen in the first month. A national launch, or a route that needs your own bank charter, does not fit.
The three phases, the gate that ends each one and the dependency that usually sets the pace.
Phase | Goal | Exit gate | Slowest dependency |
Days 1 to 30 | Route, vendors, scope decided | Counsel memo filed; every money flow has a named provider | Sponsor bank and vendor due diligence |
Days 31 to 60 | Every money flow built and tested | A deposit credits once; failed payouts have been run | Disclosures approved by counsel |
Days 61 to 90 | Pilot with real users | Go or no-go memo against written criteria | Partner sign-off before real money moves |
In this plan, the last column sets the date more than engineering speed does, because each partner reviews the app on its own calendar. A payout leg still undecided at the sponsor bank review sends the plan back to the day 30 memo.
On Lumx, the payout leg abroad and the USD funding account can be named in that memo in week one.
Days 1 to 30: choose the route, the vendors and the scope
Day 30 is decisions, not code. Name the compliance owner in week one, because the AML rule asks for a designated person.
Task | Owner | Done when |
Pick one user type, one state footprint, one money loop | Product lead | One-page scope signed off |
Write the regulatory route: sponsor bank, own registration, or both | Counsel | Memo names who holds customer funds |
Draw the money flows: in, held, out | Product, engineering | Every arrow has a named provider |
Vendor due diligence, sponsor bank included | Compliance owner | A file per vendor; AML program drafted with a named officer |
Scope the payout leg if the app sends dollars abroad | Product lead | Corridors, rails, caps per transfer decided |
Plan the vendor files from week one. The interagency guidance on third-party relationships, issued June 6, 2023, walks a bank through the life of a vendor relationship, from planning to termination. Read it as your sponsor bank's question list.
On Lumx, the app is onboarded as a business customer and discloses its activity. The docs class money services as high risk, which means Enhanced Due Diligence, and list unlicensed money services among the activities Lumx does not serve, so settle the route first.
Which vendors does a US neobank need?
A US neobank usually needs seven vendor categories, and the sponsor bank will ask who sits in each one. The table gives the decision per category and the question to expect.
Vendor categories, the decision to make in the first 30 days and what the sponsor bank is likely to ask.
Category | Decision to make | What the sponsor bank will ask |
Sponsor bank | One bank or several, and who holds customer funds | Your AML program, vendor files and growth plan |
Ledger or BaaS layer | Build the ledger or buy it | Who is the system of record for balances |
KYC | Provider, and which checks run at onboarding | What happens on a rejection or a request for more documents |
Card issuer or processor | In the pilot or the next release | Who carries card disputes (separate workstream) |
ACH and wire processor | Which provider moves dollars in and out | Return handling and cut-off times |
Transaction monitoring | Provider and alert escalation path | Who reviews alerts and how fast |
Payout provider | Corridors, rails, per-transfer caps | Who touches customer money abroad and how it is screened |
Costs sit in the same places, and this post quotes none: get each figure in writing.
On Lumx, two rows are covered: the payout provider and the USD funding account the sender deposits into. The other five stay with vendors the app chooses.
Which US legal duties sit inside the 90 days?
Three federal texts set clocks a launch plan has to respect, and several more are conditional. The first three rows were read in their primary text on November 1, 2026. The rows marked confirm with counsel were not read here.
US duties by trigger, what the text sets and when it starts to matter.
Duty | What the text sets | When it matters | Read more |
MSB registration | 31 CFR 1022.380(a)(1) requires each MSB to register with FinCEN, state-licensed or not; (b)(3) sets the form due by the end of 180 days after establishment | If counsel concludes the business is an MSB (money services business, the FinCEN registration category) | |
AML program | 31 CFR 1022.210(d) requires written controls, a designated officer, staff training and an independent review; (e) sets the end of 90 days after establishment | Before the pilot, if the business is an MSB | |
Error resolution on consumer accounts | 12 CFR 1005.11(b)(1)(i): notice within 60 days of the statement; (c): 10 business days to decide, or 45 days with a provisional credit | If the product holds consumer accounts under Regulation E | Counsel |
Remittance transfers | 12 CFR 1005.30 to 1005.36: disclosure plus cancellation and error rights for transfers abroad, as read in the linked post | If the app sends dollars abroad for consumers | |
Sanctions screening and customer identification | OFAC screening and customer identification normally run through the sponsor bank's program. Confirm with counsel | From the first onboarded customer | Counsel |
Consumer protection (CFPB, UDAAP) | Unfair, deceptive or abusive practices rules apply to terms and marketing copy. Confirm with counsel | When disclosures and fee copy are written | Counsel |
Payment stablecoins | The GENIUS Act framework | Only if the app issues or holds payment stablecoins itself |
For an MSB, the program deadline is the same clock as the launch plan. Which date counts as established, and whether the sponsor bank's registration covers the app, are for counsel. State money transmission rules differ by state, were not read here and are the first item counsel checks.
Lumx takes none of these over. It runs KYC (know your customer, the verification of an individual) on each sender through Sumsub and screens the stablecoin leg with Chainalysis, and the app's own AML program stays with the app.
Days 31 to 60: build and test every money flow
Task | Owner | Done when |
Onboarding with KYC | Engineering | Approval, rejection and RFI paths render |
Funding screen and deposit crediting | Engineering | A deposit credits once, even when the webhook arrives twice |
Ledger with pending and available balances | Engineering | Daily reconciliation runs clean |
Payout: quote, confirm, execute, track | Engineering | Completed payouts, failed ones and refunds have been run |
Terms and disclosures | Counsel | Approved, Reg E items included |
AML program and tooling | Compliance owner | Written program; a test alert reaches a person |
Cards and wallets | Product lead | Decision recorded: in the pilot or the next release |
Cards are a separate workstream with their own vendors, and folding them into this plan blocks both. The debit cards for a US neobank post covers that build.
On Lumx, the sender is an individual customer with a USD account in the sender's own name, opened by the app, and the app shows the account details for the deposit. USD funding runs over ACH, credit (push) only with no debit (2:00 PM ET cut-off, 1 to 2 business days) or FEDWIRE (the Federal Reserve's same-day wire system, 3:00 PM ET cut-off, same business day), per the cut-off table read November 1, 2026. A deposit converts through an on-ramp created in advance or a standing autoconversion rule, and without either the dollars stay in the account. onramp.success tells the app the wallet is funded. The USD account is a named virtual account in the sender's own name, described on the named virtual accounts page, and it can take up to one business day to activate.
Lumx puts an API integration at 2 to 3 weeks to go-live, an estimate and not a commitment.
Days 61 to 90: pilot against written launch criteria
Open the doors only when every criterion is met, and write them before day 61.
Task | Owner | Done when |
Employee test | Everyone | One real deposit and payout per employee, receipts matching |
Pilot cohort | Product lead | Small invited group onboarded, sized with the sponsor bank |
Weekly metrics review | Product lead | Activation, time to first deposit, payout success and tickets per 100 users reviewed weekly |
Incident drill | Operations | Failed payout and stuck deposit resolved on time |
AML review of pilot activity | Compliance owner | Alerts reviewed, nothing open past a week |
Launch decision | Product, compliance | Go or no-go memo per criterion |
The go-live checklist, each item a yes or a no:
The regulatory route is confirmed in writing and the partner agreements are signed.
The AML program is approved internally, with a named owner.
Employees have run a deposit, a payout, a failure and a refund in production.
Webhook signatures are verified and every money-moving call carries an idempotency key.
Ledger, bank statements and wallet balances reconcile every day.
Terms, fee schedule and disclosures are live in the app.
Support has playbooks and an escalation contact at each vendor.
Per-customer limits are set and shown in the app.
On Lumx, limits are set per customer and per transaction type, and they apply to every customer. A standard KYC customer starts at $7,500 per transaction and $15,000 per day and per month, and a standard KYB (know your business, the verification of a company and its owners) customer at $50,000 and $100,000, per the limits page read November 1, 2026, and these defaults may change. Lumx targets 1 business day for a standard KYC review, and an RFI (request for information, a compliance hold) resets the clock on resubmission. The sandbox simulate-deposit call returns 404 in production, so the employee test uses real money. Payout success reads from the offramp.success and offramp.failed webhooks.
Why the payout provider belongs in week one
I recommend opening the payout provider conversation in week one, in the same room as the sponsor bank, and not after the app is built. A sponsor bank reviews which counterparties touch customer money, and a payout leg still undecided at that review turns one approval into two. I would also put the corridor list and a per-transfer cap into the day 30 memo, because a cap added in month three changes screens already tested.
Each destination has its own rail, cut-offs and limits. The Brazil payout guide and the payout limits and cut-offs by rail cover the detail, and the KYB onboarding flow covers the business review.
On Lumx, KYC through Sumsub, stablecoin-leg monitoring through Chainalysis and the published cut-off table are the material to bring to that conversation, and the app keeps its own AML program.
What Lumx does not replace in a US neobank launch
Lumx is not a sponsor bank, not a BaaS provider and not a way to hold US customer deposits. A US neobank still needs its own sponsor bank and its own US money transmission and KYC program. The Lumx step is only the remittance leg.
Each sender is its own customer with its own wallet, because the nested payments page prohibits pooled funds that belong to non-onboarded parties, and the app opens each account in its own user's name.
The payout leg abroad 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.
The sender funds a USD account by ACH or FEDWIRE. The app registers the recipient as a destination under the sender, with the relationship set to RELATIVE or FRIEND, and waits for destinations.approved. At confirm it requests a locked rate, shows finalTargetAmount and sends the off-ramp with the rate ID before expiresAt. Pix (Brazil's instant payment system) and SPEI (Mexico's interbank system) pay out instantly, 24/7/365. Bre-B (Colombia's instant payment system) is also instant, with a regulatory cap of 1,000 UVB per transaction. PSE (Colombia's online bank-transfer network) is collection only. Lumx deducts no fee from the amount that reaches the recipient on Pix, SPEI or Bre-B. The USD to USDC page and the USDC to MXN page show the conversion legs, the global payments page shows how the pieces compose and the coverage page lists rails.
A transfer can be held for an RFI, so the app should not promise a delivery time it cannot keep. Check the supported countries list before a corridor enters the day 30 memo.
Methodology and sources
31 CFR 1022.380 and 1022.210 were read on November 1, 2026 in the Cornell LII text, as were 12 CFR 1005.11 in the Cornell text of Regulation E and the Federal Reserve's press release of June 6, 2023. Remittance Transfer Rule provisions come from the linked post. OFAC, CFPB, state money transmission statutes and sponsor bank agreements were not read.
Lumx statements come from docs.lumx.io pages on remittances, accounts, cut-off times, identity verification, transaction limits, prohibited activities and nested payments, read on November 1, 2026.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Isis França on Unsplash.
What should a US neobank launch checklist include?
It should include a written regulatory route, a vendor list with due diligence on each, an AML program with a named owner, money flows tested with their failure states, disclosures approved by counsel, written launch criteria and weekly pilot metrics. On Lumx, the payout abroad is one workstream: a funding account, a locked quote and webhooks for each status.
Can you launch a US neobank in 90 days?
You can launch a pilot in 90 days when the app runs on a sponsor bank, the scope is one user type and one money loop, and vendors are chosen in the first month. The Lumx API integration is estimated at 2 to 3 weeks to go-live.
Does a US neobank need its own bank charter?
A pilot usually runs on a sponsor bank's charter, but the sponsor bank still asks for the app's own AML program and vendor files. Whether FinCEN registration applies is a question for counsel. Lumx is not a sponsor bank and does not hold US customer deposits, so that relationship stays with the app.
Which US rules set deadlines while a neobank launches?
For a business that is a money services business, 31 CFR 1022.210 asks for the AML program by the end of the 90 days after establishment, and 31 CFR 1022.380 sets registration by the end of 180 days. Regulation E gives 10 business days to decide an error notice on consumer accounts. The app keeps its own program.
