> 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-3/trigger-by-user-for-equs-wallet-pull-tx_code-delivery.md).

# Trigger by User for EQUS Wallet (pull tx\_code delivery)

The Holder starts from your site, the wallet fetches the code, and your endpoint supplies the claims

The Holder is on your site, signed in, doing the thing that earns them a credential. Their wallet opens by QR code or deep link and fetches the `tx_code` itself - and when they accept, the platform calls your endpoint for the claim values.

Same Holder experience as [Flow 1's equivalent journey](/standards/issuance/flow-1/trigger-by-user-for-equs-wallet-pull-tx_code-delivery.md). Different guarantee: nothing personal is stored along the way.

### What it requires

* **The Holder uses an EQUS Wallet**, signed in as one of your users through your identity provider - see [Bring Your Own IdP](/standards/onboarding/bring-your-own-idp.md). That sign-in is what lets the wallet fetch the code by `userId`.
* **An** [**Attribute Provider**](/standards/issuance/configuration-attribute-provider.md) endpoint, called once when the Holder accepts.

### What the Holder does

1. Scans the QR code, or follows the deep link.
2. Signs in to their wallet, if they aren't already.
3. Accepts the Offer.

Nothing to read and nothing to type. The Offer also waits in their **Pending Offers**.

### 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>Two calls from your back end, and your own page shows the Offer.</td><td><a href="/standards/issuance/flow-3/trigger-by-user-for-equs-wallet-pull-tx_code-delivery/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 + Embed UI</strong></td><td>The same calls, with the wallet picker and QR code pre-built.</td><td><a href="/standards/issuance/flow-3/trigger-by-user-for-equs-wallet-pull-tx_code-delivery/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-3/trigger-by-user-for-equs-wallet-pull-tx_code-delivery.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.