ART vs EMT: How MiCA Classifies Crypto-Assets and the Software Each Needs
ART vs EMT under MiCA explained: asset-referenced tokens, e-money tokens and other crypto-assets, their obligations, supervision and the software token issuers need to build.
Updated
4 min read
218 views
Key takeaways 5
- Three distinct MiCA token categories MiCA sorts all crypto-assets into 3 groups - ART, EMT and other crypto-assets - each carrying a different authorisation and software burden.
- ART requires reserve and authorisation ART issuers must obtain authorisation, publish an approved white paper and hold a segregated independently audited reserve backing the token at all times.
- EMT demands redemption at par EMTs must be issued by a credit institution or e-money institution and redeemed at par value on demand with a 1:1 currency reserve behind each token.
- Significance thresholds trigger EBA supervision ART or EMT crossing MiCA's significance thresholds - measured by holders, market value and transactions - shifts direct supervision to the European Banking Authority.
- Classification must precede any code Choosing the wrong category means building the wrong controls or operating without proper authorisation, so qualified legal counsel must confirm classification first.
Before you write a line of code or file an application, MiCA forces one decision: what kind of crypto-asset are you dealing with? The EU Markets in Crypto-Assets Regulation (Regulation (EU) 2023/1114) sorts crypto-assets into three groups - asset-referenced tokens (ART), e-money tokens (EMT) and other crypto-assets - and each group carries a different rulebook and a different software burden. This article explains the difference and what issuers must build for each.
It is an explainer, not legal advice. Classification is a legal call for qualified counsel, and the boundary with financial instruments under MiFID II sits outside our scope. For the full build, see our MiCA compliance software development.
The three MiCA token categories
MiCA treats a crypto-asset as a digital representation of value or rights that can be transferred and stored electronically using distributed ledger technology. Within that, three categories decide your obligations:
- Asset-referenced token (ART). References any value or right, or a combination, including one or more official currencies. A token backed by a basket of currencies, commodities or other crypto-assets is an ART.
- E-money token (EMT). References the value of a single official currency. A euro-pegged or dollar-pegged stablecoin is the textbook EMT.
- Other crypto-asset. Anything that is neither an ART nor an EMT, including most utility tokens.
ART vs EMT vs other crypto-asset at a glance
| ART | EMT | Other crypto-asset | |
|---|---|---|---|
| References | A basket of assets, rights or currencies | A single official currency | Neither |
| Typical example | Multi-currency or commodity-backed token | Euro or dollar stablecoin | Utility token |
| Issuer | Authorised issuer or credit institution | Credit or e-money institution | Any legal person, with a white paper |
| Reserve | Reserve of assets | 1:1 reserve, redemption at par | None required by MiCA |
| Supervisor | National authority, EBA if significant | National authority, EBA if significant | National authority |
| Software | Reserve attestation, redemption, disclosure | Reserve, redemption at par, reporting | White paper tooling, marketing compliance |
Asset-referenced tokens (ART)
An ART issuer needs authorisation and an approved crypto-asset white paper before offering the token to the public. The core obligations are about backing the token and letting holders get their money out.
- Issuer authorisation and an approved white paper
- A reserve of assets, segregated and independently audited, backing the token at all times
- Redemption rights for holders and a clear redemption policy
- Own-funds requirements and ongoing prudential reporting
- Ongoing disclosure of reserve composition and token metrics
E-money tokens (EMT)
An EMT is closer to electronic money. It must generally be issued by a credit institution or an authorised e-money institution, and the headline obligation is redemption at par.
- Issued by a credit institution or e-money institution
- Redemption at par value, at any time, on demand from the holder
- A reserve backing the token one-to-one with the referenced currency
- White paper and ongoing reporting
Significant ART and EMT
If an ART or EMT crosses MiCA's significance thresholds - measured by holders, market value, transactions and other criteria - it falls under direct supervision by the European Banking Authority, with higher own funds, liquidity-management and interoperability obligations. Build the reserve, stress-testing and reporting systems to that higher bar if you expect scale.
Other crypto-assets and the white paper
Tokens that are neither ART nor EMT still face rules. Offering them to the public, or seeking admission to trading, generally requires a crypto-asset white paper notified to the competent authority, fair and clear marketing communications, and issuer liability for misleading information. There is no reserve obligation, but the disclosure and marketing rules are real.
Why classification comes before code
Get the category wrong and you build the wrong control set, or worse, operate without the right authorisation. Some tokens are not crypto-assets under MiCA at all: financial instruments fall under MiFID II instead, and that boundary needs legal analysis. We do not deploy a token to mainnet without evidence that classification has been reviewed by qualified counsel.
The software each token type needs
Once classification is settled, the build follows from it: reserve management and attestation for ART and EMT, redemption-at-par flows for EMT, white paper notification and versioning for everything, and marketing-communications compliance throughout. Every control writes to one immutable audit trail so disclosure and reporting are a query, not a manual project. Budgeting a build like this follows the same drivers as any regulated software project - see our software development cost guide for how scope, integrations and compliance requirements shape the estimate.
Pharos Production builds MiCA compliance software for token issuers and CASPs. See the token taxonomy in context on the MiCA page, the full compliance checklist and the cost breakdown, or request a gap assessment. We are not a law firm: token classification must be confirmed by qualified counsel.
FAQ
Quick answers to common questions about custom software development, pricing, process and technology.
Type to filter questions and answers. Use Topic to narrow the list.
Showing all 6
No matches
Try a different keyword, change the topic or clear filters
-
An asset-referenced token (ART) references a basket of assets, rights or currencies. An e-money token (EMT) references a single official currency. EMTs must be issued by a credit or e-money institution and redeemed at par on demand, while ARTs are backed by a reserve of assets. Significant tokens of either type fall under EBA supervision.
-
It depends on what it references. A stablecoin pegged to a single official currency, such as the euro or US dollar, is normally an EMT. A stablecoin backed by a basket of currencies, commodities or other assets is normally an ART. Your counsel confirms the classification before launch.
-
An ART or EMT that crosses MiCA significance thresholds, measured by number of holders, market value, transactions and other criteria. Significant tokens are supervised directly by the European Banking Authority and face higher own-funds, liquidity and interoperability obligations.
-
Generally yes. Offering an other crypto-asset, including most utility tokens, to the public or seeking admission to trading requires a crypto-asset white paper notified to the competent authority, plus fair and clear marketing communications.
There is no reserve requirement, but the disclosure rules apply.
-
Qualified legal counsel, confirmed with the national competent authority. Pharos Production builds the software for the classification your counsel confirms. We are not a law firm and do not provide legal opinions on token classification or the MiCA and MiFID boundary.
-
Genuinely unique and non-fungible tokens are largely outside MiCA, but the substance matters more than the label. NFTs issued in a large series, or that are fungible in practice or behave like financial instruments, can fall in scope. This is a classification question for counsel.
MiCA token glossary 5
- ART
- Asset-referenced token - a crypto-asset referencing a basket of currencies, commodities or other assets to maintain a stable value under MiCA.
- EMT
- E-money token - a crypto-asset referencing a single official currency and redeemable at par, similar in function to electronic money.
- MiCA
- Markets in Crypto-Assets Regulation (EU) 2023/1114 - the EU framework classifying crypto-assets and setting issuer authorisation and disclosure obligations.
- Redemption at par
- The obligation for an EMT issuer to repay holders the full face value of the referenced currency on demand at any time.
- EBA
- European Banking Authority - the EU body that takes over direct supervision of ARTs and EMTs that cross MiCA's significance thresholds.
I work with startup founders who need a dedicated software development team but don’t want to gamble on hiring, random outsourcing, or opaque delivery.
Most founders face the same problem sooner or later.
Early technical and team decisions lock the product into tech debt, slow delivery, missed milestones and constant re-hiring. By the time this becomes visible, fixing it is already expensive.As a CTO and software architect, I help founders design, build and run dedicated development teams that work as a true extension of the startup. Not as a black-box vendor.
My focus is on complex products where mistakes are costly:
- Web3 and blockchain platforms
- FinTech and regulated products
- High-load startup systems
- MVP → scale transitions
We don’t do body-shopping.
We don’t sell generic outsourcing.Instead, we help founders:
- build the right team structure from day one
- keep technical ownership and transparency
- scale delivery without losing control
- avoid vendor lock-in and hidden risks
Teams are aligned with the product roadmap, business goals and long-term architecture. Not just short-term velocity.
