> For the complete documentation index, see [llms.txt](https://docs.spydra.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spydra.app/how-to/public-chain/manage-token-lifecycle/buyback-requests.md).

# Buyback Requests

Admins can efficiently manage buyback requests through the **'Buyback'** tab available on the home page. This section is divided into two tabs: **'Pending'** and **'Complete'**.

#### 1. Pending Buyback Requests

* The **'Pending'** section lists all buyback requests that require admin action.
* Admins can click on any list item to view detailed information about the buyback request.

<figure><img src="/files/Ww7sEMGMKF9X0rYgfrEJ" alt=""><figcaption></figcaption></figure>

* After reviewing the request, the admin can choose to either:
  * **Approve the Request:**
    * The admin must connect a wallet with sufficient funds to process the payout.
    * Once the wallet is connected and the funds are approved, the buyback request is completed.
  * **Reject the Request:**
    * If the request is rejected, the admin must provide a reason for the rejection.
    * The rejection reason will be communicated to the investor via email.

#### Completed Buyback Requests

* The **'Complete'** tab displays a list of all buyback requests that have been either approved or rejected.
* This section provides a clear overview of past actions, ensuring transparency and easy tracking of completed buyback transactions.

This structured approach to buyback management ensures smooth operations and maintains clear communication with investors.

***

View how to configure buyback settings - [Investor & Buyback Settings](/how-to/public-chain/create-a-token/investor-and-buyback-settings.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.spydra.app/how-to/public-chain/manage-token-lifecycle/buyback-requests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.