Manage token trusted issuers

A trusted issuer is an identity whose signed claims your compliance policy accepts. Most issuers are configured once for the whole organization, but a single token can accept extra issuers that apply only to that asset. Review which issuers a token trusts and add or remove the ones it owns from the token's Trust Registry.

To manage issuers for the whole organization instead, see Configure trusted issuers. For the wallet, OnchainID, claim-topic, and issuer model that sits underneath both, see Claims and identity.

When to use a token-level issuer

Add an issuer at the token level when one asset needs to accept claims that the rest of the system should not. A single fund tranche that recognizes a specialist accreditation provider is a typical case. The asset still inherits every system and global issuer, so a token-level entry adds trust rather than replacing it.

Prerequisites

• The governance role on the token. Without it, the Trust Registry is read-only: you can review the chain, but the add and remove controls stay hidden.
• A signing wallet ready for wallet verification. Adding or removing an issuer writes an on-chain transaction.
• For an add, at least one claim topic available in the token's resolved topic-scheme chain. If the chain has no topics, the add form blocks until you register one. See Add a verification topic and the token topic-scheme workflow on the same Trust Registry tile.

Open the token Trust Registry

1. Open the token from the asset list and go to its detail workspace.
2. On the Token information tab, find the Trust Registry tile.
3. Open the Trusted Issuers detail page from that tile. It opens as a full page with its own breadcrumb.

Behind the Trust Registry tile, trusted issuers and topic schemes each open as their own detail page. For the related topic-scheme workflow, use the topic-scheme page reached from the same tile.

Read the resolved issuer chain

The Trusted Issuers page lists every issuer the token trusts, resolved through three tiers. Each row carries a tier badge. Filter by tier to narrow the list to a single scope:

Each row shows the issuer in the Issuer column, the claim topics that issuer can verify, and a badge for its tier. When an issuer identity resolves to a linked account, the Console displays the account ID in that column. Otherwise it shows the identity address. Inherited system and global rows show a read-only label in place of a row menu. You can see the full effective trust set in one place without editing entries that belong to a higher scope.

The table supports search, filtering by tier, and CSV export, so you can confirm exactly which issuers apply to the asset and at which scope.

Add a token-level trusted issuer

You need the governance role, and the token must have a trusted-issuer registry and at least one claim topic in its scheme chain.

After the transaction confirms, the new issuer appears as a token-tier row. Because the change settles only after the platform indexes the transaction, the page shows a short notice that the update was submitted and may take a moment to appear. The new issuer can then verify claims for the topics you assigned.

Remove a token-level trusted issuer

You can remove only token-tier issuers. System and global rows are read-only here; change those from the organization-level guide or the parent global registry.

1. Find the token-tier issuer row.
2. Open the row menu and choose to remove the issuer.
3. Confirm with wallet verification.

While a removal is in flight, that row's menu is disabled to prevent a double submission. As with an add, the change settles after indexing, and the page shows a brief submitted notice. Once removed, claims from that issuer no longer count through the token-level entry. Claims it still satisfies through an inherited system or global trust entry continue to count until you change those higher-scope registries.

Keep token trust deliberate

A token-level issuer is part of the asset's compliance policy, not a convenience list. Before you add or remove one, check these points:

• Identity address: use the deployed identity address, not the wallet address. A wallet address alone is not enough.
• Claim topics: assign only the topics the issuer is allowed to verify. A claim counts only when the issuer is trusted for the exact required topic.
• Scope: add token-level issuers only when the asset genuinely needs trust the rest of the system should not have. Otherwise configure the issuer once at the system level so every asset inherits it.

Troubleshooting

Read next

• Configure trusted issuers for the organization-wide issuer registry.
• Add a verification topic to define a claim topic before you assign issuers to it.
• Compliance overview for topics, issuers, and policy modules together.
• Claims and identity for the wallet, OnchainID, claim-topic, and issuer model.