SG custody + OTC settlement
Route institutionally held crypto or DPT-class stablecoins through partner custody admission, selected execution, and documented Singapore settlement.
Overview
Institutional digital-asset balances move through SG custody admission, selected execution, settlement booking, and documented close.
Request-gated institutional SG workspace for custody admission, selected execution, settlement booking, and close evidence.
Route coverage
- 2-stage SG institutional workspace
- Classification, custody admission, and selected execution route
- Settlement booking, close publication, and archive-ready records
- Partner boundaries remain explicit through final close
Infrastructure
- Custody, blotter, settlement, and close records stay linked
- Selected execution route with counterparty-boundary clarity
- Settlement booking and archive publication on one record
- Request-gated operator review with exported close evidence
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Funding Custody | Confirm the asset classification, funding source, custody perimeter, and SG settlement target; Apply the custody policy and statute lane before the execution ticket opens; Carry the same custody and settlement context into execution and booking; Admit the route only after classification, custody, and settlement checks agree |
| Execution Settlement | Select the approved execution, settlement, and close route, then lock the quote basis; Link execution, settlement booking, and close publication under one trade reference; Keep the selected route and close register visible through final settlement; Publish the settlement reference, close register, and archive outputs together |
Setup reference
| Field | Explanation |
|---|---|
| Settlement size | Sets the value carried through custody, execution, settlement, and close. Determines the amounts shown across the workflow records. |
| OTC path | Supports more than one OTC path. Controls how execution is sourced before settlement. |
| Traded pair | Fixed for this case. Scoped to one traded pair. |
| Trade direction | Fixed for this case. Determines how settlement and booking are read. |
| Custody model | Fixed for this case. Scoped to one custody model. Determines how custody confirmation is handled. |
| Settlement mode | Fixed for this case. Scoped to one settlement mode. Determines how settlement and close are recorded. |
| Counterparty class | Fixed for this case. Scoped to one counterparty class. Determines which counterparty context appears in the workflow. |