Coverage
What is checked in each country
A country is not enabled by a single flag. Coverage is a combination of the document issuing country, the document type, the channel and the purpose. Below is the technical coverage of the platform for the first-wave countries, with limitations.
First wave
Countries whose documents the platform checks first.
| Country | Passport, MRZ | NFC chip | Company registry | Sanctions and PEP |
|---|---|---|---|---|
| RURussia | Supported | Limited1 | Being connected | Supported |
| BYBelarus | Supported | Supported | Being connected | Supported |
| KZKazakhstan | Supported | Limited2 | Being connected | Supported |
| UZUzbekistan | Supported | Supported | Being connected | Supported |
| KGKyrgyzstan | Supported | Not available3 | Being connected | Supported |
| TJTajikistan | Supported | Supported | Being connected | Supported |
| AMArmenia | Supported | Not available3 | Being connected | Supported |
| AZAzerbaijan | Supported | Supported | Being connected | Supported |
| TMTurkmenistan | Supported | Supported | Being connected | Supported |
| MDMoldova | Supported | Supported | Being connected | Supported |
Notes
- Russia: the chip is read, but the current CSCA certificates signed with SHA-1 are not accepted, so trust in the issuer is not established.
- Kazakhstan: a chain to the CSCA signed with SHA-1 is accepted only for documents of Kazakhstan, with a mark in the report.
- Kyrgyzstan and Armenia: chip reading is not performed at launch; the document is checked without NFC.
Legend
- Supported
- the capability is implemented for the country;
- Limited
- the capability is implemented with the limitation stated in the note;
- Not available
- the capability is not performed for the country, and the checks are marked in the case as not performed with the reason;
- Being connected
- the source is connected after a review of access terms; until then company details are marked as declared.
Next wave
Countries connected on customer request after document profiles are prepared and legal conditions are reviewed.
- ARArgentina
- AUAustralia
- BRBrazil
- CACanada
- CLChile
- CNChina
- COColombia
- CZCzechia
- EGEgypt
- FRFrance
- GEGeorgia
- DEGermany
- INIndia
- IDIndonesia
- ITItaly
- JPJapan
- KEKenya
- MYMalaysia
- MXMexico
- MAMorocco
- NLNetherlands
- NGNigeria
- PHPhilippines
- PLPoland
- PTPortugal
- KRRepublic of Korea
- RORomania
- SASaudi Arabia
- SGSingapore
- ZASouth Africa
- ESSpain
- SESweden
- CHSwitzerland
- THThailand
- TRTurkey
- UAUkraine
- AEUnited Arab Emirates
- GBUnited Kingdom
- USUnited States
- VNVietnam
How coverage is defined
- Coverage is a combination of the document issuing country, the document type and generation, the channel (browser or app), the purpose and the customer jurisdiction.
- Support for a passport of a country does not automatically enable its ID card or other documents.
- Before data collection starts, the applicant sees which capabilities are available for their country and which are not.
- For your organisation, the active capabilities per country are shown in the console: they depend on the approved country profile and the legal profile of the organisation.
Frequently asked questions
Does verification work for other countries?
Sanctions screening does not depend on the country. Documents of other countries are connected by country profile; tell us which countries you need.
Why is NFC not available for some countries?
A chip check needs the country certificate from an approved trust source with acceptable signature algorithms. Without such a certificate the chip gives no verifiable result.
See it on your own scenarios
Tell us who you need to verify and where. We will prepare a demo, test API access and a price estimate.