Quick Answer: Start with the legal entity that provides the crypto service, not only the name on an app. Open ESMA's MiCA page, inspect the authorized crypto-asset service provider register, and match the entity, service, home authority, relevant dates, and country information. Check the national competent authority's record as a second source, especially when a recent authorization may not yet appear in ESMA's weekly update. A brand mention, a token white paper entry, or a company registration is not proof that a particular service is authorized under MiCA.
What does MiCA authorization cover?
The EU Markets in Crypto-Assets Regulation establishes a framework for certain crypto-assets and crypto-asset services. Its rules distinguish the authorization of a crypto-asset service provider, commonly abbreviated CASP, from the publication or notification of a crypto-asset white paper. These records may appear on the same ESMA webpage, but they answer different questions. A white paper entry relates to an asset's disclosure record; it does not license every platform that offers the asset.
Article 59 of MiCA sets the general conditions for providing crypto-asset services in the EU. The framework also allows specified financial entities to provide certain services after notification under Article 60, subject to the applicable conditions. For a consumer, the practical question is therefore precise: which legal person is providing which service, and on what legal basis? “This brand is regulated” is too broad to answer it.
Authorization also has a scope. Custody, operation of a trading platform, exchange of crypto-assets for funds, exchange of one crypto-asset for another, execution of orders, and other services are separate categories in MiCA. A provider's presence in a register should lead to a second check of the authorized services. The presence of one category does not establish permission for every category offered under a shared brand.
This article explains a verification method, not the legal status of any named trading platform. A status conclusion should be based on the current official records, the relevant corporate entity, and the reader's country and service.
Step 1: identify the company behind the service
Look for the legal entity in the platform's terms, account agreement, or local service notice. Record its full registered name and, if available, a legal entity identifier, registration number, address, and the services it says it provides. A parent company, marketing brand, payment processor, and custody provider may be different legal persons. Search results that show the brand alone can therefore match the wrong company.
Pay attention to the entity that contracts with users in the EU. A global website may direct users in different countries to different group companies. If the terms list several entities, the document should state which one applies to your account and product. If that is unclear, ask the provider for the legal entity and the competent authority before interpreting a search result as an authorization.
For example, an app could show a trading brand in the header while its European terms name a subsidiary with a different legal name. A register search for the brand might return no result even when the subsidiary appears, or it might return a similarly named company with no relationship to the account. Exact-name and identifier matching reduce both errors.
Step 2: open ESMA's official MiCA register
Use ESMA's MiCA page rather than a copied list on a commercial site. ESMA publishes several files covering different record types, including authorized CASPs and non-compliant entities. Select the CASP file for an authorization check; inspect the separate non-compliant list where relevant. Do not search a white paper file and treat a matching token name as a platform licence.
Record the file's update date before using it. On 11 November 2026, the ESMA page displayed a last update of 5 November and explained that its interim register is updated weekly. The page also says information received by national authorities may not appear immediately. A screenshot without its source date is not enough to establish a current status, especially around authorization, withdrawal, or a transition deadline.
Open ESMA's field description linked beside the register. Column names may be abbreviated and the same entity may have several service rows. The field guide is the authoritative way to interpret the data structure. A reader need not become a data analyst, but should know which columns contain the entity name, country, services, authorization or notification date, and any end or withdrawal date.
Step 3: match the entity and the specific service
Search the CASP file for the exact legal name and identifier collected in Step 1. If a row appears, compare the name and country before reading its status. Common words such as “digital,” “capital,” or “markets” are not a reliable match by themselves. A different company with a similar commercial name can create a false positive.
Then inspect the listed service code and description. If the user's intended task is custody, a row for another service does not settle the custody question. If the task is exchange of crypto-assets for funds, verify that category rather than relying on a broad statement that the company appears somewhere in the register. Where the file provides country or passporting information, check the jurisdiction relevant to the user. National rules and the provider's actual contractual setup may still require further review.
Dates matter. ESMA says a withdrawn authorization can remain in the register with an effective withdrawal date. A search hit is therefore not sufficient; read any end or withdrawal field. Also compare the date of the record with the date on which the user expects to use the service. Historical authorization does not establish current authorization.
Step 4: cross-check the national competent authority
The ESMA register receives information from national competent authorities. For a recent decision, the national authority may publish a record before it appears in ESMA's next weekly file. Search the regulator named in the ESMA row or in the provider's own disclosure, using the regulator's official website. Match the legal entity, service scope, status, and decision date. Save both source URLs and the date checked.
If the national record and ESMA file appear to disagree, do not choose whichever result is more convenient. Check whether one record is newer, whether the rows refer to different legal entities, and whether the service categories match. A delay in publication, a withdrawal, or a change in corporate structure may explain the difference. When the records still conflict, ask the regulator or seek qualified advice before relying on the authorization claim.
ESMA's public statement on transitional periods specifically encourages clients to verify providers. The point of cross-checking is to establish an evidence trail, not to make a legal judgment from a single search snippet.
What if the company does not appear?
A missing search result is a reason to investigate, not an automatic finding of unlawful activity. First check spelling, corporate name changes, local affiliates, and whether a financial entity is using the Article 60 notification route. Then compare the date of the national authority's latest record with ESMA's weekly publication date. A recently authorized entity may be absent from an older central file.
At the same time, do not treat a provider's assertion that its application is “pending” as equivalent to authorization. An application, an approval in principle, a registration in an unrelated jurisdiction, and a current MiCA authorization are different facts. Ask the provider which entity and service its claim concerns, and request the official decision or register entry. A firm's marketing page is useful for locating the claim, but the regulator's record should support the conclusion.
If a warning or non-compliant entry appears, read its date, named entity, and stated basis. A warning about one group company or service should not be applied automatically to another legal person, yet it should not be ignored because a brand uses multiple entities. The check must stay entity-specific.
Does authorization mean the service is safe?
No. Authorization concerns a regulatory status and its associated obligations; it is not a prediction of returns or a guarantee that funds cannot be lost. Crypto-assets can fall in value, technology can fail, and a provider can face operational problems. The European supervisory authorities' consumer warning explains that protection depends on the asset and service and may be limited. A user should still assess custody terms, withdrawal rules, fees, complaint routes, and the risks of the asset itself.
Authorization also does not prove that every product visible on a platform is available to every EU resident. A derivatives product, payment service, or asset type may sit under a different legal framework or restriction. Match the product and jurisdiction rather than extrapolating from a general CASP row.
A reusable verification record
Keep a short record: the provider's legal name; the contractual entity shown in its terms; the intended service; your country; the ESMA file and update date; the matching row and identifier; the national authority's record; and the date you checked both. This is more useful than a screenshot of a badge saying “MiCA compliant.”
Repeat the check when a provider changes the entity in its terms, announces a new licence, expands a service, or when a register update may affect a prior conclusion. A status is time-sensitive. For content publishers, identify the observation date next to any statement about authorization so readers can tell whether it remains current.
FAQ
Is a MiCA white paper entry proof that an exchange is authorized?
No. ESMA publishes separate record types. A white paper entry concerns an asset disclosure; CASP authorization concerns a service provider and specified services. Use the relevant file for the question being asked.
Can I search only the brand name?
Use it as a starting point, but verify the legal entity in the terms and match its identifier or full name in official records. Brands and contracting companies can differ.
Why might ESMA and a national register show different dates?
ESMA says its interim file is updated weekly and national information may not appear immediately. A newer national decision or a later central publication may explain a discrepancy. Compare dates and entities before drawing a conclusion.
Does a register entry guarantee I will recover my funds if a provider fails?
No. Regulatory status does not eliminate market, custody, or operational risk. The scope of consumer protection depends on the asset and service and is not the same as a guarantee of repayment.
