Neobank launch checklist: a 30, 60, and 90 day plan for an MVP

A neobank MVP can reach pilot users in about 90 days when it launches on partners: 30 days to pick the regulatory path, vendors, and scope, 30 days to build and test, and 30 days to run a small pilot against written launch criteria. BlindPay covers the money movement workstream in that plan: accounts in, payouts out, FX, and KYC through one integration.

The calendar only holds if the regulatory route doesn't need your own license first. This checklist gives each phase a task table, then the readiness checks and metrics that decide whether you open the doors. It closes the series on how to build a neobank.

Key takeaways

• Ninety days buys a pilot, not a national launch. Scope one user type, one country, one money loop.
• Days 1 to 30 decide everything slow: regulatory path, vendors, compliance owner, scope.
• Money movement is one workstream. Cards and wallets are separate workstreams with their own providers.
• Write launch criteria before day 61 and launch against them.
• Track four numbers weekly from user one: activation, time to first deposit, payout success, tickets per 100 users.

What does it take to launch a neobank MVP in 90 days?

A narrow scope, a partner-based regulatory path, vendors chosen in month one, and launch criteria written in advance.

Three things change the timeline more than engineering speed:

1. The licensing route. Launching through a regulated partner fits in 90 days. Your own charter or payment license doesn't. See do you need a banking license for a neobank.
2. Vendor approval. Partners review you before you go live, and their timelines are theirs. Start every vendor conversation in month one.
3. Scope creep. Every extra country adds rules, rails, and support. Every extra feature adds a workstream.

Who is on the team, and who owns what?

Five roles, sometimes fewer people.

What happens in days 1 to 30?

Decisions. By day 30 you should know who you serve, under whose license, with which vendors.

Vendor due diligence matters even with a small team. US banking regulators' interagency guidance on third-party relationships explains how banks manage fintech partners, which tells you what your partner will ask you for. For US money transmitters, check registration on the FinCEN MSB registrant search. Comparing providers by job is covered in the best stablecoin infrastructure for neobanks.

What happens in days 31 to 60?

Build and test every money flow, including the ugly ones.

The payments integration is a handful of API calls in a fixed order. The neobank API quickstart maps each screen to its call, and coding agents can write much of it under the guardrails in build a neobank with AI agents.

If your product holds consumer accounts covered by Regulation E, error resolution has deadlines: 12 CFR 1005.11 covers notices received within 60 days of a periodic statement. Ask counsel whether it applies, then write the support process before the pilot.

What happens in days 61 to 90?

Pilot with real users, fix what breaks, and launch only when the criteria are met.

What is on the go-live readiness checklist?

• Regulatory path confirmed in writing, partner agreements signed.
• Compliance program approved internally, with a named owner.
• Every money flow tested end to end in production by employees: deposit, balance, payout, failure, refund.
• Webhook signatures verified, idempotency on every money-moving call.
• Reconciliation between your ledger, bank statements, and wallet balances runs daily.
• Terms, fee schedule, and balance disclosures live in the app.
• Support playbooks for the top ten tickets, plus escalation contacts at every vendor.
• Limits per user set and explained in the app.

Which metrics matter in the first 90 days?

Four operating numbers, measured weekly from the first pilot user.

Add KYC approval rate and quote expiry rate if you have the data. Illustrative example: 80 pilot users verify, 52 fund, so activation is 65%. If median time to first deposit is four days, the account details screen or the payer instructions need work before you add a single feature.

What are the budget lines?

Plan for each line even if the amount is small: provider plans and per-transaction fees, KYC checks, legal and licensing work, compliance tooling, cloud and app store costs, support staffing, and a buffer for audits. On BlindPay, plans are listed on the pricing page and per-transaction fees appear in each quote before you execute.

What are the common mistakes?

• Starting the build before the regulatory path is decided.
• Launching three countries in the pilot.
• Folding cards into the money movement workstream and blocking both.
• Testing only completed payouts.
• No written launch criteria, so the date wins every argument.
• Nobody owns reconciliation until a balance is wrong.

How BlindPay fits

BlindPay is the money movement and compliance layer in this plan. One integration covers KYC and KYB, US virtual accounts in the customer's own name with routing and account numbers, payins over ACH, wire, Pix, SPEI, and PSE, and payouts over ACH, wire, RTP, Pix, SPEI, ACH Colombia, Transfers 3.0, SEPA, Faster Payments, and SWIFT (POBO/COBO). Quotes lock the rate and fees before execution.

Development instances let the team run every flow in month two, with KYC auto-approved and test amounts that force failed and refunded payouts. BlindPay is registered with FinCEN as a Money Services Business, and for payouts from customer-controlled wallets it is non-custodial: you authorize the exact amount and BlindPay executes that one transaction. Cards and consumer wallets stay with the providers you pick for those workstreams.

What to do next

Write your one-page scope and your launch criteria this week. Then open a development instance and run one deposit and one payout using the sandbox vs production guide to see what changes at go-live.