MiCA, DAC8 and the Travel Rule: three layers for crypto
Separate provider authorisation, transfer data and annual reporting so a US LLC can connect exchanges, own wallets and stablecoins coherently.
MiCA, DAC8 and the Travel Rule are often mentioned together, yet they govern different parts of a crypto operation. MiCA organises the EU market and the professional provision of crypto-asset services. The Travel Rule sets the information that must accompany a transfer when an in-scope provider is involved. DAC8 creates an annual tax due-diligence, reporting and information-exchange layer for relevant crypto transactions.
Treating the three as one rule produces poor decisions. A MiCA authorisation is not a tax report. A transfer to a company-controlled wallet is not automatically a disposal. A US LLC does not become subject to every EU rule merely because one provider serves it from Europe. The useful analysis separates the entity, the provider, the transfer and the reporting event.
A US LLC can collect stablecoins, hold digital treasury, use exchanges, operate self-custody and contract providers in several jurisdictions. The objective is not to narrow those options. It is to know which legal entity provides each service, what information it needs, what the LLC is doing economically and which evidence connects the entire structure.
Three layers at a glance
| Framework | What it governs | When it operates | Core information |
|---|---|---|---|
| MiCA | Crypto-asset issuance, offers and services in the EU | When issuers and providers are authorised and supervised | Provider, service, asset and conduct rules |
| Travel Rule | Information accompanying a crypto-asset transfer | Before or alongside each transfer | Originator, beneficiary, account or address and identifiers |
| DAC8 | Tax due diligence, reporting and exchange of crypto information | Throughout the year and in the following annual report | Reportable user, residence and transaction aggregates |
All three can touch the same commercial flow, but each observes a different moment. MiCA asks who is allowed to offer the service. The Travel Rule asks who sends and receives the transfer. DAC8 asks what information a reporting provider must collect and communicate for the year.
MiCA governs the provider and the market
The Markets in Crypto-Assets Regulation (EU) 2023/1114 establishes uniform requirements for crypto-asset offers and admissions to trading, certain token issuers and crypto-asset service providers.
Its service perimeter includes custody and administration, operating a trading platform, exchanging crypto-assets for funds or other crypto-assets, executing orders, placing assets, receiving and transmitting orders, advice, portfolio management and transferring crypto-assets for clients.
For a business customer, the decisive question is not only which brand appears in the app. It is which legal entity signs the agreement and under which authorisation it provides the service. One group can use different entities according to the customer's residence, product and market. The contractual entity and official register are more precise than the trading name.
MiCA also distinguishes asset categories. A token that seeks a stable value by referencing one official currency may be an e-money token. A token referencing several values or rights may be an asset-referenced token. Other assets can sit under a different financial-services framework.
MiCA does not determine the LLC's tax residence, calculate its profit or make every transfer taxable. Its principal role is to organise issuance and professional service provision within the EU perimeter.
The Travel Rule operates transfer by transfer
Regulation (EU) 2023/1113 requires certain crypto-asset transfers to be accompanied by originator and beneficiary information when an EU-established crypto-asset service provider is involved.
Originator information can include:
- name;
- distributed-ledger address and crypto-asset account number, where applicable;
- address and country;
- official document number and customer identifier or, alternatively, date and place of birth;
- an LEI or equivalent official identifier when the relevant format and data allow it.
Beneficiary information includes the name, distributed-ledger address or account and, where applicable, an LEI or equivalent identifier. The information must be submitted securely in advance of, simultaneously with or alongside the transfer. The Regulation expressly says it does not need to be attached directly to the blockchain transaction.
That distinction matters. The Travel Rule does not turn corporate and personal information into public on-chain text. Providers can exchange the required information through a separate secure channel while the ledger carries the address and transaction hash.
What happens with a company-controlled wallet
Self-custody remains available. When a transfer enters or leaves a self-hosted address and one side uses an EU provider, that provider obtains and retains the information needed to identify the transfer.
For transfers above EUR 1,000 to or from a self-hosted address, the provider must take adequate measures to assess whether its customer owns or controls the address. The European Banking Authority Travel Rule Guidelines explain how providers should identify the transfer, originator, beneficiary and control of a self-hosted address.
For an LLC wallet, a useful file contains:
- the LLC's exact legal name;
- wallet address and network;
- business purpose;
- person authorised to operate it;
- the control evidence accepted by the provider;
- the link to the exchange account sending or receiving the asset;
- transaction hash, units, date and business reason.
Proving control does not mean disclosing a seed phrase or private key. The provider chooses an appropriate technical or documentary method that can preserve wallet security.
DAC8 looks at the full reporting year
DAC8 is the eighth amendment to the EU Directive on administrative cooperation in taxation. Council Directive (EU) 2023/2226 extends automatic exchange of information to crypto-assets and providers that facilitate relevant transactions.
The first reporting year is 2026. In-scope providers collect data throughout that year, report in the following year and EU authorities make the first information exchange by 30 September 2027.
DAC8 can cover acquisitions and disposals against fiat, crypto-to-crypto exchanges and transfers. It also uses identification and tax-residence data and, for entities, can require analysis of controlling persons.
It does not authorise the exchange, execute a transfer or decide the tax result of each movement. The provider reports categories and aggregates under the framework; the LLC's books retain the economic detail behind each amount.
One operation through all three frameworks
Consider a US LLC that buys 20,000 USDC through an EU provider and then sends 12,000 USDC to its own corporate wallet.
MiCA layer
MiCA determines whether the EU entity may provide the exchange, custody or transfer service and which organisational and conduct rules apply. The LLC identifies the actual group entity delivering the service.
Travel Rule layer
When the LLC withdraws 12,000 USDC, the provider gathers originator and beneficiary information, identifies the destination address and assesses control of the self-hosted wallet. The LLC retains the hash and the relationship between both ends.
DAC8 layer
The provider places relevant transactions into the annual categories for that user and asset. The transfer may appear in reported information, but reporting does not turn it into a sale.
Business layer
The LLC records the USDC purchase and a transfer between two company-owned locations. Any crypto network fee is recorded separately. Ownership, units, valuation and purpose explain the full transaction.
These four views are compatible. None replaces the others.
What changes for a US LLC, and what does not
A US LLC remains a US legal entity. Using a European provider does not automatically change its governing state law, formation record or federal tax classification.
What changes is the perimeter of the contracted service:
- an account with an EU entity can fall under MiCA and the EU Travel Rule;
- a non-EU provider can follow another legal framework and its own verification policy;
- DAC8 looks at the reporting provider, the user, tax residence and covered transactions;
- a self-hosted wallet is not a service provider, although a connected CASP may need transfer information;
- the tax treatment of a collection, swap or investment follows the facts and relevant jurisdictions, not the name of a reporting rule.
The LLC's strength is that it can place contracts, exchanges, wallets, invoices and treasury under one clear business owner.
The contracting entity matters more than the app
Before opening or moving an account, record five facts:
| Fact | Why it matters |
|---|---|
| Provider's legal name | Identifies the actual counterparty |
| Country and register | Locates the authorisation and supervisor |
| Contracted service | Separates custody, exchange, transfer and execution |
| Account holder | Keeps the personal profile apart from the LLC profile |
| Supported assets and networks | Determines how value enters, exits and is documented |
Calling a platform European or American is not enough. The same brand can assign customers to different subsidiaries or change the contracting entity when residence or product changes.
Keep the LLC identity consistent
MiCA, the Travel Rule and DAC8 use different data, but all operate more smoothly when the company identity remains consistent across providers.
The core file should align:
- exact legal name;
- state and date of formation;
- EIN;
- registered address;
- operating address;
- activity and website;
- members, managers and authorised persons;
- stated tax residence and self-certifications;
- LLC bank accounts, exchanges and wallets;
- invoices, contracts and source-of-funds evidence.
The registered address and operating address serve different purposes. One links to the company record; the other describes where the business is directed or performed. They can be in different countries when that reflects reality. Each provider should receive the address it asks for, supported by matching evidence.
Stablecoins across four different layers
A stablecoin can appear in each layer for a different reason:
- MiCA can classify the asset and govern an issuer or service provider;
- the Travel Rule accompanies the movement between originator and beneficiary;
- DAC8 can include relevant acquisitions, disposals, exchanges or transfers in annual reporting;
- the LLC records whether it collected revenue, moved treasury, made a swap, paid a supplier or held an investment.
Collecting a USD 5,000 invoice in USDC does not make the invoice an internal transfer, and a blockchain is not a complete set of books. The company retains the contract, invoice, customer-facing address, hash, units, valuation and subsequent movement.
Structured properly, this expands the LLC's collection and treasury options. Stablecoins can connect to USD accounts, EUR solutions, exchanges and corporate wallets under one business identity.
Build the crypto stack by function
There is no universal provider for every company. The right architecture depends on where decision-makers live, who pays the LLC, which currencies it uses, which assets it holds and which services it needs.
A sound stack can separate:
- Collections. Gateway, exchange or corporate address provided to the customer.
- Conversion. Provider used to exchange crypto for USD, EUR or another asset.
- Operating custody. Balance needed for near-term payments and settlements.
- Self-custody. Corporate wallet with access and recovery rules.
- Banking. Accounts for ACH, wire, SWIFT or SEPA according to the business flow.
- Investment. A separate account when the LLC holds financial assets.
- Records. History connecting invoices, contracts, hashes, units and valuations.
Separating functions improves continuity and prevents one account from becoming the entire operation. It also makes each transfer easier to explain when a provider asks for more information.
Three distinctions that preserve flexibility
- Own transfer versus payment. Moving assets between two LLC wallets is not the same as paying a third party.
- Reporting versus taxation. A reportable transaction does not, by itself, determine income, expense, gain or an internal movement.
- Provider versus entity. The exchange supplies infrastructure; the LLC remains the economic owner of its assets and contracts.
This precision makes the structure portable. The company can change a provider, add a network or open another account without rebuilding its identity.
How Exentax helps
Exentax designs the complete structure around the real operation. We do not stop at forming the LLC or handing over a list of platforms.
We review ownership, residence, activity, customers, currencies and expected flows. We select compatible providers, prepare the corporate file, align addresses and authorised persons, and define how banking, processors, exchanges, wallets and stablecoins work together.
We also support onboarding and verification so every financial provider sees the same company. The result is an LLC with genuine options: collect, convert, invest, hold treasury and operate internationally with coherent evidence.
For the reporting calendar, read DAC8 records for 2026 and the first 2027 exchange. To connect providers and self-custody, continue with CARF, exchanges, wallets and stablecoins. For collections, see payment gateways and stablecoins for a US LLC.
Practical questions about MiCA, DAC8 and the Travel Rule
Does MiCA apply directly to a US LLC?
MiCA principally governs crypto issuance, offers and service provision in the EU. A US LLC should identify the provider entity serving it; contracting an EU entity does not turn the LLC into a European company.
Does the Travel Rule publish my details on-chain?
Not necessarily. The Regulation allows originator and beneficiary information to travel through a separate secure channel rather than being embedded directly in the blockchain transaction.
Can an LLC send assets from an exchange to its own wallet?
Yes. The provider can request information and, above EUR 1,000, adequate evidence that its customer controls the address. Self-custody remains compatible with documented business operations.
Is a DAC8-reported transfer automatically a sale?
No. Its economic nature depends on ownership and purpose. It can be an own-wallet movement, payment, collection, swap, contribution or another transaction.
Does DAC8 replace CARF?
DAC8 brings crypto reporting into the EU tax cooperation framework and draws from the international CARF model. Each has its own legal instrument and scope; the business still needs detailed records behind provider aggregates.
Can a US LLC use both EU and US exchanges?
Yes, provided each account belongs to the LLC and meets the relevant provider requirements. Keeping functions and records separate makes the multi-provider structure easier to operate.
Can Exentax structure banking, exchanges and wallets together?
Yes. We coordinate the entity, banking, payment processors, crypto providers and records, and support onboarding so the LLC can operate with continuity.
Three frameworks, one coherent business structure
MiCA, DAC8 and the Travel Rule do not remove the operating advantages of a US LLC or close the crypto ecosystem. They establish different rules around the provider, the transfer and the report.
When the LLC maintains one coherent identity, distinguishes its wallets, retains contracts and records each transaction by economic purpose, it can use more providers and currencies with stronger control. Regulation stops being a wall of acronyms and becomes part of an intelligible financial architecture.