# Dual approval

> A second person confirms large payouts before they leave. How CryptoLike sets the threshold per asset, who may approve and what awaiting_approval means.

Source: https://cryptolike.net/glossary/dual-approval
Updated: 2026-09-24

A control that holds an outgoing transfer above a set amount until a second authorised person, not the one who created it, confirms it.

## How it works in CryptoLike

In CryptoLike an owner or admin sets `dual_approval_threshold` per asset in the withdrawal settings, confirmed with 2FA; with no threshold the control is off. A payout created by a team member above the threshold goes to `awaiting_approval`: its full `total_debit` is already in `hold`, and you receive `withdrawal.awaiting_approval`.

Another owner or admin — never the creator — approves it with a 2FA code in the cabinet (Withdrawals → Approvals) or in the Telegram bot. The payout then moves to `pending` and continues to `processing`, `broadcast` and `completed`. Until processing starts, the payout can be cancelled and the hold returns to `available`.

## Which payouts need a second approval?

CryptoLike applies dual approval to payouts that people create in the cabinet or the Telegram bot and whose amount exceeds the threshold of that asset. Payouts created with an API key are not held: issuing a key with the `withdraw` permission is the account's own decision, and only an owner, admin or developer can create keys.

A manual review comes first: a payout sent to `review` (a limit, an unusual pattern, compliance) goes to `awaiting_approval` after it is approved, if the threshold still applies. Combine dual approval with the [payout whitelist](https://cryptolike.net/glossary/payout-whitelist) so that even an approved payout can go only to known addresses. Payout flows: [mass payouts use case](https://cryptolike.net/use-cases/mass-payouts).

The other payout controls — 2FA, the whitelist and review limits — are on the [security page](https://cryptolike.net/security).