MiCA Stablecoin Compliance Status — Which Tokens Pass, Warn, or Get Blocked?
Historical snapshot. Every figure, verdict and score in this article is a record of one compliance_preflight run on 18 March 2026. It has not been updated since and does not describe the current status of any token. For a current answer, run the preflight again.
MiCA has been fully applicable since 30 December 2024; transitional provisions for certain crypto-asset service providers under national regimes ended 1 July 2026 (subject to Member State extensions under Art. 143). We ran compliance preflight checks on the five most relevant stablecoins using FeedOracle evidence data.
The compliance preflight: PASS, WARN, or BLOCK
Every data point in this article comes from a FeedOracle compliance_preflight API call made on 18 March 2026. Each response was cryptographically signed (ES256K) and timestamped at generation time.
PASS, WARN and BLOCK are policy classifications, not regulatory determinations. They report how the evidence found maps onto a configurable policy rule set; the same evidence classifies differently under a different policy. They are not a statement by any regulator, and FeedOracle is not a supervisor, auditor or certification body. The current API expresses the same layer as allow, review and exempt, alongside the register evidence each is derived from.
| Token | Verdict | Grade | Score | Custodian | SIFI | Peg |
|---|---|---|---|---|---|---|
| USDC | PASS | A | 87.4 | BNY Mellon | Yes | $0.999932 (-0.007%) |
| EURC | PASS | A | 81.7 | BNY Mellon | Yes | — |
| USDT | BLOCK | A | 76.7 | Cantor Fitzgerald | No | $1.000048 (+0.005%) |
| RLUSD | WARN | B | 73.9 | Standard Custody | No | — |
| DAI | WARN | C | 50.0 | Unavailable | — | — |
fo-51a287ae5949 (USDC) · fo-ecd9d2a5c6e2 (EURC) · fo-edb576969064 (USDT) · fo-d11143934224 (RLUSD) · fo-f5fae707636c (DAI).
These identify the responses that produced the table. FeedOracle does not retain MCP tool responses server-side, so a request ID cannot be looked up here. A signed response you hold can be verified client-side against the public key at /.well-known/jwks.json (kid
feedoracle-mcp-es256k-1).
USDC and EURC: The only two that pass
Both Circle tokens — USDC and EURC — clear the compliance preflight with a PASS verdict and Grade A. The key differentiator: both use BNY Mellon as custodian, a globally systemically important financial institution (SIFI). Under DORA Article 28, SIFI custody significantly reduces counterparty risk. USDC holds an evidence score of 87.4, EURC follows at 81.7.
USDC maintains a peg deviation of just 0.007% — well within MiCA Article 35 requirements for continuous peg maintenance. Circle's MiCA authorization status is verified against the ESMA register.
decision: PASS
evidence.score: 87.4 · grade: A
custody.custodian: BNY Mellon · sifi: true
peg_deviation: -0.0068% · art35: PASS
confidence: 100% · signed: ES256K
USDT: no EU register entry found at time of lookup
The biggest stablecoin by market cap received a BLOCK classification under the policy used for this run, from reason code MICA_NOT_AUTHORIZED — which records that no EU e-money-token register entry for the issuer was found at time of lookup, not that any authority has withheld or refused authorisation. Despite a reasonable evidence score of 76.7 (Grade A) and a stable peg, Tether's USDT is flagged because it lacks MiCA authorization in the ESMA/EBA registers.
The custody situation adds to the risk profile. Cantor Fitzgerald is the custodian — a reputable firm, but not classified as SIFI, which raises the custody risk level to MEDIUM under DORA Article 28 criteria.
For compliance teams: a BLOCK verdict means any EU-regulated entity using USDT for settlement, treasury, or trading operations should have a documented risk assessment and a contingency plan before July 2026. The peg may be stable, but authorization status is binary — and USDT currently fails that check.
RLUSD: Promising, but pending
Ripple's RLUSD receives a WARN verdict with reason code MICA_PENDING_OR_UNKNOWN. The evidence score of 73.9 (Grade B) is respectable, and Standard Custody & Trust provides low-risk custody. The issue: MiCA authorization is pending or not yet verified in public registers.
RLUSD is worth monitoring. If Ripple secures MiCA authorization, this token could move from WARN to PASS relatively quickly given its otherwise solid evidence profile.
DAI: The decentralized challenge
DAI presents the most complex picture. The verdict is WARN with two reason codes: MICA_PENDING_OR_UNKNOWN and CUSTODY_UNAVAILABLE. The evidence score drops to 50.0 (Grade C) and confidence falls to just 53%.
As a decentralized stablecoin, DAI does not have a traditional custodian — which makes MiCA compliance structurally different from centralized tokens. The regulation was primarily designed for asset-referenced tokens with identifiable issuers. Algorithmic and decentralized stablecoins face an uncertain regulatory path.
What this means for compliance teams
With MiCA enforcement starting in July 2026, the practical implications are:
If you hold USDC or EURC — your compliance position is strong. Both tokens pass the evidence-based preflight check with Grade A scores and SIFI custody. Document this as part of your MiCA compliance evidence file.
If you hold USDT — you need a plan. The BLOCK verdict does not mean the peg is unstable. It means MiCA authorization is missing. Depending on your jurisdiction and use case, you may need to document a risk acceptance, set up a transition plan, or restrict USDT usage in EU-regulated operations.
If you hold RLUSD or DAI — monitor closely. Both are in a grey zone. RLUSD may resolve positively if authorization comes through. DAI faces deeper structural questions about decentralized token classification under MiCA.
Run your own compliance preflight
Every data point in this article was generated by the FeedOracle MCP — 27 compliance tools available to any AI agent or compliance workflow. Cryptographically signed, verifiable in 30 seconds.
Connect to FeedOracle MCP →Methodology
All data was collected on March 18, 2026 using the FeedOracle compliance_preflight and peg_deviation MCP tools. Each API response is signed with ES256K (RFC 7515), includes a SHA-256 content hash, and can be independently verified via the JWKS endpoint at feedoracle.io/.well-known/jwks.json.
Evidence sources include the ESMA Stablecoin Register, EBA authorization records, on-chain peg data, and FeedOracle's multi-source risk scoring model covering custody, reserve quality, market depth, and asset registry dimensions. Confidence scores reflect the completeness and freshness of available evidence.
This analysis is based on available evidence and does not constitute legal or financial advice. Regulatory status may change as MiCA implementation progresses. We recommend refreshing compliance checks regularly.