What the EBA decided
On October 14, the European Banking Authority classified USDC, issued in the EU by Circle Internet Financial Europe SAS, as a significant e-money token under the Markets in Crypto-Assets Regulation. The EBA says 45 e-money tokens are currently notified under MiCA and USDC is the first to receive the significant classification. These are the regulator’s reported facts; the engineering and operating conclusions below are Ineeza analysis.
Dual supervision begins on November 12, 2026. Direct responsibility for own funds, reserve assets, liquidity requirements, and recovery and redemption plans transfers from France’s Autorité de Contrôle Prudentiel et de Résolution to the EBA. The ACPR retains responsibility for areas including governance, qualifying holdings, fit-and-proper assessment, outsourcing, and conflicts of interest.
The EBA also says it signed a memorandum of understanding with the New York State Department of Financial Services to support supervision of cross-border stablecoin activity. USDC is issued in the EU by Circle Internet Financial Europe SAS and in the United States by Circle Internet Financial, LLC.
Dual supervision needs one versioned control map
Ineeza analysis: the classification does not replace one supervisor with another. It creates a split control plane. Reserve and liquidity evidence may answer to the EBA while outsourcing, governance, and conflicts remain in the ACPR perimeter. A single incident—such as a reserve-service outage—can cross both domains.
Operators should maintain a versioned responsibility map that binds each obligation to its owner, system of record, evidence producer, review cadence, escalation route, and receiving authority. Controls should be mapped by regulatory outcome rather than copied into separate regulator-specific checklists. Otherwise the same event can acquire conflicting definitions, timestamps, and remediation status in parallel reporting pipelines.
Redemption evidence becomes a production data product
Ineeza analysis: own funds, reserves, liquidity, recovery, and redemption are not only periodic compliance topics. They depend on production state across issuance and burn records, bank and custody positions, customer claims, settlement cutoffs, and exception queues. Supervisory evidence is only as reliable as the joins between those systems.
Teams should define reconciled state transitions for minting, redemption request, funds movement, token burn, completion, rejection, and timeout. Each transition needs stable identifiers, source timestamps, legal-entity context, and lineage back to authoritative records. Daily aggregates are insufficient when an investigator must reconstruct which claim existed, which reserve movement supported it, and who approved an exception at a specific point in time.
A shared token does not erase the legal-issuer boundary
The EBA’s announcement explicitly distinguishes the EU and US issuers and links cross-border supervision to information exchange with NYDFS. It does not say that the memorandum merges the two regulatory perimeters or makes one authority responsible for every USDC activity worldwide.
Ineeza analysis: wallets, exchanges, payment processors, and treasury systems should not infer compliance treatment from the USDC asset symbol alone. Transaction records need the product, customer, issuer, jurisdiction, reserve claim, and redemption route that actually apply. Routing and disclosure rules should consume that context from a governed source, and ambiguous cases should fail into review rather than default to a convenient jurisdiction.
The November handoff is a change-management event
The EBA says it assesses significance annually and that significant e-money tokens remain under dual EBA and national supervision. The November 12 transfer therefore starts an operating model that must support continuing assessment and cooperation, not a one-time filing.
Ineeza analysis: before the handoff, operators should freeze the applicable control inventory, test evidence delivery end to end, reconcile open findings, and record which authority owns each unresolved item. Afterward, changes to reserve providers, redemption workflows, outsourcing arrangements, or incident thresholds should trigger impact analysis across both supervisory domains. A dated, approved control baseline is the rollback point when responsibilities or reporting formats change.
Ineeza’s view
USDC’s classification is material because MiCA’s significant-token regime is moving from framework design into live stablecoin operations. The durable engineering lesson is that regulatory structure becomes system architecture: legal-entity context, reconciled redemption state, evidence lineage, incident routing, and control ownership must agree. Teams that model those boundaries explicitly can adapt to dual supervision without fragmenting the operational truth they need to prove compliance.