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

# Export & backup

> Take a custodial wallet's key with you as a passphrase-encrypted .nota file, and share addresses safely with address cards.

Custodial wallets live server-side, but they're not locked in. You can export
a wallet's private key as an encrypted [.nota file](/concepts/nota-files):
for backup, for migration to self-custody, or to import into other tooling.

<Warning>
  An exported key file **is** the wallet. Anyone who obtains the file and the
  passphrase controls the funds. Treat both like production secrets even in a
  sandbox; the habits transfer.
</Warning>

## Export a key

Key export is **session-only**: it must be performed from a signed-in browser
session (the dashboard does this under **Wallets → Export**), and API keys are
rejected with `403 session_required`. This means a leaked API key can move
sandbox funds, but it can never exfiltrate key material.

```bash theme={null}
# Run from a session-authenticated context (cookie jar), not an API key
curl -s "$BASE/wallets/$WALLET/export" \
  -b cookies.txt \
  -H "content-type: application/json" \
  -d '{"passphrase":"correct-horse-battery-staple"}' \
  | jq -r .data.nota > payouts-key.nota
```

How it's protected:

* You choose a **passphrase of 8–200 characters**; pick a long one.
* The server decrypts the stored key transiently and immediately re-encrypts
  it under your passphrase with **PBKDF2-SHA256 (310,000 iterations) +
  AES-256-GCM**. The plaintext private key never leaves the server.
* The response is `{ filename, nota }`; write `nota` to disk as the suggested
  `.nota` file.

Only **custodial** wallets can be exported; external wallets have no key
(`400`).

## Share an address, not a screenshot

For the receive side, produce an **address card**: a `.nota` file with the
public address and chain context, zero key material:

```bash theme={null}
curl -s "$BASE/wallets/$WALLET/nota" -H "Authorization: Bearer $KEY" \
  | jq -r .data.nota > payouts-address.nota
```

Address cards are safe to email or drop in a shared channel. Counterparties
import them into any Aro recipient field (including
[external wallet registration](/concepts/wallets#creating-wallets)) instead
of transcribing hex.

## Backup checklist

<Steps>
  <Step title="Export each custodial wallet you care about">
    One `.nota` per wallet, each under a strong, unique passphrase.
  </Step>

  <Step title="Store file and passphrase separately">
    File in encrypted storage; passphrase in your password manager. Together
    they are the wallet; apart they are inert.
  </Step>

  <Step title="Record the address mapping">
    Keep each wallet's address (or its address card) alongside your records so
    you can verify a restored key against the expected address.
  </Step>
</Steps>

<Note>
  Deactivating an account (an admin action) kills sessions and API keys
  immediately, but exported files you already hold remain valid ciphertext.
  Rotate what matters accordingly.
</Note>