What eIDAS Pro does

eIDAS Pro answers one question for a merchant's checkout: is this customer old enough, is this customer in the right country, or both? It returns that answer by routing a verification request to an electronic identity method, rather than asking the customer to type in a birth date or upload a document.

What it verifies

The verification API accepts three request types — age, country, and both — at the request-validation level:

• Age — is the customer at least a given age (for example, 18)?
• Country — is the customer's verified country of residence or nationality one your store allows?
• Both — age and country, in a single session.

/api/config's supportedVerificationTypes tells you which of these a given deployment can actually deliver — read it rather than assuming all three work. The currently implemented path — bank-identity methods delivered through a broker, described below — implements age verification only, so supportedVerificationTypes lists age once a broker method is configured there, and is empty when none is. Requesting country or both through that path is rejected rather than silently downgraded. Country-based verification is not available through any path yet.

Regardless of which type is requested, the response is a pass/fail decision, never a raw attribute dump — see what this deliberately does not do below.

Which identity methods are live today

No verification method is enabled in every deployment by default. Availability depends entirely on which deployment you're integrating against and which broker credentials are configured for it. GET /api/config → supportedMethods is the authoritative, live answer for a given deployment: an empty array means no method is configured yet there; a method's key (for example idin) appears only once its credentials are live for that deployment. Always read this field rather than assuming a particular method is enabled.

Bank-identity methods — iDIN (Netherlands), itsme (Belgium), and others — route through a broker integration when their credentials are configured. This broker path is the one described above, and it is age-only regardless of which bank-identity method is used.

EUDI wallet verification is on the roadmap. It is not a current capability, and no deployment or configuration change makes it one today. The production code path for the EU Digital Identity Wallet method (eudi) is intentionally disabled unconditionally until the surrounding regulatory and technical prerequisites are in place. Treat EUDI wallet support as a future addition, not something to plan a launch date around.

Coverage

GET /api/config reports:

• 32 supported countries — the 27 EU member states plus Iceland, Liechtenstein, Norway, Switzerland, and the United Kingdom.
• supportedVerificationTypes — exactly what the deployment can deliver today: empty while no method is configured there, age once a broker method is (see above for why country/both are not there yet).

Always call /api/config for the deployment you're integrating against rather than assuming a fixed answer; supported methods and supported verification types are expected to grow together as broker credentials and new paths are added.

Who it is for

eIDAS Pro is built for online merchants who need to gate a purchase or a page behind an age or country check, most commonly for age-restricted goods (alcohol, tobacco, vaping products, gambling) or geo-restricted offers. It ships as:

• A WooCommerce plugin for WordPress stores.
• A Shopify app.
• A JavaScript widget for any other stack — a store built on a custom platform, a headless frontend, or anything without a dedicated plugin.

All three talk to the same verification API, so the logic and the data you receive back are identical regardless of which integration you use, and regardless of which verification method is enabled for your deployment.

What this deliberately does not do

eIDAS Pro is not an identity verification dossier. A completed session returns a session status plus two booleans — whether the customer verified at all, and whether the specific threshold you requested was met — and nothing else. It does not return a country code, a date of birth, a name, a document number, an address, or any other personal attribute, even when that attribute is the thing you asked the customer to prove; the API is designed to answer only "did this pass," never "what is this person's data." It also does not retain identity documents or biometric data at any point. If your use case needs a full identity profile rather than a narrow pass/fail check, eIDAS Pro is the wrong tool.