Deposit lifecycle.
Read finalized deposit records, held amounts, processing fees and journal references. Gated testnet receiving is implemented; actual custody/RPC verification remains pending.
01Finality and identity
Independent RPC providers must agree on finalized EVM or solidified TRON blocks, complete receipts and native-transfer data. Contract, decimals, network, recipient and execution success are checked before posting.
02Held and available
Supported external funds are recognized as held customer liabilities. Approved deposit fees and net available funds are posted only when receiving and tariff checks pass. A 100 USDC deposit with a 0.30% tariff releases 99.70 USDC and records 0.30 USDC in fees.
03History and pagination
Workspace sessions read their own records; server keys require deposits:read. List filters support walletId, environment and state with nextCursor pagination. GET /v1/merchant/deposits/{id} returns one current testnet record without query filters. Workspace identity comes from the key. Platform movements and other workspaces return 404. Atomic amounts remain strings; rpc, test_fixture and unknown identify evidence provenance.
04Review and recovery
Inactive receiving, unavailable tariffs and dust remain held for review. Unsupported assets retain raw observations without spendable credit. Operators can queue a recheck; only the worker can revalidate and release funds. Wrong-network recovery, pre-finality observations and incident resolution remain in progress.
05Operator recheck history
Current Owner, Finance, Operations or Security access and recent admin passkey verification are required. POST /v1/admin/deposits/{id}/recheck accepts a reason of 12–500 characters and an optional Idempotency-Key. Persist the key and original body before sending. A matching replay returns the original acknowledgment, even after the worker changes deposit status. It does not credit funds or report current queue state. GET /v1/admin/deposits/{id}/rechecks provides bounded history with before and limit 1–50. Merchant keys cannot request a recheck or read operator history.
GET /v1/merchant/deposits/{id}
Authorization: Bearer <server-only-key-with-deposits:read>
GET /v1/workspaces/{workspaceId}/deposits/{id}
GET /v1/workspaces/{workspaceId}/deposits?environment=testnet&walletId=<uuid>
GET /v1/workspaces/{workspaceId}/deposits?before=<nextCursor>
// status: credited | confirmed_held | review_required | retry_queued
// amountAtomic: gross supported amount, or null for unsupported precision
// netAmountAtomic and processingFeeAtomic: populated after release
// recognitionJournalId and releaseJournalId: financial trace
// There is no client deposit-credit endpoint.Open your workspace