One Solution for Every Customer Identification Scenario.

Ways a customer verifies

Four routes in, one set of rules behind them.

A customer uses whichever way of confirming their identity is available to them.A customer uses whichever way of confirming their identity is available to them.

1. A digital identity wallet

   Cryptographically signed personal data and attestations, verified and parsed before it reaches you.

2. mObywatel

   Data from state registers, fetched after the customer approves the request in the app.

3. A chip in a passport or card

   Read over the phone's antenna, with the issuing country's signature checked against official trust lists.

4. A physical document

   Read from photos of the identity document, then checked for authenticity and consistency of the data.

Ways you can integrate

Five ways in, one final result back.

Pick the integration that matches how much of the interface you want to own.Pick the integration that matches how much of the interface you want to own.

• Hosted link
• Web iFrame
• Mobile SDK
• REST API
• Webhook

Assisted and in person

For customers who are not doing this alone.

Not every verification happens on a customer's own phone, and the same engine sits behind the ones that do not.Not every verification happens on a customer's own phone, and the same engine sits behind the ones that do not.

1. An assisted video call

   An adviser sees the document and face scores inside the call window while they talk the customer through it.

2. A scanner at the counter

   Hardware at a desk feeds captures into the identity verification engine.

3. A mobile adviser in the field

   Captures taken on an adviser's own device sync into the same queue as everything else.

4. One view across every scenario

   Verifications from every desk, device and channel land in one place rather than in separate systems.

Assisted video and counter hardware are delivered with partners. The models that read documents and match faces are our own.

What runs on the evidence

The areas of identity verification.

What the customer provides is analysed across several areas.What the customer provides is analysed across several areas.

1. Reading the document

   The data on the document is read and compared against itself, so an inconsistency or alteration shows.

2. Proving it is genuine

   Structural, logical and cryptographic checks separate a real document from a print, a screen or a forgery.

3. Matching the living face

   The live capture compared with the portrait from the document, the chip or the credential.

4. Proving a person is there

   Liveness checks, including depth from a brief movement and injection detection.

How the decision is made

Your risk appetite, not ours.

The system runs the checks. Where the line sits between pass, refer and fail is yours to set and change.The system runs the checks. Where the line sits between pass, refer and fail is yours to set and change.

1. Decision profiles you name

   A named set of rules and thresholds, applied by product, channel, country or customer segment.

2. One verdict, with reasons

   Every atomic check reports its own status and message, and the verdict says which ones decided it.

3. A human where it matters

   The platform lets you manage the data and the processes gathered along each route.

4. A manual result change, under control

   A manual change to a verification result is marked as such, so a later reader can see who made it and why.

Where the platform runs

Three deployments, one integration.

The same platform and the same integration, wherever your policy says the data has to sit.The same platform and the same integration, wherever your policy says the data has to sit.

1. Shared, and managed by us

   Multi-tenant and managed by us, processed inside the European Economic Area.

2. Dedicated and isolated

   An isolated database and an independent container environment, still managed and still inside the EEA.

3. On your own premises

   Installed on your own infrastructure with no outside access to the data, for policies that leave no room for a hosted service.

4. Certified either way

   ISO/IEC 27001:2022, and ETSI TS 119 461 identity proofing.