How do subscriptions and redemptions work in a tokenized fund?
Where the NAV strike, the cash leg and the on-chain register meet, and where they still do not.
A tokenized fund subscription still strikes at NAV. What changes is the register and the cash leg. The token record updates when the transfer agent confirms the subscription, and cash settles in fiat, a stablecoin or a tokenized deposit. The two legs rarely settle atomically today, so a timing gap remains.
How do subscriptions work in a tokenized fund?
Five steps, in this order. The investor is onboarded and verified. The receiving address is screened and added to the whitelist. The investor commits before the subscription cut-off. The administrator strikes NAV on the scheduled date. Units are minted to the whitelisted address once payment is confirmed.
- Onboard and verify. Identity, sanctions screening, jurisdiction and investor-category evidence, exactly as in a conventional fund.
- Whitelist the address. The verified wallet is recorded on-chain as eligible to hold this instrument. No whitelist entry, no units.
- Commit before the cut-off. Subscription windows come from the fund documents, not from the ledger.
- NAV strike. The administrator values the portfolio under the valuation policy on the published date.
- Mint to the address. Units are issued and the register updates in the same transaction.
Elapsed time from commitment to units in hand is typically two to five business days where the cash leg is a bank transfer, most of it waiting for payment confirmation and the strike. Where the cash leg sits on the same ledger as the units, the last two steps can collapse into a single transaction.
What tokenization removes here is the paper chain: instruction, confirmation and register update across three parties, each holding its own copy. What it does not remove is the fund’s own calendar.
How do redemptions work, and how long do they take?
Redemption reverses the sequence and takes as long as the fund documents say. Instruction before the cut-off, NAV strike, units burned or transferred back to a fund address, payment out. For an open-ended vehicle with monthly windows, two to six weeks end to end is normal; for a quarterly evergreen structure, longer.
Tokenization does not compress those terms. Notice periods, gates, lock-ups, redemption frequency and any holdback pending audit are portfolio and liquidity decisions, not register decisions. A quarterly-redemption fund does not become daily because its units are tokens, and any material claiming otherwise is describing a different fund.
One design choice matters operationally. Units may be burned on redemption, reducing units in issue and requiring the administrator’s books to move in step, or transferred to a treasury address held by the fund and treated as unissued. Both are used. The choice affects reconciliation and how units in issue are reported, and it should be settled at structuring rather than discovered at the first redemption.
What does improve is certainty. The register reflects the redemption immediately, so the holder list used for the next distribution or valuation is correct without waiting for a reconciliation cycle.
When is NAV struck, and what happens between strike and settlement?
NAV is struck on the schedule in the fund documents, by the administrator, under the valuation policy, with depositary oversight where the structure requires it. Tokenization changes neither the frequency nor the methodology. A portfolio that can be valued monthly cannot be valued hourly because its register is on a ledger.
Between strike and settlement there is a window in which the price is fixed and the transaction is not complete. In a subscription, the investor has committed at a known NAV and payment is in flight; in a redemption, units may already be locked or burned while cash has not yet arrived. That window is where operational risk lives, and it is unchanged in length by the ledger.
Two controls matter in the window. First, units in issue used in the NAV calculation should be read from the on-chain register at the strike, under a documented method — mismatches between the ledger and the books at a valuation date are the most common break in tokenized funds. Second, a subscription should not be minted before payment is confirmed unless the documentation expressly permits it and the risk is priced.
Claims of real-time NAV for private strategies should be read as marketing. What can genuinely be continuous is the units-in-issue figure, because the register is live. The asset side still depends on inputs that arrive periodically.
How does the cash leg settle — fiat, stablecoin or tokenized deposit?
Three options, with materially different timing and risk. A conventional bank transfer in fiat, which is the current default. An e-money token under MiCA, issued by an authorised credit or electronic money institution and redeemable at par. Or a tokenized deposit, where a bank represents a deposit claim on a ledger.
| Option | Timing | Who you are exposed to | Availability |
|---|---|---|---|
| Bank transfer (fiat) | Hours to days; settlement gap between legs | The banking chain and the counterparty until confirmation | Universal |
| E-money token under MiCA | Same-ledger; atomic settlement achievable | The EMT issuer and its reserves | Growing; issuer must be an authorised credit or e-money institution |
| Tokenized deposit | Same-ledger where the bank supports it | The issuing bank | Emerging, bank by bank |
| Unregulated stablecoin | Same-ledger | The issuer, on undisclosed or partly disclosed terms | Common outside regulated structures; rarely acceptable to a depositary |
Only the same-ledger options make delivery versus payment achievable inside one transaction. Where a token is used, holders take exposure to its issuer and reserves, and that exposure should be named and sized in the documentation rather than treated as cash. Under MiCA an e-money token issuer must hold full backing in low-risk liquid reserves and redeem at par on demand, which is a materially different proposition from an unregulated stablecoin.
Ask which ledger the cash sits on. That single question separates a settlement design from a settlement claim.
How is the on-chain register updated, and who updates it?
A named transfer agent or registrar updates it, appointed under the fund documentation and accountable for the accuracy of the record. Mechanically, subscriptions mint units to a whitelisted address, redemptions burn or return them, and transfers between eligible holders execute only if the token’s rules pass. Every one of those is a ledger transaction with an audit trail.
On-chain does not mean unowned. The ledger holds the record and validates transfers; it cannot be accountable for whether the record is correct, cannot respond to a court-ordered transfer, and cannot sign off a holder list at a valuation date. If the documentation names no accountable party, that is a gap.
Reconciliation at each NAV date should cover the holder list against processed instructions, units in issue on-chain against the administrator’s books, whitelist membership against current verification and sanctions status, failed or reverted transfers with reasons, and a dated sign-off retained for audit.
Then ask what happens when a break is found: who investigates, who authorises a correction to the register, and how the correction is evidenced. Read what a transfer agent does for a tokenized fund.
Where does this still break today?
In five places, and none of them is the token. First, the cash leg. Most European structures still settle cash off-ledger, so the process is fast on one side and unchanged on the other. Atomic subscription is available in specific structures and is not the market default.
Second, whitelist latency. An investor who changes custodian, moves jurisdiction or lets verification lapse cannot receive units until the on-chain state is updated, and the update depends on a human process. Investors experience this as a failed transfer with no explanation unless it has been explained in advance.
Third, corporate actions and edge cases. Distributions in kind, unit splits, probate transfers, creditor claims and regulator instructions all require a defined mechanic and an accountable party able to move or freeze a holding. Many structures have the technology and not the governance.
Fourth, secondary transfer. Documentation often permits transfer between eligible holders while no venue and no order book exist, so in practice most holders wait for a redemption window. Fifth, depositary comfort: oversight of a tokenized register is still a bespoke exercise in most markets, which lengthens launches and occasionally constrains design.
None of that makes tokenization not worth doing. It makes the benefit narrower than advertised: a better register and a lighter transfer process, not end-to-end instant settlement. Read what has to change for atomic settlement to become standard, or the tokenized fund pillar page.
- Directive 2014/65/EU (MiFID II); Regulation (EU) 2023/1114 (MiCA); Directive 2011/61/EU (AIFMD); Directive 2009/65/EC (UCITS); Regulation (EU) 909/2014 (CSDR) — EU Official Journal.
- COSIMO Digital regulatory authorisations, described as of 28 July 2026. Pending authorisations are not effective until granted.
This page is for informational purposes only. Nothing in it is an offer to sell, or a solicitation of an offer to buy, any security, and nothing here is investment, legal, tax, or financial advice. Regulatory authorisations are described as of the date stated; pending authorisations are not effective until granted.
← All Learn articles