---
title: "MSB vs money transmitter license vs VASP vs EMI: which license does a stablecoin payment flow need?"
seoTitle: "MSB vs MTL vs VASP vs EMI: stablecoin payment licenses"
description: "MSB registration, state money transmitter licenses, VASP, EMI, and PSAV compared: who needs each, what triggers it, and when your provider covers you."
date: "2026-10-01"
updated: "2026-10-01"
category: "compliance"
author: "BlindPay Team"
faq:
  - q: "Is FinCEN MSB registration the same as a money transmitter license?"
    a: "No. MSB registration is a federal filing with FinCEN under 31 CFR 1022.380, due within 180 days of starting business and renewed every two calendar years. A money transmitter license is issued by each state, with its own net worth, surety bond, and investment rules. A US money transmitter usually needs both: one federal registration and a license in each state where it serves customers."
  - q: "Does a company that pays its own suppliers in stablecoins need a license?"
    a: "Usually not. Licensing follows the act of moving money for someone else. A company paying its own suppliers or contractors from its own funds, through a licensed provider, is a user of the payment system. The picture changes when it collects money from one party to pass to another, as a marketplace or payroll platform does. Confirm your own structure with counsel."
  - q: "What is the difference between a VASP and a money transmitter?"
    a: "VASP is FATF's activity category: exchanging, transferring, or safekeeping virtual assets for others. Each country implements it through its own law. In the US the same activities fall under FinCEN's money transmitter definition and state licensing. In the EU they need MiCA authorization as a crypto-asset service provider. In Brazil they need PSAV authorization from the Central Bank."
  - q: "Do you need an EMI license to use stablecoins in Europe?"
    a: "Only to issue them. MiCA Article 48 lets only a credit institution or an electronic money institution offer an e-money token, such as a euro or dollar stablecoin, to the public in the EU. Exchanging, transferring, or holding stablecoins for EU customers needs crypto-asset service provider authorization instead. A business that just pays and gets paid through an authorized provider needs neither."
  - q: "Does my payment provider's license cover my customers?"
    a: "Only the customers your provider has onboarded and can see. A provider's license covers the activity it performs for parties it has verified. If you pool funds from your own users and push them through one provider account, the provider can't see who owns the money, and the activity may fall outside its coverage and inside your own licensing perimeter."
  - q: "Can a crypto payment processor use the payment processor exemption?"
    a: "Generally not in the US. FinCEN's 2019 guidance says payment processors that accept convertible virtual currency from customers and pay merchants are money transmitters, because they do not meet every condition of the exemption. One condition is operating through clearance and settlement systems that admit only BSA-regulated financial institutions, and public blockchains don't qualify."
---

A stablecoin payment flow needs a license wherever someone accepts money from one party and moves it to another. In the US that means FinCEN MSB registration plus state money transmitter licenses. The EU requires MiCA authorization, and Brazil a PSAV. A business that pays and gets paid through a licensed provider usually needs none of them.

This article is general information, not legal advice. Licensing turns on your exact structure, so confirm your obligations with qualified counsel before launch.

**Key takeaways**

- FinCEN MSB registration is federal and is not a license. State money transmitter licenses are separate, and a US transmitter usually needs both.
- VASP is an activity category from FATF, not a single license. Each country turns it into its own regime.
- An EMI license matters for issuing an e-money token in the EU, not for using one.
- The trigger is almost always the same: accepting value from one person and transmitting it to another, or exchanging and holding crypto for customers.
- A provider's license covers the parties it onboards and can see. Pooling other people's money through your account moves the risk back to you.

The [types of stablecoin APIs](/resources/more/types-of-stablecoin-apis) guide explains who holds funds in each provider model. This page answers the follow-up question: which license sits behind each role.

## What licenses apply to stablecoin payments?

Five regimes cover most stablecoin payment flows into and out of the Americas and Europe: US federal registration, US state licensing, MiCA, EU e-money, and national VASP regimes like Brazil's.

| License or registration | Region | Who grants it | Who needs it | Typical trigger |
| --- | --- | --- | --- | --- |
| MSB registration | United States (federal) | FinCEN | Money transmitters, currency dealers, and other money services businesses, including foreign firms doing business in the US | Accepting and transmitting funds or value for others |
| Money transmitter license (MTL) | United States (each state) | State financial regulators | Firms transmitting money for residents of that state | Same activity, assessed state by state |
| CASP authorization | European Union | National competent authority under MiCA | Firms exchanging, transferring, or holding crypto-assets for EU clients | Providing crypto-asset services in the EU |
| Electronic money institution (EMI) | European Union | National competent authority under the E-Money Directive | Issuers of e-money, including e-money tokens under MiCA | Issuing a euro or dollar stablecoin to the public |
| PSAV authorization | Brazil | Banco Central do Brasil | Firms providing virtual asset services to people in Brazil, onshore or offshore | Exchanging, transferring, or holding virtual assets for Brazilian clients |

The UK runs its own regime: cryptoasset firms register with the FCA under the money laundering regulations today, and the FCA's [new cryptoasset regime](https://www.fca.org.uk/publications/policy-statements/cryptoasset-regime) expands authorization from October 25, 2027, with applications open from September 30, 2026 to February 28, 2027.

## What is the difference between an MSB and a money transmitter license?

MSB status is a federal registration with FinCEN, and a money transmitter license is a state permission. They stack. They don't replace each other.

**The federal layer.** Under [31 CFR 1010.100(ff)(5)](https://www.law.cornell.edu/cfr/text/31/1010.100), money transmission means accepting currency, funds, or other value that substitutes for currency from one person and transmitting it to another location or person by any means. FinCEN's [2019 guidance on convertible virtual currency](https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20Guidance%20CVC%20FINAL%20508.pdf) (FIN-2019-G001) confirms that stablecoins count as value that substitutes for currency.

A money services business registers under [31 CFR 1022.380](https://www.law.cornell.edu/cfr/text/31/1022.380):

1. File within 180 days of the day the business is established.
2. Renew every two calendar years.
3. Re-register after a transfer of more than 10% of voting power or equity, or a jump of more than 50% in agents.
4. Keep a list of agents. A firm that is an MSB only because it acts as another MSB's agent doesn't register itself.
5. If the firm is located abroad but does business in the US, name a US agent for service of legal process.

Registration comes with a full AML program: policies, a compliance officer, training, and independent review.

**The state layer.** Each state licenses money transmitters separately, with its own capital, bonding, and examination rules. The Conference of State Bank Supervisors drafted the [Money Transmission Modernization Act](https://www.csbs.org/csbs-money-transmission-modernization-act-mtma) to standardize net worth, surety bond, and permissible investment requirements. As of September 2026, CSBS reports that 31 states have enacted it in full or in part. Everywhere else, the old state rules still apply.

That's why US licensing takes years to build. One federal filing, then dozens of state applications.

## Is a VASP license the same as a money transmitter license?

No. VASP is a category FATF created in 2019, and each country decides which license a VASP needs.

The FATF activity list is short: exchanging virtual assets for fiat or for other virtual assets, transferring them, safekeeping them, and taking part in issuance. The [VASP explainer](/resources/more/what-is-a-vasp) walks through each one.

What changes is the implementation:

- **United States.** No separate VASP license. The same activities fall under FinCEN money transmission and state MTLs.
- **European Union.** [MiCA](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32023R1114) Article 59 says nobody may provide crypto-asset services in the EU unless authorized as a CASP, or already licensed as a bank, investment firm, EMI, or similar entity allowed to offer them. The transitional period for firms already operating ended on July 1, 2026 at the latest.
- **Brazil.** Central Bank Resolutions 519, 520, and 521 took effect on February 2, 2026 and require PSAV authorization for anyone serving Brazilian clients. See [PSAV in Brazil explained](/resources/more/psav-brazil-explained).

So "are you a licensed VASP?" is an incomplete question. Ask which regime, in which country, for which activity.

## When do you need an EMI license for stablecoins?

You need an EMI license, or a banking license, to issue a euro or dollar stablecoin to the public in the EU. Not to hold or spend one.

MiCA Article 48 says a person may not offer an e-money token to the public in the EU unless it is the issuer and is authorized as a credit institution or an electronic money institution. The [E-Money Directive](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009L0110) sets the EMI baseline, including initial capital of at least EUR 350,000.

That's why Circle holds an EMI license in France for USDC and EURC, and why exchanges restricted USDT for EU clients. [MiCA stablecoin rules explained](/resources/more/mica-stablecoin-rules-explained) has the details. For a payments company, the EMI question is mostly about your supplier: is the stablecoin you move issued by an authorized EMI, and is your provider authorized to handle it?

## What triggers a license, and what doesn't?

The trigger is control over someone else's money in transit. The activity matters, not what you call your company.

Activities that usually trigger licensing:

1. Accepting funds or stablecoins from one party and sending them to another.
2. Exchanging stablecoins for fiat, or one crypto-asset for another, on behalf of customers.
3. Holding customer balances or private keys.
4. Issuing a stablecoin.
5. Collecting from buyers and paying sellers as a marketplace that touches the money.

Activities that usually don't:

1. Accepting stablecoins as payment for your own goods or services. FinCEN's 2019 guidance treats that business as a user, not a transmitter.
2. Paying your own suppliers, contractors, or employees from your own funds.
3. Providing software that never takes control of the value, such as unhosted wallet software.

One trap catches crypto payment processors. US rules exempt payment processors that facilitate the purchase of goods through a clearance and settlement system by agreement with the seller. FinCEN's 2019 guidance says CVC payment processors are money transmitters anyway, because they don't meet every condition, including running through settlement systems that admit only BSA-regulated financial institutions. A public blockchain isn't one.

## Does your provider's license cover your activity?

A provider's license covers what the provider does for the parties it has onboarded. It doesn't stretch to customers it can't see.

| Your setup | Who is moving the money | Licensing exposure |
| --- | --- | --- |
| You pay your own contractors through a provider | The provider, for you | Low. You're the provider's customer |
| You collect stablecoins for your own sales | You receive, the provider converts | Low. You're a user |
| Your platform onboards each end customer directly with the provider | The provider, for each verified customer | Lower. The provider can see every party |
| You pool users' money in one provider account and pay out on their behalf | You | High. You may be transmitting for others |
| Your app holds user stablecoin balances in wallets you control | You | High. You're custodying value for others |

The pooled row is the one that surprises teams. Money moving through your account for parties the provider never verified looks, to the provider, like your own activity. To a regulator, it looks like unlicensed transmission. [Who owns compliance in a crypto on-ramp](/resources/more/crypto-on-ramp-compliance-who-owns-what) runs the same test from the on-ramp side.

BlindPay draws that line explicitly: its [nested payments rule](/docs/kb/nested-payments) bars customers from moving money for any party BlindPay hasn't onboarded or can't see. A platform that needs to serve its own customers can open a separate instance and onboard them directly, so every party sits inside the verified flow.

## Who is responsible for what when you use a licensed provider?

Responsibility splits, but it never disappears. This matrix assumes you don't hold customer funds and every party is onboarded with the provider.

| Duty | You | Provider | Shared |
| --- | --- | --- | --- |
| Onboarding (KYC and KYB) | Collect accurate data, describe your business truthfully | Verify identity, ownership, and documents | Keep data current when it changes |
| Sanctions screening | Follow OFAC and local sanctions as a business | Screen customers, counterparties, and wallets | Escalate matches fast |
| Transaction monitoring | Watch for misuse of your own product | Monitor payments flowing through its platform | Answer information requests |
| Suspicious activity reporting | File your own reports if you are a regulated entity | File reports on activity it sees | Cooperate on investigations |
| Record retention | Keep invoices, contracts, and approvals for each payment | Keep transaction and KYC records under its own rules | Produce records for audits |
| Disputes and complaints | Handle your end users' complaints | Handle failed or returned payments | Agree on who answers first |

The left column never goes to zero. A [merchant accepting stablecoins](/resources/more/do-merchants-need-a-license-to-accept-stablecoins) still owns sanctions compliance and tax records, even without a license.

## What should you ask before launching?

Eight questions cover most of the licensing risk:

1. Which entity holds which license, in which country, for which activity?
2. Does the provider's coverage include your customers' countries, or only yours?
3. Will every one of your end customers be onboarded with the provider, or will funds pool in your account?
4. Do you ever hold customer funds or keys, even for a few minutes?
5. Which stablecoins does the provider support, and who issues them?
6. Who files suspicious activity reports on your flows?
7. What does the provider need from you in writing about your business model?
8. What happens to your flows if the provider loses a license or a banking partner?

BlindPay runs KYC, KYB, sanctions screening, and travel rule checks inside the payment flow, before money moves, and publishes its license status on its [licenses page](/licenses). The KYC requirements are in the [KYC reference](/docs/kb/kyc).

Start with question 3. Draw your fund flow on one page, mark every moment your company touches someone else's money, and take that diagram to counsel.