Skip to main content
Digital Asset Accounts in the European Economic Area (EEA) is operated by Circle France SAS, which holds transitional authorization from the AMF (France’s financial markets regulator) under the Markets in Crypto-Assets Regulation (MiCA) Article 60(4). This authorization covers custody and transfer of USDC and EURC for business end users across the EEA. Distributors serving the EEA interact with a different booking layer, additional authentication requirements, and stricter asset controls compared to the global model.

​
Circle France SAS and MiCA authorization

Circle France SAS contracts with EEA-resident end users and is responsible for MiCA compliance in the region. The AMF granted Circle France SAS transitional authorization under MiCA Article 60(4) on April 20, 2026, covering the custody and transfer of USDC and EURC across the EEA.
MiCA Article 60(4) is a transitional authorization; it does not confer full Crypto-Asset Service Provider (CASP) authorization. Retail and consumer custody services require full CASP authorization and are outside the current scope of Digital Asset Accounts in the EEA.

​
Booking patterns

Which Circle entity books an end user’s account depends on the distributor’s principal place of business and incorporation. Two booking patterns are supported: Cross-entity routing is handled automatically based on end-user residency. Distributors do not manage this directly. For more information, see Onboard EEA customers.

​
Onchain asset segregation

MiCA requires that customer assets be physically segregated onchain rather than pooled in omnibus wallets. Unlike the United States model, where the Direct End-User Custody model uses omnibus wallet structures and tracks individual balances at the record level, EEA subaccount balances are held in dedicated onchain reserve addresses operated by Circle Mint SAS. Distributors do not configure or manage asset segregation; Circle handles this automatically.

​
Platform address book

In the EEA, every external beneficiary address must be registered as a recipient address, with its wallet ownership declared, before an outbound transfer can be initiated; deposit addresses are excluded. An address becomes eligible for transfers only when it reaches active. For the address statuses and fail-closed behavior, see EEA API behavior.

​
Authentication

EEA integrations authenticate at two independent layers: mTLS identifies your platform; it doesn’t stand in for the end user’s approval. A protected operation for an EEA end user needs both. For details, see EEA API behavior.

​
Asset scope

Digital Asset Accounts in the EEA supports USDC and EURC only. Swap, earn, additional assets, and locally issued stablecoins are not available in the EEA and are fail-closed at the API level; requests for out-of-scope assets or operations return an error rather than a degraded result. For the full list of supported currencies and blockchains, see Supported currencies and blockchains.