SG debt issuance + servicing
Run tokenised debt through programme setup, qualified-investor gating, allocation, DvP settlement, authoritative register binding, coupon or redemption servicing, and reconciled close on one governed workflow.
Overview
Tokenised debt stays aligned across programme terms, investor gating, DvP settlement, register binding, and servicing evidence.
StableNexus coordinates the SG debt control plane while trustee, registrar, paying-agent, distribution, and settlement roles remain explicit and partner-led.
Route coverage
- Programme setup to coupon or redemption close
- Qualified-investor gating, subscription, allocation, and DvP settlement
- Authoritative register binding, notices, and entitlement control
- Payment confirmation and reconciliation exports
Infrastructure
- Trustee, registrar, paying-agent, and settlement roles stay explicit
- Authoritative register and cash-leg continuity
- Investor eligibility, holder controls, and transfer restrictions
- Event evidence and reconciliation close pack
Lifecycle stages
| Stage | Flow steps | Notes |
|---|---|---|
| Debt Setup | Confirm programme terms, tenor, and servicing mode; Record the SG perimeter outcome and distribution basis; Bind trustee, registrar, paying-agent, and dealer roles; Lock the settlement and authoritative-register model before outreach | Registrar and paying-agent performance remain appointed-role responsibilities even when orchestration is automated. |
| Qualify Fund | Screen investors against the approved distribution basis and eligibility pack; Capture subscriptions and build the allocation book; Confirm cash-leg readiness or prefunding status; Lock the final allocation and publish the book-close memo | Maker-checker controls apply before the allocation is released to issue. |
| Issue Register | Trigger issuance after allocation and cash-leg readiness are confirmed; Match asset and cash legs under DvP controls; Post allotments to the registrar-bound authoritative record; Deliver holder positions and publish issuance-close evidence | The registrar-bound register, not the token mirror alone, remains the definitive position source. |
| Service Reconcile | Freeze the record-date holder snapshot and publish the servicing notice; Release the paying-agent instruction against the holder record; Post payment, redemption, or event-state updates to the evidence spine; Publish reconciliation and closeout exports for operations, finance, and investors | Default or workout events belong in a separate exception path and should not be implied by the baseline servicing lane. |
Setup reference
| Field | Explanation |
|---|---|
| Issue size | Sets the issuance amount carried through qualification, funding, registry binding, and servicing. Determines the values shown across the workflow records. |
| Debt structure | Supports more than one debt structure. Controls the terms and servicing path. |
| Investor perimeter | Sets who the issue is open to. Controls who can be cleared, funded, and allocated. |
| Register model | Supports more than one register model. Controls how holder records are maintained. |
| Servicing event | Supports more than one servicing path. Controls which downstream event the workflow follows. |
| Tenor | Fixed for this case. Keeps the workflow on one programme timeline. Determines the servicing and maturity horizon. |
| Settlement method | Fixed for this case. Scoped to one issuance settlement method. Determines how settlement is recorded. |