Does a Pending ERC-7540 Redemption Still Earn Yield?
The ERC-7540 pending redemption exchange rate is the price at which a queued vault redemption is finally paid, and it decides whether the request keeps earning yield while it waits. The standard leaves both to the vault: pending redemptions MAY NOT be yield-bearing and MAY NOT have a fixed rate. The cutoff is a product term the offering documents must name.
TL;DR — Key Takeaways
- ✓The standard: ERC-7540 leaves the redemption price to the vault: pending redemption Requests MAY NOT be yield-bearing and MAY NOT have a fixed exchange rate, and the rate including fees and yield is up to the implementation.
- ✓The blind spot: previewRedeem MUST revert, requestRedeem returns a request ID instead of an amount, and the pending view reports shares. The investor gets no price from the interface at request time.
- ✓The three cutoffs: A vault can fix the price at request, at fulfillment, or leave it variable until claim. The cutoff decides who bears net asset value (NAV) moves while the request waits.
- ✓One production example: In Centrifuge code at commit 72a8acfd, a pending redemption keeps NAV exposure until the manager revokes the epoch. The payout is then fixed as approved shares times the manager-supplied share price.
- ✓The control: Name the cutoff event, the price source at that event and what happens between cutoff and payout, and pass only if the contract and the offering documents say the same thing.

Does a pending ERC-7540 redemption earn yield?
ERC-7540 does not decide. The Final specification says pending redemption Requests MAY NOT be yield-bearing and MAY NOT have a fixed exchange rate, so the answer for any one vault sits in its code and its offering documents.
The standard frames this as a design freedom. Its rationale section says yield on redemption Requests “can accrue or not” and that the rate of any Request “may be fixed or variable depending on the implementation.” The redeem section adds that the assets received MAY NOT equal convertToAssets(shares) at the time of the Request, because the price can change between Pending and Claimed. Two vaults can both be compliant with ERC-7540 and still pay the same investor different amounts for the same request. The Pending, Claimable and Claimed states themselves are covered in whether tokenized funds should use ERC-7540 async vaults; this page deals only with the price.
“For asynchronous Vaults, the exchange rate between shares and assets including fees and yield is up to the Vault implementation. In other words, pending redemption Requests MAY NOT be yield-bearing and MAY NOT have a fixed exchange rate.”
ERC-7540 specification (status Final), Request Lifecycle section
The practical question for a fund administrator is therefore not “does it earn yield?” but “at which event is the price fixed, and from which source?” Before that event, the redeeming investor shares in fund gains and losses. After it, the investor holds a claim to a fixed amount.
Why can the investor not see the price at request time?
Because the interface gives no price. On an async redeem flow previewRedeem and previewWithdraw MUST revert, requestRedeem returns a request ID, and pendingRedeemRequest returns a share count, not an asset value.
The specification explains the return value directly: requestRedeem “may not have a known exchange rate that will happen when the Request becomes Claimed,” so returning an asset amount “could not work.” Both pendingRedeemRequest and claimableRedeemRequest are defined as “the amount of requested shares”. No standard view converts a queued redemption into money. A wallet that shows one usually multiplies by convertToAssets, which is the vault-wide rate at the moment of the call and is not the payout under most cutoff models. The general problem of treating vault readings as prices is covered in why a vault preview cannot safely price RWA collateral.
“The view methods for viewing Pending and Claimable request states (e.g. pendingDepositRequest) are estimates useful for display purposes but can be outdated. The inability to know the final exchange rate on any Request requires users to trust the implementation of the asynchronous Vault in the computation of the exchange rate and fulfillment of their Request.”
ERC-7540 specification, Security Considerations
One rule does bind the rate. Requests that share a nonzero requestId MUST become Claimable together and receive the same exchange rate. Requests with different IDs carry no ordering or rate guarantee. How an administrator keys requests so that this rule can be checked is set out in whether two investors can share a vault request ID.
What are the three ways a vault can fix the redemption price?
A vault can fix the price at request, at fulfillment (when the request becomes Claimable), or leave it variable until the investor claims. Each moves NAV risk for the waiting period to a different party, and the standard permits all three.
The table below is analysis of the specification, not a survey of deployed vaults. We found one production implementation, Centrifuge, and it uses the fulfillment model. We did not identify a production vault that fixes the rate at request or keeps it variable to claim, so those two rows describe what the specification allows, not how a named product behaves.
| Cutoff model | Who bears NAV moves while Pending | Who bears NAV moves after cutoff | What the investor statement must say |
|---|---|---|---|
| Fixed at request | Remaining holders; the redeeming investor stops sharing returns at once | Remaining holders until payout | The price source used at request time (for example, last struck NAV) and the request timestamp |
| Fixed at fulfillment or Claimable | Redeeming investor | Nobody on the payout; it is a fixed asset amount | The fulfillment date, the price applied and that no return accrues between fulfillment and claim |
| Variable to claim | Redeeming investor | Redeeming investor, until the claim transaction | That the amount is set by the claim date, which the investor controls |
A fixed-at-request vault still cannot tell the investor the price through ERC-7540, because previewRedeem reverts and requestRedeem returns no amount. The price has to be published elsewhere. A variable-to-claim vault turns the claim date into an investment decision, which most fund documents do not contemplate. The specification's own reference code shows the variable pattern on the deposit side: its deposit function uses convertToShares at claim and comments that “it may be more common to use the rate locked in upon Claimable stage.”
When does Centrifuge fix the redemption payout?
At revocation. In code reading of the Centrifuge protocol at commit 72a8acfd, the payout equals the approved share amount times a price per share that the pool manager supplies when revoking the epoch, converted into the payout asset at the price set at approval.
This is code reading, not a test run. The steps, in order:
- Request.
requestRedeemin AsyncRequestManager.sol moves the shares to the pool escrow and records them as pending. They are not burned at this step, and the payout is not yet calculated, so the investor still carries NAV exposure. - Approve.
_approveRedeemsin BatchRequestManager.sol records an approved share amount for the epoch, capped at total pending, together with a pool-per-asset price for the payout asset. - Revoke.
_revokeShares(L392-440) stores the manager's pool-per-share price and computes the payout from the approved shares, both prices and a round-down. It emitsRevokeShareswith the price and the payout. - Reserve and burn. The
revokedSharescallback (L245-259) reserves the payout and burns the shares in one step. What that does to the outstanding share count is a separate question from the price. - Claim.
redeemorwithdrawruns_processRedeem(L421-454), which only releases already reserved assets up tomaxWithdraw.
“Earmark the redemption payout: reserving removes the assets from the hub-accounted holding atomically with the share burn, preventing NAV desync. The escrow update is deferred to claim.”
AsyncRequestManager.sol, revokedShares, Centrifuge protocol @ 72a8acfd
Two consequences follow from that code. First, NAV moves before revocation reach the investor in full; after revocation they do not. Second, the claim is a fixed asset amount. We found no path that adds return to reserved assets between revocation and claim, so in code reading a redeeming investor who claims a week late receives the same amount. Centrifuge documentation does not state this directly; it is inferred from the reserve and withdrawReserved flow.
Note the split timing for a payout asset that differs from the pool currency. The asset price is fixed at approval and the share price at revocation, so the two prices can come from different moments. We did not check how pool managers choose either price; the code treats both as manager inputs.
How much does each model pay? A worked example
On an illustrative 100,000-share redemption, the three models pay 102,000, 102,500 and 102,700 units of the payout asset, a spread of 700 that depends only on which event fixes the price. The numbers below are not from a real fund.
Assume the investor requests on day 0, when the indicative NAV is 1.0200. The vault fulfills (in Centrifuge terms, revokes) on day 5 at a NAV of 1.0250. The investor claims on day 9, when NAV is 1.0270.
| Model | Price applied | Payout | Difference vs fulfillment model |
|---|---|---|---|
| Fixed at request (day 0) | 1.0200 | 102,000 | -500: the day 0 to day 5 gain stays with remaining holders |
| Fixed at fulfillment (day 5) | 1.0250 | 102,500 | 0 |
| Variable to claim (day 9) | 1.0270 | 102,700 | +200: the investor keeps fund exposure for four more days |
In a falling market the signs reverse. Under a request cutoff the redeeming investor is protected and the remaining holders absorb the fall; under a claim cutoff the investor bears it until they claim.
Partial fills across epochs
A fulfillment-model vault that fills a request in two batches applies two prices. Continue the example: 60,000 shares are revoked at 1.0250 (61,500) and the other 40,000 in the next epoch at 1.0300 (41,200). The total is 102,700, and the per-investor redeemPrice becomes a weighted average of 1.0270. Centrifuge's fulfillRedeemRequest (L293-327) computes that weighted price from cumulative shares and assets. The investor statement must show both epochs and both prices, because the stored average alone does not show which part of the order was exposed for longer.
What should the redemption terms and investor statement say?
They should name the cutoff event, the price source at that event and what happens to returns between cutoff and payout. If the contract fixes the price at one event and the prospectus names another, every redemption leaves an unexplained difference.
Use the table as an acceptance test for each vault before it takes redemptions. Each row is one field to fill from the deployed contract and one field to fill from the offering document; the vault passes only when the two agree. This is the redemption leg of the periodic reporting set out in the RWA investor reporting and disclosure requirements guide.
| Check | Read from the contract | Read from the offering document | Evidence per redemption |
|---|---|---|---|
| Cutoff event | Function that stores the price (request, fulfillment, claim) | Dealing day or valuation point for redemptions | Transaction hash of the cutoff event |
| Price source | Who supplies the price and in what units | NAV calculation and who strikes it | Price value from the event log and the matching NAV statement |
| Return after cutoff | Whether the payout amount can change before claim | Whether interest is paid on unpaid proceeds | Claimed amount equals the amount fixed at cutoff |
| Gap to payout | Any delay between cutoff and claimability | Settlement period stated to investors | Cutoff and claim timestamps |
| Partial fills | Whether a request can fill across epochs | Gating or pro-rata rules | One line per epoch with shares and price |
For a fulfillment-model vault like Centrifuge, a disclosure that matches the code reads along these lines: “Shares submitted for redemption remain exposed to the fund until the redemption is processed. The redemption price is the price per share applied at processing. No return accrues on redemption proceeds between processing and the date you claim them.” Adapt the wording to the vault you run; do not copy it to a vault whose cutoff is different.
Who does this apply to, and what was not checked?
It applies to administrators, transfer agents and product or legal teams writing redemption terms or investor statements for an ERC-7540 vault. It does not cover how many shares count as outstanding while a request waits, or how to cancel a request.
The specification text was read from the ERC-7540 page on eips.ethereum.org (status Final). Centrifuge behaviour was read from AsyncRequestManager.sol and BatchRequestManager.sol at commit 72a8acfd; we did not run the contracts. We did not check how Centrifuge pool managers choose the price per share at revocation, and we did not check any Centrifuge pool's offering documents, so no named pool's terms are stated here. We did not find a production vault that fixes the price at request or leaves it variable to claim; those models are described from the specification only.
Sources: ERC-7540 specification (status Final, read 2026-11-11); Centrifuge protocol AsyncRequestManager.sol and BatchRequestManager.sol @ 72a8acfd (read 2026-11-11). Numerical examples are illustrative.
Frequently Asked Questions
Does a pending ERC-7540 redemption keep earning fund returns?
The standard does not say. ERC-7540 states that pending redemption Requests MAY NOT be yield-bearing and MAY NOT have a fixed exchange rate, and that the rate including fees and yield is up to the vault. Whether a queued redemption still shares in fund performance depends on the event at which the vault fixes the price. That event has to be read from the contract and named in the offering documents.
Why does previewRedeem revert on an ERC-7540 vault?
Because the vault may not know the price yet. ERC-7540 says previewRedeem and previewWithdraw MUST revert for all callers and inputs on an asynchronous redeem flow. requestRedeem returns a request ID rather than an asset amount for the same reason. The pending and claimable views report share amounts, and the specification calls them estimates for display that can be outdated.
When is the redemption payout fixed in Centrifuge vaults?
In code reading at commit 72a8acfd, at revocation. The pool manager first approves a share amount for an epoch with a pool-per-asset price, then revokes it with a pool-per-share price. The payout is approved shares times that share price, converted into the payout asset. From then until the investor claims, the payout is a reserved asset amount that does not change.
Does convertToAssets show what a pending redemption will pay?
No. ERC-7540 says the assets received on redeem or withdraw MAY NOT equal convertToAssets(shares) at the time of the request, because the price can change between Pending and Claimed. convertToAssets is a vault-wide rate at the moment of the call. It describes the payout only in a vault that prices at claim, and only at that instant.
Do all requests in one ERC-7540 vault get the same price?
Only requests that share a nonzero requestId. The standard requires them to become Claimable at the same time and receive the same exchange rate. Requests with different IDs carry no ordering or rate guarantee, so two investors who redeemed on the same day can be paid at different prices if the vault fills them in different batches.
Related Articles
Do Vault Previews Include the Fund Entry Fee?
ERC-4626 requires previews to include entry and exit fees while conversions exclude them, so a fee reconciliation has to prove which number the investor was shown.
Can You Cancel a Pending RWA Vault Request?
Cancelling a subscription or redemption is a separate workflow with its own request, approval and claim.
Why Did a Claimable Vault Exit Produce No New Event?
ERC-7540 requires no event when a request becomes Claimable, so indexers must poll the claimable views on a schedule.
Can a Fund Investor Revoke an Exit Operator?
Revoking an ERC-7540 operator removes delegated authority but does not cancel or move a pending redemption.