Screening Outcomes
What happens to incoming funds after screening.
Every incoming deposit is screened before it can enter the private balance.
Deposit passes screening
Automatically moves into the private balance
Deposit does not pass screening
Remains public at the Deposit Address
Unsolicited deposit that does not pass screening
Remains public and does not enter the private balance
Deposit is too small to settle
Remains at the Deposit Address until it can be settled
Deposits that pass screening
Funds that pass screening automatically move into the private balance without additional action from the sender or recipient.
Once there, they can be held, sent or swapped privately through Hinkal.
Deposits that do not pass screening
Funds that do not pass screening never enter the private balance.
They remain public at the Deposit Address and separate from funds that have passed screening. The funds remain under the owner's control and can be moved through the applicable public transfer or recovery flow.
For the exact API and SDK recovery methods, see the existing Receive Address documentation.
Unsolicited and dusting transactions
A public address can receive transfers without the owner's permission. This includes unsolicited transfers and dusting transactions.
Compliance Gateway screens these deposits like any other incoming transfer. If a deposit does not pass screening, it remains public at the Deposit Address rather than entering the private balance.
This prevents an unsolicited deposit that fails screening from being automatically mixed with the user's eligible funds.
Small deposits
Moving funds from the Deposit Address into the private balance requires sufficient funds to cover settlement.
Deposits that are too small to settle remain at the Deposit Address and are automatically settled with a subsequent deposit once sufficient funds are available.
Last updated