> For the complete documentation index, see [llms.txt](https://docs.toolkit.equs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolkit.equs.ai/standards/issuance/flow-2.md).

# Flow 2: Authorization + pull claims

The Holder starts the journey and the platform asks you for claim values at the moment of signing

The Holder moves first. They pick a credential type in their wallet, or start on your website and open a wallet from there, and the platform sends them to your Authorization Server to sign in. Only then does it ask you for the data - at the exact moment the credential is being signed.

Nothing personal is ever written to platform storage. And because you're asked in real time, you can answer `denied`: the decision to issue is yours at that instant, not something you committed to earlier.

```mermaid
flowchart LR
    A["Holder picks a credential<br/>in the wallet, or starts<br/>on your site"] --> B["Wallet signs in at<br/>your Authorization Server"]
    B --> C["Wallet asks the platform<br/>for the credential"]
    C --> D["Platform calls your<br/>Attribute Provider"]
    D --> E["Platform signs<br/>and returns the VC"]
    style D fill:#fff4e5,stroke:#f9ab00
    style E fill:#e6f4ea,stroke:#34a853
```

{% hint style="warning" %}
**Partially supported.** The Issuance API is ready, over both the SDK and REST. EQUS Wallet support is still being built, so today this flow runs with third-party wallets. Check with us before building.
{% endhint %}

### At a glance 👀

<table data-search="false"><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>Protocol</strong></td><td>OID4VCI authorization code</td></tr><tr><td><strong>Who starts it</strong></td><td>The Holder, from their wallet or from your website - signed in or not</td></tr><tr><td><strong>When claims are read</strong></td><td>At signing time - fresh</td></tr><tr><td><strong>What the platform stores</strong></td><td>Nothing personal</td></tr><tr><td><strong>You host</strong></td><td>An Attribute Provider endpoint, plus an Authorization Server registered with the platform</td></tr><tr><td><strong><code>tx_code</code></strong></td><td>None. The Holder signs in instead of presenting a code</td></tr><tr><td><strong>Auto-issuance</strong></td><td>No - there is no way to push a credential to a Holder who hasn't asked</td></tr><tr><td><strong>Effort</strong></td><td>The heaviest of the three</td></tr></tbody></table>

**Pick this flow** when nothing personal may ever be written to platform storage; claim values must be read at the instant of issuance; the decision to issue is made at that moment, so your endpoint may answer `denied`; or the journey naturally starts in the wallet, or on your website for visitors who aren't signed in.

**Watch out** for three things. You take on a **runtime dependency**: the platform calls your Attribute Provider synchronously on every issuance, and if it's down, issuance fails. There is **no auto-issuance** here at all. And the Holder gets an **extra login and redirect** in their path, which costs completion.

### There is only one journey 🛤️

Flows 1 and 3 branch on how the `tx_code` reaches the Holder. This flow has no `tx_code` - the Holder authenticates at your Authorization Server instead, which is both the authorization and the proof that the right person is collecting. So there is nothing to choose: one journey, and a choice of integration method.

### What you'll do ✅

{% stepper %}
{% step %}

#### Configure the Issuer and VC Schema

Identical for every flow - see [Issuer and VC Schema](/standards/issuance/configuration-issuer-and-vc-schema.md).
{% endstep %}

{% step %}

#### Register your Authorization Server and host an Attribute Provider

The Authorization Server is specific to this flow - see [Configuration: Authorization Server](/standards/issuance/flow-2/configuration-authorization-server.md). The Attribute Provider is shared with Flow 3 - see [Configuration: Attribute Provider](/standards/issuance/configuration-attribute-provider.md).
{% endstep %}

{% step %}

#### Pick an integration method

[Method 1: API](/standards/issuance/flow-2/method-1-api.md) is the only one available today.
{% endstep %}

{% step %}

#### Read the result

Every attempt leaves a pseudonymous record - see [Issuance Results](/standards/issuance/issuance-results.md).
{% endstep %}
{% endstepper %}

### Ways to integrate 🔌

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-code" style="color:$primary;">:code:</i></h3></td><td><strong>Method 1: API</strong></td><td>Configuration and a hosted endpoint, rather than a sequence of calls.</td><td><a href="/standards/issuance/flow-2/method-1-api.md">Method 1: API</a></td></tr><tr><td><h3><i class="fa-puzzle-piece" style="color:$primary;">:puzzle-piece:</i></h3></td><td><strong>Method 2: API + Embedded UI</strong></td><td>Work in progress. A pre-built website entry point for this flow.</td><td><a href="/standards/issuance/flow-2/method-2-api-+-embed-ui.md">Method 2: API + Embed UI</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.toolkit.equs.ai/standards/issuance/flow-2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.