The goal of authID's "Proof" mobile biometric identity verification system is to make identity verification faster, safer, and more efficient. Using cutting-edge facial biometric technology, this service enables users to verify their identities with their mobile devices.

Proof by authID leverages biometric technology to boost security, speed up processes, and offer a dependable and efficient way to verify someone's identification remotely. This is particularly useful when traditional in-person verification techniques are utilized, which may be less secure or impractical.

📘

Proof Transaction

1. Do not include a leading zero in the mobile number.
2. Supported documents may vary depending on your setup.

Initiate a Transaction

The Transaction is a procedure or activity of user authorization, authentication, or any action involving modifications to user profiles or access rights.

1. Go to the Identity Portal and click "New Transaction."

2. There are two ways to proceed with the customer:

   • By Phone Number
   • By Email

New Transaction

By Phone Number

1. Select the country code (by flag) from the drop-down.
2. Enter the user's phone number.

By Email

1. Enter the user's email.

Select Product

1. Click "Proceed to Product."
2. Tap Select to Product as Proof.
3. Select Device (transaction delivery method).

6. Tap Email/SMS.
7. Choose a Document Type from the dropdown list.
8. Settings: By default, the run additional document verification radio button is set to OFF; set it to ON.
9. Click "Initiate Transaction." The developer options are enabled.

🚧

We recommend switching to a mobile device for better experience.

10. Click Continue on Mobile Device.

In this example we will use a two sided document:

1. 

2. 

3. 
4. The Proof Details screen is displayed.

📘

Note:

If your project does not involve a government-issued identity document, and you're planning to use a custom identity document, there's a Corporate Badge option available.

This document type allows you to use any ID card that includes a photo of the end user, making it suitable for internal or enterprise-specific identification workflows.

All standard biometric checks — including facial matching, facial liveness, and document liveness (PAD) — are performed and the corresponding signals are provided.

However, when using a custom document type, you’ll need to implement your own custom analysis logic specifically for evaluating the document PAD (Presentation Attack Detection) signal.