On-chain identity
View your own On-Chain Identity: its record, its status, and the verifications an issuer has attached to it.
On-chain identity is where you check the ledger record that a regulated token reads before it lets your wallet hold or receive it. This page shows your own 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 from the account holder's side: what the Console knows about it, and what an issuer has verified against it. For how on-chain identity works across the platform, including how an issuer attaches a verification, see On-Chain Identity; for how an administrator manages someone else's identity, see Verify a participant.
Check this tab to confirm that your identity contract exists, whether an organisation has registered it, and which verifications an issuer has attached. Reading the tab changes no holdings or pending operations. A KYC submission that feeds a verification happens on the Profile page, and an administrator or reviewer, not you, decides when it becomes a verified claim. The same read, and the identity recovery action, exist as endpoints in the Platform API reference for an integration that needs them outside the Console.
Your identity appears on the "Identity" tab of your own ParticipantA participant lets every role grant, claim, audit row, and delegated action point at one stable subject, so a person's history never splits.Read the concept record. The tab shows an identity contract card, a status summary, and a verifications list for the network selected in the sidebar.
Open the account control in the Console's top bar, select "Switch" under "Acting as", then "View all". Open your own row to reach the tab. Acting as participants explains the participant list.
Steps
Open your identity
Open the account control in the Console's top bar, select Switch under Acting as, then View all to open the full participants table. Select your own row, the one marked Person, to open its detail page, then select the Identity tab.
Screen equivalent: an identity contract card with its address and a link to view it on the explorer, a status summary with your kind, identity, registration status, verification status, and country, and a verifications list below.
Read the status summary
Check the Identity row first, then registration status. Both describe the network selected in the sidebar, and they answer two separate questions. The Identity row says whether your identity contract exists on that network: "Present on this chain" or "Not created on this chain". Registration status says where your organisation's identity registry on that network stands on that contract:
| Registration status | What it means |
|---|---|
| Approved | Your organisation's identity registry holds an active entry for your identity contract. |
| Pending approval | The registry holds an entry that is not active yet. It stays that way until an identity manager in your organisation accepts it, so there is nothing to do here but wait. |
| Not registered | Your identity contract exists on this network, but your organisation's identity registry holds no entry for it. |
| Requires an identity | Your identity contract does not exist on this network yet, so there is nothing for the registry to hold. |
The participant's Overview tab sums the same facts across every network your organisation is connected to, for example "Present on 1 of 2 chains", and shows the registration status for the selected network on its own row.
Verification status counts how many active verifications an issuer has attached to your identity, a separate question from registration. The "Country / jurisdiction" field shows the country your registration recorded, when one is registered.
Review your verifications
Check the verifications list to see each active verification attached to your identity, including which type it is. A verification an issuer later revokes drops out of this active list; it does not show here as revoked. An "Issue verification" button sits above the list; it stays visible even when you cannot use it, showing you a reason instead of disappearing. Holding the verification issuer role is necessary to use it, but not sufficient: the button can still tell you your identity cannot yet receive verifications when your identity is not yet linked to an account, even for an issuer.
Registration and verification record different facts:
Registration
An organisation has entered your identity contract in its identity registry. Registration by itself does not mean an issuer has verified you.
Verification
An issuer has attached an active verification to your identity. Verification by itself does not mean you are registered anywhere.
A token you expect to receive may check one, the other, or both, depending on how its issuer configured it.
Troubleshooting
The page shows an explanatory message instead of my identity contract
Identity provisioning runs as a separate step right after the Console creates your account, so a transient failure can leave you without a contract even though your participant record exists. The page offers a recovery button right there to provision the missing identity; selecting it asks you to verify your wallet before it runs. Selecting it more than once is safe: if an identity contract already exists by the time you try, the Console recognizes that and does nothing further, rather than creating a conflicting second one.
My verification status shows zero even though I completed KYC
A KYC submission only becomes a verification after a reviewer approves it; a draft, a submission still under review, or one sent back for changes does not add to this count. Check the status of your submission on the Profile page, and see Acting as participants if the identity you are viewing belongs to a different participant than the one you submitted KYC as.
I cannot tell whether a failed read means I have no verifications or the page could not load them
The verifications list distinguishes the two on purpose: a genuine zero shows as an empty state telling you no issuer has attached one yet, while a failed read shows as a load error asking you to try again. Treat a load error as unknown, not as zero, and reload before concluding you have no verifications.
A link took me to the wrong identity
A direct link to your identity, such as Complete verification on a token sale eligibility check, always resolves your own person record, never the participant you are currently acting as. If you expected to see a different participant's identity, open Acting as participants and open that participant's own identity tab directly instead.
A link sent me to the participants list instead of my identity
That link needs a person-kind participant record to resolve, and it falls back to the participants list rather than showing an error when that lookup fails, whether because your account has none yet or the read failed transiently. Reload and follow the link again for a transient failure; if you land on the list again, open Acting as participants and confirm you have your own participant record before contacting an administrator.
Frequently asked questions
Does a revoked verification disappear from my record once it drops off this list?
No. This page's verifications list only ever shows active entries, so a revoked verification leaves the list the moment it stops counting, but the entry itself stays on your identity's permanent record with its revoked state visible elsewhere. See On-Chain Identity for how the ledger keeps that history. What changes on this page is only what counts toward eligibility today, not what happened before.
Who besides me can see this same identity information?
An administrator or a claim issuer can see your verification history, but not through this screen. Looking at your record from the participants roster lands them on a different one: a verifications list with no identity contract card, no status block, and no country field. It also lists verifications of yours that have been revoked, which your own tab drops the moment they stop being active. They end up with more of your history than this page shows you, not a copy of it.
API keys
Create and manage the API credentials that authenticate Platform API requests on your behalf, without a signed-in Console session.
Acting as participants
View every participant you can act for, switch which one your actions apply to, and create a new participant when your organisation needs one.