Skip to main content
POST
Registers a customer’s KYC verification on the on-chain identity registry. The address is checksummed and a KYC hash is computed, then the encoded registry call is returned for you to sign. Call it once without txHash to get the calldata, and again with txHash once you have broadcast it. The second call verifies the receipt and creates or updates the off-chain customer record. The endpoint picks verifyIdentity or updateIdentity for you depending on whether the address is already on the registry, and reports which in operation.

Request Body

string
required
Ethereum wallet address to verify.
string
required
ISO country code (minimum 2 characters).
string
default:"RETAIL"
Investor classification. Values: RETAIL, PROFESSIONAL, INSTITUTIONAL.
integer
Number of days until the verification enters a soft-expired state. When set to 0 or omitted, no soft expiry is applied.
integer
Number of days until the verification is fully expired on-chain. When set to 0 or omitted, no hard expiry is applied.
object
Optional custom data to include in the KYC hash computation. When omitted, the hash is derived from the wallet address, country, and current timestamp.
string
Hash of the transaction you broadcast. Send it to confirm the verification and write the customer record. Omit it to receive the calldata.

Response Fields

object
kycHash is derived from the current timestamp when you do not supply kycData. Requesting calldata twice produces two different hashes. Carry the kycHash from the calldata response through to your records, and confirm the transaction you actually broadcast.