> For the complete documentation index, see [llms.txt](https://docs.omypayments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omypayments.com/overview/our-products/private-withdrawals.md).

# Private Withdrawals

Move funds privately—without revealing a link between your merchant treasury and the destination address. **Private Withdrawals** route your payout through the Hinkal zero-knowledge protocol while keeping your day-to-day workflow inside the OMY dashboard.

#### How it works

1. **Enablement & network setup**\
   OmyPayments enables Private Withdrawals for your workspace and for specific networks. Per-network parameters (including a native-coin gas setting) are configured on our side.
2. **Address allowlisting (Hinkal)**\
   Your payout (destination) addresses must be allowlisted by Hinkal. As part of this, an **access NFT** is minted to the approved addresses—OmyPayments coordinates this with the Hinkal team.
3. **Create a withdrawal, then toggle “Is Private”**\
   In the dashboard, start a withdrawal as usual and tick **Is Private**. We handle the rest: approve (for tokens), deposit into Hinkal, and execute the private withdrawal via relayer.
4. **Track status & receipt**\
   You’ll see the result and on-chain hash in your standard withdrawals table; the low-level private-flow states are tracked internally by OmyPayments. Automated retries are built in, with safe failures if a step cannot be mined.

#### Key features

* **ZK privacy via Hinkal** — shields the link between source and destination.
* **Familiar UX** — same withdrawal flow, plus a single **Is Private** checkbox.
* **Token and native support** — handles approvals for tokens; deposits natively when applicable.
* **Operational safeguards** — staged processing with idempotent retries and clear terminal states (**success/failed**).
* **Unified reporting** — merchants see outcomes in the main `payment_withdrawals` view with the final tx hash.

#### Benefits for merchants

* **Treasury privacy** for sensitive payouts (vendor settlements, grants, internal rebalancing).
* **Minimal lift** — OmyPayments handles allowlisting, access NFT minting, and protocol nuances.
* **Predictable operations** — robust retry logic and explicit statuses; support can step in for rare SDK issues.

#### Getting started

1. **Request activation** of Private Withdrawals for your workspace and target networks.
2. **Submit destination addresses** for Hinkal allowlisting (we’ll coordinate and mint the required access NFTs).
3. In the dashboard, create a withdrawal, enable **Is Private**, and **run a small test**.
4. **Monitor the result** in your standard withdrawals page; contact support if a run pauses for review.

*Start in your dashboard:* [*https://dashboard.omypayments.com/*](https://dashboard.omypayments.com/)
