Trusted issuers
Authorise identity issuers for specific verification topics.
A trusted issuer is an On-Chain IdentityAn On-Chain Identity lets a subject's verification serve every asset that accepts it, so a screened wallet skips re-onboarding for the next regulated asset.Read the concept, typically an external verification provider or your own compliance team, whose signed identity evidence your system accepts. This page decides whose attestations count, and for which categories of evidence. An eligibility check is the read a compliance rule or a transfer performs to confirm a participant's identity carries the evidence it requires, and every one the platform runs afterwards reads the answer you set here.
Reach for this screen when you onboard a new verification source, such as a KYC provider, when an issuer's scope of authority changes, or when your system must stop trusting one. It does not issue evidence to anyone: a participant gets verified on Verify a participant, and the evidence categories themselves are defined on Verification topics, which must exist before you can assign them here.
The screen shows two registries. The "System" tab holds the issuers your own system trusts, and it is the only one you can change here. The "Global" tab lists the platform directory of issuers that every system inherits; inherited entries also appear in your system table with the source "Global", and nothing on this screen edits them. Eligibility checks, the identity half of Compliance PolicyA Compliance Policy lets a compliance team write eligibility and holding rules once, while a platform floor reaches every current-factory token.Read the concept enforcement, read the issuer-to-topic assignment at the moment they run. Adding a topic, removing one, or removing an issuer changes every check performed afterwards, and leaves claims already sitting on identities untouched.
Steps
Open Trusted issuers
Open "Compliance", then "Trusted issuers". The "System" tab is selected by default and lists each issuer with its "Issuer identity", "Assigned topics", and "Source". A row whose source reads "Global" is inherited from the directory: it shows the text "Managed globally" instead of a menu, so route a change to such an entry through whoever administers the directory, not through this screen.
Screen equivalent: the "System" tab lists trusted issuer identities with their assigned verification topics and whether each entry is system-owned or inherited from the global directory.
Add an issuer
Select "Add trusted issuer", enter the issuer's identity contract address, not its signing wallet, in "Issuer identity address", and choose at least one topic under "Verification topics". An address without a registered identity is refused. The Console reports: "This address must be a registered identity before it can be added as a trusted issuer." Entering an address that is already a trusted issuer turns the sheet into an update instead of a duplicate. Its current topics load into the picker, and the review step lists exactly what you are adding and removing; drop a topic the issuer already holds and that same review step warns: "Removing a topic only removes the issuer association. Existing claims issued for that topic will not be revoked." Select "Add issuer" and confirm with your wallet verification.
Decide which topics to grant
Grant only the topics this issuer's own evidence actually covers. Assigning a topic authorizes this issuer's valid claims to count for that topic. Other required claims, expiry checks, and asset rules can still block a movement. Leave a topic out instead, and checks requiring it fail for this issuer even when its evidence could have satisfied them.
- Only the topics the issuer verifies today, the default. A claim from this issuer satisfies checks for exactly those topics; every other topic still needs a different issuer. Choose it when the issuer's own verification practice is narrower than the full set of topics in your system.
- Every topic in the picker. A claim signed by this issuer satisfies every check that requires any of those topics, including ones the issuer never actually verifies. Choose it only when the issuer genuinely attests every one of those categories; otherwise it widens the issuer's authority past its real evidence.
- Fewer topics than the issuer verifies. Checks that require the unselected topics fail for this issuer's claims, even though the issuer could have satisfied them. Choose it when you are deliberately limiting this issuer's authority, such as during a phased rollout.
The same trade-off applies the next time you touch this issuer's topics, in the step below.
Change an issuer's topics
Open the menu at the end of the issuer's row and select "Edit topics". The address cannot change; the selection must differ from the current set before "Continue" activates. Removing a topic ends only the authorisation: existing claims already issued for that topic are not revoked, but from that point on, a claim this issuer signed for the removed topic no longer satisfies a check.
Remove an issuer
Select "Remove issuer" in the same row menu when the system must no longer trust the issuer at all, then confirm the dialog and your wallet verification. Removal deletes the registry entry; there is no paused state. Claims the issuer already signed stay on identities but stop counting toward verification while the issuer is untrusted, so a participant whose only evidence came from this issuer starts failing checks. A failure can appear as a missing required claim rather than naming the removed issuer. Check the current trust registry when investigating it.
Each of these changes is an operation the organisation's Audit trail records, with your name and the role you held at the time, so an attribution question afterwards has an answer inside the trail's window. The same operations exist as trusted issuer endpoints in the Platform API reference, covering register, replace the topic set, and remove, for deployments that manage trust from code.
Removing an issuer cannot be undone in one step, but trust is restorable. Add the same identity address back with the topics it should hold, and the claims it issued count toward verification again, because checks read the current registry rather than its history. Plan the gap, though. Between removal and re-add, every check treats that issuer's claims as absent evidence.
Troubleshooting
The issuer address is rejected
No verification topics are selectable
The picker stays disabled until you choose an issuer address, and it can only offer topics that exist. Select the issuer first; if the list is empty, create the topic on Verification topics and return.
A row shows Managed globally instead of a menu
The entry is inherited from the global directory, and this screen cannot change directory entries. Ask a directory administrator to adjust it; your system-level rows stay editable.
Continue stays inactive on Edit topics
The selected set matches the issuer's current topics, or is empty. Change the selection so it differs and keeps at least one topic; to drop every topic, remove the issuer instead.
The page reports management as unavailable
Your account lacks the "Verification policy manager" role on this system. Ask an administrator to grant it, or hand the change to someone who holds it.
Frequently asked questions
Can an issuer be trusted for one asset only?
Yes, but not from this screen. Each token resolves its trusted issuers across three tiers: its own token-level registry, the system registry you manage here, and the global directory. A token-level entry, added on that token's own trusted issuers screen, scopes trust to that one asset, and removing it leaves the inherited system and global trust intact. Use this page when the issuer should count for the whole system.
Why can I see the Global tab but not change it?
Because this screen never edits the directory. Without the directory administrator role, the tab shows a read-only notice instead of the table. With it, you can browse and search the directory per network, but the Console still offers no way to add, edit, or remove an entry there; directory changes happen outside this screen, and every system inherits the result.