> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/getting-started/tutorial/testing-verification.md).

# Testing the Verification Flow

**What We Are Doing:**

* Running through the entire process: issuance, verification, and accessing the dashboard.

**Why:** To ensure all components work together smoothly.

**Steps:**

1. Start the server:

   ```bash
     node src/index.js
   ```
2. Issue a credential by submitting the form and scanning the QR code with the Empe DID Wallet.
3. Click "Authorize with KYC Credential" to request a verification QR code.
4. Scan the verification QR code with the wallet. If you meet the criteria (age ≥ 18), you should be verified.
5. You are redirected to the dashboard, where the user\`s DID and credential attributes are displayed.

If everything works, you\`ve successfully completed the end-to-end flow!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.empe.io/getting-started/tutorial/testing-verification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
