Register user

Registering a user links a wallet address, OnchainID identity, and jurisdiction in the identity registry. DALP uses that registry entry when it evaluates regulated asset mints and transfers.

Registration does not make the user eligible for every asset by itself. Eligibility still depends on the asset's required claim topics, trusted issuers, country rules, and transfer restrictions.

Use this guide to register identities from an integration or automation script. For the portal workflow, see Register user.

Prerequisites

• Platform API base URL, such as https://your-platform.example.com.
• API key with permission to register identities.
• A user wallet with an existing OnchainID identity. See Create users.
• A confirmed jurisdiction for the user. The API accepts ISO 3166-1 alpha-2 country codes, such as BE, DE, or US.
• Wallet verification when you authenticate with a browser session. API key authentication does not require a walletVerification body.

What registration does

Registration queues an on-chain system.identity-register transaction against the active identity registry. The API accepts the country as an ISO alpha-2 code and encodes the numeric country value for the on-chain registry call.

Register a user

curl "https://your-platform.example.com/api/user/[email protected]" \
  -H "X-Api-Key: YOUR_API_KEY"

[
  {
    "id": "usr_abc123",
    "name": "John Doe",
    "wallet": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb",
    "role": "member"
  }
]

curl -X POST "https://your-platform.example.com/api/v2/system/identity-registrations" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Prefer: respond-async" \
  -d '{
    "wallet": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb",
    "country": "BE"
  }'

{
  "transactionId": "txreq_123",
  "status": "QUEUED",
  "statusUrl": "/api/v2/transaction-requests/txreq_123"
}

curl "https://your-platform.example.com/api/v2/system/wallets/0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb/identity" \
  -H "X-Api-Key: YOUR_API_KEY"

{
  "data": {
    "id": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890",
    "account": {
      "id": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb",
      "contractName": null
    },
    "isContract": false,
    "hasIdentity": true,
    "registered": {
      "isRegistered": true,
      "country": "BE"
    },
    "claims": []
  },
  "links": {
    "self": "/v2/system/wallets/0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb/identity"
  }
}

Request body

Wallet verification object

CLI equivalent

The CLI identities command calls the same identity APIs and is useful for scripts that already run through a DALP CLI profile.

dalp identities register \
  --wallet 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb \
  --country BE

dalp identities read-by-wallet 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb

Send the same alpha-2 country code that you would send to the API.

Compliance boundaries

• Registration is required before a wallet can pass regulated asset eligibility checks.
• Registration stores the wallet-to-OnchainID relationship and country in the identity registry.
• KYC, KYB, AML, sanctions, accreditation, and document review happen off-chain before a trusted issuer issues claims.
• Asset eligibility still depends on required claim topics, issuer trust, country rules, and transfer restrictions.
• Keep legal residence, incorporation, approval, and evidence records in your own operating workflow.
• If a registered wallet is lost or compromised, use the identity recovery workflow. A normal user profile edit does not replace the registry binding.

Troubleshooting

Related guides

• Create users explains how to create users with wallets and OnchainID identities.
• Transaction tracking explains how to follow queued blockchain operations.
• Verify KYC explains how to issue claims after review.
• Claims and identity explains how wallet registration, OnchainID claims, and trusted issuers work together.
• Identity and compliance covers the identity checks used by compliance modules.
• Register user covers the portal workflow.