> 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/auto-issuance.md). # Auto-issuance The Offer arrives by itself, and the claim values are pulled only when the Holder accepts Identical to [Flow 1's auto-issuance](/standards/issuance/flow-1/auto-issuance.md) from where the Holder stands: a business event fires, the Offer waits in their **Pending Offers**, an email and a push notification say so, and accepting is all they do. The difference is what you sent. The trigger carries no claim values - only a Schema version, an Issuer and your own user ID. The platform comes back to your [Attribute Provider](/standards/issuance/configuration-attribute-provider.md) for the values at the moment it signs. So the credential carries what was true when the Holder collected, not what was true when you triggered, and nothing personal is ever written to platform storage. ### 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). * **An email address** for the notification. Used to tell them, not stored. * **An** [**Attribute Provider**](/standards/issuance/configuration-attribute-provider.md) that answers within 5 seconds. This is a runtime dependency: if it's down when the Holder accepts, that issuance fails. ### Ways to integrate The [API](/standards/issuance/flow-3/auto-issuance/api.md) is the only path here: one call, carrying `autoIssuance` and no claim values. Neither of the other two applies. **Embed UI** has nothing to render, because this journey has no Holder-facing screens at all. And the **Operator Portal** collects claim values in its Issue VC modal, which is Flow 1's model - on this flow the values come from your endpoint instead. --- # 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/auto-issuance.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.