# 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.

<figure><img src="https://sandbox-doc.readthedocs.io/en/latest/_images/hybrid_onboard_user_with_beacon.png" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://altme-documentation.gitbook.io/altmes-documentation/altme-saas/beacon-integration/under-the-hood-the-process-flow-of-a-beacon-verifier.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.