Skip to main content
Wallet sign-in is one of the three ID Verification methods. The user signs in with a digital identity they already hold — a national eID or a bank identity — and that provider shares a signed set of attributes with Didit. The result carries the assurance tier cryptographic: an identity provider authenticated the person and signed the attributes it returned. That is all the tier claims. It is not a ranking against the other two tiers — they describe different evidence, not more or less of the same thing — and how long a sign-in takes is the wallet’s own flow, which Didit neither controls nor promises.
No wallet is live in production yet. The launch switch is off there, so every wallet below reads Coming soon, cannot be enabled on a workflow, and is not offered to end users — whatever a wallet’s own row would otherwise say. The table is the roadmap, not today’s capability. Talk to your account team about being in the first cohort.

What the user does

  1. Picks their country in the ID step and chooses a wallet from the ones you accept.
  2. Signs in with that wallet, the way they sign in to their bank or their government portal.
  3. Approves sharing their identity attributes with you.
  4. Comes back verified.
Same-device sign-in hands the user to the wallet app and returns them to the verification flow when they are done. Cross-device sign-in shows a QR code on the desktop screen that they scan with the phone holding the wallet. Both are offered where the wallet supports them; the user picks. A started sign-in stays valid for a limited window (10 minutes by default). After that the user has to start it again.

Wallets are an accept-list

wallet.providers is the list of wallets a country may offer. It is not a ranking: the order you send carries no meaning, is normalised into catalog order on save, and the end user chooses from whatever you accepted. Enable one wallet or every wallet in a country — the choice is theirs. The API rejects a workflow that enables a wallet the catalog does not offer in that country, or one that is still Coming soon.
Every wallet’s attribute list below includes a signed assertion. Didit verifies that signature and reports the verdict as wallet_verification.signature_valid on the session; the assertion itself is not handed back, so there is no reference to fetch or store. The On the session column says which of the two you get for each attribute.

Supported wallets

Availability is served by the capability catalog, not hand-maintained here. Coming soon means the wallet is visible in the console and cannot be switched on yet; it carries no committed date. Prices marked On request are not published yet — wallets are priced per wallet and quoted by your account team.

Level of assurance

Every wallet asserts a eIDAS level of assurance — low, substantial or high — and Didit records the level the wallet actually asserted on the result, not the level the catalog hoped for. If the wallet returns a weaker level than the one that was requested, the sign-in fails rather than quietly downgrading. Check wallet_verification.level_of_assurance on the session when your compliance rules depend on it.

Per-wallet reference

MitID

mitid · Denmark · Coming soon Attributes requested: Name · Date of birth · CPR alias (pseudonymised)

BankID

bankid_se · Sweden · Coming soon Attributes requested: Name · Personal number

BankID

bankid_no · Norway · Coming soon Attributes requested: Name · Date of birth · National identity number

Vipps

vipps · Norway · Coming soon Attributes requested: Name · Date of birth · National identity number

Buypass ID

buypass · Norway · Coming soon Attributes requested: Name · Date of birth · National identity number

itsme

itsme · Belgium, Luxembourg, Netherlands · Coming soon Attributes requested: Name · Date of birth · National register number

iDIN

idin · Netherlands · Coming soon Attributes requested: Name · Date of birth · Address

Finnish Trust Network

ftn · Finland · Coming soon Attributes requested: Name · Personal identity code

Personalausweis

personalausweis · Germany · Coming soon Attributes requested: Name · Date of birth

Freja eID

frejaid · Sweden · Coming soon Attributes requested: Name · Personal number

UAE PASS

uae_pass · United Arab Emirates · Coming soon Attributes requested: Name · Emirates ID number · Nationality · Portrait

gov.br

govbr · Brazil · Coming soon Attributes requested: Name · CPF

OneID

oneid · United Kingdom · Coming soon Attributes requested: Name · Date of birth

GOV.UK Wallet

govuk_wallet · United Kingdom · Coming soon Attributes requested: Name · Date of birth · Portrait

Smart-ID

smart_id · Estonia, Latvia, Lithuania, Belgium · Coming soon Attributes requested: Name · Personal identification code

Mobile-ID

mobile_id · Estonia, Latvia, Lithuania · Coming soon Attributes requested: Name · Personal identification code

Bank iD

bankid_cz · Czechia · Coming soon Attributes requested: Name · Date of birth

MojeID

mojeid · Czechia · Coming soon Attributes requested: Name · Date of birth

Diia

diia · Ukraine · Coming soon Attributes requested: Name · Date of birth · Portrait

FranceConnect

franceconnect · France · Coming soon Attributes requested: Name · Date of birth

Auðkenni

audkenni · Iceland · Coming soon Attributes requested: Name · Kennitala

EUDI Wallet

eudi · 30 EU/EEA member states · Coming soon Attributes requested: PID - person identification data

Failure and fallback

Anything other than verified follows the country’s wallet.on_failure switch: fallback_to_document sends the user to document capture, decline ends the session with a declined ID Verification. fallback_to_document with document capture disabled for that country declines instead, because there is nowhere to fall back to. Only a completed sign-in is billed. Abandoned, cancelled, timed-out and failed sign-ins cost nothing.

What lands on the session

attributes holds exactly what that wallet shared, keyed the way the per-wallet table above lists it. portrait is present only for the wallets that share one. signature_valid is the result of validating the signed assertion the wallet returned. It is true on a completed sign-in: an assertion that does not validate fails the sign-in and follows wallet.on_failure instead of producing an approved result. Full field types are in the ID verification data model.

Configuring wallets

Enable at least one wallet when wallet.enabled is true, or the save is rejected. The full reference is in Workflow feature configs.