Usually no: a merchant that accepts stablecoins as payment for its own goods or services is generally a customer of the payment system, not a regulated provider, in the United States, Brazil, Mexico and the European Union. The license attaches to whoever moves, converts or holds funds for someone else.
This is not legal advice. Thresholds and exemptions depend on how the merchant receives the funds, so confirm the structure with counsel before launch.
Which merchant activities need a license, and which do not?
All four regimes draw the same line: being paid for your own sale is one thing, and providing a payment service to others is another.
What a merchant does with stablecoins, whether it needs a license of its own, and the reason
What the merchant does | License of its own? | Why |
Sells its own goods or services and is paid in USDC | No | It is the payee of its own sale, not a provider of a payment service |
Sells the stablecoins it received to a licensed provider for local currency | No | The provider performs the exchange and the merchant is its customer |
Sells or exchanges stablecoins with its own customers, as a business | Yes | Exchange for funds is a regulated service in the EU (MiCA Art. 3(1)(19)), in Brazil (Resolution BCB 520, Art. 7) and in Mexico (Art. 17, section XVI, of the anti-money-laundering statute) |
Holds stablecoins for customers or sellers | Yes, or a partner that holds it | Custody is a service of its own (MiCA Art. 3(1)(17), Resolution BCB 520, Art. 9) |
Collects payments for other businesses, or pays out on their behalf | Yes, or every party onboarded with a licensed provider | The money belongs to someone else, and moving it is the activity the licenses cover |
On Lumx, the same test is written into the onboarding rules: ask whose money it is and whose business it pays for. Funds that belong to a party Lumx has not onboarded count as nesting and are not allowed.
United States: the exemption for funds integral to a sale
In the United States, the federal question is whether the merchant is a money transmitter under the Bank Secrecy Act. 31 CFR 1010.100(ff)(5)(ii)(F) excludes a person who "accepts and transmits funds only integral to the sale of goods or the provision of services, other than money transmission services, by the person who is accepting and transmitting the funds." FinCEN's guidance FIN-2019-G001 of May 9, 2019 restates the exemption for convertible virtual currency and adds that FinCEN interprets exemptions strictly.
A merchant paid in USDC for its own sale fits the wording. A merchant whose business becomes moving value for others does not, because the transmission is then the product, and it would register as an MSB (money services business, the FinCEN registration category), as the FinCEN MSB guide explains.
The GENIUS Act (Public Law 119-27, signed July 18, 2025) is about issuers and providers. Section 3(a) bars anyone but a permitted issuer from issuing a payment stablecoin in the United States, and Section 3(b) bars a digital asset service provider from offering or selling one a permitted issuer did not issue, three years after enactment. Section 2(7) defines that provider by the business it does for others, for compensation or profit. None of these sections describes a merchant paid for its own sale, and the GENIUS Act guide has the timeline.
On Lumx, Lumx US OP LLC is a FinCEN-registered Money Services Business and not a state-licensed money transmitter, and regulated money transmission is conducted through licensed financial-institution partners.
Brazil: the authorization belongs to the provider
In Brazil, the authorization sits with the company that provides virtual asset services to third parties. Resolution BCB 520 of November 10, 2025, in force since February 2, 2026 (Art. 92), describes the SPSAV (Sociedade Prestadora de Serviços de Ativos Virtuais, the company type that holds Brazil's virtual asset authorization) as an institution authorized by the Central Bank of Brazil (BCB) that performs those services "em nome de terceiros", on behalf of third parties (Art. 4). It is Brazil's form of a virtual asset service provider. Intermediation, which covers buying, selling and swapping virtual assets, is defined as done "por conta de terceiros" (Art. 7), and custody has its own article (Art. 9). The SPSAV explainer covers the company type.
Resolution BCB 521, issued the same day, added Article 76-A to Resolution BCB 277: international payments with virtual assets are foreign exchange operations, and moving funds in a third party's interest through those services is barred unless the provider serves an exchange-authorized institution acting for its clients. A Brazilian merchant paid in USDC for its own sales is none of that. The Brazil merchant guide covers the steps.
One date matters for choosing a provider. Article 91 of Resolution 520, as rewritten by Resolution BCB 589 of September 23, 2026, bars financial and payment institutions, from November 6, 2026, from enabling virtual asset operations with counterparties that provide those services and are not authorized in Brazil, except as the resolution allows.
On Lumx, Lumx Sociedade Prestadora de Serviços de Ativos Virtuais Ltda acts as a virtual asset service provider and is adapting to the SPSAV regime under Resolution BCB 520/2025, operating under the Article 88 transition regime, and it has filed its authorization request.
Mexico: no license for the merchant, but two texts to read
Mexico has no virtual asset license, and neither text below addresses a merchant. The Fintech Law of March 9, 2018 restricts the ITFs (instituciones de tecnología financiera, the fintech institutions it licenses). Under Article 30, an ITF may operate only with the virtual assets Banxico determines, with Banxico's prior authorization. The article defines a virtual asset as a representation of value used among the public as a means of payment, and excludes legal tender and foreign currencies. Banxico's Circular 4/2019 (published March 8, 2019 in the Diario Oficial) names credit institutions and ITFs as its subjects.
The second text is Article 17, section XVI, of the federal anti-money-laundering statute, added by the same 2018 decree. It makes a vulnerable activity of the habitual and professional offering of exchange of virtual assets by non-financial entities, through platforms they operate, facilitating purchases or sales of assets belonging to their clients, or providing means to custody or transfer them. A merchant selling its own goods does not match, and one that adds a "buy crypto" feature for customers may. Whether a dollar stablecoin is a virtual asset at all, given the Article 30 exclusion, is a question for Mexican counsel. The Mexico regulation guide walks through both texts.
On Lumx, a Mexican merchant onboards as a business customer and asks for an MXN account, a named account in its own name issued through a banking partner, that takes SPEI (Mexico's interbank transfer system, run by Banxico) payments, including from payers abroad, and is active right after approval. A merchant has to request each currency's account before it can collect or pay out in it.
European Union: MiCA regulates the service, not the sale
Regulation (EU) 2023/1114 (MiCA) of May 31, 2023 applies, under Article 2(1), to persons that issue crypto-assets, offer them to the public, seek their admission to trading or provide services related to them. Each crypto-asset service in Article 3(1)(16) is defined by a relationship with clients: custody on their behalf, exchange for funds by concluding purchase or sale contracts with them using proprietary capital, or transfer on behalf of another person. Article 59(1) bars anyone from providing those services unless authorized as a CASP (crypto-asset service provider) or allowed to as a credit institution, electronic money institution or another listed entity.
A merchant that takes stablecoins for goods concludes no crypto-asset sale contract with its clients, so the definitions do not describe it. The line moves when it offers customers a way to buy, hold or send crypto-assets. The MiCA guide covers payment companies.
On Lumx, EUR accounts run through a banking partner, and Lumx holds no CASP authorization or other license in the EU.
What the merchant still owes the provider
The provider's license does not exempt the merchant from everything. Four things stay: passing KYB (know your business, the verification of a company and its owners), describing the business accurately, respecting sanctions rules in who it sells to, and keeping records.
The KYB file is the concrete part, and the KYB explainer covers the process. On Lumx, a business customer provides:
company name, country, tax ID, incorporation date and address
company formation documents, which in Brazil typically means the articles of incorporation or bylaws, an ownership chart and, if applicable, the director minutes and the share register
an ID and a proof of address from the last 90 days for the representative, each UBO (ultimate beneficial owner) and each shareholder above 25%
source of funds, monthly revenue, expected transaction volume and the counterparties involved
any regulated activity the company carries out and, when it applies, the license
Lumx targets one business day for standard KYB once the documents are complete (effective November 2026). An invalid or inconsistent item moves the customer to RFI (request for information, a compliance hold that asks for a document before a transaction clears), and the review clock resets when corrected documents arrive.
Checking a provider's authorization before you sign
The merchant does not hold the license, so the provider's file is what to check; see Lumx's supported countries, coverage page and operator map. Ask in writing, for each market where the provider collects or converts, for the authorization and the entity that holds it. In the United States that is the MSB registration number plus the state licenses or licensed partner behind money transmission. In Brazil it is the SPSAV authorization, or proof that the request is filed and the provider operates under Article 88, with its plan for Article 91. In Mexico it is whether the provider is registered for the Article 17, section XVI activity or works through a licensed institution. In the European Union it is the CASP authorization number, or the institution allowed to provide the service under MiCA Article 59(1).
When the no-license answer is the wrong answer
The answer is wrong in four situations, each starting with the merchant's own growth. A marketplace that collects buyer funds and pays sellers moves money for third parties, so it needs its own authorization or a provider that has onboarded every seller. A payroll or platform business paying out for other companies is in the same position. A merchant letting customers buy, hold or send stablecoins in its app has added an exchange or custody service. A business that issues its own token faces an issuer question.
I recommend that a merchant treat the first request to collect for another business as a new product, and run the license question again before building it. The reason is that the answer in this post flips on that day: a merchant paid for its own sale is a customer, and a merchant routing money for a seller is doing the activity the licenses cover. Before signing, I would ask any provider for its authorization status and its written rule on who may be a counterparty. A provider that cannot say whose money may flow through the account has not decided yet.
The marketplace payouts guide shows the structure, and the wider country-by-country question has its own post, are blockchain payments legal.
What this looks like on Lumx for a merchant
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
A merchant is a business customer. It accepts the Terms of Service, completes KYB, and once approved gets a custodial wallet on each supported blockchain. A payer can send stablecoin straight to the wallet address, which receives direct transfers. For payers who pay in local currency, the merchant can hold a named virtual account (a local account number issued in the customer's own name), and an on-ramp tagged with the trade transactions purpose converts the deposit into stablecoin in the merchant's wallet.
The merchant takes money out with an off-ramp to a bank account in its own name.
Methodology and sources
Each norm is cited by number and date, with a link to its official source. On November 1, 2026 two hosts served no text to our checker: bcb.gov.br returns a JavaScript shell, so the BCB resolutions came from its normative search endpoint, and EUR-Lex returned nothing, so MiCA came from the Publications Office. Law 14.478/2022 is cited through the resolutions because planalto.gov.br did not answer, and Banxico's Circular 4/2019 was read on its index page only, so its link goes to Banxico's regulatory portal. Lumx's requirements come from docs.lumx.io. State laws, tax rules and the UK were not reviewed.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice. 31 CFR 1010.100 (eCFR text as of October 29, 2026) and FIN-2019-G001 checked against fincen.gov on November 1, 2026. GENIUS Act (Public Law 119-27, July 18, 2025) checked against congress.gov on November 1, 2026. BCB Resolutions 520 and 521 (November 10, 2025) and 589 (September 23, 2026) read from the BCB normative search endpoint on November 1, 2026. Fintech Law and anti-money-laundering amendment (March 9, 2018) checked against dof.gob.mx on November 1, 2026. MiCA, Regulation (EU) 2023/1114 (May 31, 2023), read from the Publications Office of the European Union on November 1, 2026 (EUR-Lex served no text).
Cover photo: Dmitry Voronov on Unsplash.
Do merchants need a license to accept stablecoin payments?
In the United States, Brazil, Mexico and the European Union, a merchant paid in stablecoins for its own goods or services generally needs no license of its own, because the licensed activity is moving, converting or holding funds for someone else. That changes when the merchant collects for other businesses, holds customers' stablecoins or sells stablecoins to the public. On Lumx, a merchant onboards as a business customer through KYB and collects its own revenue, and the operator map shows which Lumx entity handles each step.
Does a merchant become a money transmitter by converting stablecoins to local currency?
Not when it sells its own receipts to a licensed provider, because the provider performs the exchange. The US exemption for funds handled only as part of the merchant's own sale is read strictly, and converting for others as a product is different. On Lumx, the merchant converts through an off-ramp from its own wallet to a bank account in its own name, and a destination held by someone else has to be a disclosed, approved third party.
Can a marketplace or platform that collects for sellers skip the license?
No, not on its own. Passing buyer funds to sellers is moving funds for a third party, which US money transmission rules, Brazil's Article 76-A and MiCA's custody and transfer services each reach. On Lumx, each seller is onboarded as its own customer with its own wallet, the platform earns a partner fee, and buyer funds pooled in the platform's account for sellers Lumx has not onboarded are not allowed.
What does a provider ask a merchant during KYB?
Expect company details and tax ID, formation documents, an ID and proof of address for the representative and every owner above 25%, source of funds, monthly revenue and expected volume, and any regulated activity with its license. On Lumx, standard KYB targets one business day once the documents are complete (effective November 2026), and an RFI pauses the review until the corrected document arrives.
Do the GENIUS Act and MiCA change whether a merchant needs a license?
Not directly. The GENIUS Act duties in Sections 2, 3 and 20 fall on issuers and digital asset service providers, and the MiCA authorization duties fall on issuers, offerors and CASPs. They do shape which tokens a provider may offer, so ask which tokens it supports in your market.
