The custody journal's deposit, withdrawal, position, policy and fee screens have been retired. Operators use gateway records for current gateway deposits and withdrawals. Generic organisation Cases, withdrawal-destination review and registrar reconciliation remain available with their current access and approval rules.
The custody watch and journal are retired, current gateways use records and custody receipts, and Cases and registrar reconciliation stay separate.
Steps
The former ordered custody-book workflow is retired. Use gateway detail and records for current deposits and withdrawals, Cases for organisation investigations, and Reconciliation for registrar breaks and destination review. The following historical tasks are reference questions, not steps that create a replacement journal.
Read the deposits list
The former organisation Deposits table is retired. Current gateway detail and records show gateway deposits and their stage history. They do not recreate a global custody-journal table or its customer-identifier contract.
Release, return or refuse a held deposit
The former held-journal deposit actions are retired. Read the current gateway deposit and act only through the decisions its stage, role and checker requirements permit. Current holds have different causes. The old release, return and refusal dialogs do not apply to them all.
The withdrawal requests table lists every customer's withdrawals, newest first, 50 to a page. Each row shows “Customer”, “Status”, “Amount”, “Destination” and “Requested”. The destination shows its network's name, or “Network <chain ID>” when the Console does not know the network. A “Network” column appears when the page holds withdrawals from more than one network. Open a row for its “Asset”, “Network” and “Destination”. Filter by customer with the Customer ID field.
Withdrawal-destination review remains available after the journal screens are retired. Open Reconciliation and use Withdrawal destinations awaiting review, or follow Review destination from Actions. Clear or refuse the proved address with a reason under the current reviewer and address-uniqueness rules. A cleared proof does not automatically authorise that address for gateway payouts.
Open Cases. “Operations cases” lists every operations case in the platform's order. Each row names the case in words, such as “Held by screening”, “Screening unavailable”, “Withdrawal needs an operator”, “Deposit reversed by a chain reorganisation”, “Unexpected custody outflow”, “Privileged action on a custodied token” or “Upgrade scheduled for custodied tokens”, and shows “State”, “Customer”, “Related to” and “Raised”. Select the “Case”, “State”, “Customer” or “Raised” header to sort the whole list by that column on the platform.
Open a row for the “Reason”, the “Raised” time, the “Expires” time in UTC, or “Expired” once it has passed, the “Case id” and, once resolved, the “Resolution”. An open case shows “No resolution recorded” in the “Unknown transactions report”. Resolve opens “Resolve this operations case”, where you write an “Investigation note” and select “Resolve”.
The old parked-withdrawal consume and release screen is retired. Current gateway requests expose their actual evidence, stages and authorised decisions. There is no replacement parked-payout resolver or automatic translation of an uncertain journal payout.
Work an operations case
Generic organisation Cases remain available after the custody books are retired. Owners and platform administrators can acknowledge an open case or resolve it with a note, page through the list, and inspect its state. If somebody else changes its state or row version, read the current case before deciding again. Cases no longer enrich rows with journal deposits or withdrawals, offer their actions, or show an unknown-transactions report.
The Cases table lists organisation cases with their acknowledge or resolve actions.
The Cases table shows organisation cases and their acknowledge or resolve actions. An open row offers Acknowledge or Resolve with a note. It remains available to owners and platform administrators when custody operations are off.
Read customer positions
The old customer Positions tab and attribution report are retired. Current custody receipt holdings and gateway records may answer an investor's holdings and stage questions. They do not reproduce the old Spendable and Reserved balances or their location attribution.
Set the withdrawal approval policy
The legacy withdrawal approval-policy screen and route are retired. Current gateway profiles, settings and checker requirements belong to the add-on. Registrar break approvals remain separately governed by the organisation's approval family. There is no automatic translation of the old withdrawal limits or checker windows.
The old per-asset custody fee-schedule editor is retired. Current gateway settings define its fee mode and terms, and gateway records show the resulting fee evidence. The old schedule versions and journal fee history are not regenerated from those records. What a withdrawal costs explains the retired journal fee flow.
Troubleshooting
A missing journal tab is expected because those screens are retired. For current surfaces, distinguish a feature or authority refusal from a gateway stage restriction. Read current Cases again after a conflicting decision, and follow the destination-review refusal guidance when proof review fails. Enabling custody operations does not bring the old journal screens back.
API routes
The former deposit, held-deposit, withdrawal, position, movement, policy, fee and daily reconciliation API groups are retired. Current gateway settings and records, destination whitelist operations, generic organisation Cases, and break or reserve operations remain available through their current roles and scopes. Consult the Platform API reference for the served routes.