> ## Documentation Index
> Fetch the complete documentation index at: https://second.tech/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Back up your wallet

> Back up your store's Bark wallet in BTCPay Server: write down the recovery phrase, set up continuous backups of the wallet directory, and restore a wallet from its phrase.

Before accepting any payments, make sure you back up your store's wallet.

1. **[Write down the recovery phrase](#write-down-the-recovery-phrase):** This is enough to recover the wallet's balance in the event of a system failure. Recovery from the phrase alone requires the Ark server's cooperation, and it doesn't restore the payment history or the state of any in-progress exits.
2. **[Set up continuous backups](#set-up-continuous-backups)** (optional): A backup that you fully control, with the entire payment history included.

The [Backups](/docs/backups) page explains the mechanics behind both in more depth.

## Write down the recovery phrase

<Steps>
  <Step title="Open the Bark settings">
    Go to **Bark** > **Settings**.
  </Step>

  <Step title="Reveal the phrase">
    Select **View Recovery Phrase** in the **Backup** section.
  </Step>

  <Step title="Write down the 12 words">
    Copy them in order, somewhere safe and offline. The phrase never changes, so this is a one-time step. Select **Done** to return to Settings.
  </Step>
</Steps>

## Set up continuous backups

Each store's wallet lives in BTCPay Server's data directory, under `bark/stores/<store ID>`, with its recovery phrase alongside. The **Backup** section of **Bark** > **Settings** shows the exact path, with a copy button. On a standard Docker deployment, that directory sits inside the BTCPay data volume on your server's disk.

<Warning>
  Your backups contain the wallet's keys. The recovery phrase is stored in plain text. Anyone who can read the wallet directory or its backups can spend the wallet's bitcoin, so restrict access to both.
</Warning>

Second doesn't have a mature continuous backup solution for the Bark plugin yet. If you're comfortable experimenting, consider these options:

* **[bark-backupd](https://gitlab.com/ark-bitcoin/labs/bark-backupd):** Second's experimental backup daemon. It watches a wallet directory and snapshots the database on every change. It encrypts each snapshot with a key derived from the recovery phrase, then ships it to a cloud drive or any S3-compatible target. Test `bark-backupd restore` before you rely on it.
* **[Litestream](https://litestream.io/):** A streaming replicator that keeps a live, off-machine copy of the wallet database. The wallet database isn't formally tested in the WAL journal mode Litestream requires, so treat the approach as experimental.

Regular [BTCPay backups](https://docs.btcpayserver.org/Docker/backup-restore/) are a baseline whole-server backup, but they typically aren't frequent enough for a reliable Bark wallet backup.

<Warning>
  If a backup misses your latest wallet changes, recovering the whole balance will require restoring from the recovery phrase, which relies on the Ark server's cooperation.
</Warning>

## Restore a wallet from its recovery phrase

To bring a wallet back on a store that has no Bark wallet yet, select **Import existing wallet** on the **Set up Bark** screen and enter the 12 words in the **Seed phrase** field. [Set up a Bark wallet for your store](/docs/btcpay/install#set-up-a-bark-wallet-for-your-store) walks through that screen. The plugin rebuilds the wallet with the Ark server's help, and the balance appears once the wallet has synced.

<Frame caption="Import existing wallet turns the Set up Bark screen into a 12-word entry form">
  <img src="https://mintcdn.com/second-0659a37d/oyMVF3OPOvsi31EU/images/btcpay/setup-bark-import.png?fit=max&auto=format&n=oyMVF3OPOvsi31EU&q=85&s=6681cd58d092cb4dfd649ac67fe8d8d4" alt="Screenshot of the Set up Bark screen with Import existing wallet selected and the 12 numbered word fields under Seed phrase" width="1920" height="1000" data-path="images/btcpay/setup-bark-import.png" />
</Frame>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.