5️⃣Customer Verification

This step assumes you have successfully created a new customer record using Customer Creationstep and signed a provided challenge

Once the customer challenge has been signed and signature verified, we will proceed to customer screening and verification. Our Sandbox is currently set up to automatically approve the screening stage proceeding to verification. At this stage, you can use our Simulator to verify or reject a newly created customer.

Assuming you would like to verify the customer and proceed with next steps, you need to make an empty PATCH request to /simulator/customers/{customerId}/verify.

Verify customer

patch

/simulator/customers/{customerId}/verify

Simulates customer verification success

Authorizations

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

customerIdstring · uuidRequired

Unique customer ID

Header parameters

SignaturestringRequired

HTTP message signature

Signature-InputstringRequired

HTTP message signature input

Idempotency-Keystring · uuidRequired

Idempotency key (UUID)

Responses

202

Successful operation

No content

400

Invalid request

401

Not authorised

404

Customer not found

500

Internal error

patch/simulator/customers/{customerId}/verify

PATCH /v1/simulator/customers/{customerId}/verify HTTP/1.1
Host: api.offblocks.xyz
Authorization: Bearer YOUR_SECRET_TOKEN
Signature: text
Signature-Input: text
Idempotency-Key: 123e4567-e89b-12d3-a456-426614174000
Accept: */*

No content

If your request was successful, you will receive an empty response with status 202 (Accepted).

The customer will be automatically activated, which you can verify by making a GET request to /customers/{customerId}.

Retrieve customer

get

/customers/{customerId}

Retrieves customer's details

Authorizations

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

customerIdstring · uuidRequired

Unique customer ID

Header parameters

SignaturestringRequired

HTTP message signature

Signature-InputstringRequired

HTTP message signature input

Responses

200

Successful operation

application/json

idstring · uuidRequired

Unique customer ID

externalIdstringRequired

Unique customer ID in a form of an external ID

chainIdstringRequired

Unique customer ID in a form of a valid on-chain address. This would normally correspond to customer's EOA wallet address

Example: eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb

statusstring · enumRequired

Customer status

Possible values:

createdAtstring · date-timeRequired

Date this customer was created (ISO-8601)

updatedAtstring · date-timeRequired

Date this customer was updated (ISO-8601)

400

Invalid request

401

Not authorised

404

Customer not found

500

Internal error

get/customers/{customerId}

GET /v1/customers/{customerId} HTTP/1.1
Host: api.offblocks.xyz
Authorization: Bearer YOUR_SECRET_TOKEN
Signature: text
Signature-Input: text
Accept: */*

{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "externalId": "text",
  "chainId": "eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb",
  "status": "initiating",
  "createdAt": "2026-01-01T00:00:00.000Z",
  "updatedAt": "2026-01-01T00:00:00.000Z"
}

{
    "chainId": "eip155:280:0x43158f45b5EbD7b1179130130DF00393928C2691",
    "createdAt": "2024-01-12T14:53:02.653457Z",
    "externalId": "27c9aa3b-f12d-43b9-8e91-5264ccc998de",
    "id": "04c5851c-4386-5bd9-9f89-08312f8aee3a",
    "status": "active",
    "updatedAt": "2024-01-12T15:05:32.166028Z"
}

Once the customer has been created and successfully verified, we can proceed to setting up accounts and cards.