> 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/develop/wallet-server/flows-claim-and-presentation.md).

# Flows: Claim and Presentation

Wallet Server can process the same QR‑based flows used by mobile wallets. Flows are initialized from a QR URL and then confirmed. A flow remains active for \~10 minutes before expiring.

## Initialize from QR

* POST `/flows`
  * Body:
    * `qrContent` (string): URL you scanned from issuer/verifier
    * `did` (string, optional): explicitly pass holder DID, if applicable
  * Response: `{ flowType: 'claim' | 'presentation', data: ... }`

Depending on the QR type, one of the following happens:

### Claim Flow (issuer QR)

1. Initialize: `POST /flows` returns `{ processId, status: 'initialized', offering }`.
2. Confirm: `POST /flows/:processId/confirm` with body `{ "type": "claim" }`.
3. Response: `{ status: 'confirmed', message: ... }` after the SDK completes.

### Presentation Flow (verifier QR)

1. Initialize: `POST /flows` returns `{ processId, matchingCredentialIds, matchingCredentials, status }`.
   * If there are no matches, status is `failed` with an error.
2. Confirm: choose a credential and send:
   * `POST /flows/:processId/confirm`
   * Body: `{ "type": "presentation", "selectedCredential": { ...full VC json... } }`
3. Response: `{ status: 'confirmed', message: 'Presentation verified' }` or an error if verifier rejects.

## Examples

Initialize:

```
curl -X POST http://localhost:3000/flows \
  -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' \
  -d '{"qrContent":"https://issuer-or-verifier.example.com/qrcode-data", "did":"did:example:123"}'
```

Confirm claim:

```
curl -X POST http://localhost:3000/flows/<processId>/confirm \
  -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' \
  -d '{"type":"claim"}'
```

Confirm presentation:

```
curl -X POST http://localhost:3000/flows/<processId>/confirm \
  -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' \
  -d '{"type":"presentation","selectedCredential":{ ... your VC ... }}'
```

## Expiration & Concurrency

* Each initialized flow stores a short‑lived promise; if unconfirmed for \~10 minutes, it expires and is cleaned up.
* Confirmation must be performed by the same authenticated user that initialized the flow.
* Presentation confirmation requires the complete VC object (not just id).


---

# 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/develop/wallet-server/flows-claim-and-presentation.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.