Gateway capabilities
- Permissioned asset lifecycle
- Eligibility policy
- NAV & register evidence
Funds & Assets · Design record
Tokenized funds and private credit
Represent regulated fund or credit interests with controlled eligibility, transfer, pricing, servicing, and cash settlement.
01Issuer or fund manager→
02Administrator→
03Investor→
04Transfer agent or registry
Target business outcome
An inspectable asset lifecycle that can support atomic delivery-versus-payment and existing legal records.
Gateway implementation layer
Translate the workflow into a deployable operating boundary.
The record defines the financial problem. Gateway then maps the relevant Platform capabilities, privacy fit, deployment, specialist dependencies, and validation path.
Open Privacy Suite applicability
Keeps holder identity and positions private; transfer agents see their book.
Deployment
Placed beside the legal register; the administrator remains authoritative.
Partner dependencies
- Fund administrator
- Custody
- Transfer agent
Implementation path01 · Map the flow02 · Validate the hardest assumption03 · Define the production boundary
Actors
- Issuer or fund manager
- Administrator
- Investor
- Transfer agent or registry
- Custodian
- Oracle
- Regulator
Confidential data
- Investor positions
- NAV and pricing inputs
- Credit terms
- Collateral and borrower information
- Transfer rationale
Public or shared evidence
- Asset identifier and approved terms
- Eligibility proof
- Signed price or NAV reference
- Transfer and settlement receipt
Regulator and auditor access
Authorised administrators, auditors, and regulators receive full or scoped lifecycle views; investors receive only their positions and permitted disclosures.
Institutional constraints
- The legal registry and token record must be reconciled
- Eligibility and transfer restrictions can change
- Asset servicing extends beyond issuance
- Oracle and cash-leg failure modes must be defined
Viable approaches
Permissioned token standard
Encode eligibility and transfer controls using a regulated-asset standard such as ERC-3643.
Private asset domain
Keep positions and terms inside a controlled execution environment with external settlement evidence.
Hybrid privacy
Use commitments or selective disclosure for positions while keeping necessary registry facts available.
Questions to resolve during discovery
- Which record has legal authority?
- Who calculates and signs valuation data?
- How are corporate actions and servicing handled?
- Which secondary transfers are permitted?
Relevant standards and frameworks
- ERC-3643
- ICMA terminology where applicable
- Fund or securities regulation
- DvP settlement policy
Related cases
Continue through the adjacent operating questions.
Financial workflows rarely stand alone. These records cover the closest dependencies and alternatives.
TradingDesign record
Private DvP and secondary markets
Coordinate asset transfer and cash settlement while limiting exposure of intent, price, position, and counterparty data.
Open use-case record →Data & OraclesDesign record
Signed data and private oracles
Use external prices, events, and institutional facts while limiting disclosure of query identity and protected source data according to the access model.
Open use-case record →Identity & ComplianceDesign record
Selective disclosure for oversight
Provide authorised oversight roles with a scoped, time-bound view while limiting broader disclosure of confidential workflow data.
Open use-case record →Start with the architecture
Turn tokenized funds and private credit into an institution-specific architecture.
A workshop maps the actors, authoritative records, disclosure requirements, operating boundary, and highest-risk assumptions into a proposed architecture.