LEI Price Check Methodology

Ranking

The default ranking first checks provider eligibility for the selected country, action and term. It then prefers country-specific rows over provider-global fallback rows. Within those tiers, sortable price columns use estimated requested-currency amounts where FX data is available, while the provider's native listed price remains the source of truth.

Native price first

The provider's native price is never replaced by an FX estimate. If a provider only has EUR or USD evidence for a country whose default currency is different, that row can show an estimated local equivalent for comparison, but it is still treated as a provider-native foreign-currency quote rather than a verified local-currency offer.

Two-tier coverage

The comparison table can include two kinds of reviewed price rows. Tier one is country-specific pricing: a provider publishes a price for the selected country, ideally in that country's default currency. Tier two is provider-global pricing: a provider publishes a global or broad-market quote in USD, EUR, GBP or another native currency and appears eligible to serve the selected jurisdiction. Tier two rows improve provider coverage, but they do not become local-currency claims.

For providers with many country/currency variants, the data engine should first discover the provider's global default prices, then audit localized pages, hreflang alternates, sitemap URLs, country selectors, currency selectors, public JavaScript bundles and public API clues. A localized row replaces a global fallback only when the localized price source passes evidence checks.

Data engine

Country and default-currency coverage is generated from structured country data. GLEIF issuer and registration-agent candidates are refreshed from GLEIF's API. Provider price pages and provider-level currency audits are checked for availability, content changes, currency hints, price-like snippets, localized URL clues and public API hints. Active offer rows are generated only from configured provider price sources whose evidence and parser checks pass.

The data pipeline stores source observations separately from generated comparison rows. This keeps provider discovery, source health, local-currency coverage and public offer rows auditable instead of blending them into one manually edited dataset.

Completeness

A country page is complete enough for local-currency claims only when at least one reviewed provider source publishes a country-specific price in that country's configured default currency. Countries with only EUR, USD, GBP or other global fallback data can still be useful with FX estimates, but they should not be described as complete local-currency comparisons.

Source rules

Source checks use public pages, public registries, provider-supplied information or partner feeds that are intended for publication. We do not create final price rows from private checkout sessions, account-only discounts, payment-card steps, user-specific offers or hidden API responses unless the provider authorizes publication.

Registration agents

Many commercial LEI checkout flows are registration agents or intermediaries partnered with accredited LEI issuers. The site can list registration agents when they publish public pricing, but issuer status and registration-agent status are shown separately where known.

Manual review

Provider identities and candidate registration agents can come from public registries, but active price rows must have source evidence. Rows marked stale or needs review should not be used for cheapest-price claims.

Corrections

Providers can ask for source corrections, stale row review or profile updates. Disputed rows can be downgraded to needs review or stale while source evidence is checked.

How LEI Price Check ranks providers