> 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/docs/issuance/flow-1/trigger-by-user-for-any-wallet-email-tx_code-delivery.md).

# Trigger by User for any Wallet (email tx\_code delivery)

Any compliant wallet, with the tx\_code traveling out of band for the Holder to type

The journey that assumes nothing. The Holder needs no account with you and no particular wallet - the `tx_code` leaves the wallet's world entirely and they carry it back in by hand.

It costs the Holder one extra step, and buys you reach: this is the only journey that works with third-party wallets, which makes it the default for issuing to the general public.

### What it requires

Nothing. No identity provider, no endpoint, no assumption about which wallet the Holder uses.

What you do decide is **who sends the code**:

| Who delivers | What happens                                                                                 | What the platform stores                             |
| ------------ | -------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| The platform | You pass the Holder's address; the platform emails the code and gives you a resend URL       | The address, encrypted, pruned with the claim values |
| You          | The Offer response hands you the `txCode`; you send it however you like - email, SMS, in-app | Nothing beyond the claim values                      |

Both are supported on this flow. On [Flow 3](/docs/issuance/flow-3/trigger-by-user-for-any-wallet-email-tx_code-delivery/method-1-api.md) only the second exists, because storing an address there would break that flow's guarantee.

### What the Holder does

1. Scans the QR code, or follows the deep link.
2. Accepts the Offer in their wallet - no sign-in needed.
3. Types the `tx_code` they received.

The code lasts three minutes and can be regenerated. The Offer does **not** appear in Pending Offers here, so the link is the only way in - and it stops working after five days.

### Ways to integrate

<table 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, or one if you deliver the code yourself.</td><td><a href="/docs/issuance/flow-1/trigger-by-user-for-any-wallet-email-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>Address collection, QR code, code entry and resend, all pre-built.</td><td><a href="/docs/issuance/flow-1/trigger-by-user-for-any-wallet-email-tx_code-delivery/method-2-api-+-embed-ui.md">Method 2: API + Embed UI</a></td></tr><tr><td><h3><i class="fa-table-columns" style="color:$primary;">:table-columns:</i></h3></td><td><strong>Method 3: Operator Portal</strong></td><td>Assisted issuance with the Holder present or on a call.</td><td><a href="/docs/issuance/flow-1/trigger-by-user-for-any-wallet-email-tx_code-delivery/method-3-operator-portal.md">Method 3: Operator Portal</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/docs/issuance/flow-1/trigger-by-user-for-any-wallet-email-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.