More businesses are figuring out how to accept crypto payments, and most of the guidance out there stops at the technical part: get a wallet, pick a gateway, done. What it usually skips is the question that actually matters once the payments start coming in. Taking crypto for a sale and running a crypto business are two different things in the eyes of regulators, and the line between them is narrower than most founders assume.

For the vast majority of businesses, simply accepting crypto as payment for goods or services doesn’t trigger licensing. Where that line sits, though, moves depending on what the business does with the crypto after it lands, and in which market.
What “accepting crypto payments” actually covers
At its simplest, accepting crypto payments means a customer pays in Bitcoin, Ether, or a stablecoin instead of a card or bank transfer, and the business either keeps that crypto or converts it to fiat. Nothing in that transaction involves exchanging value on someone else’s behalf, holding custody of funds that belong to a third party, or running a platform that matches buyers and sellers. It’s a sale, settled in a different currency.
That distinction, “settling a sale” versus “providing a financial service,” is the one regulators keep coming back to, and it’s worth understanding before building a payment flow around it.
How to accept crypto payments as a business, step by step
In practice, most businesses don’t touch the regulatory question directly, because they route payments through an intermediary that already carries the relevant licenses. The usual setup looks like this:
- Choose a payment processor, such as BitPay, Coinbase Commerce, or a regional equivalent, rather than building wallet infrastructure from scratch. These processors generate the invoice, handle the blockchain confirmation, and often convert to fiat automatically.
- Decide on settlement currency. Most merchants convert crypto to fiat immediately to avoid holding price risk; some keep a portion in stablecoins or the original asset as treasury.
- Integrate at the point of sale, either through a plugin for an existing e-commerce platform (Shopify, WooCommerce) or a QR-code-based terminal for in-person retail.
- Set up accounting for crypto receipts. Most tax authorities, including the IRS, treat crypto as property rather than currency, so each sale needs to be booked at the fair market value on the date received, with any later conversion gain or loss tracked separately.
- Add the disclosures customers expect: price in fiat terms, final settlement amount in crypto, and a clear refund policy, since on-chain transactions can’t be reversed the way card payments can.
None of this requires a money transmitter license, a crypto exchange registration, or a central bank authorization in most jurisdictions, because the business is using a crypto service, not providing one to anyone else.
The point where accepting payments becomes running a regulated business
What regulators actually ask, across the major markets, is whether a business acts as an intermediary between two other parties’ money or as custodian of someone else’s assets. Simply touching crypto isn’t the test. A merchant selling its own goods for crypto is neither of those things. A business doing any of the following usually is:
- Exchanging crypto for other people, even informally (for example, letting customers swap one token for another through the business).
- Holding crypto on behalf of customers in a wallet the business controls.
- Transmitting funds between two other parties, rather than simply receiving payment for its own sale.
Here’s how that plays out jurisdiction by jurisdiction:
- United States
FinCEN defines “money transmission” as accepting value from one person and transmitting it to another person or location. A business that receives crypto and keeps it as payment for its own goods doesn’t meet that test; FinCEN’s 2013 guidance states plainly that a person who uses convertible virtual currency to buy goods or services is a user, not an MSB, a position its 2019 guidance carries forward. The regulation also carves out anyone who “accepts and transmits funds only integral to the sale of goods or the provision of services” (31 CFR 1010.100). It’s the processor sitting between buyer and merchant, converting and forwarding value, that tends to need the registration.
- European Union
Under MiCA, a Crypto-Asset Service Provider authorization is required for one of ten listed services provided “to clients” (Article 3(1)(16) and Article 59), such as exchange, custody, or payment processing as a service. A merchant selling its own goods for crypto has no client relationship in that sense; the crypto is just the currency the client paid in, not a service the business delivered to them. The CASP authorization requirement has applied across the bloc since 30 December 2024.
- United Kingdom
The UK’s registration regime (under the Money Laundering Regulations 2017) only catches two activities: operating as a cryptoasset exchange provider or a custodian wallet provider. The FCA’s own guidance confirms exchange tokens sit outside its regulatory perimeter for authorization purposes, which is a large part of why so few UK merchants have historically accepted crypto directly. That perimeter is about to widen: new rules under the Financial Services and Markets Act 2000 (Cryptoassets) Regulations 2026 bring dealing in and safeguarding certain cryptoassets into FCA authorization from 25 October 2027, so this describes the registration regime as it stands today, not the one that follows.
- Singapore
MAS administers the Payment Services Act 2019, which licenses anyone providing a “digital payment token service,” including dealing in or exchanging digital payment tokens. The First Schedule to the Act defines “dealing in” a token as buying or selling it, then explicitly excludes two things from that definition: accepting a digital payment token as a means of payment for goods or services, and using one to pay for them. Both sides of an ordinary crypto sale, the merchant accepting it and the customer paying with it, are named exclusions, not an inference from a broader test. It’s the most direct of the four regimes covered here.
None of this is legal advice, and these positions reflect each regime as of November 2026; every one of these tests is fact-specific, and some of them (the UK’s in particular) are scheduled to change, so a business with an unusual setup is better off having its actual flow reviewed than assuming it fits neatly into the merchant carve-out.
Why the gateway usually absorbs the hard part
The reason most merchants never have to think hard about any of this is structural: payment processors like BitPay disclose, in their own merchant terms, that they hold the relevant licenses (money transmitter registrations in the US, a MiCA crypto-asset service provider authorization in the EU) and act as the merchant’s agent for receiving the payment. The merchant is treated as having been paid directly, while the processor carries the compliance load in the background. That’s the trade a business is making when it uses a third-party gateway instead of building its own: slightly less control over the flow of funds, in exchange for staying out of a license application entirely.
Where the line actually gets crossed
The businesses that do end up needing a license are rarely the ones that set out to accept crypto payments. They’re the ones that started there and then added something else. Some let customers trade between assets on the platform, or start holding balances for users between purchases. Others begin offering to convert crypto for third parties, or build a rewards or loyalty system that ends up functioning like an exchange. Each of those shifts the business from “merchant” to “financial service provider” in a regulator’s eyes, even if the underlying technology looks similar.
If a product roadmap includes any of that, the planned activity is worth mapping against the applicable licensing perimeter well before launch, since regulators tend to ask the question only after it’s already a problem. That kind of perimeter analysis, working out which activities actually require authorization versus which fall outside it, is the kind of question regulatory advisory work resolves early, before a product ships.
Before building further
The rule of thumb holds steady across every market covered here: selling goods or services for crypto doesn’t require a license, while acting as a go-between for other people’s money or assets does. Most businesses stay cleanly on the merchant side for their entire life. The ones that drift usually do it one feature at a time, so checking a roadmap against the relevant licensing perimeter before a new feature ships is a cheap habit to build early.


