> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/retailer-wallet-management/archiving-and-unarchiving-wallets.md).

# Archiving and unarchiving wallets

### Archiving and unarchiving wallets

Archive wallets to remove them from selection when creating new campaigns. Archived wallets can be restored later if needed.

{% hint style="warning" %}

## Archiving a wallet does not stop existing campaigns from spending.

Campaigns currently associated with the wallet will continue to use it until they end or are paused.
{% endhint %}

#### To archive a wallet

1. Find the wallet in the table
2. Click the **actions menu** (three dots)
3. Select **Archive**
4. Confirm the action in the modal

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2Fy1PjCx06zks4VMsEyreD%2FCleanShot%202026-03-20%20at%2010.29.42.png?alt=media&amp;token=e8ceac63-155f-44fe-a564-5d388c6f8093" alt=""><figcaption></figcaption></figure>

#### To unarchive a wallet

1. Filter the wallet list to show **Archived** status
2. Find the wallet you want to restore
3. Click the **actions menu** (three dots)
4. Select **Unarchive**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.citrusad.com/retail-media-interface/retailer-wallet-management/archiving-and-unarchiving-wallets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
