Contacts

Contacts is your personal address book: a list of names paired with wallet addresses that you reuse instead of retyping them during issuance, transfer, or settlement. Every saved contact belongs to the account that saved it within the active organisation. A colleague in the same organisation keeps a separate list of their own, cannot see the contacts you save, and cannot reuse them; there is no shared or organisation-wide address book behind this page.

Any account onboarded to an active organisation can manage its own contacts. Contact records require no additional role. Users and Entities have separate permission checks. Contacts appears in the sidebar under "User settings" for every onboarded account. The records carry no role gate, and the sidebar entry that reaches them carries none either.

This page is the wrong page for two things it can look like at a glance. A contact is not a User; saving one creates no login, grants no permission, and registers no on-chain identity. A contact is not an Entity either; it proves nothing about eligibility, and the platform does not check a contact's address against any compliance rule when you save it. A contact is a label on an address, nothing more: every operation that later uses that address still runs its own independent eligibility and compliance checksTransfer-Path Compliance enforces a regulated token's rules inside the on-chain transfer itself, so a movement that fails any rule reverts and never settles.Read the concept, whether the address came from Contacts or from typing it by hand.

Because a contact carries no verification of its own, the address you save is only as trustworthy as the channel you got it from. The Console autofills the address field from a stored contact, but picking a contact saves a keystroke, not a review step, so review it before submitting. Confirm the address through your institution's approved channel before you save it, and compare the full address shown on the record against that source again before you submit value against it. Nothing on the record or in any later operation compares the saved address against the source you copied it from, so a single mistyped character during entry persists unnoticed until you check it yourself.

A contact carries no compliance or eligibility status of its own, so there is nothing on the record for a later compliance change to update. If an address you saved becomes ineligible after you save it, the contact itself does not change, is not flagged, and does not disappear; the next operation evaluates its current eligibility. Because contacts are private to the account that saved them, no organisation-wide log records who added, edited, or deleted a contact. The only record of a change is the "Updated" timestamp on that one contact, visible only to the account that owns it.

StepsCopy Anchor Link

What editing and deleting actually doCopy Anchor Link

Editing a contact overwrites the existing record in place; it does not create a new one alongside it. The name and wallet a counterparty last had before your edit are not kept anywhere once you save the change. Contacts stores only the current values and the two timestamps, with nothing that plays the role of a version log. If you need to know what an address used to be before an edit, that information has to come from outside the Console, such as your own change records or the approved channel you originally confirmed it through.

Deleting a contact is permanent, as step 3 covers, and it does not touch anything that already used its address; neither does editing one. A transfer, issuance, or settlement you completed while that contact still existed keeps its own record of the address at the time, entirely independent of whether the contact row still exists or what it now says. Editing or removing a contact only changes the shortcut for typing that address again in the future, including for an operation still in flight when you make the change. Nothing in that operation reads the contact row again once it has resolved the address. Saving, editing, or deleting a contact is also private to your own account: the counterparty whose address you saved is never notified, and nothing about the change is visible to them from inside or outside the Console.

TroubleshootingCopy Anchor Link

The contact does not appear

Clear the search, or search with the wallet address instead of the name. If loading failed rather than returning zero rows, the page shows an alert with a "Try again" button in place of the table; select it to retry the load.

The wallet is wrong

Edit the contact before using it again. Saving a contact never verifies ownership, identity, or eligibility for a transfer, so a saved address can be wrong for as long as nobody checks it against the approved source.

Saving rejects the address as a duplicate

Another of your contacts already holds that wallet address; the Console stores nothing new and names the conflict in the rejection rather than overwriting the existing record. Open that existing contact and edit it instead, or save a different address. The wallet field can appear on only one of your contacts, whatever name each entry uses.

A deleted contact needs to come back

Re-add the contact with the same name and address; deletion leaves nothing else in the product to restore from.

An edited contact does not match what I remember saving

Contacts keeps only the current name and address, never a history of prior edits, so there is nothing in the record itself to compare against.

Check the "Updated" timestamp to confirm whether a change happened recently, and reconcile the current value against your own external record of what it should be.

Frequently asked questionsCopy Anchor Link