About iDIN

iDIN is a Dutch eID scheme directed by the Dutch Payment Association (BVN, Betaalvereniging). It is a collaboration between all major Dutch banks to leverage the familiar authentication process of online banking in order to provide major eID coverage to the Dutch market.

Product description


Acquirer The bank of the merchant (or the bank with which the DISP has an agreement)
Consumer The end-user
DISP Digital Identity Service Provider
Issuer The bank of the consumer
Merchant The service provider

Use case

The consumer visits the merchant website and proceeds to log in with iDIN. The merchant redirects to Signicat and Signicat displays a list of banks that the end-user can choose from. The end-user chooses one of the listed banks and authenticates. Signicat then retrieves a confirmation of a successful authentication in addition to the requested end-user attributes and maps the response to a SAML or OIDC response and redirects back to the merchant.

Flow diagram

Conceptually, iDIN is based on the four-corner model analogous to the IDEAL payment scheme:

In the figure:

  • CONSUMER is the End-User
  • MERCHANT is the service provider
  • DISP (Digital Identity Service Provider) is an optional intermediary part between the MERCHANT and the ACQUIRER
  • ACQUIRER is the bank of the MERCHANT, or the bank with which the DISP has an agreement
  • ISSUER is the bank of the CONSUMER

Signicat enters the iDIN scheme as a DISP, using one or more of the dutch Banks as the acquirer.


Different attributes are available to the merchant when authenticating their users with iDIN. To specify which attributes are relevant, please contact Signicat Service Desk, at The following classes are available:

address gender
ageRelated name
consumerId telephone


The BSN attribute is no longer available through iDIN. To retrieve a Dutch BSN, the Signicat DigiD method must be used. See more about DigiD here: DigiD.


No iDIN specific certificates are needed.

Graphical customization

iDIN generates a form with a dropdown of banks to choose from. This form can be added to an iFrame and used as it is and has no styling by default.

Signicat support will help out with the requirements regarding merchant usage and presentation.

Optionally, Signicat’s standard graphical profile can be used for styling. See this page for more info: Graphical adjustments and customization.


Test information

Signicat offers 24/7/365 free access to the preproduction environment,

Starting a transaction in preproduction will result in the following “banks” being available in the issuer list:

The WL Issuer SIM iDIN RABO INT and the Success “banks” will produce successful authentication results with the requested attributes in the response. The other options will produce errors according to the status codes in the dropdown list.

You will not be able to use production bank credentials for testing purposes, however Signicat has built functionality to provide custom test users. If you want to add custom test users to your service, please contact us at The available custom test users and their attributes are as follows:

    "Marnick van de Braak": {
        "urn:nl:bvn:bankid:1.0:consumer.transientid": "TRANS0123456789",
        "urn:nl:bvn:bankid:1.0:bank.deliveredserviceid": 2
    "Martin Henken": {
        "urn:nl:bvn:bankid:1.0:consumer.bin": "NLRABO0000000001",
        "urn:nl:bvn:bankid:1.0:bank.deliveredserviceid": 16384
    "Eser Cairo": {
        "urn:nl:bvn:bankid:1.0:consumer.bin": "NLRABO0000000002",
        "urn:nl:bvn:bankid:1.0:consumer.legallastname": "Cairo",
        "urn:nl:bvn:bankid:1.0:bank.deliveredserviceid": 20480
    "Ünal Roukens": {
        "urn:nl:bvn:bankid:1.0:consumer.bin": "NLRABO0000000003",
        "urn:nl:bvn:bankid:1.0:consumer.legallastname": "Roukens",
        "urn:nl:bvn:bankid:1.0:consumer.dateofbirth": "19750725",
        "urn:nl:bvn:bankid:1.0:bank.deliveredserviceid": 20928
    "Armand van Binsbergen": {
        "urn:nl:bvn:bankid:1.0:consumer.bin": "NLRABO0000000004",
        "urn:nl:bvn:bankid:1.0:consumer.legallastnameprefix": "van",
        "urn:nl:bvn:bankid:1.0:consumer.legallastname": "Binsbergen",
        "urn:nl:bvn:bankid:1.0:consumer.18orolder": false,
        "urn:nl:bvn:bankid:1.0:bank.deliveredserviceid": 20544
    "Theodoor Sijbers": {
        "urn:nl:bvn:bankid:1.0:consumer.bin": "NLRABO0000000004",
        "urn:nl:bvn:bankid:1.0:consumer.legallastnameprefix": "van",
        "urn:nl:bvn:bankid:1.0:consumer.legallastname": "Binsbergen",
        "urn:nl:bvn:bankid:1.0:consumer.street": "Utrechtplein",
        "urn:nl:bvn:bankid:1.0:consumer.houseno": "127",
        "urn:nl:bvn:bankid:1.0:consumer.postalcode": "5709DK",
        "": "Helmond",
        "urn:nl:bvn:bankid:1.0:bank.deliveredserviceid": 21504
    "Anders Notten": {
        "urn:nl:bvn:bankid:1.0:consumer.bin": "NLRABO0000000005",
        "urn:nl:bvn:bankid:1.0:consumer.legallastname": "Notten",
        "urn:nl:bvn:bankid:1.0:consumer.intaddressline1": "Vagnvägen 76",
        "urn:nl:bvn:bankid:1.0:consumer.intaddressline2": "45678 Ballefjongberga",
        "": "SE",
        "urn:nl:bvn:bankid:1.0:bank.deliveredserviceid": 21504
    "Martha de Goedbloed-Stokkink": {
        "urn:nl:bvn:bankid:1.0:consumer.bin": "NLRABO0000000006",
        "urn:nl:bvn:bankid:1.0:consumer.initials": "GS",
        "urn:nl:bvn:bankid:1.0:consumer.legallastnameprefix": "de",
        "urn:nl:bvn:bankid:1.0:consumer.legallastname": "Goedbloed",
        "urn:nl:bvn:bankid:1.0:consumer.preferredlastname": "Goedbloed-Stokkink",
        "urn:nl:bvn:bankid:1.0:consumer.partnerlastname": "Stokkink",
        "urn:nl:bvn:bankid:1.0:consumer.dateofbirth": "19750726",
        "urn:nl:bvn:bankid:1.0:consumer.gender": 2,
        "": "",
        "urn:nl:bvn:bankid:1.0:consumer.telephone": "+31666867727",
        "urn:nl:bvn:bankid:1.0:bank.deliveredserviceid": 20950

In order to fetch the attributes, you can use the following OIDC scopes:

  • profile
  • address
  • phone