Required Verifications

The Required Verifications feature allow partners to define a set of requirements that users must verify about their identity. Partner applications can create a series of required verifications and surface them for users to complete through the globaliD Connect and globaliD Web Client interfaces.

How it works

The end goal of a required verification is to encode a series of requirements for users and generate an acrc_id. This unique identifier is used to implement with the globaliD authentication APIs to surface a series of verification requirements for users.

Once a user completes the required verifications through the globaliD app or the globaliD web client, partners will be able to retrieve an authorization token. The fact that partner applications posses this token token means that the user has authenticated themselves, and partners can be sure that that user was the one who signed into their system.

At the moment, the best way to create a required verifications set and to generate an acrc_id is to interface directly with the globaliD team.

You can do so by emailing Feel free to also ask questions on our discord server.

PII Sharing

In some cases, partners may need access to the underlying user personal and identifiable user information (PII). globaliD will rarely allow partners access to such sensitive data, and do so only for legal and compliance reasons. For more information, visit the Vault and PII Sharing page.