DEOSX OTC.

Explore OTC

DEOSX Tokenisation · Digital ID Framework

Verify once, use everywhere.

Identity verification and credentialing built for institutional onboarding.

Two phone screens showing a verification portal where entity, ownership and signatories are each marked verified

Interactive demo

See Digital ID Framework in action.

Tap through Digital ID Framework on screen, or use Next. The panel shows each API request and the webhook events your systems receive.

Interactive demo · Example data
9:41
DEOSXDigital IDTR
Entity
Registered
Ownership
Declared
Authorised people
Declared

Digital ID Framework

Details go in once with POST /v1/identity/verifications. The result works across every DEOSX product.

Submit entity and individual details for verification.

POST/v1/identity/verifications
curl --request POST \  --url "$DEOSX_API_URL/v1/identity/verifications" \  --header "Accept: application/json" \  --header "Authorization: Bearer $DEOSX_API_KEY" \  --header "Content-Type: application/json" \  --data '{  "entity": {    "name": "Example Holdings"  }}'

Response 202

{  "verification_id": "VR-1102",  "status": "IN_PROGRESS"}

What it unlocks

Why institutions use Digital ID Framework.

Verification for institutions

Entity checks, ownership and the people authorised to act, verified before the first product goes live.

Credentials that travel

A verified identity becomes a credential every product on the platform recognises, so onboarding is not repeated.

How it works

From instruction to record, in three steps.

01

Verify

Submit entity and individual details for verification.

02

Credential

Verified identities receive credentials tied to roles and permissions.

03

Use

Credentials are checked by every product, on every action.

Where this fits

Credentials checked on every action.

Connects institutions to the infrastructure needed to issue, wrap, hold and verify digital value, delivered under the same controls that govern the rest of the platform.

Explore DEOSX Tokenisation

Security

Bank-grade by default.

Compliance is not a department we consult. It is the rail the platform runs on.

KYB before the first quote

Every counterparty is verified before it can request a price.

Dual approval on every trade

No single person moves institutional money. Booking and approval are separated by role.

Screening inside the settlement path

Sanctions and Travel Rule checks run inside the lifecycle, not after the fact.

An audit trail that holds up

Every quote, approval and settlement leg is timestamped with its actor and kept.

FAQ

Answers about Digital ID Framework.

Didn't find your answer? Talk to our desk.

Do we verify again for each product?
No. A verified identity becomes a credential every product on the platform recognises, so onboarding is not repeated.
What gets verified?
Entity checks, ownership and the people authorised to act, before the first product goes live.

Talk to our desk.

Tell us what your institution needs to move, hold or issue. The desk replies within one business day.