> 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-3/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 delivered by you rather than by the platform
The journey that reaches anyone, on any OID4VCI-compliant wallet. The `tx_code` travels out of band and the Holder types it in.
One thing here is specific to this flow, and it is the reason the flow exists: **you deliver the code**. The platform hands it back to you rather than sending it, because sending it would mean holding a contact detail - and then "nothing personal at rest" would no longer be true.
### What it requires
* **A channel of your own** for the code: email, SMS, in-app message, whatever you already have.
* **An** [**Attribute Provider**](/docs/issuance/configuration-attribute-provider.md) endpoint, called when the Holder accepts.
No identity provider, and no assumption about the Holder's wallet.
### How this differs from Flow 1
| | [Flow 1](/docs/issuance/flow-1/trigger-by-user-for-any-wallet-email-tx_code-delivery.md) | Flow 3 |
| ----------------------- | ---------------------------------------------------------------------------------------- | ------------ |
| Who sends the `tx_code` | The platform, or you | **You only** |
| Contact detail stored | The address, when the platform sends it | **Never** |
| Claim values stored | Until issuance, or five days | **Never** |
### What the Holder does
1. Scans the QR code, or follows the deep link.
2. Accepts the Offer - no sign-in needed.
3. Types the code you sent them.
The code lasts three minutes and can be regenerated. The Offer does not appear in Pending Offers, and stops working after five days.
### Ways to integrate
---
# 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-3/trigger-by-user-for-any-wallet-email-tx_code-delivery.md?ask=&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.