Delivery Backlog
Product delivery backlog
A single initiative broken into delivery epics and user stories, each with clear acceptance criteria — structured for cross-functional delivery across Product, Engineering, Operations, Legal, Compliance, Financial Crime and Risk.
24/7 Tokenised Treasury Settlement
Enable corporate treasury clients to issue, transfer and redeem tokenised bank deposits across approved group entities, 24 hours a day, with the same control standards as traditional wholesale payments.
Definition of Ready
- Acceptance criteria defined and agreed with Risk / Compliance where applicable
- Dependencies identified and sequenced against other stories
- API / data contract agreed where the story touches an integration point
- Estimated and sized by the delivery team
- Non-functional requirements identified (security, resilience, auditability)
Definition of Done
- Acceptance criteria met and demonstrated to the product owner
- Automated test coverage in place for the change
- Security and compliance review passed where applicable
- Reconciliation and audit-trail behaviour verified where applicable
- Documentation updated and change released to the target environment
Non-functional requirements
Apply across every epic, not just where called out explicitly
Defined RTO / RPO per service; failover tested; graceful degradation under partial outage.
Continuous automated reconciliation between tokenised and core ledgers, with a defined break-resolution SLA.
Scoped, authenticated API access with payload validation, rate limiting and policy-engine enforcement.
Immutable, timestamped audit trail for every settlement-affecting action, independent of outcome.
Entity and user onboarding
As an implementation manager, I want to onboard a client's group entities and named users so that only approved participants can access the platform.
Acceptance criteria
- Each entity is linked to verified KYC and legal-entity records
- Users are assigned a role (initiator, approver, viewer) per entity
- Onboarding cannot complete until compliance sign-off is recorded
- Client receives confirmation with go-live date
Entitlement configuration
As a client administrator, I want to configure which entities can transact with each other so that transfers only occur between approved counterparties.
Acceptance criteria
- Entity-to-entity entitlement pairs are configurable per client
- Attempted transfers to non-entitled entities are blocked pre-submission
- Changes to entitlements require dual approval
- Entitlement changes are logged with timestamp and approver identity
Role-based approval limits
As a risk manager, I want transfer approval authority to scale with transaction value so that larger transfers require senior sign-off.
Acceptance criteria
- Approval tiers configurable by currency-equivalent thresholds
- Transfers above a tier require a second, more senior approver
- System prevents self-approval by the initiating user
Issue tokenised deposit
As a treasury manager, I want to issue tokenised deposits backed 1:1 by a funded bank deposit so that I can move value on the settlement ledger.
Acceptance criteria
- Issuance amount cannot exceed the underlying funded deposit
- Each issuance is recorded with a unique reference and timestamp
- Ledger balance updates only after underlying funds are confirmed
Transfer tokenised deposit between approved entities
As a corporate treasury manager, I want to transfer tokenised USD deposits between approved group entities so that I can move liquidity outside traditional cut-off times.
Acceptance criteria
- Only authorised users can initiate transfers
- Beneficiary must be an approved entity
- Sanctions and entitlement checks must complete before settlement
- Transfer is either atomically settled or fully rejected
- Receipt includes timestamp, unique transaction ID and audit events
- Balances and reports update after settlement
Redeem tokenised deposit to fiat
As a treasury manager, I want to redeem tokenised deposits back into the underlying bank account so that I can use funds outside the settlement platform.
Acceptance criteria
- Redemption reduces token balance and releases underlying funds same day
- Redemption is blocked if token balance is insufficient
- Redemption receipt is generated with a unique reference
24/7 availability and scheduled maintenance windows
As a treasury manager, I want the platform to be available outside banking hours so that I can settle urgent liquidity needs at any time.
Acceptance criteria
- Platform available 24 hours a day excluding published maintenance windows
- Maintenance windows are communicated at least 5 business days in advance
- Status page reflects real-time platform availability