> 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-1/trigger-by-user-for-any-wallet-email-tx_code-delivery/method-3-operator-portal.md).

# Method 3: Operator Portal

Issue to a Holder on any wallet from the Portal, with the code sent out of band

The same **Issue by user** path as the EQUS Wallet journey, for a Holder who has no account with you. The Offer appears on screen, and the `tx_code` reaches them out of band.

{% hint style="info" %}
This is the assisted, over-the-counter case: an operator issues while the Holder is present, or on a call. For issuance at volume, use [Method 1: API](/standards/issuance/flow-1/trigger-by-user-for-any-wallet-email-tx_code-delivery/method-1-api.md).
{% endhint %}

**Before you start** you need an [Issuer and VC Schema](/standards/issuance/configuration-issuer-and-vc-schema.md). Nothing else - this journey assumes nothing about the Holder.

### Issue the credential

Open **Issuance** in [the Portal](https://portal.us.equs.ai/) and press **Issue VC**. In the modal:

{% stepper %}
{% step %}

#### Set the issuance method to **Issue by user**

The Holder has no account with you, so there is nothing for *Auto issuance* to deliver into - this is the only path open on this journey.
{% endstep %}

{% step %}

#### Choose the Issuer and the VC Schema

Both are required. If you haven't created them yet, the **＋** beside each field creates one without leaving the modal.
{% endstep %}

{% step %}

#### Enter the Holder's user ID and email

The user ID is your own identifier for them. The email is where the `tx_code` goes, and it is what makes this journey work for a Holder you have no other channel to.
{% endstep %}

{% step %}

#### Fill in the claims

The claims panel is built from the Schema you picked: one entry per claim, with the type of input the claim declares. The structure is fixed by the Schema and read-only here - you are supplying values, not shaping the credential. Every mandatory claim needs a value before **Issue VC** is enabled.
{% endstep %}
{% endstepper %}

The Offer is shown as a QR code or a web wallet link. The Holder scans or opens it, accepts, and enters the `tx_code` - which lasts three minutes and can be regenerated if it lapses.

Any OID4VCI-compliant wallet works here, because nothing in the journey depends on the wallet knowing the platform.

### Track the result

The **Issuance** list carries the outcome and the revoke action, which becomes available once the status is **Accepted**. See [Issuance Results](/standards/issuance/issuance-results.md) for the same record over the API.


---

# 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-1/trigger-by-user-for-any-wallet-email-tx_code-delivery/method-3-operator-portal.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.