> For the complete documentation index, see [llms.txt](https://extension-doc.rocky.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://extension-doc.rocky.exchange/using-the-wallet/offers.md).

# Offers

Offers are incoming transfers that may require a wallet decision before receipt completes. The Offers badge counts pending offers that have not expired.

## Understand offer status

* **Pending:** the offer is still within its decision window and can have available actions.
* **Expired:** if a loaded offer passes its expiration time, Rocky Wallet marks it expired locally, removes its actions, and excludes it from the pending badge. The Offers API returns only **Pending** offers, so the offer may disappear after a refresh once the backend marks it **Expired**.
* **Accepted:** you authorized acceptance. The offer may leave the active list after refresh; confirm the completed receipt in **History** or the ledger result.
* **Rejected:** you declined the offer. Do not expect the offered quantity to be added to the wallet.
* **Failed:** acceptance or the incoming transfer did not complete. A related **Received failed** row can appear in **History** when that result is reported.

## Review and decide

1. Open **Offers** from the bottom navigation.
2. Select an offer to inspect its sender, exact asset label and symbol, amount, creation time, expiration, and offer ID when those fields are provided.
3. Verify the sender's complete Party ID with the copy control. Do not rely on a shortened address or familiar-looking party-name prefix.
4. Select **Accept** only if you recognize the sender, expect the transfer, and trust the exact configured asset identity. Select **Reject** if the offer is valid and actionable but unwanted.
5. Enter the account password or authenticate if Rocky Wallet asks you to unlock before it signs the decision.
6. Refresh **Offers** and **History**, then verify the ledger result.

Accept or reject an offer only through the Rocky Wallet Extension UI. A website or DApp cannot silently make this decision for you.

> **Security note:** An unknown sender can remain visible, so you must decide whether to trust the complete Party ID. An unconfigured asset can also remain visible, but the Extension does not enable acceptance until the asset's exact identity is configured, enabled, and eligible. A display name, symbol, logo, or local label alone is not identity proof. Actions can also be unavailable after expiry.

## Receive preapproval and existing offers

Enabling receive preapproval does not accept or alter offers that are already pending. Those offers remain manual and still require **Accept** before they expire. Preapproval applies only to qualifying future transfers within its configured registrar scope.

If an action fails because an offer expired or is no longer available, refresh the list before trying anything else. Never infer receipt from a button press alone.

Next: [Receive Preapproval](/permissions-and-security/receive-preapproval.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://extension-doc.rocky.exchange/using-the-wallet/offers.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.