> For the complete documentation index, see [llms.txt](https://csigma-asset-tokenization.gitbook.io/atlas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://csigma-asset-tokenization.gitbook.io/atlas/lender/withdraw.md).
# Withdraw
### Overview
The **Withdraw** feature allows lenders to redeem their **LP tokens** and receive the equivalent amount of **underlying tokens (USDC / USDT)** from the Tokenized Pool.
When a withdrawal is processed:
* The lender’s **LP tokens are burned**
* The corresponding amount of **underlying tokens is transferred to the lender’s wallet**
* The pool’s **Reserve Balance is used to fulfill the withdrawal**
Withdrawals depend on the **available liquidity in the pool reserve**. If the reserve balance is insufficient, the withdrawal may be partially fulfilled or placed in the **Withdrawal Queue**, depending on the pool configuration.
### Navigation
To withdraw funds from a pool:
1. Navigate to the **Asset Tokenization** tab.
2. Select the **Tokenized Pool** where the investment was made.
3. Click the **Withdraw** tab located next to the **Invest** tab.
### Withdrawal Interface
In the Withdraw tab, the lender can view:
* **LP Token Balance** — The total LP tokens held by the lender
* **Current Exchange Rate** — The current value of LP tokens
* **Receivable Amount** — The underlying tokens that will be received based on the entered LP amount
### Withdrawal Process
#### Step 1 — Enter LP Token Amount
The lender enters the number of **LP tokens** they wish to redeem.
#### Step 2 — Review Receivable Amount
The platform automatically displays the **amount of USDC / USDT** that will be received based on the **current LP token exchange rate**.
#### Step 3 — Submit Withdrawal
The lender clicks the **Withdraw** button and confirms the transaction in their wallet.
### Withdrawal Scenarios
#### Case 1 — Sufficient Reserve Balance
If the **Reserve Balance is sufficient**, the withdrawal is processed immediately.
* LP tokens are burned
* Underlying tokens are transferred to the lender’s wallet
#### Case 2 — Withdrawal Amount Exceeds Reserve Balance
If the requested withdrawal amount is greater than the **Reserve Balance**, two outcomes are possible depending on whether the Withdrawal Queue is enabled.
**Queue Not Enabled**
If the Withdrawal Queue is **not enabled**:
* The lender can withdraw **only up to the Reserve Balance**
* The withdrawal amount must be reduced to match the available reserve liquidity
**Queue Enabled**
If the Withdrawal Queue **is enabled**:
* The portion equal to the **Reserve Balance** is transferred immediately to the lender
* The **remaining amount is placed in the Withdrawal Queue**
The queued portion will be fulfilled once liquidity becomes available.
### Example
Assume the following situation:
| Category | Amount |
| ------------------------- | -------- |
| Reserve Balance | 200 USDC |
| Lender Withdrawal Request | 500 USDC |
If the Withdrawal Queue is enabled:
* **200 USDC** is immediately transferred to the lender
* **300 USDC** is added to the **Withdrawal Queue**
The remaining amount will be processed when liquidity becomes available.
### Important Notes
* Withdrawals burn the lender’s **LP tokens**.
* Withdrawals are served using the **Reserve Balance** of the pool.
* If reserve liquidity is insufficient, queued withdrawals may occur.
* Withdrawal Queue behavior depends on the **pool configuration set by the Pool Manager**.
### Role Responsibility
**Lender Responsibilities**
* Enter the correct LP token amount to withdraw
* Review the receivable amount before confirming the withdrawal
**Pool Manager Responsibilities**
* Maintain adequate reserve liquidity
* Manage queued withdrawals when liquidity becomes available
**cSigma Platform Responsibilities**
* Track withdrawal queue
This withdrawal process ensures lenders can **redeem their investments while maintaining liquidity stability within the Tokenized Pool.**
