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

# Reconciliation files

> Reconcile your accounts every day from a suite of CSV files: accounts, positions, transactions, assets, prices, and a manifest, delivered by SFTP.

Anchorage Digital will deliver a set of files every day for your operations team. Together they support a complete, independent reconciliation of the accounts we hold for you: which accounts exist, what they hold, what moved, and how it was priced. The v4 API stays the intraday source of truth. Every identifier in the files is usable against it.

## What's available

| Action | Status | Notes |
| :- | :- | :- |
| Daily reconciliation files | Under construction | Not yet delivered to any client. The file layout below is the contract we're building to, and the delivery mechanics (SFTP, encryption, manifest, restatements) are being finalized with the first clients. Both can still change before first delivery. |

> [!NOTE]
>
> Build your loader against the column names on this page, not column positions, and read the manifest first. When delivery starts, this page will say so, and the manifest's `spec_version` will tell you which version of the layout each batch follows.

## The daily file set

| Dataset | Kind | One row per | Delivered |
| :- | :- | :- | :- |
| `accounts` | Snapshot | Account | Always |
| `positions` | Snapshot | Account, asset, and balance type | Always |
| `transactions` | Delta | Transaction entry (leg) | Always |
| `assets` | Snapshot | Asset | Always |
| `prices` | Snapshot | Asset | Always |
| `compliance_profiles` | Snapshot | Compliance profile and party | Disclosed accounts only, optional |
| `manifest` | Control | Delivered file | Always, written last |
| Account statements | PDF | Statement | Optional, in a `statements/` subdirectory |

The suite works the same for disclosed and undisclosed account models. The core files carry no holder-level personal data. Clients on the disclosed model can receive one extra file, `compliance_profiles`, with registration and holder information.

## Account model and identifiers

The files use the same account model as the [Accounts](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-accounts.md) guide:

* **`account_id`** is the UUID Anchorage Digital assigned. It's the primary key of every account-scoped row and the path parameter for the API.
* **`parent_account_id`** is, for a `SEGREGATED` account, the FBO or omnibus it sits under. Empty for top-level accounts.
* **`external_id`** is the identifier you supplied when you created the account: your join key back to your own books. We treat it as opaque and return it unchanged.
* **`account_type`** is `SEGREGATED`, `FBO`, or `OMNIBUS`. An FBO always has segregated accounts under it, and its positions and transactions are reported on those accounts, never on the FBO row. An omnibus with `ledgering: SEGREGATED` works the same way. A pure omnibus (`ledgering: SELF`) has no child accounts, so its positions and transactions appear on the omnibus itself and customer-level reconciliation runs against your own subledger.
* **Disclosed or undisclosed** is a property of the FBO or omnibus parent (`is_disclosed`), inherited by the accounts under it. An undisclosed segregated account never references a compliance profile: the owner of record is your organization.

There are no rep codes, firm codes, or custodian identifiers anywhere in the files. Anchorage Digital is the sole custodian, and any books-and-records hierarchy beyond `parent_account_id` is yours, keyed by `external_id`.

## Delivery

Files will be generated by Anchorage Digital and pushed to your SFTP server. Every file will be encrypted with your PGP public key before it leaves us and only ever transferred in that form. At rest inside Anchorage Digital, files are protected by our standard storage encryption and organization-scoped access controls.

### What you provide at onboarding

1. The SFTP username we connect as.
2. The host address, and the port if it isn't 22.
3. The upload directory, if files shouldn't land in the directory the user starts in.
4. Your PGP public key. See [Set up a PGP key](#set-up-a-pgp-key) if you don't have one.
5. Your reconciliation cutoff preference. See below.

### What Anchorage Digital provides

1. The SSH public key our delivery service authenticates with. Register it against the SFTP username you created for us.
2. Our egress IP addresses, if you restrict inbound SFTP connections by source.
3. The short `org_id` we assign to your feed and use in file names. It isn't the 64-character organization key ID the API uses.

### Reconciliation cutoff

Each client has a daily cutoff: the moment positions are struck and the transaction window closes. The default is 00:00 UTC, which matches the valuation time of Anchorage Digital account statements, so files and statements agree by construction. A different cutoff can be agreed at onboarding.

* The reconciliation date `T` of a batch is the calendar date, in the cutoff timezone, of the day that ends at its cutoff. With the default cutoff, `T`'s batch covers the UTC day `T` and is struck at 00:00 UTC the next day.
* `accounts`, `positions`, `assets`, `prices`, and `compliance_profiles` are snapshots as of `T`'s cutoff.
* `transactions` covers the window from the previous cutoff, exclusive, to `T`'s cutoff, inclusive.
* Timestamps inside the files are always RFC 3339 UTC, whatever the cutoff timezone.

### Schedule

* Files are produced every calendar day, seven days a week. If you reconcile on business days only, consume the weekend files together with Monday's.
* Files are uploaded under temporary names and renamed on completion, so a file visible under its final name is complete. The `manifest` is uploaded last. Its appearance means the batch is ready to consume.
* An empty dataset still produces a file with a header row, so a missing file always means a delivery failure, never "there was nothing".

### Redelivery, backfill, and restatements

* **Redelivery** (same content, delivery failed): ask your Anchorage Digital operations contact and the files are pushed again.
* **Backfill**: a historical `transactions` file covering any window back to account inception, in the same layout as the daily file, is available on request. Useful when you enable the feed for an organization with existing activity.
* **Restatement** (content was wrong and is corrected): the affected files are reissued with a revision suffix (`_r1`, `_r2`, and so on) and a new manifest listing the revised files. A restatement never patches individual rows. Reload the full file. Your operations contact is notified whenever a restatement is issued.

## File conventions

* **Format:** RFC 4180 CSV, UTF-8, LF line endings, one header row of `snake_case` column names. Fields containing commas, quotes, or newlines are double-quoted, and embedded quotes are doubled.
* **Naming:** `anchorage_<dataset>_<YYYYMMDD>_<org_id>[_rN].csv.gpg`, for example `anchorage_positions_20261105_a1b2c3.csv.gpg`. `YYYYMMDD` is the reconciliation date, `org_id` is the short identifier assigned at onboarding, and `_rN` appears only on restatements. Decrypting with your private key yields the plain `.csv`.
* **Account statements** (opt-in) land in a `statements/` subdirectory as `<account_id>_<statement_name>_<YYYYMMDD>[_corrected].pdf.gpg`, where `YYYYMMDD` is the date the statement became available and `_corrected` marks a revised version.
* **Quantities** are decimal strings in the asset's native unit, full precision, no exponent notation, no thousands separators, for example `10.45234733`. Don't parse them as floats. Precision matters at 18 decimals.
* **USD values** are decimal strings rounded to the cent.
* **Timestamps** are RFC 3339 UTC with microsecond precision, for example `2026-11-05T21:04:05.123456Z`. **Dates** are `YYYY-MM-DD`.
* **Booleans** are lowercase `true` and `false`. An empty string means null or not applicable.
* **Column contract:** key on column names, not positions. Additive changes (new columns, new enum values) ship with advance notice. Breaking changes ship as a new major version delivered in parallel during a transition window. The manifest carries the version each batch was produced under.

## Accounts file

A full snapshot of every account in your organization, all types, including recently closed accounts so that closures reconcile. One row per account.

| Column | Type | Null | Description |
| :- | :- | :- | :- |
| `as_of_date` | date | no | Reconciliation date `T` |
| `account_id` | uuid | no | Anchorage Digital account ID. Primary key. |
| `account_type` | enum | no | `SEGREGATED`, `OMNIBUS`, or `FBO` |
| `parent_account_id` | uuid | yes | For `SEGREGATED` rows, the FBO or omnibus parent. Empty for top-level accounts. |
| `external_id` | string | yes | Your identifier, as supplied at creation. Empty on accounts Anchorage Digital created itself, such as the default FBO parent of a migrated organization. |
| `account_name` | string | yes | Display name, if set. May be generic or absent in the undisclosed model. |
| `status` | enum | no | `OPENING`, `OPEN`, `FROZEN`, `CLOSING`, or `CLOSED` |
| `is_disclosed` | boolean | no | On `FBO` and `OMNIBUS` rows, whether the accounts under it are disclosed. On `SEGREGATED` rows, copied from the parent for convenience. |
| `ledgering` | enum | yes | `OMNIBUS` only: `SELF` (pure omnibus) or `SEGREGATED` (per-customer accounts under it) |
| `compliance_profile_id` | uuid | yes | Reference into `compliance_profiles`. Always empty for undisclosed segregated accounts. |
| `created_at` | timestamp | no | When the account was created |
| `closed_at` | timestamp | yes | When the account reached `CLOSED` |
| `updated_at` | timestamp | no | Last modification |

Registration type, tax classification, and holder information are deliberately not on this file. See the `compliance_profiles` file.

## Positions file

A full snapshot of holdings as of the day's cutoff. One row per account, asset, and balance type. The rows for one account and asset are views of a single holding, not parts to be summed: the `TOTAL` row is the holding, and the other rows break it down or qualify it.

| Column | Type | Null | Description |
| :- | :- | :- | :- |
| `as_of_date` | date | no | Reconciliation date `T`. Quantities are as of `T`'s cutoff. |
| `account_id` | uuid | no | Account holding the position |
| `parent_account_id` | uuid | yes | Parent linkage, for grouping without a join |
| `asset_type` | string | no | Asset code, such as `BTC`, `ETH`, or `USD`. Joins to `assets` and `prices`. |
| `balance_type` | enum | no | See the vocabulary below |
| `quantity` | decimal | no | Units of the asset in this balance bucket, full precision |
| `price_usd` | decimal | no | USD reference price of one unit at the cutoff. Identical to `price_usd` in that day's `prices` file. |
| `market_value_usd` | decimal | no | `quantity × price_usd` for this row's balance type, rounded to the cent. Don't sum this column across the rows of one account and asset. |

### Balance types

| `balance_type` | Meaning | Relation to `TOTAL` |
| :- | :- | :- |
| `TOTAL` | Settled holdings of the account in the asset: everything booked and confirmed, whether or not part of it is encumbered. Excludes `PENDING`. Always present for every held asset. | The holding itself |
| `AVAILABLE_FOR_WITHDRAWAL` | Unencumbered settled holdings that can be withdrawn now | `TOTAL − HOLD`, capped by `AVAILABLE_FOR_TRADING` |
| `AVAILABLE_FOR_TRADING` | Trading power: unencumbered settled holdings plus pending credits | `TOTAL − HOLD + PENDING` |
| `HOLD` | Settled holdings encumbered by pending debits (pending withdrawals, open orders) or restrictions, as a positive amount | The encumbered part of `TOTAL` |
| `PENDING` | Credits not yet settled, such as deposits awaiting confirmations | Outside `TOTAL` |

For every account and asset, `AVAILABLE_FOR_TRADING = TOTAL − HOLD + PENDING` and `AVAILABLE_FOR_WITHDRAWAL = min(TOTAL − HOLD, AVAILABLE_FOR_TRADING)`. These are the definitions `GET /v4/accounts/{accountId}/balances` uses, so a position row and the API agree on what each bucket means. Component rows appear only when non-zero. `TOTAL` always appears.

New balance types (for example staking states) ship as additive changes with notice. Each states its relation to `TOTAL` and never changes the five definitions above. Treat a `balance_type` you don't recognize as informational: keep it out of your roll-forward and valuation checks, which run on `TOTAL`, and don't fail the batch on it.

### Population rules

* A position row appears while any balance type for the account and asset is non-zero, plus one final day after everything reaches zero (a `TOTAL` row with quantity `0`), so you see a position close rather than vanish.
* Accounts holding nothing produce no rows. They're still in `accounts`.
* For a pure omnibus, positions exist only at the omnibus `account_id`. For an omnibus with `SEGREGATED` ledgering, and for an FBO, positions are reported on the accounts under it, and no parent-level row is emitted, so nothing is double counted.

Cost basis and gain or loss figures aren't in this file. In this integration model you're the basis of record. Columns can be added later where that changes.

## Transactions file

A delta file: everything that happened in day `T`'s window. One row per transaction entry (leg). A single business transaction (`transaction_id`) has one row per account and asset movement it caused, so a transfer between segregated accounts has two rows and a trade has two or more.

Every row is a ledger entry booked within `T`'s window. `booked_at` is the criterion, not the transaction's creation time. The ledger is append-only, so a transaction appears on every day it books something. A deposit books `PENDING` legs when detected. On the day it confirms, it books the legs that move the amount from `PENDING` to `AVAILABLE`, reported with `status: POSTED`. A cancellation books reversing legs, reported with `status: CANCELED`. `status`, `created_at`, and `posted_at` describe the transaction as a whole, as of the cutoff.

Rows are uniquely keyed by `transaction_id` and `entry_seq`.

| Column | Type | Null | Description |
| :- | :- | :- | :- |
| `as_of_date` | date | no | Reconciliation date `T` |
| `transaction_id` | string | no | Transaction ID, usable against `GET /v4/accounts/{accountId}/transactions` |
| `entry_seq` | int | no | 1-based leg number within the transaction, stable across days |
| `booked_at` | timestamp | no | When this leg was booked. Rows are selected into `T`'s file by this timestamp. |
| `transaction_type` | enum | no | See the vocabulary below |
| `status` | enum | no | `POSTED`, `PENDING`, or `CANCELED`, as of the cutoff |
| `account_id` | uuid | no | Account this leg hits |
| `parent_account_id` | uuid | yes | Parent linkage |
| `asset_type` | string | no | Asset moved by this leg |
| `direction` | enum | no | `CREDIT` (in) or `DEBIT` (out), from the account's perspective |
| `quantity` | decimal | no | Absolute quantity moved, native units |
| `balance_type` | enum | no | Bucket this leg affects: `AVAILABLE`, `HOLD`, or `PENDING`, the same labels the transactions API uses on entries. `AVAILABLE` legs are the settled movements that change the `TOTAL` row in `positions`. |
| `price_usd` | decimal | yes | Indicative USD unit price at posting time |
| `value_usd` | decimal | yes | `quantity × price_usd`, rounded to the cent |
| `created_at` | timestamp | no | When the transaction was created |
| `posted_at` | timestamp | yes | When it reached `POSTED`. Empty for `PENDING`. For `CANCELED`, the cancellation time. |
| `order_id` | uuid | yes | `TRADE` and `TRADE_SETTLEMENT` rows: the order this booking belongs to |
| `order_external_id` | string | yes | Your external ID for that order |
| `symbol` | string | yes | Trade rows: the order symbol, such as `BTC-USD` |
| `side` | enum | yes | Trade rows: `BUY` or `SELL` |
| `avg_price` | decimal | yes | Trade rows: average fill price for this account's allocation, in the quote currency, excluding fees |
| `avg_price_all_in` | decimal | yes | Trade rows: average fill price including fees |
| `fee_quantity` | decimal | yes | Trade rows: fee apportioned to this account's allocation |
| `fee_asset_type` | string | yes | Asset the fee is charged in |
| `withdrawal_id` | string | yes | `WITHDRAWAL` rows: the withdrawal ID |
| `destination_id` | string | yes | `WITHDRAWAL` rows: the trusted destination withdrawn to |
| `network_id` | string | yes | On-chain movements: the network the transfer settled on |
| `onchain_tx_hash` | string | yes | On-chain movements: the blockchain transaction hash |
| `counterparty_address` | string | yes | Deposits: source addresses, `;`-separated. Withdrawals: the destination address. |
| `reversal_of_transaction_id` | string | yes | `RETURN` and correction rows: the transaction being reversed |
| `description` | string | yes | Free-text operational memo, if any |

### Transaction types

| Category | Types |
| :- | :- |
| Funding | `DEPOSIT`, `WITHDRAWAL`, `RETURN`, `DEPOSIT_SWEEP`, `GAS_FILL` |
| Trading | `TRADE`, `TRADE_SETTLEMENT` |
| Transfers | `SUBACCOUNT_TRANSFER` (a transfer between segregated accounts, named as in the API), `TRANSFER` |
| Fees | `MANAGEMENT_FEE`, `CUSTODY_FEE`, `ADVISORY_FEE`, `MODEL_FEE`, `TRANSACTION_FEE`, `FEE_SETTLEMENT`, `SEGREGATED_WALLETS_FEE` |
| Staking | `STAKE`, `UNSTAKE`, `CLAIM`, `STAKING_REWARD`, `DELEGATION_REWARD`, `HYPERCORE_SPOT_TO_STAKE_TRANSACTION`, `HYPERCORE_STAKE_TO_SPOT_TRANSACTION` |
| Other | `TRADING_STRATEGY_INCOME`, `MINT`, `BURN`, `PRE_BURN`, `REDEEM`, `UNLOCK`, `INTEREST`, `CONSOLIDATE` |

Every transaction type the API lists appears in the file under the name the API returns. Like the API, the file reports a deposit that is a reward as `STAKING_REWARD` or `DELEGATION_REWARD`.

* **Trades:** trade economics are on the `TRADE` rows themselves (`order_id`, `avg_price`, fees) rather than in a separate trades file. They're the account's pro rata share of the parent order, so allocation-level reconciliation works from this file. The orders API gives the order-level view.
* **Corrections:** a mis-booked entry is corrected by a reversing transaction that references the original in `reversal_of_transaction_id`. History is never mutated. A restated file corrects file-generation errors, not bookings.
* In the undisclosed model, `counterparty_address` is still populated. It's chain data, not personal data. Originator and beneficiary names never appear in the suite.

## Assets file

A full snapshot of every asset enabled for your organization: the reference data needed to read `positions`, `transactions`, and `prices`. One row per asset.

| Column | Type | Null | Description |
| :- | :- | :- | :- |
| `as_of_date` | date | no | Reconciliation date `T` |
| `asset_type` | string | no | Asset code. Primary key across the suite. |
| `asset_name` | string | no | Human-readable name, such as `Bitcoin` or `US Dollar` |
| `asset_class` | enum | no | `CRYPTO`, `STABLECOIN`, or `FIAT` |
| `networks` | string | yes | Networks the asset settles on, `;`-separated. Empty for USD. |
| `quantity_decimals` | int | no | Maximum decimal places a quantity can carry. Size your decimal storage accordingly. |
| `staking_supported` | boolean | no | Whether staking balance types can occur for this asset |
| `status` | enum | no | `ACTIVE` or `DELISTED`. Delisted assets keep appearing while any account holds a balance. |
| `description` | string | yes | Short description |

Crypto assets have no CUSIP or ISIN. `asset_type` is the identifier. If you keep your own security master, map from it.

## Prices file

A full snapshot of end-of-day reference prices for every asset enabled for your organization: the prices used to value that day's `positions` file. One row per asset.

| Column | Type | Null | Description |
| :- | :- | :- | :- |
| `as_of_date` | date | no | Reconciliation date `T` |
| `asset_type` | string | no | Asset priced. Joins to `assets`. |
| `price_usd` | decimal | no | Anchorage Digital's end-of-day USD reference price of one unit at the cutoff. The same value prices `positions.market_value_usd` for the date. |
| `price_as_of` | timestamp | no | The exact instant the price corresponds to |
| `price_source` | string | no | Reference-price methodology label. `ANCHORAGE_EOD` for the end-of-day reference price. New labels ship with notice. |
| `open_usd`, `high_usd`, `low_usd` | decimal | yes | Day's open, high, and low, where available |
| `volume` | decimal | yes | Day's traded volume, where available |

These are reference prices for valuation and reconciliation, not execution prices. Trade rows in `transactions` carry their own `avg_price`.

## Compliance profiles file

Holder-level data is deliberately not on `accounts`. In the undisclosed model it doesn't exist at Anchorage Digital. Clients on the disclosed model receive this extra snapshot. Undisclosed clients don't, and the manifest simply won't list it.

A compliance profile carries the registration type, tax classification, owners, and authorized signers for one or more accounts that reference it through `accounts.compliance_profile_id`. A profile can be shared by several accounts, such as one investor's taxable and IRA accounts.

One row per profile and party. Profile-level columns repeat on every row of the profile. A profile with no parties yet still produces one row with the party columns empty.

| Column | Type | Null | Description |
| :- | :- | :- | :- |
| `as_of_date` | date | no | Reconciliation date `T` |
| `compliance_profile_id` | uuid | no | Profile ID. Joins from `accounts.compliance_profile_id`. |
| `profile_type` | enum | yes | `INDIVIDUAL`, `JOINT`, `CUSTODIAL`, or `INSTITUTION`. Empty if not set. |
| `tax_type` | enum | yes | `TAXABLE`, `IRA`, `ROTH`, `IRA_ROLLOVER`, `ROTH_ROLLOVER`, `ROTH_CONVERSION`, or `IRA_CONVERSION`. Empty if not set. |
| `party_type` | enum | yes | `CUSTOMER` (an owner) or `SIGNER` (an authorized signer). Empty on a placeholder row. |
| `party_seq` | int | yes | 1-based sequence of the party within its `party_type` |
| `cif_profile_id` | string | yes | `CUSTOMER` rows: the owner's customer identifier |
| `customer_role` | enum | yes | `CUSTOMER` rows: `PRIMARY` or `SECONDARY`. Exactly one `PRIMARY` per profile. |
| `signer_first_name`, `signer_last_name`, `signer_email` | string | yes | `SIGNER` rows only |
| `created_at` | timestamp | no | Profile creation time |
| `updated_at` | timestamp | no | Profile last-modified time |

## Manifest file

A control file, uploaded last, that makes the batch verifiable. One row per file delivered for the date (itself excluded), including any statement PDFs.

| Column | Type | Null | Description |
| :- | :- | :- | :- |
| `as_of_date` | date | no | Reconciliation date `T` |
| `cutoff_at` | timestamp | no | The cutoff instant this batch was struck at. Snapshot files are as of this instant. `transactions` covers the window from the previous batch's `cutoff_at`, exclusive, to this one, inclusive. |
| `file_name` | string | no | Exact delivered file name |
| `dataset` | enum | no | `accounts`, `positions`, `transactions`, `assets`, `prices`, `compliance_profiles`, or `statement` |
| `record_count` | int | yes | Data rows in the file, excluding the header. Empty for statement PDFs. |
| `sha256` | string | no | SHA-256 of the file as delivered, that is of the encrypted `.gpg` |
| `generated_at` | timestamp | no | When the file was produced |
| `spec_version` | string | no | Version of this layout the file follows, starting at `1.0.0` |
| `revision` | int | no | `0` for the original batch, `N` for restatement `_rN` |

Verify presence, counts, and checksums against the manifest before consuming anything. Treat a missing manifest past the agreed delivery window as an incident and contact your operations contact.

## Run the daily reconciliation

The intended flow on your side, once the manifest arrives:

**1. Completeness**

Verify every file the manifest lists is present with a matching `record_count` and `sha256`, then decrypt.

**2. Account reconciliation**

Diff `accounts` against your master: every expected `external_id` present, statuses as expected, hierarchy (`parent_account_id`) intact.

**3. Position roll-forward**

For every account and asset, `TOTAL(T) − TOTAL(T−1)` must equal the signed sum (`CREDIT` positive, `DEBIT` negative) of `quantity` over `transactions` rows with `balance_type = AVAILABLE`.

**4. Valuation check**

`market_value_usd = quantity × price_usd` on every position row, and `price_usd` matches `prices.price_usd` for the same date.

**5. Trade reconciliation**

Match `TRADE` rows to your order records through `order_id` or `order_external_id`. Verify allocation quantities, `avg_price`, and fees.

**6. Funding reconciliation**

Match `DEPOSIT` and `WITHDRAWAL` rows to expected flows through `onchain_tx_hash` and `transaction_id`. `PENDING` rows explain the `PENDING` and `HOLD` balances in `positions`.

**7. Breaks**

Raise them with your Anchorage Digital operations contact, quoting `as_of_date`, `account_id`, and the `transaction_id` values or account and asset pairs involved.

## Set up a PGP key

Every file is encrypted with your PGP public key before transmission. You can provide a key generated with any PGP or GPG-compatible tool. If you don't have one, the steps below use GnuPG. On Windows, substitute `gpg.exe` for `gpg`.

**1. Install GPG**

Check whether it's already available with `gpg --version`. If not: `sudo apt install gnupg` on Ubuntu or Debian, `brew install gnupg` on macOS, or [Gpg4win](https://gpg4win.org) on Windows.

**2. Generate a key pair**

```shell theme={null}
gpg --generate-key
```

Enter a name (for example `Anchorage recon files`), an email address, and an optional passphrase. A blank passphrase makes automated decryption easier, but a private key without one is less protected if someone gains access to the system holding it. Confirm the key exists with `gpg --list-secret-keys`.

**3. Export the public key**

```shell theme={null}
gpg --armor --output anchorage-recon-files.asc --export engineering@yourcompany.com
```

Send the `.asc` file to Anchorage Digital. The public key is safe to share over any channel. Never export or send your private key.

**4. Test decryption**

```shell theme={null}
echo "This is a GPG encryption test." > test-file.txt
gpg --output test-file.txt.gpg --encrypt --recipient engineering@yourcompany.com test-file.txt
gpg --output decrypted-test-file.txt --decrypt test-file.txt.gpg
```

If your private key has a passphrase, GPG prompts for it. Confirm `decrypted-test-file.txt` matches the original. The same decryption applies to every file you receive from Anchorage Digital.


## Related topics

- [Transactions](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-transactions.md)
- [Overview](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-overview.md)
- [Balances](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-balances.md)
- [Accounts](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-accounts.md)
- [Web dashboard](https://docs.anchorage.com/knowledge-base/porto/vaults-wallets/web-dashboard.md)
