Public Register Integration
Public register integration is an additional identity verification control used within Evrotrust's e-Identification products to reconcile, validate, and, where legally permitted, correct user identity data captured during the remote identification process.
This is a pure backend process — completely invisible to end users. It requires no customer interaction, no additional steps, and adds no friction to the identification flow.
This control improves data accuracy, reduces residual identity risk, and supports regulatory-grade assurance in jurisdictions where authoritative public registers are available.
⚡ At a Glance:
- What it is: Backend verification against government identity registers
- User experience: Completely invisible — no additional steps, forms, or delays
- When it runs: Automatically during identification, between document and biometric checks
- Processing time: Miliseconds (real-time)
- Result: Single unified identification outcome with enhanced data accuracy
- Availability: Bulgaria, North Macedonia, Moldova
- Integration effort: Zero — it's already embedded into our solution
Why public registers are used
During remote identification, user identity data is primarily obtained from:
- identity documents (OCR, MRZ, NFC), and
- biometric verification (face match and liveness).
Public registers act as an authoritative reference source to:
- detect inconsistencies between captured data and official records,
- confirm the current validity of identity attributes, and
- eliminate common data capture errors (e.g. transliteration ).
This is particularly relevant for AML/KYC regulated onboarding, and qualified trust services, where incorrect identity data has legal and compliance implications.
Supported countries
Evrotrust currently has public register integrations in the following countries:
| Country | Register type | Availability |
|---|---|---|
| Bulgaria | (1) National civil and identity register; (2) Trade register for legal person identification flow | Available |
| North Macedonia | National population and identity register | Available |
| Moldova | National population register | Available |
ℹ️ Public register integrations are implemented only where legally permitted and technically reliable. Availability depends on local regulatory frameworks and agreements with the competent authorities.
How public registers are used?
Public registers are used as a verification and reconciliation layer, not as a primary data source. This process runs entirely in the background during the identification flow, with no user-facing elements.
Data reconciliation
During identification, identity attributes captured from the user are sent against public register data automatically and transparently and all ID document data is retrieved back from the register:
- Full data list from the presented data attributes on the ID document
- Picture of the user in high-resolution (where available)
- Lost and stolen flag check
- Death status check
Position in the e-Identification flow
Typical flow:
- ID document capture and validation (OCR / MRZ / NFC)
- Public register check (where available)
- Face biometrics and liveness detection
- Final identification decision
- Identification result returned
This sequencing ensures that register checks will enable the best verification of identity data.
Position in the e-Signatures flow
Typical flow:
- Prior to issuing of qualified certificate for the user.
- Any time the user confirms eSign of documents.
Integration notes
No additional API parameters or SDK setup are required.
Availability depends on:
- the user’s country issuer of the ID document,
Partners always receive a single, unified identification result, regardless of whether a public register check was performed.
🚀 Zero user friction: Public register checks happen server-side in miliseconds. Your users never see additional forms or any indication that a government database lookup occurred. The identification flow remains smooth and uninterrupted.
Frequently Asked Questions
What happens if the government database is unavailable?
Evrotrust has fallback mechanisms in place:
- Manual verification workflow with trained operators in e-Identification flows, except of Evrotrust Ident Lite Basic.
How fresh is the data from public registers?
Data is retrieved in real-time from government databases. Each verification query fetches the current status directly from the source system. There is no caching of government data.
Will this service be available in other countries?
Evrotrust is actively working on expanding to additional countries in the Balkans and Eastern Europe. Contact our sales team to express interest in specific countries or to discuss custom integration opportunities.
Updated 15 days ago