Skip to main content

About iDIN

iDIN is an eID offered by Dutch banks (referred to as iDIN issuer banks). It allows consumers to securely use their bank's login method to identify themselves, log in and confirm their age on the websites of other organisations.

iDIN is directed by Currence and is a collaboration between all major Dutch banks to use the familiar authentication process of online banking in order to provide major eID coverage to the Dutch market.

iDIN enables natural persons, who have been checked against the requirements of the the Anti-Money Laundering and Anti-Terrorist Financing Act (Wet ter voorkoming van witwassen en financieren van terrorisme - Wwft), to provide your organisation with their personal information, through a channel designed for this purpose by their bank.

Use cases​

When you integrate with iDIN, you can choose among the following use cases:

  • Identification and onboarding of new end-users.
  • Login of returning end-users.
  • Age verification.
  • Electronic signing of documents (feature available on request).

The above use cases are based on Issuer-issued credentials and return distinct data attributes. For a complete list of available attributes and response examples, see the Attributes reference page.

Your agreement with Signicat

Note that each use case corresponds to a separate billing plan with Signicat.

Features​

iDIN is designed to offer the following features:

  • eIDAS Substantial Level of Assurance (LoA).
  • Checks for natural persons against the Anti-Money Laundering and Anti-Terrorist Financing Act (Wwft, in Dutch).
  • Targeted authentication with a mobile app where the end-user has full control over their information.

To learn how to apply these features in your integration, get started with the Setup of iDIN guide.

iDIN QR code flow

Signicat supports the iDIN QR code flow for point-of-service identification. Learn more in the iDIN QR code flow documentation.

User flows​

User flows outline the step-by-step process that users follow during authentication and identification with iDIN.

On the web​

Typical flow when an end-user authenticates with iDIN on web:

  1. The end-user selects iDIN as the authentication method.
  2. The end-user chooses their issuer bank.
  3. The end-user authenticates in one of two ways:
    • In the same browser.
    • By scanning a QR code with their banking app and completing the transaction in the app.
  4. The web browser retrieves transaction result and displays it.

On mobile​

Typical flow when an end-user authenticates with iDIN on a mobile device:

  1. The end-user selects iDIN as the authentication method.
  2. The end-user chooses their issuer bank.
  3. The end-user authenticates in one of two ways:
    • The mobile browser.
    • The banking app installed on their phone.
  4. The end-user returns to the mobile browser, where the result is displayed.

QR code flow​

The user flow for iDIN QR code flow for point-of-service identification is different from the above examples. Learn more in the iDIN QR code flow documentation.

Using iDIN with eIDVs​

Electronic identity document verification (eIDV) help you perform identity verification by scanning and reading the data on ID documents. Using eIDVs simplifies the onboarding process of new customers, shares reliable data and makes it easy for returning users to log in. eIDVs also ensure that European regulations and legal requirements are met.

Benefits of using iDIN with eIDVs
  • Comply with European regulations and legal requirements (like Wwft).
  • Provide a High Level of Assurance (LoA).

If you need to meet a level of security higher than iDIN alone provides, you can add an extra layer of verification with Signicat eIDV services. This applies when you require more personal data than iDIN provides, or if an additional check of an identity document is required by law, like Wwft in the Netherlands.

Support​

If you have any questions, you can contact us by creating a support ticket in the Signicat Dashboard.

Relevant sources​

On this page