Non-AUTH-initiated transaction block

Configure the non-AUTH-initiated transaction block so you can block any transactions initiated outside of the AUTH flow.

An end user can send digital assets to a deposit address without starting a transfer through AUTH. If your platform enables this control, zerohash records the received funds under the recovery_quarantine account label instead of making them available as an ordinary end-user balance. Direct the end user to an available recovery option.

The control applies to deposits, not every transfer outside AUTH. It does not reject an on-chain transfer like an API request; it changes how received funds are held and made available.

What happens to a deposit outside AUTH

1. Send funds outside AUTH - The end user sends funds to a deposit address without initiating the transfer in AUTH
2. Quarantine the deposit - zerohash records the funds under recovery_quarantine rather than making them available for ordinary end-user activity
3. Receive the status - Your platform receives a deposit.status_changed webhook with a state of recovery_quarantine
4. Offer recovery - Direct the end user to the agreed platform-hosted or zerohash-hosted recovery flow

Funds in recovery_quarantine do not add to the end user’s available trading balance. Do not treat the webhook as a completed deposit or assume that the funds were returned to the sender. Use the deposit status updates reference to implement status handling.

Prepare your platform

1. Confirm the setting - Ask zerohash whether the block is enabled for your platform
2. Plan the end-user experience - Decide how your application will display a quarantined deposit and direct the end user to recovery
3. Test the outcome - Verify your webhook handling, displayed status, and recovery path with zerohash before relying on the control in production

See AUTH controls for the other controls and Configure AUTH for setup choices. Contact zerohash about this control to confirm availability and configuration.