A DALP Instance tells a client where to send a deposit through the client's own custody gateway. The gateway belongs to one client identity and has an address. The client sends coins to that address, and the gateway records the deposit, screens it and mints receipts. No deployment setting lists accepted coins, and no route watches a wallet for deposits. The operator decides what is accepted in the Console.
What must be in place
Which coins are accepted
A coin is accepted when it is enabled on the add-on. A deposit of any other coin lands on the gateway's “Unsupported” list and is returned, recovered or ignored by an operator. See Review deposits and withdrawals.
A coin can be set to wait for custody. The gateway then mints the receipts to the client and holds them until the custodian accepts the coins the gateway forwarded. A deposit in that state rests at Awaiting custody.
Where a client sends a deposit
A client sees the gateway address in the Deposit dialog of the Investor portal, and reads it through GET /api/. A gateway has no client wallet when it is created. A gateway manager binds one before the client's own routes work, as the custody gateway API describes.
What happens to a deposit
Every deposit enters a screening stage first. The screener clears it, the gateway mints the receipts and the coins move on. Deposit and withdrawal stages lists each stage, who moves it and the time limits.