Early Access

ID WALLET

Let people reuse a verified identity, one consented share at a time

An extension of Identity Verification, and a separate product. A person who has been verified can save details in a wallet that Noxtica runs, then share chosen details with another business after consenting to each share.

  • Early Access, not open yet: contact us
  • Consent for each business and each detail
  • Identity details shared only when ticked

Early Access. Not generally available, not self-serve, and not open yet. Contact us about Early Access. Businesses will need to accept wallet-specific terms before taking part; those terms are being finalised. No service level and no date is promised.

Availability
Early Access. Contact us about Early Access.ID Wallet documentation
Consent
Each share needs the person's consent, per business and per detail. Nothing is pre-ticked.How a share works
Revoking
Revoking a share stops future reads. It does not delete what a business already received.Limits
Identifier
Each business gets a different identifier for the same person.What a business receives

Scenarios

What the wallet is designed to help with

  • Reusing a verified identity
  • Sharing only chosen details
  • Taking sharing back

How it works

How it is designed to work

1. Verify as usual

A person completes a hosted identity verification at a business taking part in Early Access. That verification is unchanged.

2. Save, if the person chooses

The person may save the verified details to a wallet that Noxtica runs, under a separate consent that is not pre-ticked. The wallet opens with a passkey.

3. Consent to a request

Another business sends a request. The person signs in with a passkey, sees who is asking and why, and ticks each detail to share. Nothing is ticked for them.

4. Receive, then revoke

The business receives only the identity details the person ticked, plus a business-specific identifier, information about how and when the identity was verified, and a consent receipt digitally signed by Noxtica. The person can revoke at any time, which stops future reads.

Consent flow: the issuing business, the person's consent, the wallet, the receiving business and revoke.

Flow in words

Inputs

  • Issuing businessVerified the person with Identity Verification
  • The person's consentPer business and per detail, with a passkey

Noxtica ID Wallet

Early Access

Outputs

  • Receiving businessGets the ticked details, an identifier, verification information and a receipt
  • RevokeStops future reads

Illustration of the designed flow, not customer data. Early Access.

Capabilities

What the Early Access wallet is designed to do

For the person

  • Saves only if the person agrees

    Saves details from a completed verification only when the person agrees, under its own consent. Saved details: given and family name, birth date, nationality, document country, type and expiry.

  • Opens with a passkey

    The wallet opens with 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.

  • Lists and revokes shares

    Shows every share with its status and how often it was read, and lets the person revoke any of them.

For the receiving business

  • Ticked details only

    Identity details arrive only when the person ticks them. A detail the wallet does not hold is left out.

  • A business-specific identifier

    The identifier is different for every business, and 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.

  • How it was verified

    The methods used with each result, whether a method is advisory only or a rule-based check, the review state, the date and a freshness label. A business can set a minimum; if the saved verification falls short, the request is not offered to the person.

  • A signed consent receipt

    A consent receipt, digitally signed by Noxtica, records what was shared and when.

Limits on sharing

  • A bounded read window

    By default a business can read an approved share once, within 24 hours. An ongoing share exists only if the business asked and the person ticks “keep sharing until I revoke”, for at most 90 days.

  • Revoke stops future reads

    The next read after a revoke is refused. Details a business already received stay with that business.

  • Delete, or leave it

    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, and the passkey reactivates it.

  • 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.

Example

What a business receives in one share

Illustrative
Details
Only those the person ticked, for example given name and age over 18
Identifier
A business-specific identifier
Verification
How and when the identity was verified, as saved
Receipt
A consent receipt, digitally signed by Noxtica
Read window
One read within 24 hours, unless the person ticks an ongoing share (at most 90 days)
After a revoke
Future reads stop. Details already received stay with the business

Illustration with example labels, not customer data. Early Access: no date or scope is committed.

Where it fits

Where it fits

  1. Returning customers

    A verified person joins another business

    • The person decides which details move, one share at a time.
    • A business can state the minimum it accepts, such as a review approved by a person, or a verification not older than a set number of days.
    • If the saved verification falls short, the request is not offered and the business can run its own verification.
    ID Wallet documentation
  2. Age and country checks

    Share only what a check needs

    • A business can ask for “age over 18” instead of the birth date.
    • Document country, type and expiry can be asked for separately.
    • Nationality is shared only with a stated purpose and a tick.
    What a business receives
  3. Businesses on both sides

    One business can save and ask

    • A business that verifies people can offer to save the result; a business that wants verified details can ask for them.
    • Each side is switched on separately, per business, and neither is on by default.
    Who it fits

Data protection

What is saved, and what is not

Facts about the designed wallet. Notices, terms and other legal documents for the wallet are being finalised, and nothing here replaces them.

  • Details that can be saved

    Given and family name, birth date, nationality, document country, type and expiry, and how the verification was checked. Nationality is shared only with a stated purpose and a tick.

  • Not saved or shared

    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.

  • Passkey check on the device

    The passkey check happens on the person's device. Noxtica does not receive the fingerprint or face used to unlock it.

  • Not used for other purposes

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

Limits

  • Early Access. Not generally available, not self-serve, and not open yet. No service level and no date is promised. Businesses will need to accept wallet-specific terms before taking part; those terms are being finalised.
  • 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. A share is not an approval: the receiving business makes its own decision.
  • 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. The passkey check happens on the person's device; Noxtica does not receive the fingerprint or face used to unlock it.

Scores, reasons and verdicts are probabilistic estimates, not statements of fact. Your team makes every decision. Read the disclaimer

FAQ

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: 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.

Next steps

Next steps

  1. Try

    What the wallet does, who it fits and where it stops.

    Read the documentation
  2. Learn

    The wallet extends Identity Verification. Read how a verification works first.

    Identity Verification
  3. Talk

    Early Access has not opened yet. Nothing here is a commitment on scope or timing.

    Contact us about Early Access