Register user

The identity registry entry is the prerequisite DALP checks first on every mint and transfer. Without it, regulated asset transactions are blocked regardless of what other claims or approvals the user holds. Registration alone does not make the user eligible for every asset: claim topics, trusted issuers, country rules, and transfer restrictions all apply after the registry resolves the wallet.

KYC evidence stays off-chain with the verifier and operator workflow. DALP records the result on the user's OnchainID as claims, such as KYC or AML topics, plus the issuer that signed them. When a regulated token checks a mint or transfer, DALP resolves the wallet through the registry, reads the required claims, verifies that each claim issuer is trusted for the matching topic, and then evaluates the configured compliance modules. Missing claims, untrusted issuers, or failed country and transfer rules can all block eligibility.

For the underlying identity model, see Claims and identity.

Prerequisites

• Identity Manager role or equivalent permissions.
• A user with a wallet and OnchainID created during onboarding.
• A confirmed jurisdiction for the user. DALP registration routes use ISO 3166 alpha-2 country codes, and the Console submits the selected country on-chain.
• Wallet verification for the signing user. The Console asks for the wallet approval method before it submits the registration transaction.

What registration changes

Registration writes the wallet-to-identity relationship into the identity registry. The user moves from pending to registered once the transaction is confirmed and indexed.

Registration is therefore the identity-registry step in a broader compliance flow. Trusted issuer claims, KYC review, country restrictions, and transfer approval rules still control whether a specific asset can be minted or transferred to the user.

Before you register

Review these details before submitting the transaction:

• The selected user is the intended holder or operator account.
• The wallet address shown on the user profile is the one you want to bind to the OnchainID.
• The OnchainID belongs to the selected user.
• The country selection reflects the user's legal residence or incorporation, not a temporary location.
• Any required KYC, KYB, AML, sanctions, accreditation, or other off-chain review is complete before a trusted issuer issues claims.

Register a user

Compliance impact

Token mints and transfers

• Non-registered identities are blocked from regulated asset transactions.
• Registered identities are eligible only when the token's compliance rules pass.
• An identity-verification rule can require one claim topic, such as KYC, or a logical expression such as KYC and AML.
• The required claim must be present on the user's OnchainID and issued by a trusted issuer authorised for that topic.
• Different assets can require different claim topics, trusted issuers, country rules, or transfer approvals.

Compliance modules

• Identity verification modules confirm registry enrolment and required claim topics.
• Country and transfer-restriction checks can apply additional rules after identity lookup.
• One failing module is enough to block the mint or transfer.
• Compliance reporting shows enrolment and verification status and flags users blocked from transacting.

Verification process

• KYC, KYB, AML, sanctions, accreditation, and document review happen off-chain before a verifier issues a claim.
• The on-chain claim records the verification result, topic, issuer, signature, and supporting reference data.
• Only issuers trusted for the relevant topic should issue claims used for transfer eligibility.
• Multiple verifications can be issued per enrolled identity when different assets require different topics.

Operational checks

• Register users after onboarding creates the wallet and OnchainID.
• Verify the user's legal residence or incorporation evidence before selecting the country.
• Keep the off-chain evidence and approval record in your operating workflow.
• Review duplicate or stale user records before registration.
• Use the identity recovery workflow when the registered wallet is lost or compromised. A normal profile edit does not replace the registered wallet binding.

Troubleshooting

Related guides

• User onboarding: how users get a wallet and OnchainID before registration.
• Claims and identity: how wallet registration, OnchainID claims, and trusted issuers work together.
• Identity and compliance: how identity checks fit into the broader compliance architecture.
• Provide KYC data: how users complete their KYC profile.
• Manage KYC data: how operators review KYC submissions.
• Verify KYC: how verifiers issue claims after review.
• Configure trusted issuers: the issuer and claim-topic framework.
• Recover a user's identity: lost or compromised wallet access.