--- title: "How to build a neobank in 2026: a 10-step roadmap with BlindPay" seoTitle: "How to build a neobank in 2026: a 10-step roadmap" description: "How to create a neobank in 2026: pick a niche, a regulatory path and partners, then add accounts, KYC, deposits, payouts and cards. 10 steps with BlindPay." date: "2026-10-03" updated: "2026-10-03" category: "payments" author: "BlindPay Team" howto: name: "How to build a neobank in 10 steps" steps: - name: "Pick a market and a niche" text: "Choose one customer group and one money problem, for example freelancers in Brazil who get paid in US dollars. Write down the first three things they need to do with money." - name: "Choose a regulatory path" text: "Decide between your own license, a sponsor or partner bank, a payment or e-money license, or embedding regulated providers. Get legal advice in every market you serve." - name: "Select partners" text: "Pick the providers for accounts, money movement, compliance, cards, and your ledger. Check what each one is licensed for and what stays with you." - name: "Give customers accounts" text: "Issue account details customers can share, such as US virtual accounts with their own routing and account numbers." - name: "Build onboarding and KYC" text: "Collect identity data, run KYC or KYB and sanctions checks, and set tiered limits before any money moves." - name: "Build money in" text: "Accept bank deposits, convert them as needed, and credit the customer's balance in your ledger when the deposit settles." - name: "Build money out" text: "Let customers send money to bank accounts over local rails with a quote that shows the rate, fees, and arrival time before they confirm." - name: "Add cards and extras" text: "Add a card program through a card issuing provider, plus features like savings or bill pay once the core flows work." - name: "Launch a pilot" text: "Open to a small group, watch deposits, payouts, failures, and support tickets daily, and fix what breaks." - name: "Iterate" text: "Add corridors, rails, and features based on what customers actually use, and review compliance controls as volume grows." faq: - q: "What is a neobank?" a: "A neobank is a financial app that offers accounts, payments, and often cards without its own branch network. Most neobanks do not hold a banking charter. They work with a licensed partner bank or with regulated providers that hold the accounts and move the money, while the neobank owns the product, the customer relationship, and the app experience." - q: "Can you start a neobank without a banking license?" a: "Yes, most neobanks launch without their own banking license. They partner with a licensed bank or use regulated providers for accounts, payments, and compliance. You still carry your own obligations, which can include money transmission registration or licensing depending on what you do and where. This is educational content, not legal advice, so confirm your path with counsel." - q: "How long does it take to build a neobank?" a: "A focused MVP built on existing providers can take a few months, while a neobank with its own charter takes years. The biggest variables are your regulatory path, partner due diligence, and how many markets you launch in. Engineering on top of a payments API is rarely the slowest step. Partner reviews, compliance setup, and account approvals usually are." - q: "What technology does a neobank need?" a: "A neobank needs a ledger that tracks customer balances, account details for deposits, onboarding with KYC and KYB, payment rails for money in and out, FX, fraud and risk controls, a customer app, and admin tools for operations. Most teams build the app and the ledger and buy accounts, rails, compliance tooling, and cards from regulated providers." - q: "Where does BlindPay fit in a neobank?" a: "BlindPay is the money movement and compliance layer. It issues US virtual accounts in each customer's name, converts deposits into stablecoins, and pays out in local currency over rails such as Pix, SPEI, ACH, SEPA, and SWIFT (POBO/COBO). KYC, KYB, and sanctions screening run inside the same API. Cards and consumer app features come from other providers and your own product." - q: "How much does it cost to build a neobank?" a: "Costs depend on the regulatory path and the number of providers. Plan for legal and compliance work, provider platform fees, per-transaction fees, per-account fees, KYC checks, and support. On BlindPay, plans start at $499 per month, US virtual accounts cost $1.50 per month each, and per-transaction fees show up in each live quote before you execute." --- To build a neobank in 2026, pick one customer group and one money problem, choose a regulatory path (usually a partner bank or regulated providers), then add accounts, onboarding, money in, and money out on top of providers you trust. BlindPay covers accounts, KYC, deposits, FX, and local payouts through one API, while cards come from a card issuing provider. This guide breaks the build into 10 steps. Each step lists what you decide, what you end up with, and where BlindPay fits. It closes with a worked example, a dollar account app for Brazil, and a plan for your first 30 days. **Key takeaways** - Most neobanks launch without their own charter. They pair a licensed partner with a product they own. - A neobank is a stack of layers: ledger, accounts, onboarding, rails, FX, cards, risk, app, and ops tools. - Build what makes you different (the app, the ledger, the pricing). Buy regulated money movement. - Start with one corridor and one customer type. Expand from usage data, not from a feature wishlist. - BlindPay handles accounts in, payouts out, FX, and compliance checks in one API. ## What is a neobank? A neobank is a financial app that gives customers accounts and payments without its own branches, and usually without its own banking charter. The neobank owns the customer, the app, and the pricing. A licensed bank or a regulated provider holds the accounts and moves the money. That split is the whole business model, and it shapes every decision below. In 2026 there is a second split. Many neobanks still show customers dollars, reais, or pesos, but settle part of the flow in stablecoins (digital tokens such as USDC that track the US dollar one to one). Customers see a bank transfer. The stablecoin leg runs behind the scenes. For a plain explanation of the parts involved, see [what stablecoin infrastructure is](/resources/more/what-is-stablecoin-infrastructure). ## How do neobanks make money? Neobanks earn from a mix of interchange on card spend, FX margin on conversions, transfer fees, subscription plans, and interest or lending products. Which lines you can use depends on your licenses and partners. A dollar account app for Latin America leans on FX margin and transfer fees. A US debit card app leans on interchange. Pick the revenue line before you pick partners, because it decides which provider features you actually need. ## What are the layers of a neobank, and who provides each? A neobank has about nine layers. Most teams build two or three and buy the rest. | Layer | What it does | Usually built or bought | Typical provider | | --- | --- | --- | --- | | Customer app | Screens, notifications, support entry points | Built | Your team | | Ledger | Customer balances, holds, transaction history | Built or bought | Your team or a ledger vendor | | Onboarding and KYC/KYB | Identity, business verification, sanctions | Bought | BlindPay API, KYC vendors | | Accounts | Account details customers can share | Bought | BlindPay virtual accounts, partner banks | | Money in | Bank deposits, conversion to a settlement asset | Bought | BlindPay payins | | Money out | Transfers to bank accounts at home and abroad | Bought | BlindPay payouts | | FX | Rates and conversion between currencies | Bought | BlindPay live quotes | | Cards | Debit or prepaid cards and card spend | Bought | Card issuing providers | | Risk and operations | Monitoring, disputes, admin tools | Mixed | Your team plus vendors | The layers that make you different are the app, the pricing, and how you treat the customer. The layers that need licenses, bank relationships, and audits are the ones you buy. [Build vs buy for stablecoin payouts](/resources/more/build-vs-buy-stablecoin-payments) covers the payout layer in detail. ## What are the 10 steps to build a neobank? Here is the roadmap. Each step has a decision, an output, and the BlindPay piece where one applies. ### 1. Pick a market and a niche Decide who you serve and the one money problem you solve first. "Everyone who needs a bank" is not a niche. "Brazilian designers paid by US clients" is. - **Decide:** country, customer type (individuals or businesses), first use case. - **Output:** a one-page brief with the three money actions your customer does most. - **BlindPay fit:** check that your corridor has a named rail, such as Pix for Brazil or SPEI for Mexico. ### 2. Choose a regulatory path You can apply for your own charter, partner with a sponsor bank, get a payment or e-money license, or embed regulated providers. Each path changes your timeline and your obligations. - **Decide:** which entity holds customer funds, and which licenses you need yourself. - **Output:** a legal memo per market. This is educational content, not legal advice. - **BlindPay fit:** BlindPay is registered with FinCEN as a Money Services Business. It runs KYC, KYB, and sanctions screening on its side of the flow, but your own obligations stay yours. For how these licenses differ, read [MSB vs money transmitter license vs VASP vs EMI](/resources/more/stablecoin-payment-licenses-msb-mtl-vasp-emi). In the US, national bank charters come from the [OCC](https://www.occ.gov/topics/charters-and-licensing/index-charters-licensing.html). A money services business registers with FinCEN on [Form 107 within 180 days of being established](https://www.fincen.gov/money-services-business-msb-registration), and renews every two years. ### 3. Select partners Pick providers per layer. Ask each one what it is licensed for, who holds the funds, how failed payments get refunded, and what you must do yourself. - **Decide:** one provider per layer for launch, with a backup for the money movement layer. - **Output:** signed agreements and a responsibility map. - **BlindPay fit:** accounts, deposits, payouts, FX, and compliance checks behind one integration. ### 4. Give customers accounts Customers need account details they can hand to an employer, a client, or their own bank. - **Decide:** which currencies and which account type. - **Output:** an "account details" screen per customer. - **BlindPay fit:** [virtual accounts](/resources/more/what-is-a-virtual-account) are real US bank accounts in the customer's own name, with their own routing and account number. They accept ACH, wire, and SWIFT deposits, cost $1.50 per month each, and go through a compliance review and a bank review before approval. ### 5. Build onboarding and KYC No money moves until you know who the customer is. - **Decide:** the data you collect, the order of screens, and the limits per verification tier. - **Output:** an onboarding flow with clear rejection and retry paths. - **BlindPay fit:** customers accept BlindPay's terms of service, then go through KYC. KYC Standard is automated and typically completes in about 60 seconds. Individuals from high-risk countries go through KYC Enhanced, with manual review. See the [KYC reference](/docs/kb/kyc) and [how to automate KYC and KYB](/resources/more/how-to-automate-kyc-kyb-stablecoin-payments). ### 6. Build money in A deposit has to land, convert if needed, and show up in the customer's balance. - **Decide:** when a deposit counts as available in your app. - **Output:** a deposit pipeline from webhook to ledger entry. - **BlindPay fit:** each deposit into a virtual account creates a payin. BlindPay converts it and sends USDC or USDT to the wallet linked to the account, and a signed webhook tells your backend. ### 7. Build money out Customers want to send money home, pay a supplier, or cash out to a local bank. - **Decide:** which rails you launch with, and how you show price and arrival time. - **Output:** a send flow with a quote screen and status tracking. - **BlindPay fit:** payouts over Pix, SPEI, ACH, RTP, wire, SEPA, ACH Colombia, Transfers 3.0, and SWIFT (POBO/COBO). Each payout starts with a quote that locks the rate and fees for 5 minutes. No pre-funding: the payout pulls the quoted amount at execution, so you don't park money with BlindPay in advance. [What "no pre-funding" means](/resources/more/no-pre-funding-stablecoin-payouts) walks through it. ### 8. Add cards and extras Cards drive daily use and interchange revenue, but they are their own workstream. - **Decide:** debit, prepaid, or stablecoin-backed card, and which provider issues it. - **Output:** a card program agreement and a spend flow tied to your ledger. - **BlindPay fit:** cards come from a card issuing provider. BlindPay funds the balance behind them with deposits and pays out what customers send to bank accounts. [Bridge cards and BlindPay payouts](/resources/more/bridge-cards-and-blindpay-payouts) shows one such stack. ### 9. Launch a pilot Open the app to a small group you can talk to. - **Decide:** pilot size, limits, and the metrics you watch daily. - **Output:** a dashboard with activation, time to first deposit, payout success rate, and tickets. - **BlindPay fit:** build and test on a development instance first. It uses a test token (USDB) and auto-approves KYC, so you can run full flows without real money. See [sandbox vs production](/docs/learn/sandbox-vs-production). ### 10. Iterate Add what customers ask for, in the order they ask. - **Decide:** the next corridor or feature, based on usage data. - **Output:** a quarterly roadmap and a refreshed compliance review. - **BlindPay fit:** new rails are new bank account types on the same API, not a new integration. ## Should you get a banking license or use a partner bank? Most early neobanks use a partner bank or regulated providers, because a charter takes years and heavy capital. | Route | Who holds funds | Time to launch | Best for | | --- | --- | --- | --- | | Own bank charter | You | Years | Large, well-funded teams that want full control | | Sponsor or partner bank | The partner bank | Months | US consumer and business accounts with cards | | Payment or e-money license | You, under safeguarding rules | Months to years | Payments-first apps in one jurisdiction | | Embedded regulated providers | The providers | Weeks to months | MVPs and cross-border products | The routes mix. Many teams start embedded, then add a partner bank or their own license once volume justifies it. Deposits held at an FDIC-insured bank are covered up to [$250,000 per depositor, per insured bank, per ownership category](https://www.fdic.gov/resources/deposit-insurance/brochures/deposits-at-a-glance). A neobank is not a bank, so be exact in your app about which entity holds the money and what protection applies. ## How long does it take, and what does it cost? Expect months for an embedded MVP and years for a charter. Costs follow the same split. Budget for these lines: 1. Legal and compliance setup per market. 2. Provider platform fees. On BlindPay, plans start at $499 per month (Basic), with US virtual accounts on the Business plan at $1,999 per month. See [pricing](/pricing). 3. Per-account fees, such as $1.50 per month per US virtual account. 4. Per-transaction fees. On BlindPay these vary by rail and network and appear in the live quote before you execute. 5. KYC checks, support, and fraud losses. ## What does a worked example look like? A dollar account app for Brazil Illustrative example. The product is "Dólar", an app for Brazilian freelancers paid by US clients. 1. **Niche.** Brazilian designers and developers with US clients. Three actions: receive USD, hold it, send reais to their own bank. 2. **Regulatory path.** The team works with counsel in Brazil and the US and embeds regulated providers. It reviews Brazil's rules for virtual asset service providers, explained in [PSAV in Brazil](/resources/more/psav-brazil-explained). 3. **Onboarding.** Ana signs up, accepts BlindPay's terms of service, and passes KYC Standard with her ID. 4. **Account.** The app requests a US virtual account in Ana's name. After compliance and bank review, she gets a routing and account number to send her client. 5. **Money in.** Her client sends $2,000 by ACH. A payin lands, BlindPay delivers USDC to the wallet linked to her account, and the app shows $2,000 minus fees as available. 6. **Money out.** Ana sends $800 to her own Brazilian bank. The app requests a quote for Pix, shows the BRL amount, the fees, and a countdown, and Ana confirms. The payout lands in her bank account over Pix. 7. **Revenue.** The app adds its own fee on each payout through partner fees, shown in the same quote. [How to send USDC to a bank account in Brazil](/resources/more/how-to-send-usdc-to-bank-account-brazil) covers the Pix leg step by step. ## What are the most common mistakes when building a neobank? These show up again and again: - **Launching in five markets at once.** Each market adds licenses, rails, and support hours. - **No ledger of your own.** Provider balances are not your customer balances. You need your own record. - **Hiding fees until the end.** Show the rate, fees, and arrival time before the customer confirms. - **Treating KYC as a form.** It is a funnel. Measure drop-off per screen. - **Ignoring failure paths.** Decide what the app says when a deposit is held or a payout fails. - **Skipping the development instance.** Test webhooks and failures before real money moves. [Common payout mistakes](/resources/more/stablecoin-payout-mistakes) lists the usual ones. ## What should you do in the first 30 days? Use the first month to decide, not to build everything. | Week | Focus | Done when | | --- | --- | --- | | 1 | Niche and corridor | One-page brief with three money actions | | 2 | Regulatory path | Counsel engaged, route chosen per market | | 3 | Partners | Providers shortlisted, development instance running | | 4 | First flow | Test customer onboarded, test deposit and test payout complete | ## How does BlindPay fit? BlindPay is the money movement and compliance layer of a neobank. One API covers four jobs. - **Accounts in.** US virtual accounts in each customer's own name, with their own routing and account numbers, accepting ACH, wire, and SWIFT. - **Payouts out.** Local currency over Pix, SPEI, ACH, RTP, SEPA, ACH Colombia, Transfers 3.0, and SWIFT (POBO/COBO), with UETR tracking on SWIFT. - **FX.** Live quotes that lock the rate and fees for 5 minutes before you execute. - **Compliance.** KYC, KYB, and sanctions screening inside the same flow. BlindPay operates as a non-custodial payment processor for payouts from customer-controlled wallets. If a payout can't be delivered after the stablecoins are collected, BlindPay refunds them to the refund wallet on the quote, or the sending wallet. On Pix and other non-USD local rails that refund is automatic, while USD payouts are refunded after an operator review. Optional managed wallets (beta) are custodial when you choose them. Developers get a REST API, an OpenAPI spec, and SDKs for Node.js, Python, Go, PHP, and Swift ([SDKs](/docs/sdks)). Operators get a dashboard and a native iOS app. BlindPay is backed by Y Combinator (W25) and moves $2.5 billion in annualized volume across a network reaching 100+ countries. ## What to do next Write your one-page niche brief, then open a development instance and run one test customer from onboarding to a test payout. The [BlindPay introduction](/docs/introduction) walks you through the API, and you can [create an account](https://app.blindpay.com/sign-up/) to get your keys.