Data quality
Regulatory data arrives imperfect. Website addresses lose their https://, schemes get mistyped, and a field meant for a URL sometimes holds a postal address. This page lists every such value in the ESMA interim MiCA register, what the tracker did about it, and the value exactly as published.
The governing rule is that nothing is ever deleted. A value that fails validation is preserved verbatim next to the corrected form, so any correction can be checked against the source. We repair what can be repaired unambiguously, and we never guess at what we cannot read.
How to read this page
Does the tracker change ESMA's data?
It repairs values that cannot be used as published. The most common case is a website address with no scheme, which no browser will open. The value as published is kept verbatim in the underlying data, and every correction appears on this page. Nothing is deleted, and no row is ever dropped: the number of authorisation records always equals the number of rows in the source register, and the build fails if it does not.
Why do some entities appear more than once?
A firm may legitimately hold more than one authorisation, and two separately named firms may share a legal entity identifier. These are listed under Observations because they look surprising, not because anything is wrong. Both records are retained.
What happens when a field cannot be interpreted?
It is preserved exactly as published and shown as plain text. The tracker never invents a URL, and it never renders a value that failed validation as a clickable link.
Is this the official record?
No. The tracker is a first-look tool. Always verify a provider's authorisation status against the ESMA interim MiCA register or the relevant national competent authority. See the methodology for how the data is collected.