EU Financial Entities: MiCA, PSD2 & Insurers Register avatar

EU Financial Entities: MiCA, PSD2 & Insurers Register

Pricing

from $2.10 / 1,000 entity returneds

Go to Apify Store
EU Financial Entities: MiCA, PSD2 & Insurers Register

EU Financial Entities: MiCA, PSD2 & Insurers Register

Pricing

from $2.10 / 1,000 entity returneds

Rating

0.0

(0)

Developer

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Share

EU Financial Entities Register - MiCA, PSD2 and Insurers

EU Financial Entities Register puts three official EU registers in one clean table: MiCA crypto-asset service providers (CASPs), token issuers, white papers and non-compliant entities (ESMA), payment and e-money institutions under PSD2 (EBA) and insurance undertakings (EIOPA). One row per entity with LEI, home country, competent authority, services, passporting countries, authorisation dates, status and a cross-register LEI match (other_registers); a delta mode returns only what changed - new licences, withdrawals, new passports.

What data you get

About 11,900 entities (counts of 24 Oct 2026):

RegisterSourceWhat it coversEntities
esma_micaESMA interim MiCA registerCrypto-asset service providers, EMT and ART token issuers, white-paper offerors, non-compliant entities~1,670
eba_psd2EBA register of payment and e-money institutions (PSD2)Payment institutions, e-money institutions, exempted institutions, account information service providers, branches (agents excluded)~6,640
eiopaEIOPA register of insurance undertakingsInsurance undertakings: domestic, third-country branches and cross-border (passported) activity~3,570
FieldDescription
register, register_familyEntity type (e.g. mica_casp, eba_emoney_institution, eiopa_insurance_undertaking) and source register
entity_keyStable key for joins and change tracking
name, commercial_name, national_idLegal name, trade name and national reference code (EBA, EIOPA)
lei, lei_sourceLEI as published (register) or matched by name and country from another register (name_match)
home_country, competent_authorityHome Member State and the authority that authorised the entity
address, city, postal_code, websiteAddress data as published (city and postal code: EBA, EIOPA)
authorisation_date, authorisation_end_date, statusauthorised, withdrawn, notified (white papers) or warning (non-compliant)
services, service_labelsMiCA services, PSD2 service codes with labels (PS_03C = Credit transfers), or insurance status (domestic, third_country_branch)
passporting_countries, branch_countriesWhere the entity operates outside its home country
other_registersOther registers in which the same LEI appears
source_status, source_updated_at, quality_flagsFreshness of the source, its own update time and data-quality flags
first_seen_at, last_seen_at, change_type, changed_fields, previous_valuesDelta tracking

Why use it

🧩 Three registers, one schemaESMA CSVs, the EBA 220 MB JSON and the EIOPA export are normalised into the same fields.
🔗 LEI crosswalkother_registers shows when the same LEI appears in another register (e.g. a CASP that is also an e-money institution). EBA entries (no LEI in the source) get an LEI when ESMA publishes the same name and country (lei_source = name_match).
🌍 Passportingpassporting_countries and branch_countries: filter "who can operate in Spain".
🔔 Change feeddelta returns only new, changed (changed_fields, previous_values) and removed entities; unchanged entities are free.
🧹 CleanISO dates, validated LEIs, service labels, quality_flags. Rows are flagged, never dropped.

Snapshot vs delta: what each mode returns and charges

ModeKindWhat you getWhat is charged
Snapshotfull list in scopeEvery entity that matches your filters, on every runentity-record per row
Delta (default)changes only1st run: everything in scope as baseline. Later runs: only new, changed and removed entities since your last run1st run: entity-record per row. Later runs: entity-change per changed row only. Unchanged entities are never charged; if no register changed, the run returns nothing and costs only the start fee

Each combination of filters keeps its own change stream (in a named key-value store, eu-fin-entities-state, in your Apify account), so a filtered run never consumes the changes another run should see.

Use cases

  1. KYB / onboarding - banks, fintechs, marketplaces and payment partners: check that a counterparty holds a MiCA, PSD2 or insurance authorisation and in which countries.
  2. Compliance monitoring - schedule delta weekly to catch withdrawals, new warnings (mica_non_compliant) and changes for your counterparties.
  3. B2B sales and partnerships - RegTech, KYC, custody, core banking and payment-processing vendors: every newly authorised CASP, EMI or insurer, by country.
  4. Market intelligence - count CASPs by home country, services and passporting; map the EU payment, e-money and insurance landscape.
  5. Data enrichment - join to your CRM by lei or national_id.

How to use

  1. Keep the pre-filled values and click Start: 10 MiCA crypto-asset service providers that can operate in Spain, about $0.05.
  2. Choose Registers (all three by default), Entity types, Home countries, Operating in or Name contains to change the scope. Clear the filters and set Max rows to 0 to get everything (~11,900 entities).
  3. For monitoring, switch Mode to Delta and add a weekly schedule.

Input

FieldTypeDescription
modeenumdelta (default when empty) or snapshot
registersarrayesma_mica, eba_psd2, eiopa. Default: all three
entityTypesarraye.g. mica_casp, eba_emoney_institution, eiopa_insurance_undertaking
countriesarrayHome Member State codes
passportingToarrayCountries where the entity operates (passport or branch)
nameContainsstringText search in the names
includeWithdrawnbooleanInclude ended authorisations (default on)
maxItemsintegerRow limit and spending cap (pre-filled 10; 0 = none)
stateKeystringName of an independent change-tracking stream
proxyConfigurationobjectFallback proxy for ESMA and EIOPA (default: Apify Residential, Germany)
{ "mode": "delta", "registers": ["eba_psd2"], "entityTypes": ["eba_emoney_institution"], "countries": ["LT", "MT"] }

Proxy (proxyConfiguration)

ESMA and EIOPA answer HTTP 403 to cloud (datacenter) IP addresses. For each of them the Actor sends the request directly first and, only if it is refused, repeats the same request through the proxy you configure here. The default is the Apify Residential proxy in Germany (EU), which needs no setup. The EBA register is always fetched directly.

  • Cost: proxy traffic is included in the Actor's price; you only pay the events below. The EIOPA register is a large export (about 58 MB) that has to go through the residential proxy, so a run that needs it is charged one insurance-register-download event ($0.10) once per run. It is only downloaded when it can contribute rows: leave eiopa out of Registers, or filter Entity types to MiCA / PSD2 types, and it is skipped (and not charged). If your spending limit does not cover that event, the insurance register is skipped and reported in RUN_SUMMARY.
  • Different country or group: choose another proxy in the field (for example another EU country) if you need to.
  • No proxy: if you disable the proxy, ESMA and EIOPA cannot be fetched; the run finishes as completed_partial and tells you in RUN_SUMMARY (source.blocked).

Output example

Real MiCA row (run of 24 Oct 2026, lists shortened here):

{
"entity_key": "esma:CASPS:AT:254900ERDZ4CZ5IF7P56",
"register": "mica_casp",
"register_family": "esma_mica",
"lei": "254900ERDZ4CZ5IF7P56",
"lei_source": "register",
"name": "WB-Shields Innovations GmbH",
"commercial_name": "WhiteBIT EU",
"national_id": null,
"home_country": "AT",
"competent_authority": "Austrian Financial Market Authority (FMA)",
"address": "Stella-Klein-Löw-Weg 8 1020 Vienna, Austria",
"city": null,
"postal_code": null,
"website": "https://whitebit.eu",
"authorisation_date": "2026-06-18",
"authorisation_end_date": null,
"status": "authorised",
"services": [
"a. providing custody and administration of crypto-assets on behalf of clients",
"c. exchange of crypto-assets for funds"
],
"service_labels": [
"a. providing custody and administration of crypto-assets on behalf of clients",
"c. exchange of crypto-assets for funds"
],
"passporting_countries": [
"AT",
"BE",
"BG",
"CY",
"CZ",
"DE",
"..."
],
"branch_countries": [],
"white_paper_url": null,
"notes": null,
"is_name_redacted": false,
"quality_flags": [],
"other_registers": [],
"source": "ESMA interim MiCA register",
"source_url": "https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica",
"source_updated_at": "Thu, 22 Oct 2026 15:16:00 GMT",
"source_status": "current",
"first_seen_at": "2026-10-24T21:11:33Z",
"last_seen_at": "2026-10-24T21:11:33Z",
"detected_at": "2026-10-24T21:11:33Z",
"change_type": "baseline",
"changed_fields": [],
"previous_values": null
}

Real insurance row (EIOPA):

{
"entity_key": "eiopa:AT:116",
"register": "eiopa_insurance_undertaking",
"register_family": "eiopa",
"lei": "529900B0OFX1G2LS5L25",
"lei_source": "register",
"name": "UNIQA Österreich Versicherungen AG",
"commercial_name": "UNIQA Oesterreich Versicherungen AG",
"national_id": "116",
"home_country": "AT",
"competent_authority": "Finanzmarktaufsicht (FMA)",
"address": "Untere Donaustraße 21",
"city": "Wien",
"postal_code": "1029",
"website": "www.uniqa.at",
"authorisation_date": "1991-01-01",
"authorisation_end_date": null,
"status": "authorised",
"services": [
"domestic"
],
"service_labels": [
"domestic"
],
"passporting_countries": [
"BE",
"BG",
"CY",
"CZ",
"DE",
"DK",
"..."
],
"branch_countries": [],
"white_paper_url": null,
"notes": null,
"is_name_redacted": false,
"quality_flags": [],
"other_registers": [],
"source": "EIOPA Register of insurance undertakings",
"source_url": "https://register.eiopa.europa.eu/registers/register-of-insurance-undertakings",
"source_updated_at": "2026-10-24T21:12:37Z",
"source_status": "current",
"first_seen_at": "2026-10-24T21:12:09Z",
"last_seen_at": "2026-10-24T21:12:09Z",
"detected_at": "2026-10-24T21:12:09Z",
"change_type": "baseline",
"changed_fields": [],
"previous_values": null
}

Key fields

FieldDescription
register, register_familyEntity type and source register
lei, lei_sourceLEI as published (register) or matched by name and country (name_match)
statusauthorised, withdrawn, notified (white papers), warning (non-compliant)
services, service_labelsMiCA services, PSD2 service codes (PS_03C -> Credit transfers) or insurance status
passporting_countries, branch_countriesWhere the entity operates outside its home country
other_registersOther registers in which the same LEI appears (only registers fetched in the run)
source_statuscurrent, or stale_source_blocked if the entity's register could not be fetched in this run and the last known data of your stream was kept
quality_flagsinvalid_lei, lei_inferred_by_name, multiple_names_in_source, no_legal_form_in_name, possible_natural_person_redacted, no_home_record (EIOPA: cross-border activity without a home record), duplicate_in_source. Rows are flagged, never dropped

Personal data

PSD2 agents (about 325,000 entries, many of them individuals) are not included. Some registers also admit natural persons (exempted payment institutions, excluded activities, white-paper offerors, warnings). In those registers, an entry without LEI whose name looks like a person's has its name, address and national ID set to null and is flagged possible_natural_person_redacted. Authorised payment and e-money institutions, CASPs, issuers and insurers are legal persons by law and are only flagged when the name shows no legal form.

Pricing

Pay per event. Tier discounts: Silver -15 %, Gold and above -30 % (Free plan +15 %).

EventPrice (Bronze)
entity-record - one entity in a snapshot or baseline$3.00 / 1,000
entity-change - one new / changed / removed entity in delta$5.00 / 1,000
insurance-register-download - EIOPA register fetched in this run (only when insurers are requested)$0.10 per run
Actor start$0.01 per run

Only returned rows are billed; unchanged entities in delta are free, and a delta run where no register changed costs only the start fee. The pre-filled example (10 MiCA CASPs) costs about $0.04; 200 MiCA CASPs operating in Spain about $0.61; all registers (~11,900 entities) about $36.10 (including the one-time insurance register download). A scheduled delta run that includes insurers costs $0.11 when nothing changed. Max rows caps what a run can bill.

Sources, licences and limits

  • ESMA interim MiCA register (page). ESMA plans to move the interim CSV register into its IT systems; the Actor stops with source_format_changed rather than returning wrong data if the files change.
  • EBA Register of payment and electronic money institutions under PSD2 (register). The EBA states the register "has no legal significance and confers no rights in law"; national registers prevail. EBA material may be reproduced provided the source is acknowledged.
  • EIOPA Register of insurance undertakings (register). Reproduction is authorised provided EIOPA is acknowledged as the source; national registers prevail.
  • If a register still refuses the request after the proxy retry (or the proxy is disabled), the run continues with the other registers, keeps the last known data of that register in your stream (no false removals), marks its rows source_status: stale_source_blocked and reports it in RUN_SUMMARY (status: completed_partial, source.blocked). If all registers refuse, the run fails.
  • The Actor downloads public register files only: no login, no captcha solving. Not affiliated with or endorsed by ESMA, the EBA or EIOPA. Not legal advice: for a binding check use the competent national authority's register.

FAQ

Which registers are covered? ESMA (MiCA), EBA (PSD2 payment and e-money institutions) and EIOPA (insurance undertakings). The default is all three.

How often do the sources change? ESMA republishes the MiCA CSVs regularly (weekly in practice), the EBA file is regenerated several times a day and EIOPA refreshes its register regularly. A weekly delta schedule is plenty for monitoring.

Do I need to set up a proxy? No. The default (Apify Residential, Germany) works out of the box and is only used when ESMA or EIOPA refuse the direct request. See Proxy for the cost.

Is it legal to use this data? The registers are public by law and the Actor only downloads the public files. Reproduction is allowed with attribution (see Sources); entries that look like private individuals are redacted.

Why do some EBA rows have an LEI? The EBA does not publish LEIs; when ESMA lists exactly the same name in the same country, the Actor adds it and marks lei_source = name_match.

Why is other_registers empty? The cross-register match only considers registers fetched in that run (for example, not EIOPA if you filtered to MiCA types).

Are UK entities included? Only if a register still lists them; the EBA is removing UK entries.

Built by Rastriq - reliable data from official registers. Questions or feature requests: use the Actor's Issues tab.