Manage address book

Prerequisite

Each address belongs to a counterparty so you must create a counterparty before adding any addresses.

Create a counterparty

Select ‘Create counterparty’
Enter the counterparty details, including name and description
Select the type of counterparty This may be a decentralized application (dApp), individual or organization.
If you select individual or organization, enter the individual or organization’s details, including legal name and full address

Add an address

Select ‘Add address’
Select the counterparty that the address will belong to
Enter the destination wallet address
Select one or more blockchains that are supported by the address
If you selected XRP Ledger, you can optionally enter a destination tag to identify a specific counterparty at this r-address (see XRP Ledger destination tags)
Enter the name of the address (description is optional)
If the destination address is custodial (ie. controlled by a custodian such as Coinbase), you must select ‘add custodian details’. A search bar will appear so you can search and select the correct custodian
Click the ‘submission’ checkbox to confirm that the custodial information you are submitting regarding ownership of the destination wallet is correct

Compliance checks

Any counterparty/address details are subject to compliance checks and may not be available for immediate use.

XRP Ledger destination tags

Destination tags are optional 32-bit unsigned integers (0 to 4,294,967,295) that identify a specific counterparty at an XRP Ledger r-address. Exchanges commonly use a single r-address for many customers and rely on the destination tag to route funds to the correct account.

When adding an XRP Ledger address, you can enter a destination tag alongside the r-address. Wallet-as-a-Service (Palisade) treats the r-address and destination tag together as a unique address, so you can add multiple entries that share the same r-address but differ by tag.

Tagless addresses

You can leave the destination tag empty for r-addresses that don't require a tag. A tagless entry is distinct from any entry with a tag — matching is exact.

How destination tags affect matching

Address lookup — Searches match on the full r-address and destination tag combination. Two address book entries with the same r-address but different tags resolve independently.
Transaction history — New transactions display the counterparty whose r-address and destination tag exactly match the transaction's destination. Palisade doesn't backfill historical transactions.
Policies — Policies that reference an address book entry apply to the specific r-address and destination tag combination on that entry.

Delete a counterparty or address

Counterparties and addresses can be deleted from the ‘actions’ bar in their respective tables.

API documentation