> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://doc.cheddar.biz/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://doc.cheddar.biz/_mcp/server.

# Withdrawal approval emails

The **Withdrawal approval email allowlist** lets you self-serve a list of customer
emails on **Dashboard → Organization** (`/dashboard/organization`). When a
custodial withdraw’s customer email matches an active entry, Cheddar skips manual
approval holds — without changing destination-address checks, low-liquidity holds,
or risk screening.

This is **not** the same as your organization’s **whitelisted withdrawal
addresses** (destination addresses managed by the Cheddar team). See
[Organization security](/guides/organization#whitelisted-withdrawal-addresses).

## Manage the allowlist

On the Organization security page, find **Withdrawal approval email allowlist**:

1. Enter a **Customer email** and click **Add email**.
2. Active entries appear in the table with **Remove** to soft-archive an email.

Removed entries are archived, not deleted. Re-adding the same email restores it.

## How matching works

Matching uses the customer’s **`organizationExternalEmail`** — the email Cheddar
stores for that customer, typically set when you first create a deposit address:

* Pass `customerEmail` on [`POST /deposit`](/guides/deposits#get-a-deposit-address)
  (optional; normalized to lowercase).
* If the customer has no email on file, allowlist entries never apply.

Only emails on **your** organization’s allowlist are checked. Another
organization’s list does not affect your customers.

## What is overridden

For a matching customer email, custodial `POST /withdraw` skips:

* **`requireApproval: true`** — the withdraw is not held for manual approval.
* **Customer USD withdraw threshold** — over-threshold holds that would normally
  land in [Transactions to Approve](/guides/withdrawals#approving-withdrawals).

See [Withdrawals & approvals](/guides/withdrawals#customer-withdrawals-api) for
API usage and webhooks when approval *is* required.

## What is not overridden

Even with an allowlisted email, withdraws can still be held or blocked by:

* **Destination-address whitelist** — `toAddress` must still be allowed for your org.
* **Low liquidity** — insufficient balance in the hot wallet.
* **Risk screening** — flagged funds may still return `451` or other holds.

## Related guides

* [Organization security](/guides/organization) — thresholds, destination whitelist, risk controls
* [Withdrawals & approvals](/guides/withdrawals) — `POST /withdraw`, approval flow, webhooks
* [Deposits](/guides/deposits) — setting `customerEmail` when creating deposit addresses