For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

For the complete documentation index, see llms.txt

About itsme®

How it works​

itsme® allows you to securely identify end-users digitally with validated attributes.

Through Signicat, you can implement itsme® in your application and provide your end-users with the possibility to identify and/or authenticate themselves through their trusted bank environment.

Itsme® uses multi-factor authentication and each itsme® action requires consent from the end-user. These features allow the end-user to decide what data to share and with whom.

Geographic coverage​

itsme® is an eIDAS-notified identity provider in Belgium. While the scheme originated in Belgium, it is now available in many countries in Europe.

itsme® has millions of users in the Belgium market. In other countries, adoption of itsme® is limited but increasing steadily.

To discover supported documents and coverage throughout Europe for itsme®, visit the official coverage page at https://www.itsme-id.com/coverage.

Process flow​

A digital identity flow with itsme® consists of the following steps:

  1. The end-user visits your website and proceeds to onboard/authenticate through itsme®.
  2. Your backend sends a request to the Signicat platform to trigger an itsme® process for the end-user.
  3. The end-user is redirected to itsme®, where they must scan the QR code displayed in the itsme® UI using the itsme® mobile app. On a mobile device, the itsme® app opens directly without the need to scan a QR code.
  4. In the itsme® mobile app, the end-user must consent to sharing their data. After consenting, the end-user is redirected back to your website.
  5. Signicat then retrieves a confirmation of a successful transaction and returns the attributes to you.

The following video shows an example of an identity verification flow with itsme®:

itsme® demo

Note that itsme® offers separate services to address different use cases for digital identity. This means that for each itsme® service, you need to consider the following variants:

  • The end-user follows a distinct UX flow.
  • You need to tailor your request to Signicat.
  • The end-user data you can receive in return varies per itsme® service.

itsme® services​

The itsme® scheme supports different digital identity scenarios. Each scenario corresponds to an itsme® service. Signicat supports the following itsme® services:

  • Authentication: Allows you to authenticate returning end-users. Use this to log in your end-users already registered with your platform.
  • Identification: Allows you to identify and onboard new end-users, access their verified data and sign documents with Advanced Electronic Signature (AES).
  • Qualified signature: Allows you to sign documents electronically with Qualified Electronic Signature (QES) (this is an advanced configuration only available on request).

To determine which service to use when you verify the end-user's identity, you need to specify appropriate attributes in your request to Signicat. Learn more about how to trigger a specific itsme® service in the Attributes reference documentation.

UX flows and services

Note that every itsme® service leads to a distinct UX flow for the end-users and requests different personal information.

Level of Assurance (LoA)​

The European Union (EU) officially recognised itsme® as a reliable means of identification at a high Level of Assurance. Therefore, connecting to itsme® through Signicat always leads to processed with High LoA.

User data​

The itsme® Identification service provides the following user information (note that other itsme® services return less information):

  • First name(s)
  • Family name
  • Sex
  • Date of birth
  • Email address*
  • Phone number
  • (Legal) address*
  • Postal code*
  • City*
  • Country*
  • Locale*

Additional protected information​

To obtain additional data attributes, you must request them to an onboarding manager before you start integrating with Signicat. For example, access to the Belgian national identification number is subject to legal restrictions that require you to justify the purpose. Additional attributes you may request are:

  • Place of birth
  • eID card number (the eID card serial number)
  • National identification number (in Belgium: "Rijksregisternummer")
  • Nationality*
  • Issuance locality*
  • Validity of the eID card*
  • eID picture* (portrait picture of the cardholder)

* itsme® does not guarantee the availability of these attributes for all end-users.

Note

Data availability varies depending on the type of account you are using. These are:

  • In a sandbox account, you can test your integration with all the available attributes.
  • In a production account, certain attributes may be restricted by GDPR regulations or subject to specific legislation. In such cases, you must apply for additional authorisation.

For additional information, contact the Signicat onboarding team.

Subject ID and logins​

The itsme® Authentication service only returns a unique ID (know as subject ID) for a specific end-user. To verify an end-user across recurring authentications, you need to match the new unique ID with the unique ID obtained from a previous itsme® identity verification process. Therefore, the subject ID acts as a way to log in the end-users when they return to your application.

For an overview of all attributes and claims for each itsme® service, read the Attributes reference documentation.

National identity number (NIN)

The national identity number (NIN) is only available for individuals with a document issued by the Belgian government.

Note that itsme® does not return the NIN for citizens of other countries. However, you can still retrieve information about their ID document, such as document number, expiration date and document type.

Here is a list of useful references itsme® concepts:

Next steps​