Tokenized Deposits & Programmable Cash
Coordinate tokenized deposits and programmable cash runs across program setup, institution controls, issuer-authorized issuance, maker-checker release, receiving-bank acknowledgment, settlement finality, and reconciliation-led reporting close.
Overview
Bank-issued digital money with maker-checker release, receiving-bank finality, and reconciliation-led close.
For bank-issued digital-money programmes that need issuer control, governed release, receiving-bank confirmation, and report-ready close.
Route coverage
- 6-stage bank-money lifecycle
- Programme perimeter, participant acceptance, and control-account readiness
- Issuer-authorised funding, issuance, and maker-checker release
- Receiving-bank confirmation, settlement finality, and exception routing
- Published close records and export handoff
Infrastructure
- Explicit issuer, receiving-bank, and control-account boundaries
- Counterparty acceptance, screening, and operating-window controls
- Issuance authority, rule trace, payment trace, and receiving-bank confirmation on one governed spine
- Reconciliation reports, exception register, and export records ready for review
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Program Setup | Fix the programme perimeter, issuer authority, currencies, and settlement anchor; Bind participant scope, control accounts, and close posture before onboarding opens; Record the operating window and exception owner for the lane |
| Participant Controls | Approve the receiving institution, registry coverage, account prevalidation, and route policy; Link control accounts, screening, and release limits; Keep window status visible before funding opens |
| Funding And Issuance | Validate source funds and reserve the issuance amount; Record issuer mandate and mint acknowledgement against the position; Hold release until funding, authority, and reservation agree |
| Allocation And Policy | Convert the issued position into a payment order with rule trace and quorum; Clear holdbacks and set return posture before settlement handoff; Release only inside the approved operating window |
| Settlement And Payout | Submit the order with trace reference and receiving-bank destination; Track acknowledgement, finality, and return control as separate states; Hand close only after the receiving bank confirms outcome |
| Redemption And Evidence | Post the close reference and settlement-day reconciliation batch; Run settlement-day reconciliation, resolve exceptions, and release reports and exports; Finish on published close records, not a generic success state |
Setup reference
| Field | Explanation | Related terms |
|---|---|---|
| Programme mode | Supports more than one path. Controls which steps execute and which records are created. | Tokenized deposit, Tokenized cash, Bank money |
| Participant scope | Defines who can send and receive. Controls which participants are accepted on the route. | |
| Currency set | Sets the currency scope. Controls which balances and movement paths are in play. | |
| Movement scope | Supports more than one movement path. Controls whether the workflow stays internal, crosses banks, or uses interop. | Bank money, Tokenized cash |
| Treasury intent | Sets the operating purpose behind the movement. Controls which policy path the workflow follows. | |
| Institution acceptance | Sets how receiving institutions are approved. Controls which acceptance checks apply before release. | |
| Disposition routing | Sets release and return behavior. Controls the release, retry, hold, and return path. | Release disposition |
| Operating window | Sets when movement can proceed. Controls whether the workflow releases now, waits, or returns. | Operating window |
| Evidence mode | Sets closeout evidence depth. Controls how the workflow is closed and what records are exported. | Liability evidence |