> 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/wallets/web-wallet.md).

# Web Wallet

A browser wallet the platform hosts for your Holders, for when keys held on the Holder's own device aren't practical.

The **Web Wallet** is an EQUS Wallet that runs in the browser, so your Holders have nothing to install. It is **custodial**: the platform holds each Holder's keys and credentials on their behalf, rather than the Holder's own device. Holders can use it on its own or inside your site.

{% hint style="info" %}
The **Web Wallet** is disabled by default and is only available on request.
{% endhint %}

### Web Wallet or Mobile Wallet? ⚖️

| Feature                  | Web Wallet                                  | Mobile Wallet                                                       |
| ------------------------ | ------------------------------------------- | ------------------------------------------------------------------- |
| **Custody**              | Custodial                                   | Non-custodial                                                       |
| **Keys and credentials** | Held by the platform, server-side           | On the Holder's device, hardware-bound where the device supports it |
| **Runs in**              | The browser, on its own or inside your site | An app on the Holder's phone                                        |
| **Availability**         | On request                                  | Available by default                                                |

The Web Wallet suits audiences for whom keys held on their own device are impractical. When your Holders should control their own keys, use the [Mobile Wallet](/docs/wallets/equs-wallet.md). A non-custodial web wallet isn't part of the standard offering, but may be available on request.

### Get it enabled 🔓

Ask for the Web Wallet in [the Operator Portal](https://portal.us.equs.ai/): under **Instructions**, the Web Custodial Wallet section has a **Book a call with EQUS** button. Once it's enabled for your Tenant, the same section shows the link to your Web Wallet.

Your Holders sign in with the account they already have with you, so connect your identity provider too. See [Bring Your Own IdP](/docs/onboarding/bring-your-own-idp.md).

<figure><img src="https://701364325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaucIkpW1i4WOAQC06fj%2Fuploads%2FET0Jn3CkRRUg2PMAfA0F%2Fimage.png?alt=media&amp;token=a6ccc1d5-7bfc-404b-a989-8513d5b27738" alt=""><figcaption></figcaption></figure>

### How Holders use it 🧑‍💻

#### Signing in

Holders sign in through your identity provider: in the wallet itself, or in a sign-in pop-up when the wallet is embedded in your site.

#### On its own or inside your site

* **Standalone** - the wallet opens in its own browser tab, at an address specific to your Tenant.
* **Embedded** - you bring the wallet into your own site: a button that opens the Holder's credentials over your page, an Offers tab, and a notifications bell for new Offers. See [Embedding Web Wallet](/docs/embedded-ui/embedding-web-wallet.md).

#### What Holders can do

* **See their credentials.**
* **Pick up Offers.** Holders are notified of new Offers and find them in the Offers tab. An Offer link from your site opens straight in the wallet.
* **Accept without typing a code.** In the `pull` tx\_code journeys of [Flow 1](/docs/issuance/flow-1/trigger-by-user-for-equs-wallet-pull-tx_code-delivery.md) and [Flow 3](/docs/issuance/flow-3/trigger-by-user-for-equs-wallet-pull-tx_code-delivery.md), the Holder signs in and accepts. The wallet fetches the code itself.
* **Share credentials.** When your site asks for a [presentation](/docs/presentation/flows-1-and-2.md), the request opens in the Web Wallet on the same device. The Holder reviews what is being asked for and approves.
* **Approve AP2 mandates.** When an agent asks to act for the Holder, the request opens in the wallet for the Holder to approve. See [Agentic Payments (AP2)](/docs/agentic/ap2.md).

### Branding 🎨

Your Tenant's branding (colors, fonts, light or dark) applies to the Web Wallet and its notifications list. You set it once for your Tenant. See [Styles and Branding](/docs/embedded-ui/styles-and-branding.md).

### Custody and personal data 🔐

Because the wallet is custodial, the platform holds each Holder's keys and stores their issued credentials server-side, for as long as the wallet account exists.

That changes some of the guarantees described in [Personal Data and Encryption](/docs/security-and-privacy/personal-data-and-encryption.md), which are written for the Mobile Wallet. Three of them don't apply to the Web Wallet: that the signed credential is never written to disk, that credential keys are controlled only by the Holder, and that Issuance Flows 2 and 3 leave no personal data at rest. If you're considering the Web Wallet, ask EQUS for its data-handling details.

### Next steps

<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-window-restore" style="color:$primary;">:window-restore:</i></h3></td><td><strong>Embedding Web Wallet</strong></td><td>Bring the wallet into your own site.</td><td><a href="/docs/embedded-ui/embedding-web-wallet.md">Embedding Web Wallet</a></td></tr><tr><td><h3><i class="fa-user-lock" style="color:$primary;">:user-lock:</i></h3></td><td><strong>Bring Your Own IdP</strong></td><td>Let Holders sign in with the account they already have with you.</td><td><a href="/docs/onboarding/bring-your-own-idp.md">Bring Your Own IdP</a></td></tr><tr><td><h3><i class="fa-mobile-screen" style="color:$primary;">:mobile-screen:</i></h3></td><td><strong>Mobile Wallet</strong></td><td>The non-custodial alternative, with keys on the Holder's device.</td><td><a href="/docs/wallets/equs-wallet.md">EQUS Wallet (mobile)</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/wallets/web-wallet.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.