On this page

Noxtica ID Wallet (Early Access)

The Noxtica ID Wallet lets a person who has completed an identity verification reuse some of those details with another business. The person keeps a copy of the verified details in a wallet that Noxtica runs, and shares chosen details with a business only after consenting to each share. It is an extension of Identity Verification and a separate product.

This page is for a product owner, a privacy owner or an engineer who wants to understand what the wallet does before talking to us. It describes the designed behaviour of the Early Access wallet. It is not an integration guide.

How this page is organisedBar length shows each section’s share of the text. Select a section to jump to it.

What it is

Availability: Early Access, which has not opened. The wallet is not generally available, not self-serve, and not open yet. Contact us about Early Access through the contact page. No service level and no date is promised.

Businesses will need to accept wallet-specific terms before taking part. Those terms, and the notices that go with the wallet, are being finalised. Nothing on this page replaces them.

There are three roles:

RoleWhoWhat they do
HolderThe person who owns the walletSaves details, answers requests, revokes shares, deletes the wallet
Issuing businessThe business whose hosted verification produced the detailsOffers the person the option to save the result to the wallet
Receiving businessA business that asks the person to share detailsSends a request, then reads the details the person approved

A business can be both. Each side is switched on separately, per business, and neither is on by default.

The wallet is not a second verification and does not skip the original one. A business that needs a fresh verification still runs its own Identity Verification session. A wallet share is not an approval: the receiving business makes its own decision.

  • For the person

    • Saves only if the person agrees
    • Opens with a passkey
    • Lists and revokes shares
  • For the receiving business

    • Ticked details only
    • A business-specific identifier
    • How it was verified
    • A signed consent receipt
  • Limits on sharing

    • A bounded read window
    • Revoke stops future reads
    • Delete, or leave it
What the Early Access wallet is designed to doIllustration with example labels, not customer data.

Who it fits

  • A business that already verifies people with Identity Verification and wants to let those people reuse the result elsewhere, with the person in control.
  • A business that wants verified details about a returning person without repeating a full verification, and accepts that the person decides what to share.
  • A person who wants to decide, detail by detail, what another business sees.

It does not fit a business that needs a login or identity provider, a credential the person carries outside Noxtica, a way to search for people, or a check that skips a verification.

How a share works

  1. A person is verified as usual. They complete a hosted Identity Verification at a business taking part in Early Access. That verification and its review do not change.
  2. The person may save the result. The hosted page can offer to save the verified details to the wallet, under a separate consent that is not pre-ticked. The wallet opens with a passkey. Face images, biometric data, document numbers and machine-readable zone (MRZ) data are not saved.
  3. Another business sends a request. The person gets a single-use link, signs in with a passkey, and sees who is asking, why, which details are requested, and how the saved verification was checked. Each detail has its own checkbox, and nothing is ticked for the person. If a required detail is not ticked, the request cannot be approved. The person can also decline.
  4. The business reads the approved details. It receives only the details the person ticked, plus the items listed below.
  5. The person can revoke. Revoking stops future reads.

What a business receives

A share returns:

  • The ticked identity details only. A detail the person did not tick, or the wallet does not hold, is left out. Available details are given name, family name, birth date, nationality, document country, document type and document expiry, and “age over 18”, which is worked out when the share is read so that a business can avoid receiving the birth date.
  • A business-specific identifier. It is different for every business, so two businesses cannot match the same person by it. The wallet gives businesses no way to search for a person. A business could still recognise someone from the details that person chooses to share.
  • Information about how and when the identity was verified. The methods used with each result, whether a method is advisory only or a rule-based check, the review state, the date the identity was verified and a freshness label. The wallet carries this and never raises it. It claims no external certification or assurance level.
  • A consent receipt, digitally signed by Noxtica. It records what was shared, with which purpose and when.

A business can state a minimum when it asks, such as a review approved by a person, a verification not older than a set number of days, or required checks. If the saved verification falls short, the request is not offered to the person, and the business sees only that the request did not go ahead, with a general reason. The business can then run its own verification.

Nationality can reveal sensitive information by inference. It is shared only when the request states a purpose and the person ticks it.

How long a business can read

  • By default, a business can read an approved share once, within 24 hours.
  • An ongoing share exists only when the business asked for one and the person ticks “keep sharing until I revoke”. It lasts at most 90 days and allows a limited number of reads. The person can revoke it at any time.
  • After a revoke, expiry or the last allowed read, the next read is refused and returns no details.

What is saved

The wallet keeps the details listed above and how the verification was checked. It does not store or share face images, biometric data, document numbers or machine-readable zone (MRZ) data. The original verification stays under Identity Verification and its own retention rules.

The passkey check happens on the person’s device. Noxtica does not receive the fingerprint or face used to unlock it. Recovery is by extra passkeys and ten single-use recovery codes. A person who loses every passkey and every code loses the wallet. There is no email, SMS or re-verification recovery.

Wallet data is not used for risk signals, models or training.

The person can delete their wallet at any time. Deleting erases the saved details, passkeys and recovery codes and ends every share. It does not delete details a business has already received. A pseudonymised record of past shares is kept. A wallet is not deleted automatically: after 24 months without a sign-in it is suspended, nothing is shared from it, and signing in with the passkey reactivates it.

Limits

  • Early Access, which has not opened. Not generally available, not self-serve, and not open yet. No service level and no date is promised.
  • Revoking a share stops future reads. It does not delete details a business has already received. That business is responsible for what it holds, and the person asks it directly to delete them.
  • The wallet carries how a verification was checked and never raises it. It claims no external certification or assurance level.
  • In the original verification, liveness and presentation-attack checks are advisory signals and there is no fully automated approval: a person reviews the case. A wallet share is not an approval.
  • The wallet is not a login, an identity provider or a credential the person carries outside Noxtica.
  • The wallet gives businesses no search, no list of people and no lookup by identity.
  • A person who loses every passkey and every recovery code loses the wallet. The business’s own verification is unaffected.

Common questions

Is the ID Wallet available?

Not yet. It is in Early Access, which has not opened. Businesses will need to accept wallet-specific terms before taking part, and those terms are being finalised. It is not self-serve. Contact us about Early Access. No date is promised.

How is it different from Identity Verification?

Identity Verification checks a person for a business. The wallet is an extension of it and a separate product: it lets a person who has been verified reuse some of those details with another business, with their consent. A wallet share is not an approval, and the receiving business makes its own decision.

Does a business keep access after a person agrees?

Only for the read window of that share. By default that is one read within 24 hours. An ongoing share exists only if the business asked and the person ticked “keep sharing until I revoke”, for at most 90 days. The person can revoke it at any time.

Does revoking delete what a business received?

No. Revoking stops future reads. A business keeps what it already received and is responsible for it. To ask it to delete those details, the person contacts that business directly.

Can a business look people up?

The wallet gives businesses no way to search for a person. A business receives details only when the person approves its request, and could still recognise someone from the details shared. The identifier is different for every business.

Does the wallet store a face or biometric data?

No. The wallet does not store or share face images, biometric data, document numbers or machine-readable zone (MRZ) data. The original verification stays under Identity Verification and its own retention rules.

Is there automatic approval?

No. In the original verification, liveness and presentation-attack checks are advisory signals and there is no fully automated approval: a person reviews the case. A wallet share is not an approval.