Under the hood : the process flow of a Beacon Verifier
This is the most common use case because most web3 applications already have centralized management of their users. It is likely that the application also keeps track of users’ data in its local database for later use of the data (CRM).
Application is client/server with dApp features as SPA
There are 3 protocols that are used in these interactions:
Wallet -Application: it is the synchronization between a crypto wallet and a dApp. We use Beacon in this example.
Wallet - Verifier: this is the protocol that makes it possible to transfer a credential from the wallet to a verifier. We use verifiable presentation request.
Verifier - dApp : As the dApp has a local server, we use an application webhook.