Skip to main content
Coverage

The documents your customers actually present, recognised with no configuration

The coverage of a verification engine is not measured by the number of countries announced, but by its ability to process the document a customer pulls out of their pocket: a laminated card, reprinted, from an earlier generation, sometimes worn. We build our coverage document by document, generation by generation, in the field.

12
countries covered, from UEMOA to Central Africa
4
document types: ID card, passport, licence, and the CIP in Benin
2
flow languages: French and English
43 s
median verification time
Countries covered

Twelve countries, with the documents accepted for each

Filter by UEMOA membership to find the perimeter matching your obligation. The documents listed are those the platform reads and authenticates natively, with no configuration on your side. In Benin, the CIP issued by ANIP is accepted alongside the ID card, passport and licence.

12 countries · FR / EN flow
Senegal
Available
ID CARDPASSPORTLICENSE
Ivory Coast
Available
ID CARDPASSPORTLICENSE
Benin
Available
ID CARDCIPPASSPORTLICENSE
Burkina Faso
Available
ID CARDPASSPORTLICENSE
Mali
Available
ID CARDPASSPORTLICENSE
Togo
Available
ID CARDPASSPORTLICENSE
Niger
Coming soon
ID CARDPASSPORTLICENSE
Guinea-Bissau
Coming soon
ID CARDPASSPORTLICENSE
Gabon
Coming soon
ID CARDPASSPORTLICENSE
Cameroon
Coming soon
ID CARDPASSPORTLICENSE
Guinea
Coming soon
ID CARDPASSPORTLICENSE
Comoros
Coming soon
ID CARDPASSPORTLICENSE
Supported documents

What we process, and how far

Applicable checks depend on the document presented: not all of them carry a machine-readable zone or a chip. The table below sets out what is actually verified for each document type.

Checks performed by document type
CheckNational ID cardCIP (Benin)PassportDriving licence
Model and generation identificationYesYesYesYes
Structured field extractionYesYesYesYes
NPI reading (personal identification number)NoYesNoNo
MRZ readingModel-dependentNoYesNo
Check-digit validationModel-dependentNoYesNo
Font and background consistencyYesYesYesYes
Portrait substitution detectionYesYesYesYes
Comparison with the captured faceYesYesYesYes
Screen photo and reprint detectionYesYesYesYes

“Model-dependent” flags cases where the check relies on the generation of the document issued by the State: the platform runs it where the format allows, and states explicitly in the file when it does not apply. The Beninese CIP is a single-sided certificate with no MRZ: its verification relies on reading the 10-digit NPI together with the visual and biometric checks.

Document checks

What the platform examines on a document

Every check is logged separately with its result. A rejection therefore says which check failed, so your teams can decide and your customer can understand.

Model and integrity
The document is matched against the official model expected for that country and generation: dimensions, field positions, typography, background patterns and visible security features.
Data consistency
Extracted fields are cross-checked against each other and against the MRZ where present: dates, number, name and validity, catching the inconsistencies typical of a retouch.
Portrait
The printed portrait is analysed for pasting or substitution, then compared with the face captured live by the customer.
Physical medium
Glare, texture and image noise make it possible to rule out screen photographs, colour photocopies and reprints.
Validity
Issue and expiry dates checked against the processing date, with configurable handling of expired documents according to your policy.
Duplicate flags
Documents already presented within your perimeter are detected, surfacing reuse and multiple-registration attempts.
Extending coverage

How a country enters the perimeter

We do not add a country on the strength of a single reference image. Adding one follows a sequence that takes a few weeks and ends with measurement on real cases.

  1. Collecting modelsA survey of the document generations in circulation, their variants and their security features, with local partners and your own samples.
  2. Modelling and checksBuilding the reading model, defining which checks apply and which do not, then calibrating thresholds on authentic documents and known forgeries.
  3. Field testingValidation on real captures, in field conditions: variable lighting, entry-level handsets, worn documents, unstable connections.
  4. Go-live and monitoringProgressive rollout, measurement of acceptance and rejection rates by reason, then adjustments. Recognition failures stay logged and feed the next iterations.
Flow and languages

A flow your customers understand

Document coverage is only worth something if the flow stays readable for the person following it, whatever their device.

Capture interfaces in French and English, selected per customer
Short, illustrated instructions suited to a first-time user
Works on entry-level handsets and unstable connections
Flow resumes at the last validated step after a drop
Explicit failure messages, giving the next step rather than an error code
Frequently asked

What we are asked about coverage

Can a document from a country outside the perimeter be processed?

It can be collected and routed to human review with its capture, but it does not benefit from automatic authenticity checks. We say so explicitly rather than issuing an opinion the file would not support.

How do we request a new country?

Raise it during scoping: we assess the expected volume, the availability of document models and a realistic integration timeline, then we give you a date.

Is the Beninese CIP accepted in the same way as an ID card?

Yes. The personal identification certificate issued by ANIP is recognised natively in Benin: the platform reads the 10-digit NPI and the civil-status fields, checks the visual consistency of the document and compares the portrait with the captured face. Just declare the “cip” document type when creating the verification.

Are older card generations accepted?

Yes, where they are still in circulation and still valid. That is precisely the point of our collection work: coverage that ignores earlier generations rejects legitimate customers.

Is an NFC chip needed for a good level of assurance?

No. Chip reading strengthens assurance where available, but most documents in the zone do not carry one: assurance then rests on medium analysis, the MRZ where present, and face biometrics.

Next step

Let’s test coverage on your own cases