> 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/frontend-issuance.md).
# Frontend for Credential Issuance
**What We Are Doing:**
* Creating a simple HTML form to collect the holder's details.
* When the form is submitted, it calls our backend route, which asks the Issuer for a credential offer and returns the offer data, including a URL for a QR code image.
* The user scans this QR code with a compatible wallet to claim the credential.
**Why:** A user interface is essential so that a real person can enter their details and receive a credential. The browser never talks to the Issuer directly — it talks to our backend, which holds the access token and shapes the request.
**How the QR works:** This is the two-step flow we built on the [Issuing Credentials](/getting-started/tutorial/issuing-credentials.md) page. First the form `POST`s to our backend route `/issuer/kyc-credential`, which creates the offer at the Issuer and responds with **JSON** — `{ credentialOfferUri, issuanceSessionId, qr_code_url }`. The `qr_code_url` points at our own backend route `GET /issuer/kyc-credential/:sessionId/qr-code`, which proxies the **PNG image** of the QR code. So the frontend reads the POST response as JSON, then simply points an `![]()
` at the returned `qr_code_url` to load the QR. The QR encodes an `openid-credential-offer://...` URI; scanning it tells the wallet where to claim the credential.
**Steps:** In `public/index.html`:
```html
EVDI Tutorial
KYC Credential Issuance
![Credential offer QR code]()
```
The backend routes are the ones we built on the [Issuing Credentials](/getting-started/tutorial/issuing-credentials.md) page. The `POST /issuer/kyc-credential` route maps the submitted fields into the offer's `issuanceMetadata.claimsByConfigurationId` for `KYCCredential@1.0:sd-jwt`, calls the Issuer's credential-offers endpoint with the operator's Bearer token, and responds with `{ credentialOfferUri, issuanceSessionId, qr_code_url }`. The browser then loads `qr_code_url` (our `GET /issuer/kyc-credential/:sessionId/qr-code` route), which fetches the Issuer's `GET /issuance-sessions/:sessionId/qr-code` PNG with the same Bearer token and streams it straight back to the `![]()
`.
Now you can test issuing a credential by filling out the form and scanning the generated QR code with a compatible wallet. The wallet reads the embedded `openid-credential-offer://` URI, claims the `KYCCredential@1.0:sd-jwt` credential, and stores it.
---
# 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/frontend-issuance.md?ask=&goal=
```
`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.