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

By Phone Number

1. Select the country code (by flag) from the drop-down.
2. Enter the user's phone number.
3. Click "Proceed to Product."
4. Tap Select to Product as Proof.
5. Select Device (transaction delivery method).

6. Tap Email/SMS.
7. Choose Document from the dropdown.
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.

11. The Proof Details screen displays.

By Email

1. Enter the user's email.
2. Click "Proceed to Product."
3. Tap Select to Product as Proof.
4. Select Device (transaction delivery method).

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

🚧

We recommend switching to a mobile device for better experience.

9. Click Continue on Mobile Device.

10. The Proof Details screen displays.

🔐 Comparing Privacy Key to Existing Verified Accounts

In scenarios where the user has been previously enrolled with Privacy Key, the Proof transaction can offer additional insights by comparing the current identity data with existing verified identities.

This is particularly useful when:

• A user who enrolled with Privacy Key under a different organization is being verified again.
• There's a need to confirm if two different Proof attempts belong to the same individual.

If the Proof transaction is performed with Privacy Key enabled, the system can:

• Automatically detect if the same Privacy Key is already associated with another Verified Account.
• Provide context to determine if this is the same person, even if identifiers differ (e.g., new email or phone number).

💡

This comparison does not overwrite or merge existing accounts. It is used strictly for contextual identity verification and decision-making.

This feature allows administrators and systems to make better decisions about onboarding, re-enrollment, or potential duplicate accounts — improving both security and user experience.