# Claiming shUSD

After the cycle advances a user's *pending deposit* gets converted into a *staked deposit.*  A user may then choose to claim their `shUSD` share tokens.

<figure><img src="https://3023247704-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmGY4Whi8NfSk5tdGdtt1%2Fuploads%2FozaInZNWw6uCQO2sjmLR%2Fimage.png?alt=media&#x26;token=96aab89e-20ec-4910-aa1f-24e57072c841" alt=""><figcaption><p>Clicking the 'Claim Now' button to proceed with the redemption process.</p></figcaption></figure>

Claiming is an optional step.  If a user decides not to claim they will still earn the base `USDC` yield on their entire deposit.  All additional points yield will be forgone for users who do not claim their `shUSD` and hold the tokens in their possession.  See the [Yields](https://docs.sherpa.trade/sherpaearn-vault/shusd/yields) page for more info.

There is no deadline or time window for claiming `shUSD` tokens.  The user's `shUSD` entitlement will he held within the vault indefinitely until the user manually redeems it or withdraws it.

#### **Auto-redemption Mechanism**&#x20;

This allows for claiming of vault held `shUSD` while also triggering a withdrawal request, resulting in a multi-function call transaction.  There are three possible scenarios that trigger this:

1. A user tries to withdraw already claimed `shUSD` from the vault while still having unclaimed shUSD.
2. A user withdraws a combination of both claimed and unclaimed shares at the same time.
3. A user withdraws without claiming any `shUSD`.

<figure><img src="https://3023247704-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmGY4Whi8NfSk5tdGdtt1%2Fuploads%2FOKxbODuqeoafm4G5CbW9%2Fimage.png?alt=media&#x26;token=7237e95c-38e3-48e6-a49b-d6f5ed083a2b" alt=""><figcaption><p>Example withdrawal using both claimed and unclaimed shares</p></figcaption></figure>