Tokenized Deposits & Programmable Cash
Coordinate bank-money runs with an explicit tokenized-deposit vs programmable-cash choice across program setup, institution acceptance and controls, funding and issuance, disposition and governed release, settlement with confirmation and return, and redemption, reconciliation, and evidence across same-bank, cross-bank, and cash-leg routes.
Scope
Bank money with explicit tokenized-deposit vs programmable-cash choice, same-bank / cross-bank / cash-leg modes, governed release, receiving confirmation, and recredit-aware closeout.
Scope
- Money forms
- Tokenized deposit; Programmable cash
- Route modes
- Same-bank; Cross-bank; Cash-leg
- Boundary
- StableNexus orchestrates policy, workflow, and proof only
Boundary
StableNexus role: orchestration, policy, workflow, proof. Not the issuing bank, receiving bank, settlement bank, control-account owner, or liability obligor.
Actor-lane operating map
Six actor lanes plus StableNexus orchestration overlay.
Route-mode phase map
How the six chapters sequence across each route mode.
Money-form vs route-mode matrix
| Axis | Options | Close basis |
|---|---|---|
| Money form: Tokenized deposit | Runtime class: tokenized_deposit | Liability context: bank_liability |
| Money form: Programmable cash | Runtime class: bank_issued_tokenized_cash | Liability context: bank_money_program |
| Route mode: Same-bank movement | Receiving confirmation: false | Close basis: internal posting |
| Route mode: Cross-bank coordination | Receiving confirmation: true | Close basis: receiving institution confirmation |
| Route mode: Cash-leg coordination | Receiving confirmation: conditional | Close basis: paired cash leg reconciliation |
Lifecycle states
From draft through route-mode branching to evidence close.
Closeout-first technical sequence
Settlement resolution across same-bank, cross-bank, and cash-leg close paths.
Canonical chapters
| Chapter | Outcome | Lifecycle states |
|---|---|---|
| 1. Program Setup | Program perimeter, currencies, institutions, and allowed movement scope defined. | draft, scoped |
| 2. Institution Acceptance & Controls | Institution acceptance, control-account readiness, and control discipline established. | institutions_ready |
| 3. Funding & Issuance | Source funding confirmed and issuer authorization obtained before issuance becomes active. | funded, issued |
| 4. Disposition & Governed Release | Issuance separated from governed release; release policy made explicit. | release_held, release_authorized |
| 5. Settlement, Confirmation & Return | Same-bank posting, cross-bank receiving confirmation, cash-leg coordination, return, or recredit resolved. | same_bank_posting, awaiting_receiving_confirmation, cash_leg_in_progress, settlement_closed, returned_or_recredited |
| 6. Redemption, Reconciliation, & Evidence | Redemption, reconciliation, and evidence publication completed as one governed layer. | redemption_or_outstanding, reconciled, evidence_closed |
Artifact and evidence matrix
| Chapter | Runtime artifacts | Docs-derived surfaces |
|---|---|---|
| 1. Program Setup | program_blueprint, entity_scope_matrix | money_form_state |
| 2. Institution Acceptance & Controls | participant_registry_snapshot, receiving_institution_profile, control_account_matrix, policy_route_profile, operating_window_profile, eligibility_limit_report | participant_control_state |
| 3. Funding & Issuance | source_funds_validation, liquidity_position_snapshot, reservation_record, issuance_authorization, treasury_mint_record | issuance_authorization_state, liability_packet_view |
| 4. Disposition & Governed Release | allocation_release_note, release_disposition_policy, programmable_transfer_decision, payment_order_receipt | release_policy_state, liability_packet_view |
| 5. Settlement, Confirmation & Return | settlement_resolution_packet, settlement_return_record, interop_settlement_receipt | receiving_institution_confirmation, return_or_recredit_state, settlement_window_state |
| 6. Redemption, Reconciliation, & Evidence | redemption_burn_record, ledger_reconciliation_snapshot, exception_state_report, evidence_pack_export | close_reporting_packet |
Control overlay matrix
| Overlay | Applies to chapters | Failure branch |
|---|---|---|
| Policy gate | Funding & Issuance; Disposition & Governed Release | Release blocked until policy re-evaluation |
| Control-account validation | Institution Acceptance & Controls; Funding & Issuance | Funding blocked until control-account validation passes |
| Operating-window / cutoff governance | Disposition & Governed Release; Settlement, Confirmation & Return | Release or settlement deferred to next window |
| Finality confirmation | Settlement, Confirmation & Return | Settlement held pending finality or escalated to exception |
| Idempotent release / recovery | Disposition & Governed Release; Settlement, Confirmation & Return | Duplicate replay safe-returned or conflict escalated |
| Return / recredit handling | Settlement, Confirmation & Return; Redemption, Reconciliation, & Evidence | Return or recredit processed before close |
Derived surfaces
| Surface | Description | Active in chapters |
|---|---|---|
| Money-form state | Current money form, route mode, close basis, and receiving-confirmation requirement. | Ch. 1 |
| Participant control state | Institution acceptance, control-account validation, limit state, and operating window. | Ch. 2 |
| Issuance authorization state | Funding state, issuer authorization, and issuance status. | Ch. 3 |
| Release policy state | Policy snapshot, release decision, idempotency, and cutoff state. | Ch. 4 |
| Receiving-institution confirmation | Confirmation requirement, status, source, and credit-evidence presence. | Ch. 5 |
| Return / recredit state | Return or recredit status, trigger, and reference presence. | Ch. 5 |
| Settlement window state | Window type, status, and finality state. | Ch. 5 |
| Liability packet view | Money form, route mode, liability obligor, redeemability path, and reference presence. | Ch. 3, 4 |
| Close reporting packet | Reconciliation state, evidence completeness, and included reference types. | Ch. 6 |
Support terms
- Tokenized deposit
- A bank liability represented in programmable form.
- Tokenized cash
- Bank-issued settlement value used between approved institutions.
- Same-bank movement
- A route that stays inside the issuing institution's own balance context.
- Cross-bank coordination
- A route that requires destination-institution acceptance before close.
- Cash-leg coordination
- The payment-side workflow that supports a separate tokenized action.
- Control account
- The governed bank-side account or balance used for controls.
- Receiving institution
- The approved bank or institution profile that can accept governed movement.
- Recredit
- A controlled return of value when the instructed route does not close.
Support docs
- Bank Money & Programmable Cash: Run institutional bank-money programs with explicit money-form choice, governed release, receiving-institution confirmation, and closeout evidence.
- Tokenized Deposits: Bank-liability money-form reference and release rules.
- Interactive case: Run this case interactively on the public proof surface.
- Case projector: View the full-screen projector for this case.
Non-goals
StableNexus is not the issuing bank, receiving bank, settlement bank, control-account owner, or liability obligor on any leg.
Same-bank movement, cross-bank coordination, and cash-leg coordination are distinct close conditions — a close on one route does not imply close on another.