> For the complete documentation index, see [llms.txt](https://docs.tesseract.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tesseract.fi/earn-direct-and-earn-api/earn-direct/organizations/managing-whitelisted-wallets.md).

# Managing Whitelisted Wallets

Once an address is [verified](/earn-direct-and-earn-api/earn-direct/organizations/team-management.md#wallet-verification), your [organization](/earn-direct-and-earn-api/earn-direct/organizations.md) can manage it from **Profile → Whitelisted Wallets** — change which wallet receives a product's withdrawals, or retire a deposit wallet you no longer use.

Both actions are **requested by the client and approved by Tesseract**. Nothing changes silently: a request stays pending until a Tesseract operator actions it, so a payout address can't be redirected — and a wallet can't be retired — without that review.

> Who can do what: changing a product's **withdrawal address** — and cancelling such a request — is **Admin-only**. **Deactivating a deposit wallet** (and cancelling a pending deactivation) can be done by a **Whitelisting Manager** or an **Admin**. See [Team Management](/earn-direct-and-earn-api/earn-direct/organizations/team-management.md).

### Wallet states

Each wallet in the list shows its state as colour-coded tags:

| Tag            | Meaning                                                                                                  |
| -------------- | -------------------------------------------------------------------------------------------------------- |
| **Deposit**    | Whitelisted and deposited from — usable for deposits.                                                    |
| **Withdrawal** | The product's current payout address. Each product has exactly one at any time.                          |
| **Pending**    | A change or deactivation for this wallet is awaiting Tesseract approval.                                 |
| **Inactive**   | The wallet has been deactivated. It stays listed as a record and can be brought back by re-verifying it. |

A wallet can be both **Deposit** and **Withdrawal** — a product's payout address always starts as a wallet you've deposited from.

## Changing a product's withdrawal address

By default, a product pays out to the first wallet you whitelisted and deposited from. To route withdrawals elsewhere:

1. Open **Whitelisted Wallets** and choose **Change withdrawal address** on the product.
2. Pick the new address. Only wallets you have **already whitelisted and deposited from** are offered — there is no free-text address entry, and the current payout address isn't selectable.
3. Submit. The request enters a **Pending** state and appears for Tesseract operators to review.

The change only takes effect once Tesseract approves it. Until then:

* The **current** payout address stays active — withdrawals already made are unaffected.
* **New withdrawals for that product are paused** and can't be started, with a notice explaining why. Other products are unaffected — holds are per product.
* Any **Admin** in the organization can **cancel** the pending request at any time before it's actioned; the current address stays in place and the hold releases.

If Tesseract can't confirm the new address, the operator **rejects** the request — the current address is kept and the hold releases. On approval, the **Withdrawal** tag moves to the new wallet and future withdrawals for that product route there.

> A change can't be requested for a product that already has a withdrawal in progress — wait until it settles.

## Deactivating a deposit wallet

To retire a deposit wallet you no longer use, choose **Deactivate wallet** on it.

Deactivation is **not immediate** and is **not a deletion**. It creates a pending request that a Tesseract operator confirms out-of-band. While pending, the wallet keeps working for deposits. On confirmation:

* The wallet is marked **Inactive** — its **Deposit** tag is replaced.
* It **stays visible** in the list as a historical record.
* Later deposits from it are quarantined for review rather than credited automatically.

A wallet **can't be deactivated** while it is a product's active withdrawal address, or while it's the target of a pending withdrawal-address change. To retire a wallet that is also a payout address, first change that product's withdrawal address away from it, then deactivate it.

To use an inactive wallet again, simply **re-verify** it (deposit → verification link → confirm ownership). Completing verification restores its **Deposit** tag — there is no separate "reactivate" step.

## Approvals & timing

Because Earn Direct payouts are controlled by Tesseract, approval sits on the Tesseract side. Operators action requests after completing the required compliance checks (including the Sumsub / Fireblocks steps that can't be automated), so a request may sit **Pending** briefly — for example over a weekend when no operator is available. This is expected and keeps the control step evidenced rather than automatic.

### Activity log

Every step — requested, approved / effective, rejected, cancelled, and wallet deactivations — is recorded in the organization's **Activity** tab, showing who did what, when, and the outcome (including the old → new address for changes). See [Organizations → Activity log](/earn-direct-and-earn-api/earn-direct/organizations.md#activity-log).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tesseract.fi/earn-direct-and-earn-api/earn-direct/organizations/managing-whitelisted-wallets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.