ID connector

Support every certified wallet and ID

The ID Connector makes your services wallet-ready and eIDAS 2.0 compliant: one interface to every certified European wallet, and to every other ID. When every ID works, anyone can become your customer, wherever they are and whatever they hold.

Test the ID Connector
See how it works

Every ID in.
One verified result out.

Today, every system builds every ID integration alone: one for each wallet, each eID scheme, each document check. The ID Connector replaces that with one verifier, one connection, three steps.

Your customer shows an ID

Whatever they hold: an EUDI wallet, a government eID, a bank login, a mobile driving licence or a physical document. Any of them works.

We check it with the party that issued it

Is the proof genuine, is it still valid, does it really belong to this person? The connector checks each of these with the issuer itself. The answer comes back with a level of certainty attached: substantial or high.

Your systems get one simple answer

One answer, in the same format every time. Your business process acts on it: a customer onboarded in one session, or access granted to a patient record. Whatever ID was shown, the result reads the same.

Every ID speaks a different language. We speak them all.

Behind every ID sits its own protocol: 27 national wallet implementations on the European standards, eID schemes, bank protocols, the ISO standard for driving licences, chip reads for physical documents. That translation work is the hard part of identity, and exactly the part we take off your hands. Your systems talk to one interface, OpenID Connect, the one they already know. We carry every protocol behind it, including the ones that don't exist yet.

Six benefits unlocked by a single connector

Each one covers work that a relying party would otherwise carry itself.

Reach every wallet and every ID from one integration

Connect the business process once. Every wallet certified after that comes through the same interface. So does every other ID the connector supports: business wallets, eIDs, bank logins and document reads.

Stay current as the framework develops

We track the eIDAS 2.0 implementing acts, the Architecture & Reference Framework and wallet protocols. As requirements evolve, updates ship through the connector so your integration stays current.

EUDI Wallet integration, handled

To accept EUDI Wallets, relying parties must be registered, authenticate to the wallet with valid certificates, request only data covered by their registration, and validate the identity data and attestations they receive. The ID Connector handles EUDI Wallet acceptance through a single integration with your existing systems.

Run it on-premise or as a service

Run it as a managed service, in your private cloud, or inside your own estate. Containerised, with HSM and keystore integration for keys that must stay under your control.

Embed it in your own interface

The flow runs under your brand, on your domain and inside the process your users already know. Build your own front end with the API, or use the white-label component.

Keep control of what you accept

You decide which wallets you accept, which attributes you ask for and which assurance level each process requires. Configured per business process, changed without a release. Every request stays bound to the purpose you registered.

The ID verifier in detail

Wallets and sources

  • Certified EUDI Wallets, all member states

  • Non-certified and business wallets

  • A wallet carrying your brand

  • DigiD and notified eID schemes

  • Bank login

  • NFC document read with liveness

  • Population register data

  • New sources connected on request

Trust & accountability

  • Relying-party registration under Article 5b

  • Relying-party access certificates

  • Wallet unit attestation checks

  • Revocation and status lists

  • Requests bound to registered purpose

  • DPA and sub-processor agreement per source

  • End-to-end audit trail per request

  • Supports your Wwft and GDPR obligations

Delivery & operations

  • Substantial and High assurance

  • Normalised result across every source

  • Automatic fallback between routes

  • White-label in your environment

  • Uptime and response by SLA tier

  • Containerised, or as a service

  • HSM and keystore integration

  • Sandbox with sample data

Standards

  • OpenID4VP and OpenID4VCI, HAIP profile

  • SD-JWT VC

  • ISO/IEC 18013-5 and -7 (mdoc, mDL)

  • DCQL credential queries

  • ETSI signature formats

  • EU trusted lists

  • Attribute mapping across sources

  • REST API and SDKs

One connection enables
three use cases

Each product runs on the same verifier and returns the same response format: the attributes you requested, who signed each one, the assurance level reached, and a reference to the logged request. One schema, so a journey built once reads them all.

PID

Identification

Attributes arrive signed by the party that issued them. Name, date of birth and address arrive as attributes, at the level of assurance the journey requires.

Explore identification

SCA

Login and authentication

Returning customers authenticate with the wallet they already carry. The key stays on their device, and the identity is the same one that opened the account.

Explore login and authentication
AES / QES

Signing

A qualified signature requires an identity verified at high assurance. Once that check is complete, the signature is applied in the same session.

Explore signing

Test-run the ID connector in your business process

Choose a business process and see exactly what a live EUDI Wallet sends to your systems through the ID Connector.

Request a demo
Get in touch