Library · Neobanks
Launch neobank guide
A twelve-week planning scaffold — not a promise — from structure through authorisation evidence, safeguarding and sponsor sequencing. Bank account first, rails second, FX third, compliance throughout. Every outcome stays with licensed providers.
Why founders still plan in weeks
A neobank launch is a chain of reviewers: supervisor, safeguarding bank, BaaS sponsor, BIN sponsor and processor. Each reviewer asks for the same underlying evidence in a slightly different shape. The fastest launches are the ones that build the evidence once and present it consistently across all of them.
The twelve-week frame is a planning structure. The point of the frame is not the deadline; it is the order of operations. Skip steps and the file goes back to the start of someone else's queue.
The twelve-week scaffold
Weeks 1–2
Structure
Incorporate in the target jurisdiction; lock down ultimate beneficial ownership, board composition and senior-manager roles. Decide on licence track (EMI, PI, MSB, agent-of, BaaS) based on customer mix, geography and capital available. Draft programme of operations and three-year projections in the shape the supervisor expects.
Deliverables
- Holding-company and operating-company structure with UBO chart to natural persons.
- Senior-manager / fit-and-proper plan for at least the CEO, CFO, MLRO / nominated officer and head of operations.
- Licence-track decision memo with the rationale for the chosen authorisation route.
Weeks 3–6
Authorisation evidence
Build the authorisation pack alongside the safeguarding-bank narrative. Draft customer flow-of-funds diagrams, safeguarding methodology, AML / KYC operating model, customer risk assessment, sanctions screening procedure and transaction monitoring framework. The pack is built once and reused across supervisor, safeguarding bank, BaaS sponsor and BIN sponsor with provider-specific cover notes.
Deliverables
- Programme of operations and projections aligned with the licence-track decision.
- Customer flow-of-funds diagrams (top-up, payment-out, refund, dispute, FX where applicable).
- Safeguarding methodology, AML / CFT policy, customer risk assessment and screening procedure.
Weeks 7–9
Safeguarding bank and BaaS partner readiness
Approach safeguarding-bank and BaaS-sponsor reviewers with the same evidence pack and provider-specific cover notes. Run BIN-sponsor and processor selection in parallel where relevant. Document material outsourcing contracts and operational-resilience evidence. Track every reviewer question and update the pack so the next reviewer does not re-ask the same question.
Deliverables
- DDQ-aligned cover notes for safeguarding bank, BaaS sponsor and BIN sponsor.
- Outsourcing register and material third-party contracts (KYC, screening, processor, ledger).
- Operational resilience document set: incident plan, BCP, key-personnel matrix.
Weeks 10–12
Go-live readiness
Complete BIN certification, end-to-end testing across ledger, processor and safeguarding bank, and finalise customer-protection collateral. Run a controlled pilot with a small cohort, monitor reconciliations daily, and rehearse the incident response. The go-live is followed by an early-life provider review where reviewers want to see the model running against the pack.
Deliverables
- End-to-end test evidence across ledger, processor, BIN sponsor and safeguarding bank.
- Customer-protection collateral aligned with the safeguarding methodology.
- Reconciliation and incident-rehearsal evidence ready for early-life provider review.
Critical decisions before week 1
- Jurisdiction and licence track: EMI vs PI vs MSB vs agent-of, and where to incorporate.
- Build vs partner: BaaS sponsor route vs direct licence with own safeguarding banks.
- Card programme: direct BIN sponsor relationship vs sponsor-EMI bundled programme.
- Customer corridors and currencies in scope at launch vs deferred to phase 2.
- Ledger architecture: third-party core vs internal ledger with reconciliation to processor and bank.
- Operational hubs: where the MLRO / nominated officer, compliance and operations functions sit.
Risks that delay launch
- Compressing weeks 3–6 to chase a launch date; reviewers see the gaps before customers do.
- Approaching safeguarding banks before authorisation perimeter is settled.
- Treating BaaS sponsor approval as a substitute for safeguarding-bank readiness.
- Volume projections that do not reconcile with the marketing channels actually planned.
- Outsourcing register missing material third parties; reviewers ask and the file pauses.
FAQ
Is the twelve-week frame a promise?
No. It is a planning scaffold so founders do not skip evidence order. Real timelines depend on jurisdiction, licence track, capital and how complete the file is on day one. The Founder Advisory Seat is about judgement on serious calls and DDQs — not a countdown vendor.
Does VeriRail apply for the licence on my behalf?
No. VeriRail does not file licences. Applications stay with you and your counsel. In the seat we align programme of operations, flow of funds, projections and AML evidence so what you file matches what you will defend to banks and sponsors.
What if I want to go live as a BaaS-sponsored neobank instead of getting my own licence?
The same readiness work applies, with the BaaS sponsor as the principal reviewer instead of the regulator. Sponsors typically ask for the programme of operations, AML model, projections, escalation matrix and operational resilience evidence, plus their own commercial onboarding.
When should I start the safeguarding-bank conversation?
Usually once the authorisation perimeter is settled and the customer flow-of-funds is drawn end-to-end. Earlier conversations are possible but tend to circle back to the same documents, costing time on both sides. Readiness work sequences the conversations to minimise re-work.
Does this guide cover crypto-adjacent neobanks?
Yes at the structure and evidence level. Crypto-adjacent neobanks layer the digital asset readiness work on top of the neobank readiness path. See the Web3 & Crypto solution and the VARA / MiCA / CASP readiness pages for the additional reviewer themes.
How does this fit with the Provider Readiness Library?
The Library is the framing; the Advisory Seat is the work. This page is a long read on sequencing. Pair it with the MSB Banking Guide for safeguarding files and the licensing guide for capital/timeline context — then Apply when you want operator judgement beside you.
Related pages
Next step
Apply for a Fit Call when you want the Founder Advisory Seat to map this scaffold to your actual file — account-route readiness, DDQ / RFI answers and serious provider calls. No guaranteed approvals; every decision stays with licensed institutions.
Apply for a Fit CallVeriRail is a trading name of MAN IT BUSINESS SOLUTIONS FZCO. VeriRail gives MSB founders an external operator-advisory seat through provider judgement — flow of funds, account-route readiness, DDQ and RFI answers, serious provider calls, closures and sequencing. Bank account first, rails second, FX third, compliance throughout. VeriRail is not a bank-account broker, success-fee introducer, software platform, legal advisor, regulated financial service provider, or guaranteed approval service. VeriRail is not a bank, payment service provider, EMI, MSB, custodian, law firm or regulated financial institution. VeriRail does not provide legal advice, hold client funds or guarantee approvals, account opening or rail access. Licensed institutions provide all financial services; every decision remains theirs and subject to due diligence.