Coverage

What we can verify, and what we will not claim

This page describes coverage by dimension rather than by headline number. The dated coverage list is available to your compliance and procurement teams on request.

Request the coverage list See the modules

Documents

Document classes we handle

Every class is checked for authenticity, tampering, and extractability, not just read for text.

Class	What is checked	Scope
Passport	Machine-readable zone, printed page, and chip where present.	Global issuers
National identity card	Emirates ID and GCC national cards, front and back, with chip read where available.	GCC and international
Residence permit	Residency cards and visa pages used for residency evidence.	GCC and international
Driving license	Accepted where the journey permits it as a secondary identity document.	Selected issuers
Proof of address	Utility bills, bank statements, tenancy contracts, municipality letters.	Configurable per journey
Corporate documents	Trade license, certificate of incorporation, memorandum, shareholder registers, board resolutions.	Registry dependent

Exact template counts per issuer are shared during onboarding.

Dimensions

Coverage is six separate questions

Issuing jurisdictions

Document templates are maintained per issuer and version, so a redesigned card is treated as a new template rather than a failure.

Business registries

KYB pulls from official registries and licensing authorities. Where a registry has no machine interface, the journey falls back to document-based verification with the source recorded.

Screening sources

Sanctions regimes, domestic and international PEP data, watchlists, and adverse media, with the source and snapshot date stored on every match.

Blockchain coverage

Wallet screening and transaction tracing across supported chains and asset types, with exposure categories on every result.

Languages

Capture flows in Arabic and English, with right-to-left layouts, plus additional languages configurable per journey.

Channels

Hosted flow, embedded SDK, verification links, and one-time codes over email and messaging channels.

Questions

How coverage works in practice

Why are coverage numbers not printed on this page?

Because coverage changes weekly and a headline number is not something a compliance team can rely on. We publish the current list per document class, issuer, and registry on request, dated and versioned.

What happens when a document is not supported?

The session returns a specific unsupported_document reason code rather than a generic decline, and the journey can route to a fallback path such as manual review or an alternative document type.

How are new templates added?

Unrecognized documents are captured as coverage requests with the issuer and version. Adding a template does not require a change on your side; existing journeys pick it up automatically.

Can we restrict which documents are accepted?

Yes. Each journey defines its accepted document classes and issuers, so a UAE-only product does not accept documents that fall outside its policy.

Send us your document mix

Give us the nationalities and document types in your book and we will tell you exactly what is covered today.

Book a demo Request sandbox