---
title: "Do you need a banking license to launch a neobank? Four routes compared"
seoTitle: "Do you need a banking license to launch a neobank?"
description: "Most neobanks launch without a bank charter. Compare the four routes, from own charter to embedded providers, in the US, Brazil, Mexico, and the EU."
date: "2026-10-06"
updated: "2026-10-06"
category: "compliance"
author: "BlindPay Team"
faq:
  - q: "Can you launch a neobank without a banking license?"
    a: "Yes. Most neobanks launch without their own bank charter. They partner with a licensed bank, hold a narrower payment or e-money license, or embed regulated providers that hold the licenses for each activity. What you cannot do without a charter is take deposits in your own name or advertise deposit insurance you don't have. Your own obligations still depend on what your product does with customer money."
  - q: "What is the difference between a bank charter and a sponsor bank?"
    a: "A bank charter makes your company the bank. In the US, the OCC charters national banks and states charter state banks, and the bank holds deposits on its own balance sheet. A sponsor bank model keeps the license at a partner bank: accounts sit at that bank, and your app is the interface and program manager. You move faster, but the bank supervises your program."
  - q: "Is a money transmitter license the same as a banking license?"
    a: "No. A money transmitter license lets a company move money for others, but it does not allow it to take deposits or lend them out. In the US, money transmitters register with FinCEN as money services businesses and need state licenses where they serve customers. Many payment-first neobanks hold, or rely on a partner that holds, transmitter licenses instead of a charter."
  - q: "Does using stablecoins change the license a neobank needs?"
    a: "It adds rules rather than removing them. FinCEN applies its money transmission rules to businesses that accept and transmit convertible virtual currency. The EU regulates crypto-asset service providers under MiCA, and Brazil authorizes virtual asset service providers under its PSAV regime. Crypto assets are also outside FDIC deposit insurance, which changes what you can say to users."
  - q: "Does BlindPay hold licenses that cover my neobank?"
    a: "BlindPay is registered with FinCEN as a money services business and runs KYC, KYB, sanctions screening, and Travel Rule checks inside its payment flow. That covers BlindPay's own role in each payout and payin. Your neobank's licensing depends on what you do outside that flow, such as holding customer balances or lending, so map it with counsel. This is educational content, not legal advice."
---

You can launch a neobank without your own banking license, and most do. The usual paths are a partner (sponsor) bank, a payment or e-money license, or embedding regulated providers such as BlindPay, a FinCEN-registered money services business, for money movement. What you need depends on the activity: holding deposits, moving money, or lending.

A neobank is a product, not a legal category. The legal question is always "who holds the money, and who is licensed to do what with it?" This guide compares the four routes and how they look in the US, Brazil, Mexico, and the EU. It is part of our [guide to building a neobank](/resources/more/how-to-build-a-neobank).

This is educational content, not legal advice.

**Key takeaways**

- "Neobank" describes the app. The license sits with whoever holds deposits or transmits funds.
- There are four routes: own charter, partner bank, payment or e-money license, and embedded regulated providers.
- Each country names the licenses differently: OCC charters and state money transmitter licenses in the US, payment institutions in Brazil, IFPEs in Mexico, PIs and EMIs in the EU.
- Stablecoins add rules (FinCEN CVC guidance, MiCA, PSAV) and remove deposit insurance from the picture.
- A provider's license covers the provider's role. Yours depends on the rest of your product.

## What is a neobank, legally?

Legally, a neobank is usually not a bank. It is a company that offers accounts, cards, or transfers through an app while a licensed institution holds the money or moves it.

That distinction matters for three things: who can accept deposits, who can claim deposit insurance, and who answers to the regulator when something breaks. In the US, the [FDIC insures deposits](https://www.fdic.gov/resources/deposit-insurance/brochures/deposits-at-a-glance) up to $250,000 per depositor, per insured bank, for each account ownership category. Only money at an insured bank qualifies. The same FDIC page lists crypto assets among the things it does not insure.

So the first design decision is not the app. It is where customer money sits.

## What are the four routes to launch?

Most teams choose one of four routes, or combine two. Here is how they compare.

| Route | Who holds customer funds | What you own | Main trade-off | Best for |
| --- | --- | --- | --- | --- |
| Own bank charter | You, as a chartered bank | Deposits, lending, full supervision | Longest path, highest capital and exam burden | Well-funded teams that want to lend from deposits |
| Partner (sponsor) bank | The partner bank | Program management, customer experience | The bank's risk appetite shapes your roadmap | US consumer and SMB accounts with cards |
| Payment, e-money, or money transmitter license | You, under safeguarding rules | Transfers and stored value, no deposit lending | Licenses per country or state, ongoing audits | Payment-first products in one or two markets |
| Embedded regulated providers | Each provider, for its activity | Product, brand, and your own compliance scope | Less control over each provider's rules | Fast launches, cross-border and multi-country products |

Timelines vary too much by jurisdiction and team to quote a number. The rough order, longest to shortest, is charter, license, partner bank, embedded. Ask each regulator or partner for its current process before you plan a date.

## How do a charter, sponsor bank, EMI, and money transmitter differ?

They differ in what the license allows you to do with customer money.

- **Bank charter.** Lets you take deposits and lend them. In the US, the [OCC's chartering department](https://www.occ.gov/topics/charters-and-licensing/index-charters-licensing.html) decides filings to establish national banks and federal savings associations. States charter state banks.
- **Sponsor bank.** A chartered bank opens accounts for your users and issues cards under its license. You run the program. The bank stays responsible to its own regulators, so it will review your onboarding, monitoring, and complaints.
- **E-money or payment institution.** Holds client funds for payments without lending them. EU e-money institutions and payment institutions are authorized nationally and covered by EBA guidance.
- **Money transmitter.** Moves money for others. In the US this means [FinCEN MSB registration](https://www.fincen.gov/money-services-business-msb-registration), filed within 180 days of establishment and renewed every two years, plus state licenses where required.

If you want a deeper comparison of MSB, MTL, VASP, and EMI, see [which license a stablecoin payment flow needs](/resources/more/stablecoin-payment-licenses-msb-mtl-vasp-emi).

## How does it work in the US, Brazil, Mexico, and the EU?

Each market has its own names. The table maps them.

| Market | Regulator | Licenses a neobank-style product usually meets | Stablecoin layer |
| --- | --- | --- | --- |
| United States | OCC, state regulators, FDIC, FinCEN | Bank charter, or a sponsor bank, plus MSB registration and state money transmitter licenses for transfers | FinCEN treats CVC transmission as money transmission; the GENIUS Act covers payment stablecoin issuers |
| Brazil | Banco Central do Brasil | Payment institution authorization under Resolução BCB 80, or a partner institution | PSAV authorization for virtual asset service providers |
| Mexico | CNBV, Banco de México | IFPE (electronic payment funds institution) under the Fintech Law, or a bank partner | Virtual asset operations sit with authorized institutions |
| European Union | National authorities, EBA | Payment institution or e-money institution under PSD2 and the E-Money Directive | MiCA authorization for crypto-asset service providers |

A few specifics worth reading at the source:

- Brazil's [Resolução BCB 80](https://www.bcb.gov.br/estabilidadefinanceira/exibenormativo?tipo=Resolu%C3%A7%C3%A3o%20BCB&numero=80) governs how payment institutions are set up and how they apply for authorization. For crypto, our [PSAV explainer](/resources/more/psav-brazil-explained) covers the virtual asset license.
- Mexico's Fintech Law was published on March 9, 2018. The [CNBV describes IFPEs](https://www.gob.mx/cnbv/acciones-y-programas/instituciones-de-tecnologia-financiera) as companies it authorizes to issue, administer, redeem, and transmit electronic payment funds.
- In the EU, the [EBA's payment services and e-money hub](https://www.eba.europa.eu/regulation-and-policy/payment-services-and-electronic-money) tracks how PSD2 and MiCA overlap for providers that transact electronic money tokens. Its no-action transition on that overlap ended on March 2, 2026.

## What changes when a neobank uses stablecoins?

Stablecoins change the money movement layer, not the need for licenses.

Three things shift. First, more rules apply: crypto rules (MiCA, PSAV, FinCEN's CVC guidance) sit on top of payment rules. Second, deposit insurance is off the table for any balance held as a stablecoin, so your copy has to say where money sits. Third, the Travel Rule and wallet screening join KYC as daily obligations. Our [stablecoin regulation tracker](/resources/more/stablecoin-regulation-tracker-2026) follows the main regimes.

The user shouldn't need to know any of this. They see a dollar balance and a bank transfer. Your compliance team needs to know all of it.

## Who is responsible for compliance in each route?

Responsibility follows the license, and the partner always keeps some of it.

| Duty | Own charter | Partner bank | Own payment license | Embedded providers |
| --- | --- | --- | --- | --- |
| Customer KYC and KYB | You | Shared; the bank sets the standard | You | Each provider for its flow; you for the rest |
| Sanctions screening | You | Shared | You | Provider in its flow; you at signup |
| Transaction monitoring and SARs | You | Shared | You | Provider for its transactions; you for your ledger |
| Safeguarding customer funds | You | The bank | You | Each provider |
| Complaints and disclosures | You | You, with bank oversight | You | You |

The 2023 interagency guidance from the FDIC, the Federal Reserve, and the OCC on third-party relationships (FDIC FIL-29-2023) explains why sponsor banks review fintech programs so closely: the bank stays accountable for activity run through its partners.

## Worked example: which route fits a Brazil dollar account app?

Illustrative scenario, no real company. A five-person US startup wants Brazilian users to receive US dollars from abroad and cash out to Pix.

1. **Money in.** Users get US account details. A provider issues virtual accounts in each user's name and converts deposits to USDC.
2. **Balance.** Users see dollars. The app's ledger tracks what each user owns; the stablecoin sits in a wallet the team controls or with a custodial provider.
3. **Money out.** A payout API converts USDC to BRL and pays over Pix.
4. **Licensing review.** Counsel checks whether holding balances triggers US state money transmitter licensing, and whether Brazilian users trigger anything under BCB rules.

The embedded route gets the product live first. A charter would add years and capital the team doesn't have. The license questions in step 4 still need answers before launch.

## What are common mistakes?

- Calling the app a bank or implying FDIC insurance for balances that sit at a non-bank or in stablecoins.
- Assuming the provider's license covers your whole product.
- Picking a sponsor bank before checking that it accepts your use case and your target countries.
- Treating crypto rules as optional because "users never touch a wallet."
- Planning a launch date before the partner's review dates are confirmed.

## How does BlindPay fit?

BlindPay is the money movement layer in the embedded route. It is registered with FinCEN as a money services business (details on the [licenses page](/licenses)), and its API runs KYC and KYB, sanctions screening, and Travel Rule checks inside each payin and payout.

What that gives a neobank team:

- **Virtual accounts** that give each customer US account details in their own name, with deposits converted to USDC or USDT.
- **Payouts** over Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO/COBO), funded from stablecoins at a locked quote.
- **Compliance inside the flow,** so each transaction is screened without a separate vendor stack.

Your own obligations stay with you: how you hold balances, how you market the product, and what each country requires of you. Review the [prohibited activities list](/docs/kb/prohibited-activities) early, since it shapes what you can build on top. For a view of other providers, see the [neobank infrastructure comparison](/resources/more/best-stablecoin-infrastructure-for-neobanks-2026), and for the build or buy split, the [neobank tech stack guide](/resources/more/neobank-tech-stack-build-vs-buy).

## What to do next

Write one sentence for each market you plan to serve: who holds the money, and who moves it. Take that list to counsel. Then open a development instance from the [BlindPay docs](/docs/introduction) and test the money movement part while the licensing work runs in parallel.