Entities lists every identity registered in the system's identity registry on the active network: tokens, the system itself, contracts, smart wallets and key wallets, people's wallets included. It is also where an identity manager registers an identity that already exists, such as an investor's identity another organisation created or a participant's new wallet, in the organisation's identity registry. Registration lists a participant's wallets, under one country, in the registry that every regulated token of the organisation checks before it lets a wallet hold or move value. A person's sign-in, KYC and roles are on Users, and the entity that represents your organisation holds its own KYC profile here.
Each row joins two addresses. The contract address is the account the identity belongs to: the token or system contract, or the wallet. The identity address is its on-chain identity, the separate contract that holds its claims and that the identity registry lists. Registered means the registry lists the identity as active. It does not mean any token accepts the entity, because each token also checks the verifications its compliance rules require, at the moment of the operation.
The “Entities” page, with “Register existing identity” in the header.
The page describes itself as “Every identity registered in the system: assets and tokens, the system itself, contracts and wallets.” The table shows “Name”, with each entity's type under its name, then “Identity address” and “Status”. The “Contract address” and “Type” columns are hidden by default, and the toolbar reads “2 hidden”.
Steps
Register an existing identity
Select Register existing identity. Enter the “Identity address”: the identity of a participant in your organisation, or of one that asked to register here. Choose the “Country”. The platform writes it to the identity registry as an ISO 3166-1 numeric code, and country allow and block lists read it when a transfer is checked. Review the summary, enter your transaction PIN or transaction code, and confirm.
The “Register existing identity” sheet open over the “Entities” table, with two steps, “Details” and “Review”.
On the “Details” step, the required “Identity address” field carries the hint “The on-chain identity contract address of the participant.” and the required “Country” field carries the hint “All wallets will be registered under this country.” The sheet ends with “Cancel” and “Review” buttons.
One registration covers every active wallet the participant holds on the network, its smart wallet included, under the one country you chose. The participant does not need to agree. When some of the participant's wallets are already registered here, the registration adds only the unregistered wallets bound to the participant's identity, under the same identity and the country you choose. Nothing forces that country to match the one the participant is already registered under, so choose the same one. “Accept” on a “New wallet” row fills it in for you.
Accept or reject a registration request
A participant that already exists, for example an investor whose identity another organisation created, can ask to register in yours. Each request shows in Pending participant registrations with the participant's name, kind and request date. The panel shows only to an identity manager, only while a request waits, and lists the 20 newest requests. A Canton party request shows “Canton party” and has no actions, because the registry operator approves Canton parties.
Select Accept to open the registration sheet with the request's identity address filled in, and the country too when the request proposes one. Choose or confirm the country, enter your transaction PIN or transaction code and confirm. The request leaves the panel once the indexed identity registry shows the identity as active. Accept needs both an identity address and a wallet address on the request.
When a registered participant adds a wallet, the panel shows a New wallet row that names the wallet “for an approved identity”. The row has no “Reject”. “Accept” opens the sheet as “Register new wallet” with the wallet named. It starts at “Review” with the identity's registered country, or at “Details” when the registry holds no country for the identity. “Register wallet” registers the named wallet and any other bound wallet of the participant that is not registered yet.
Select Reject and confirm to remove a request. Rejecting needs no verification code. The participant can ask again later, which reopens the same request, so a rejection only removes the request from the queue. It records no compliance decision. A direct registration of a rejected participant is refused until the participant asks again.
Open an entity
Select a row to open the entity. The page shows the contract address, the identity address and a registered or pending badge, with the tabs “Overview”, “Verifications”, “Activity log” and “Data feeds”, and, on your own organisation's entity, “KYC”. An identity with no linked account shows an empty “Overview”, and its “Activity log” reads “No identity yet”. The activity log lists the on-chain events tied to the entity's account, the registration transaction included.
To take a user's wallet out of the registry, use Remove registration on the user's page, which Users describes.
Review the verification profile of your own organisation
The entity that represents your own organisation has a KYC tab. The tab holds the organisation's KYC profile, its know-your-business record: the same field-by-field review that Users runs for a person, applied to the organisation. The tab shows only on the page of an entity whose identity address belongs to your organisation, and only to an identity manager or a verification issuer. On any other entity page the tab is absent, and opening its address directly shows the not-found page.
The profile card shows the status, the country, and the organisation details: legal name, registration number, registered address, and legal entity identifier (LEI). Legal name and registration number are required. Each field shows its review state: waiting for review, approved, or changes requested, with the name of the person who edited or reviewed it. A verification issuer reads the card. An identity manager also edits it.
- Edit the fields and select Save. The saved fields wait for review.
- Select Approve all to approve every field of the latest version, or “Request changes” to name the fields that need correction and write a note.
- Read the Version history card below the profile for every version, the latest marked “Current”, with its status and when it was created.
The person who edited a field cannot approve it or request changes on it. The Console hides “Approve all” and “Request changes” while a field you edited waits for review, and another identity manager must review it. A platform administrator who edited the field while impersonating that person cannot approve it or request changes on it either. Saving an edit to an approved profile removes its approval, so the Console asks you to confirm before it saves. The edited fields then go back for review.
Read the data feeds of an entity
An entity's detail page can show a Data feeds tile summarising the market data feeds related to it: a “Related feeds” count and a “Last updated” time, rather than a list of the feeds themselves. A feed counts as related for one of two reasons, and the tile's count does not say which applies:
- The feed is scoped to this entity's own contract or identity address, so the feed describes the entity. This does not say who published it.
- The entity is a trusted issuer for the feed's topic, so it may attest to that kind of data even though the feed belongs to another contract.
If the count is higher than you expected, select View feeds to open the individual feeds it covers, since a trusted-issuer relationship can inflate the count without this entity publishing anything itself. “Last updated” is a single aggregate: the most recent publish time across every related feed, or “Never” when none of them has published yet. The tile shows a “No data feeds configured” state when no feed relates to the entity, or when the deployment has no feeds directory installed.
Columns in the Entities table
The table opens with the most recently registered identities first.
The Type column reads “Token”, “Asset”, “Bond”, “Equity”, “Fund”, “Deposit”, “Stablecoin”, “Real Estate”, “Precious Metal”, “System”, “Smart wallet”, “Operator wallet”, “Wallet” for a key account, or “Contract”. In the “Name” column, each entity's type shows under its name. An entity with no name shows its address in its place.
Troubleshooting
No participant found at this address on this chain
The address you entered is not the identity of a participant on the active network, or the identity belongs to a participant that is not in your organisation and has no pending request to register here, for example one you rejected. Check that you entered the identity address, not the participant's wallet or contract address, and that the active network is the one the participant's identity lives on. A rejected participant asks to register again first.
The registration is refused as already registered
Every wallet of the participant is already registered in this organisation. Nothing is left to register. When the participant added a wallet, its request shows as a “New wallet” row in Pending participant registrations.
The new wallet is not bound to the identity
The platform refuses with DALP-12402 when no new wallet of a registered participant is bound to its identity. Retry
once the participant adds the wallet's key to its identity.
The registration is refused for a participant you rejected
After a rejection, a direct registration of that participant is refused until the participant asks to register again. Its new request then appears in Pending participant registrations.
“Accept” is unavailable on a request
The request carries no identity address or no wallet address, and the row says “The request has no identity yet, so there is nothing to register.” Ask the participant to complete its identity first. Reject stays available.
The KYC tab is missing
The tab shows only on the entity that holds your organisation's own identity address, and only to an identity manager or a verification issuer.
“Approve all” or “Request changes” is missing or refused
The buttons do not show while a field you edited waits for review: ask another identity manager. When the Console says the profile changed, reload the page and review it again.
Registered, but a token still refuses the entity
Registration does not make a participant eligible. Open Verify a participant and confirm the identity holds the verifications the token requires, from an issuer the token trusts.