Prove · Identity

Check a buyer once. Every listing knows them.

An investor is checked when they join. After that, every asset on the marketplace already knows whether they may hold it.

Check the buyer once, and the tenth sale costs what the first one did.

Identity · ID Wallet

Verified identity

Issued by an approved checker · valid

Legal entityVerified
JurisdictionSE
Over 18Proven
DocumentNot shared

The holder proved they are over 18 without the date of birth being shared.

  1. Site access

    The gate asks: is this contractor cleared?

    Answered from the proof · no documents collected
  2. Equipment hire

    The depot asks: is this firm qualified to take it?

    Answered from the proof · no second check
  3. Payment provider

    Authorisation asks: is this the same verified party?

    Answered from the proof · no signing up again

Checked once. Three services satisfied, and the documents never left them.

One check, before anything happens.

The same customer is checked three times before they can do anything: at onboarding, by the credit desk, by the payment provider. One check replaces all three.

Sign up, get checked, get a wallet and start, all in the same service. The check runs once, and an approved checker signs the result.

After that, each service checks only what it needs: the payment checks who may pay, the asset checks its owner, the contract checks who signed.

Subjects
People, organisations, and machines: the same model for all three.
Compliance
Checking a person and checking a company are built in, not bought from somebody else afterwards.
Disclosure
Prove one attribute without exposing the record behind it.
Reuse
Checked once, then reusable across every connected service, and it cannot be altered without that showing.
Access
Staff sign in without a password, under your access rules, with a record of who opened what.
Delivery
Our identity app, or straight from your own code.

Payments and assets read the same identity.

The payment knows who is behind it, and the asset stays tied to an owner who was checked. Nothing else needs its own identity check.

A one-day rental, a single customs clearance, a machine that will exist for an hour. None of those ever justified a full onboarding round.

The documents never move.

Verify

A clinician's registration, an investor's eligibility, a company's ownership, a device's serial. You set how deep it goes.

Issue the proof

The approved result becomes a proof its subject holds, and it opens whichever service needs it.

Present and check

A gate, a booking page or another system asks one question, and gets its answer without a new sign-up.

Audit

The auditor asks who was approved and when, and your team answers without opening a file.

Identity · Device
Sensor array · 4021Active
Gateway · NorthActive
Meter · 8817Revoked
Agent · schedulerActive

Each device holds its own credential. One revocation touches one device.

Revoke one, not all

The same model, whatever the subject.

An employee, a meter, a patient, a resident, a borrower, a buyer old enough to be served. Only the subject changes.

Enterprise access

An employee or a company laptop proves itself before it opens anything. No shared password store to leak.

Authentication documentation

Setting up devices

A meter gets an identity and a role of its own. Compromise one unit and an operator revokes its access without touching the fleet.

Device provisioning documentation

Healthcare consent

A patient says which provider may see what, and can withdraw it later. The pattern fits any consent you honour.

Agreement documentation

Citizen services

A resident proves they qualify without the municipality keeping another copy of them.

Federated trust documentation

Financial onboarding

A borrower is checked before the loan, then reaches the wallet and the asset purchase already cleared.

Legal identity flow

Answering one question only

Ask whether they are over 18, or authorised to sign, and store neither passport nor mandate. One fact, not the file behind it.

Authorise identity access

Three things identity makes possible.

A proof reused, a signature that acts, a machine with its own identity. Start with the one you need; the other two are there.

Verify once, reuse everywhere

A supplier presents one approved check to another service. Each service still decides whether that check meets its requirements.

Read more Reusable verification

Sign with legal force

A works order signed on site updates the schedule itself, and the signer is provably who you checked.

Read more Signing and agreements

Give machines an identity

A sensor, a gateway or an AI agent acts on its own authority, with no password shared across the fleet.

Read more Device identity model

The parts of the identity layer.

Explore the modules

Identity App

Your customer creates an identity, holds their proofs, approves requests and signs, all on a phone.

Account and user onboarding

ID Wallet

Holds the proofs for a person, a vehicle or a device.

Legal identity operations

Digital Signature

A contract, a payment approval, a form — signed by a person or a machine, binding either way.

Request a verified signature

Checks as a service

A new supplier is checked inside the sign-up you already have. You set how deep it goes.

Identity review and approval

Digital Identity

The proof itself, which every one of your services can check without calling us.

How identity works

Authentication

Staff sign in without a password, with the rules and audit log you need behind it.

Authentication and sessions

What needs proof before it can move?

Identity · signature

Agreement signed

Bound to a verified identity

SignerVerified entity
Legal forceBinding
ExecutableBy machine

Not a PDF. An instrument a system can act on.