Tokenization setup + register
Define what a token represents, who issued it, who keeps the official register, what supports the claim, and how issuance and servicing records stay aligned.
Overview
A bank creates the first tokenized version of an approved asset. The route defines what investors own, who keeps the legal register, what backs the asset, who may hold it, and when the first tokens are issued.
Use this when a bank, issuer, or asset sponsor needs to create the first tokenized version of an approved asset: what the token represents, who keeps the official register, what backs the asset, who may hold it, and how the first issuance closes.
Route coverage
- Defines the asset claim and issuer authority before technical issuance starts
- Binds official register and custody or backing proof as the source of truth
- Sets holder, wallet, transfer, and revocation rules before allocation
- Creates token metadata and first issuance allocation only after legal, register, and eligibility controls are aligned
- Closes with allocation, fees, custody proof, register match, and servicing calendar
Infrastructure
- Issuer authority, registrar, custodian, holder-rule registry, and tokenization engine stay as separate roles
- Official register, token metadata, custody proof, and servicing schedule remain matched
- Economics are visible as setup, issuance, custody, registrar, transfer-agent, and servicing rows
- The close state produces a reusable base for fund order, collateral, and secondary transfer cases
Lifecycle stages
| Stage | Flow steps |
|---|---|
| Asset Claim Scope | Bind product type, issuer authority, legal claim, governing law, and appointed roles before issuance opens; Show setup fee, legal review charge, and issuer approval reference as first commercial rows |
| Register Custody Bind | Name the official register owner and custody or backing controller before token metadata is created; Show registrar setup fee, custody control charge, and backing statement reference on the same screen |
| Eligibility Transfer Rules | Set investor class, jurisdiction, wallet, concentration, transfer, and revocation rules; Show eligibility check cost, transfer-rule maintenance fee, and policy version as operational fields |
| Metadata And Issuance | Create symbol, supply cap, permission model, register linkage, and token representation fields before first allocation; Show metadata reference, permission version, and register linkage before issuance fee rows appear |
| Issuance Allocation | Release the first issuance batch only after legal claim, register, custody proof, holder rules, and metadata are bound; Show allocation quantity, issuance instruction, idempotency key, and issuer fee invoice as operational rows |
| Register Sync Close | Match official register, token ledger, custody proof, fee ledger, and servicing calendar; Close with setup revenue, custody accrual, registrar rows, and next servicing date visible |