For the complete documentation index, see llms.txt. This page is also available as Markdown.

Managing Whitelisted Wallets

Once an address is verified, your organization 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.

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.

Last updated

Was this helpful?