Page Summary
-
A challenge can be issued to a user if the initial proofing evidence is insufficient for identity confirmation.
-
The proofing request will expire if the user does not respond to the identity challenge within thirty days.
-
The process involves the user submitting evidence, the Issuer reviewing it, and Google relaying status updates.
-
The Issuer can challenge the user, and upon completing the challenge the user can be approved.
-
The process concludes with the Issuer providing the
acceptedstatus to Google, who then relays this to the user.
In some cases, the evidence provided during the original proofing request may not be sufficient to confirm the identity of the user. In these cases, a challenge can be submitted to the user to provide additional information before an approval status is determined.
Request flow
Flow description
| Step | Source | Description |
|---|---|---|
| 1 | Android-powered device | A user submits the liveness video and physical identity document images for Verifiable Digital Credentials registration. |
| 2 | Google servers |
Google calls proofUser, sending the
evidence and a proofing ID to the Issuer.
|
| 3 | Issuer servers |
The Issuer sets the approval to pending and reviews the
submitted evidence.
|
| 4 | Issuer servers |
The Issuer calls notifyProofingStatusUpdateAvailable to
notify Google that a status update is available for this proofing
request.
|
| 5 | Google servers |
Google calls getProofingStatus to determine the status of
the proofing request.
|
| 6 | Issuer servers | The Issuer returns the challenged status. |
| 7 | Google servers | Google relays the status to the user. |
| 8 | Android-powered device | The user completes the challenge. |
| 9 | Issuer servers | The Issuer approves the user. |
| 10 | Issuer servers |
The Issuer calls notifyProofingStatusUpdateAvailable to
notify Google that a status update is available for this proofing
request.
|
| 11 | Google servers |
Google calls getProofingStatus to determine the status of
the proofing request.
|
| 12 | Issuer servers | The Issuer returns the accepted status. |
| 13 | Google servers | Google relays the status to the user. |