In this article
Every professional who has closed a traditional fund redemption, wound up a property SPV, or settled a private credit exit knows the same headache: the money arrives in one place, the obligations are spread across many, and the clock is ticking on getting everything right. Tokenized real-world assets (RWAs) do not eliminate that choreography. What they change is the precision and speed with which the final distribution can occur — and that is where the settlement layer, done well, earns its value.
This article walks through the full mechanics of a tokenized asset redemption, from the moment a holder submits a request to the moment every party has received their correct share. It is written for the professionals who sit inside those workflows — transfer agents, fund administrators, settlement agents, closing attorneys, escrow officers, and OTC desks — because they are the ones who need to understand exactly where onchain payment routing fits alongside the work they already do.
Worked example from the private credit scenario below: an $800,000 USD position redeemed at the quarterly window.
The market context: why redemption has become the hard problem
With tokenized RWAs crossing $50B in total value locked in 2025, boosted by institutional products like BlackRock's BUIDL and Ondo's USDY, the industry is finally realising something important: the real challenge isn't tokenization, it's liquidity and redemption.
Real-world asset tokenization refers to the process of creating digital representations of off-chain assets — such as private credit facilities, trade receivables, government bonds, real estate, and structured products — on a blockchain, enabling these assets to be fractionalized, traded, and programmatically managed through smart contracts. That description captures the entry and holding phases well. The exit phase is where the engineering gets demanding and where the off-chain and on-chain worlds have to meet with precision.
The common mistake developers make is assuming redemption is just a _burn() call. In reality, it is a coordinated workflow involving queues, NAV updates, custodian transfers, settlement windows, and regulatory checks.
Settlement agents and fund administrators already know this. The question is not whether the off-chain process is complex — it always is — but whether the payment distribution at the end of that process can be made simultaneous, certain, and auditable. That is the productive question.
What a redemption actually involves: the full stack
Before focusing on payment mechanics, it helps to map every layer that a redemption touches, because payment certainty depends on each layer operating correctly.
The legal wrapper
The legal structure behind an RWA token determines what rights token holders actually possess. In many cases, holding a token does not mean directly owning the underlying asset. The token may represent a beneficial interest in a special purpose vehicle (SPV), a fund unit, a debt claim, or a fractional ownership right in a trust structure. Legal documents define what token holders are entitled to: ownership, beneficial interest, redemption rights, or profit-share. The redemption payment amount and priority are entirely a function of that legal wrapper. A settlement agent processing a redemption must read the fund or SPV documents first; the smart contract is the execution layer, not the governing document.
NAV calculation and pricing
Redemption terms — like lock-up periods, liquidity thresholds, and NAV calculation processes — can be built directly into digital systems and handled automatically. But the NAV figure that feeds into those systems still originates off-chain. Tokenization does not displace the principles behind independent valuation. If a system displays or uses NAV, the provenance and decision process behind that figure remain essential.
For a tokenized money market fund or a Treasury product, NAV updates can be extremely frequent. Spiko updates NAV daily through its registered fund administrator, while Superstate pushes this further with a continuous oracle updating every second. For private credit or real estate, NAV may update quarterly and require a formal external appraisal before a redemption request can be priced. The timing of NAV confirmation directly affects when a redemption can be approved and how much the exiting holder will receive.
Compliance verification
When a redemption request is approved, the broker sells the necessary asset fraction, cash is wired to the custodian's omnibus account, and funds are distributed to investors on a pro-rata basis — but this flow must remain compliant with regulatory requirements. That compliance layer sits between the approval step and the cash movement step, and it is not optional. Sanctions screening, eligibility re-verification, and large-redemption review all operate here. No issuer handles this alone. A production RWA product involves a tokenization platform, a custodian, legal counsel in each relevant jurisdiction, a KYC provider, an oracle network, and smart contract auditors.
The custody and liquidation step
Burning tokens on-chain is only half the story — real redemption happens through traditional financial rails. Custodians are responsible for holding both the underlying assets and the cash used for payouts. Qualified custodians like Anchorage, BitGo, or banks such as BNY Mellon must meet strict institutional standards.
The issuer checks the blockchain to confirm the holder actually owns those tokens, then locks them in the smart contract so they cannot be sent or sold while the redemption is being processed. The issuer then instructs the custodian to sell the corresponding underlying assets on the traditional market. The custodian executes the sale through standard brokerage channels.
Settlement follows traditional timelines — typically one business day (T+1) for US equities under SEC Rule 15c6-1(a). Cash from the sale arrives in the issuer's account once settlement clears. For less liquid asset classes, the window is longer. Some tokenized money market funds process withdrawals the next business day. Others, particularly private credit, real estate, and structured products, have redemption windows of 60 to 180 days.
The token burn
The redemption request triggers queue entry and eligibility checks. The custodian liquidates the relevant fractions and disburses proceeds via wire or SWIFT. Oracles attest to delivery. Post-confirmation, tokens are burned, supply contracts, and events are logged for audit.
The two burn models and what they mean for payment risk
There are two primary ways protocols structure redemption flows: the burn-first model, in which tokens are burned immediately and the issuer is trusted to complete the payout off-chain; and the confirmation-first model, where the burn occurs only after off-chain settlement is verified.
These two models carry very different risk profiles for a settlement agent managing the payment side.
Burn-first is faster and simpler technically, but it creates a window where the token has been destroyed and the cash has not yet moved. If the payment rail fails, the issuer is left with an obligation that has no on-chain backing. For a fund administrator managing a large redemption — say $2,400,000 USD (~AUD 3,700,000) across multiple exiting holders — the exposure during that window is material.
Confirmation-first is more operationally conservative. The token is held in a locked state until an oracle or authorised administrator confirms that the cash proceeds have been disbursed. Only then does the burn execute and the registry update. The principle is: validate the request, pay proceeds under the liquidity terms, and extinguish the redeemed units. A payment or token can look complete in an interface before every obligation, registry, and settlement record is actually complete.
This is why settlement agents and fund administrators remain central to any well-run tokenized asset structure. They are the authorised parties who confirm cash finality, trigger the oracle attestation, and approve the burn. The smart contract executes; the human professional with legal authority and institutional accountability makes the call.
Where the payment distribution gets complicated: multiple parties, one pool of cash
Once the custodian has delivered the redemption proceeds to the fund or SPV account, the straightforward assumption is that the money flows to the exiting token holder. In simple structures, that is broadly correct. In most real-world structures, it is not the full picture.
Consider a mid-sized tokenized real estate fund processing a partial redemption of $1,500,000 USD (~AUD 2,310,000) as four holders exit simultaneously at a quarterly window. From that single inbound amount, the following parties typically have claims that must be satisfied before or alongside the net holder proceeds:
- The fund administrator or transfer agent, who is owed a redemption processing fee, typically calculated as a basis-point percentage of the redeemed NAV
- The fund manager, who may be entitled to a performance fee on realised gains above the hurdle rate, calculated at the time of exit
- The custodian, who is owed a transaction or account fee for executing the underlying asset sale
- Legal counsel, if a redemption triggers a reporting obligation or consent requirement under the fund's constitutional documents
- The placement agent or introducing broker, in structures where a trail fee or exit fee is owed to the party who placed the capital originally
- Each of the four exiting token holders, each receiving a pro-rata share of the net proceeds after the above deductions
In a traditional fund redemption, this distribution is handled sequentially — the administrator receives the gross proceeds, applies the fee schedule manually, and wires each party in separate transactions, typically over one to three business days. The exiting holders wait; the parties providing services wait; reconciliation is manual; and each wire introduces a new moment of potential error or delay.
Subscription and redemption can take T+1 to T+3 minimum. Investor capital sits idle during settlement. Geographic restrictions and high minimums lock out entire investor segments. Pricing, fee processing, and investor reporting require spreadsheets and manual reconciliation.
This is not a criticism of the professionals managing the process — it is a structural limitation of the sequential payment model. The administrator cannot send the net holder proceeds until fees have been confirmed. Fees cannot be confirmed until accounting has run the numbers. Each step waits for the previous one.
What onchain routing changes about the payment step
The payment distribution step — once gross proceeds are confirmed and the fee schedule is locked — is a routing and disbursement problem, not a compliance or custody problem. It has exactly the shape that onchain payment routing is designed to solve.
Once the fund administrator has confirmed:
- The gross redemption amount
- The applicable fee schedule for each party
- The wallet addresses or bank account destinations for each recipient
…the entire distribution can be encoded as a single outbound transaction that splits the inbound total into its preset shares and delivers every party's portion simultaneously, in one on-chain settlement.
This is what shaka.deal does. It acts as a payment router on Ethereum: one incoming payment, preset percentage shares per party, simultaneous payout to every address, final settlement in one transaction. The fund administrator retains full control over the share configuration — shaka.deal routes, it does not hold funds. The moment the transaction confirms, every party's balance is updated and no further reconciliation is required.
Atomic settlement is a mechanism where asset transfer and payment occur simultaneously in a single transaction, removing the counterparty risk window that exists in traditional T+1 or T+2 settlement. Applied to the redemption distribution step, this means the administrator no longer sends four separate wires across three business days. The configured routing fires once. The exiting holders, the fund manager, the custodian, the administrator, and any other party with a preset share all receive their portion in the same block.
Distribution and waterfall rules can be encoded directly into the fund's architecture, ensuring that payouts follow agreed seniority and tiering, with no manual intervention needed. The fund administrator sets the rules; the router enforces them on execution.
A concrete scenario: tokenized private credit fund exit
To make this tangible, consider the following structure.
A tokenized private credit fund has issued ERC-3643 tokens representing pro-rata claims on a pool of trade receivables. The fund has 200 token holders. One holder — an institutional treasury — is exiting a position worth $800,000 USD (~AUD 1,230,000) at the quarterly redemption window.
Step 1 – Request and eligibility check. The holder submits a redeem instruction through the issuer's platform. The smart contract locks the relevant token balance, preventing any further transfer.
Step 2 – NAV confirmation. The fund administrator confirms the current NAV per unit with the fund's appointed valuation agent. Because this is a private credit pool with monthly NAV cycles, the redemption is priced at the most recent NAV rather than a live market quote.
Step 3 – Custodian liquidation. The fund manager instructs the custodian to liquidate a proportionate slice of the receivables book — in this case, partially from a maturing tranche — and receive the cash proceeds into the fund's settlement account. This takes three business days on traditional rails.
Step 4 – Fee and distribution calculation. The fund administrator calculates the waterfall:
| Waterfall line | Amount | Basis |
|---|---|---|
| Gross proceeds | $800,000 USD | Position redeemed at the most recent NAV |
| Management fee accrued on exit | $3,200 USD | 1.60% annualised, pro-rated to quarter |
| Performance fee on gains above hurdle | $12,000 USD | Calculated against this holder's entry price |
| Custodian transaction charge | $800 USD | Charge for the liquidation |
| Net holder proceeds | $784,000 USD | Gross proceeds less the three deductions |
Step 5 – Payment routing. The fund administrator configures a single payment transaction with the calculated shares: management fee to the fund manager wallet, performance fee to the manager's carry wallet, custodian charge to the custodian's settlement address, and net proceeds to the holder's verified address. This configuration is routed through shaka.deal. When the gross proceeds arrive at the routing address, the split executes in one transaction. Every party receives their portion simultaneously. The transaction is final; there is no reversal, no float, no further reconciliation step.
Step 6 – Token burn. On confirmation of the successful payment transaction, the oracle attestation triggers and the smart contract burns the locked tokens. The on-chain cap table updates. The fund administrator's register and the smart contract are now in agreement.
The holder has exited cleanly. The service parties have been paid. The remaining token holders are unaffected. The entire distribution step took one transaction.
Redemption models by asset class: what settlement agents need to know
Not every tokenized asset has the same redemption profile. The payment mechanics are constant — proceeds arrive, parties are owed shares, the routing step distributes — but the timing, liquidity source, and fee structure vary considerably by asset class.
Tokenized government bonds and money market funds
Tokenized Treasuries and money-market funds currently pay roughly 3–5% with daily redemption windows. These are the most liquid RWA structures. Redemptions process quickly because the underlying assets can be liquidated within standard market hours. Franklin Templeton's BENJI token, representing the U.S. Government Money Market Fund (FOBXX), was among the first U.S.-registered mutual funds on a public blockchain, offering daily liquidity and redemption. For settlement agents working in this segment, the distribution calculation is straightforward — fees are low, NAV is continuously updated, and the main challenge is ensuring that payment routing is configured correctly for the management fee, the transfer agent fee, and the net holder amount.
Tokenized real estate
Real estate has historically been one of the most illiquid asset classes. Real estate has always been considered profitable and relatively safe. Regardless of what happens in the world and in the stock market, people will always need places to live and work. But transactions in this field are complex and expensive, rendering real estate relatively illiquid. Tokenization changes the fractionalization and secondary trading dynamics, but a primary redemption from an SPV holding a physical property still requires either a property sale or a refinancing event to generate cash. Distribution waterfalls, capital calls, and property-level events like a refinancing that triggers a partial redemption must all be handled in the operating documents and confirmed by the settlement agent before any distribution fires.
In a property exit, the gross redemption figure may include sale proceeds net of mortgage payoff, accrued property management fees, legal fees for the conveyancing, transfer tax, and the manager's carried interest. That is five or more distinct payment obligations flowing from a single gross amount. Configuring the payment routing to honour all five simultaneously — rather than processing them as sequential wires — is exactly the operational improvement that reduces settlement risk and accelerates time-to-close for every party.
Tokenized private credit
Private credit pays higher yields of 8–15%, but carries lockups and illiquidity risk. Redemptions in private credit pools are typically batch-processed at fixed windows — monthly or quarterly — because the underlying loans cannot be liquidated on demand. Centrifuge batches all deposit and redemption requests into epochs. At epoch close, the pool manager approves orders at the current NAV, shares are issued or revoked with balanced accounting entries, and fulfilment callbacks are sent cross-chain to each spoke where investors can claim.
For the payment distribution at epoch close, a private credit fund may be distributing simultaneously to hundreds of exiting holders alongside fee obligations to the fund manager, the originator, and the servicer. Doing this as individual sequential wires is impractical at scale. A properly configured routing layer that receives the gross payout pool and distributes preset shares to all parties in a single transaction is the correct tool for this volume.
Tokenized commodities
Tokenized US Treasuries crossed $10 billion for the first time in February 2026. Gold-backed tokens PAXG and XAUT dominate the commodity segment, which rose 289% to reach $5.5 billion by Q1 2026. Gold-backed token redemptions are typically straightforward because the underlying is highly liquid and market prices are continuous. The distribution mechanics are simpler: the holder receives spot value at the redemption price, less a handling fee to the vault custodian. Two parties, one split, one transaction.
What makes a redemption payment final
Settlement professionals trained in traditional finance understand that a wire is not truly final until it clears, reversals are possible, and disputes can unwind a payment long after the sender's screen showed "sent." These risks introduce real-world friction in complex distributions — every party who has been paid is, technically, exposed to a clawback until the settlement window closes.
In atomic settlement, asset transfer and payment occur simultaneously in a single transaction, removing the counterparty risk window that exists in traditional T+1 or T+2 settlement. When a redemption distribution is routed on-chain through a payment router, the settlement is final at transaction confirmation. There is no reversal mechanism, no counterparty float, and no reconciliation window. Each party's share arrives in their wallet in the same block in which the gross amount was submitted. Every party knows, immediately and with certainty, that their portion has been received.
When an investor triggers a redemption, a smart contract can automate redemption approval and payment at an agreed price, at which point stakeholders are updated in real time with a complete audit trail. This audit trail — the on-chain record of every address that received funds and the exact amount at the exact block — is available to the fund administrator, the regulator, and all parties at the moment of settlement. There is no post-settlement reporting lag.
The role of the settlement professional in an onchain redemption
It is worth being direct about something that sometimes gets confused in commentary about tokenization: the professionals who manage redemptions are not replaced by smart contracts. Their roles shift in character but remain essential.
Transfer agents and fund administrators face perhaps the most significant operational shift. The core TA function — maintaining the share register, processing subscriptions and redemptions, managing records — does not disappear, but the tools and workflows change fundamentally. TAs that adopt tokenization technology can automate much of their manual processing through smart contracts, reduce reconciliation burdens, and offer real-time register visibility to all stakeholders.
The fund administrator still owns the fee schedule, still confirms NAV, still approves the redemption at the correct price, and still authorises the payment. What changes is that the execution of the distribution — the routing of the gross amount to the correct parties in the correct proportions — no longer requires sequential manual wires. The configuration is set once, the authorisation is given once, and the routing fires once.
For a closing attorney managing the wind-down of a tokenized real estate SPV, the value is the same: confirm the waterfall sequence in the operating agreement, set the routing configuration, and the distribution executes with one transaction at closing — management fee, carried interest, legal fee reserve, and net holder proceeds all settled simultaneously.
For an OTC desk facilitating a large block exit from a tokenized credit fund, the routing certainty means counterparty settlement risk disappears at the moment the payment router confirms. The desk does not need to hold proceeds overnight waiting for wires to clear. The split runs at submission.
Structuring the routing configuration correctly
For professionals new to configuring onchain payment routing, a few practical points on how to approach the redemption distribution step.
Map the waterfall before the window opens. The worst time to calculate fee obligations is after the custodian has already delivered the gross proceeds. The fee schedule — management fee, performance fee, custodian charge, legal reserve, and any trailing obligations — should be fully calculated and agreed before the redemption window opens. That figure then becomes the preset configuration for the routing.
Use verified addresses only. Each party receiving a share in the routing configuration must have a verified, allowlisted address. In a permissioned RWA environment, this is typically already enforced by the smart contract's transfer restrictions. A transfer agent maintains the cap table; a smart contract enforces transfer restrictions including whitelists, jurisdiction blocks, and lock-ups.
Verify NAV provenance. Oracles and attestations feed off-chain facts on-chain: asset valuations, bond maturities, reserve balances. Proof-of-reserve feeds and periodic third-party attestations let holders verify that the backing actually exists rather than taking the issuer's word for it. The NAV figure used to calculate the gross redemption amount must trace back to a defensible, authorised source — not a platform-generated estimate.
Sequence the burn correctly. As noted above, the token burn should follow payment confirmation, not precede it. Customer-facing tokenized fund balances, token ledgers, legal registers, custody accounts, and cash records may update at different times. The product is reliable only when its rules explain which record controls and how every other record is reconciled to it. The settlement agent's job is to ensure these records are in sync at the moment the burn is authorised.
Conclusion: the redemption is where the structure proves itself
The minting of a tokenized asset is, in many ways, the easy part. It is a moment of optimism — capital is deploying, the structure is working, and the technology is performing as designed. Redemption is where the on-chain and off-chain connection gets tested. It is also where problems tend to surface first.
A well-designed redemption — one where the custodian, the NAV administrator, the settlement agent, and the payment routing layer are all working in sequence — can be faster, more auditable, and more certain than its traditional equivalent. The exiting holder receives their net proceeds immediately on settlement confirmation. Every fee party is paid in the same transaction. The cap table updates atomically. The audit trail is complete from the moment the transaction confirms.
The settlement professionals who build expertise in this workflow — who understand the legal wrapper, the NAV calculation, the compliance verification, and the payment routing configuration — are the ones who will handle the redemptions of a global asset tokenization market projected to grow from USD 1,756 billion in 2025 toward USD 24,479 billion by 2033.
For the payment distribution step specifically, shaka.deal provides the routing infrastructure on Ethereum: one incoming gross amount, preset shares per party, simultaneous settlement to every address in a single transaction, with finality. The work of configuring those shares correctly, and authorising the execution, remains exactly where it belongs — with the settlement professionals who know the deal.
