iDIN Merchant Implemention Guide (EN)

  • Push the icon with three dots to the upper right

  • Choose "Export to PDF"

  • Wait until the PDF Export is done

  • Push Download to download the PDF

EN / NL

Terms and conditions

Terms and conditions for provision of the iDIN Merchant Implementation Guidelines:

  • Currence Services BV (also referred to as ‘Currence’) provides these iDIN Merchant Implementation Guidelines to Merchant Banks that distribute it to (potential) Merchants and Digital Identity Service Providers (DISPs) to enable them to implement iDIN;

  • Currence reserves the right to deny access to the iDIN Merchant Implementation Guidelines to (potential) Merchants and DISPs on reasonable grounds, in consultation with the Merchant Bank with which the Merchant/DISP has a contract;

  • These Implementation Guidelines are explicitly and exclusively provided for the purpose mentioned above, and no other use is permitted. No rights can be derived from the information provided in this document or the accompanying notes. Currence is in no way liable for the consequences of later changes to the iDIN Standards or the iDIN Merchant Implementation Guidelines. If banks or other interested parties take decisions and/or make investments on the basis of the information that they obtain via the iDIN Merchant Implementation Guidelines, Currence accepts no liability for this in any way;

  • These implementation Guidelines are based on the information in the iDIN Standards documents. In the event of any discrepancy between the iDIN Merchant Implementation Guidelines and the iDIN Standards documents, the text in the iDIN Standards documents prevails.

For any questions concerning this document or requests for further information, please contact your Bank or DISP. 

Contents


1. General Introduction 

 

1.1 Target audience

This document is intended for Merchants that want to connect to iDIN via their Acquirer. It provides a detailed description of all messages that are exchanged between the Merchant and the Routing Service of his Acquirer. The messages that are exchanged between the Routing Service of the Merchant’s Acquirer and the Validation Service of the Consumer’s Issuer are not of importance to the Merchant, and therefore will not be discussed in this document unless they have specific relevance.

This document is not Acquirer specific, which means that only generic specifications are mentioned in this guide. Information concerning Acquirer specific connections that are not standard and assistance that is provided by Acquirers to connect to iDIN are not part of this guide. Please contact your Acquirer for any information or support on an Acquirer specific connection or implementation.

To further support Merchants, Digital Identity Service Provider (DISPs) and Signing Service Providers (SSPs), software libraries have been developed in .NET, PHP and Java. Software libraries can be found on github.com (via https://www.idin.nl/softwarelibraries/) or you can contact your Acquirer about this for more information To receive updates on the software libraries please subscribe on github.com.

1.2 Document structure

The document has the following structure:

  • Chapter 2: Introduction to iDIN and all parties involved in the process;

  • Chapter 3: Introduction to the various messages exchanged within the scope of iDIN and the overall structure of the exchanged messages;

  • Chapter 4: Overall message formats;

  • Chapter 5: Data dictionary: All parameters that are relevant to the Merchant within the iDIN environment;

  • Chapter 6: Directory protocol: Providing a list of participating Issuer banks;

  • Chapter 7: Transaction protocol: Requesting consumer authentication/attributes;

  • Chapter 8: Status protocol: Receiving consumer authentication/attributes;

  • Chapter 9: Error handling;

  • Chapter 10: Security and certificates;

  • Chapter 11: Presentation of iDIN on the Merchant’s website.

1.3 Other references

Title

Version

Issued by

Title

Version

Issued by

AES, FIPS 197/ SO/IEC 18033-3

-

FIPS/ISO

Base16, Base32, and Base64 Data Encodings
https://tools.ietf.org/html/rfc4648

Oct 2016

Network Working Group

Base64 Content-Transfer-Encoding
http://tools.ietf.org/html/rfc2045iDxsection-6.8

November 1996

Network Working Group

GUIDELINES ON ALGORITHMS USAGE AND KEY MANAGEMENT
https://www.europeanpaymentscouncil.eu/document-library/guidance-documents/guidelines-cryptographic-algorithms-usage-and-key-management-0

Version 1.1 approved 23 February 2009

EPC

ISO 9362, 8901 Standard

2014

ISO

Multilingual European Subset 2 (MES-2)
Unicode.org
http://www.utf8-chartable.de/unicode-utf8-table.pl

15 April 2000

CEN

NEN 1888_2002, NEN 5825_2002

2002

NEN

Open SSL Library http://www.openssl.org

March 2015

OpenSSL

Security Assertion Markup Language (SAML) Core

2.0

OASIS

TLS Protocol version 1.1
http://www.ietf.org/rfc/rfc4346.txt

1.1, April 2006

IETF

TLS Protocol version 1.2
http://www.ietf.org/rfc/rfc5246.txt

1.2, August 2008

IETF

XML Signature Syntax and Processing
https://www.w3.org/TR/xmldsig-core/

Version 1.1, W3C Recommendation 11 April 2013

World Wide Web Consortium (W3C)

XML Encryption Syntax and Processing, W3C Recommendation  https://www.w3.org/TR/xmlenc-core/Overview.html#sec-EncryptedData

10 December 2002

World Wide Web Consortium (W3C)

EPC guidelines for country specific information on provision of the CreditorID which is the same legal identifier as the LegalID (https://www.europeanpaymentscouncil.eu/document-library/guidance-documents/creditor-identifier-overview).

latest version

European Payments Council (EPC)

Table 1: References

1.4 Notational conventions

Messages and redirects are printed like this, and data elements are printed like this.

1.5 Definitions of Internet and online banking

In this document there are many references to Merchant and Issuer websites or online environments. To facilitate mobile use of iDIN, these references must be supplemented with ‘..... or mobile website / mobile app’ where appropriate. For every instance where Internet or online related-terminology is used, please interpret this as including the mobile channel. Where mobile use of iDIN leads to specific requirements for iDIN, this is indicated separately in the text.

1.6 Revisions

Version

Description

Release date

Version

Description

Release date

1.00

Initial version

11th of August 2015

1.04

  1. Addition of error handling when the Issuer cannot provide the minimal set of Consumer attributes

  2. Adding the possibility to seperately request the Consumer gender by the Merchant

  3. Clarification on the format of DateTimestamp

Note: No other versions have been published between v1.00 and v1.04. This is due to levelling of the version numbering with other documentation

23rd of October 2015

1.041

  1. Added recommendations for Merchant screens

  2. Update of the standard Consumer error messages

  3. Corrected the format of TransactionID in the Data-dictionary. This ID has 16 digits.

  4. Added some minor clarifications

22nd of January 2016

1.05

  1. Re-arrangement of the Requested- and DeliveredServiceID bits

  2. Included telephone and email attributes

  3. Enhancements and update of the Issuer front end text

  4. Removed Appendix B which contained all possible valid values of RequestedServiceID

  5. Changed minimum TLS version to be used by Merchant to 1.2

  6. Minor corrections and clarifications

30th of September 2016

1.051

  1. Added examples and clarifications to consumer attributes

27th of January 2017

1.053

  1. Added clarifications and more examples in the consumer attributes in Table 13

17th of February 2017

1.06

  1. Added Section 0 to describe how Digital Identity Service Providers should register their Merchants

  2. Added Section 0 to describe the optional deselecting and/or changing of the telephone number and/or email address by Consumers in the Issuer environment.

March 2017

1.07

Changes with respect to the use of LoA2:

  1. The use of LoA2 for iDIN is ceased. Changes have been made to §3.2.2.

Changes with respect to the character set used for consumer attributes:

  1. Changes have been made to §5.4 footnote 6. Consumer initials are allowed to have letter-based characters like ligatures and digraphs (e.g. á, ç, Æ)

Corrections:

  1. Out of scope is removed from §2.2.

  2. Use case is changed into product type throughout the document.

  3. The definition of the level of assurance “substantial” is added to §2.2

March 2018

1.08

Role of DISP/Ondertekendienst (Signing Service Provider (SSP)) is added

Product type iDIN signature is added

May 2018

1.09

  1. Added reference to EPC guidelines in CreditorID which is the same legal identifier als the LegalID

2. added possibility to execute a mobile transaction in Safari View Controler and Chrome Custom Tabs

September 2020

1.1

Added description on display demands for issuer list for iDIN signing

November 2020

Table 2: Revision table

1.7  Changes from previous version

Changes compared to version 1.00

  1. Addition of error handling when the Issuer cannot provide the minimal set of Consumer attributes: Addition of the elements DeliverdServiceID and the 2nd SAML status code in the AcquirerStatusRes that are both used to communicate to the Merchant whether the attributes are delivered conform the minimal set (see Section 5.5). This error handling is described in Section 12.4;

  2. Adding the possibility to separately request the Consumer gender by the Merchant: Added the possibility to request the consumer gender separately (using the RequestedServiceID), instead of being part of the group name attributes. This has impact on the number of valid combinations that can be made with the RequestedServiceID;

  3. Clarification of the use of DateTimestamp (for all fields where DateTimestamp is used, such as the createDateTimestamp): Merchants are allowed to use zero to three decimals after the seconds for DateTimestamp elements in the messages they send to their Routing Service. DateTimestamps in messages from the Routing Service will always contain three decimals behind the seconds. See Table 10 for more information.

Changes compared to version 1.04

  1. Added recommendations for Merchant screens: This is described in chapter 8;

  2. Update of the standard Consumer error messages: This is described in chapter 5;

  3. Format of TransactionID: In the Data Dictionary the TransactionID contained an error which has been corrected in this version. This ID consists of 16 digits; the first four digits are made up of the AcquirerID.

  4. Added some minor clarifications:

    1. In the format description of DateTimestamp in Table 10, clarification is added

      • YYYY must be the calendar year

      • 24-hour notation must be used;

  5. In the description of displaying the last login in Section 0 showing the time is replaced by showing the date and time. The rationale for this requirement has been added;

  6. In Appendix B a column ‘product type’ is added which indicates the product type that belongs to each ServiceID;

  7. In Section 1 a recommendation on the use of TLS has been added: Merchants are advised to use TLS version 1.1 or up. Use of version 1.0 is not recommended because it has become out-dated.

Changes compared to version 1.041

  1. The structure of the bits in the RequestedServiceID and DeliveredServiceID has been re-arranged (see Section 0) to include telephone and email and to make room for (possible) new attributes. The re-arrangement does not have an impact on the numerical values of ServiceIDs, hence it is backwards compatible;

  2. The consumer.telephone and consumer.email attributes are added in Table 13;

  3. Update of Issuer front-end texts that are shown to the Consumer depending on which attributes are requested by the Merchant (see Section 0);

  4. Appendix B has been removed. This Appendix included all the possible RequestedServiceID integer values. With the inclusion of telephone and email address this table would have become too large. The Excel ‘160529A_ServiceID_Calculator’ provided along this Implementation Guidelines provides an easy method to calculate the ServiceID;

  5. In the future out-dated TLS versions are no longer supported by the Routing Service. Therefore, the Merchant must use a minimum version of TLS 1.2 (see Section 1);

  6. Minor corrections and clarifications:

    1. In Section 0 : added that the X509SubjectName element may be included by the Validation Service in the Signature element inside the Assertion;

    2. Added description in Section 3 on the optional use of xsi type definitions inside the AttributeValue elements;

    3. Included the x509 data element in Table 11. The description of this element was missing;

    4. Removed error codes SE2000 and changed error code SE2100 to SE2700. Neither error codes are used in iDIN;

    5. Changed the time of attribute @NotOnOrAfter to be 30 seconds after the time in attribute @IssueInstant (see Table 28). It incorrectly stated it was 40 seconds;

    6. Updated the encryption examples and the unencrypted example messages with namespace declarations. The namespace declarations were not shown in one encryption example and in the unencrypted attributes of the example messages;

    7. The display of the last login by the Merchant to the Consumer in Section 0 has been changed from mandatory to strongly recommended;

    8. Updated the LegalIDs in the example messages with valid check digits.

Changes compared to version 1.05

  1. Added examples and clarifications to consumer attributes

Changes compared to version 1.053

  1. Added Section 0 to describe how Digital Identity Service Providers should register their Merchants. To prevent the name of the DISP in the Issuer screens and to ensure BINs are different for each Merchant DISPs need to register their Merchants in a specific way.

  2. Added Section 0 to describe the optional deselecting and/or changing of the telephone number and/or email

Changes compared to version 1.06

  1. The use of LoA2 for iDIN is ceased as of May 1st All references to LoA2 have been deleted.

  2. Consumer initials are allowed to have letter-based characters like ligatures and digraphs (e.g. á, ç, Æ). This is added to the document.

Changes compared to version 1.07

  1. Description of the role of DISP/ Ondertekendienst (Signing Service Provider (SSP)) is added.

  2. Product type signature is added to the document

Changes compared to version 1.08

  1. Added reference to EPC guidelines in CreditorID which is the same legal identifier als the LegalID

2. added possibility to execute a mobile transaction in Safari View Controler and Chrome Custom Tabs

Changes compared to version 1.09

  1. Added description on display demands for issuer list for iDIN signing.

2 Overview

This chapter gives a description of the general elements of iDIN.

2.1 The four-corner model

The iDIN system is based on the ‘four-corner’ model. Figure 1 shows the roles in this model, along with their mutual primary relationships in the context of iDIN. The roles are those of Consumer, Merchant, Acquirer, Issuer, Routing Service and Validation Service and the Digital Identity Service Provider (DISP)[1]:

  • The role of Consumer is fulfilled by a natural person, holding credentials provided by the Issuer;

  • The role of Merchant must be fulfilled by a legal entity that wishes to identify its Consumers in an authentic manner;

  • The role of Acquirer must be fulfilled by a legal entity, providing iDIN services to its Merchants;

  • The role of Issuer must be fulfilled by a legal entity, providing digital identities and credentials to its Consumers;

  • The role of Routing Service must be fulfilled by an Acquirer or by a third party endorsed and contracted by an Acquirer;

  • The role of Validation service must be fulfilled by an Issuer or by a third party endorsed and contracted by an Issuer;

  • The role of Digital Identity Service Provider (DISP) must be fulfilled by a third party, which is endorsed and contracted by the Acquirer as well as the Merchant.

    • The role of DISP /Ondertekendienst: a DISP certified for iDIN Ondertekenen. Within the iDIN Scheme we refer to such a party "DISP / Ondertekendienst" because it is a special (sub-) form of a DISP. Signing Service Provider (SSP) is used in the external communication and in the remainder of this document.

2.1.1 The relations between these roles

Both contractual and technical relations exist between the roles. These are described below.

Contractual relations:

  • Merchant - Acquirer: The Merchant has a contract with an Acquirer;

  • Consumer - Issuer: The Consumer has a contract with the Issuer. The identity related to this contract is used for identification, authentication, signing and provisioning of attributes of the Consumer;

  • Consumer - Merchant: The Consumer may use iDIN services at the Merchant domain to access the service supplied by the Merchant;

  • Acquirer - Issuer: Bound by a license agreement with the iDIN scheme.

Technical relations:

  • Merchant - Routing Service: The Merchant has a technical relation with the Routing Service. The Routing Service offers the Merchant the possibility of sending iDIN requests to a Validation Service. They exchange messages to this end;

  • Routing Service – Validation Service: The Routing Service and Validation Service have an iDIN solution relationship. They exchange messages in this context;

  • Consumer – Validation Service: The Validation Service offers the Consumer the possibility of using their iDIN towards Merchants, by using the credentials issued by the Issuer.

Figure 1: Four-corner model

2.1.2 Exceptions for DISPs or SSPs

In a model where a Merchant outsources its iDIN activities to a SSP or DISP[1] the contractual relation between Merchant - Acquirer is replaced by the following relations:

  • Merchant – SSP or DISP: The Merchant has a contract with a DISP;

  • SSP or DISP - Acquirer: The SSP or DISP has a contract with an Acquirer.

The technical relation between Merchant - Acquirer is replaced by the following relations:

  • Merchant – SSP or DISP: The Merchant has a technical relation with the SSP or DISP. The SSP or DISP offers the Merchant the possibility of sending iDIN requests to a Routing and Validation Service. They exchange messages to this end;

  • SSP or DISP - Routing Service: The SSP or DISP has a technical relation with the Routing Service. The Routing Service offers the SSP or DISP the possibility of sending iDIN requests to a Validation Service. They exchange messages to this end.

[1] For due diligence reasons, the SSP or DISP may be subject to extra audits

2.2 iDIN services

This paragraph introduces the iDIN services offered to both Merchants and Consumers.

iDIN facilitates the following services:

  • Identification of Consumers based on Issuer issued credentials

  • Age verification of Consumers based on Issuer issued credentials

  • Login of Consumers using Issuer issued credentials

  • Signing of documents by Consumers using Issuer issued credentials

Note: In this document the iDIN process of providing one of the above services is referred to as an iDIN transaction.

The services provided by iDIN can be used by the Merchant, amongst others, to:

  • Set-up new user accounts for Consumers in the Merchant’s domain based on the identification and/or attributes provided by the Issuer;

  • Login of existing users that created their account with iDIN, or connected an existing account with iDIN;

  • Age verification.

  • Signing of documents

The level of assurance for iDIN is “Substantial”. This has been determined in accordance with the iDIN Rules & Regulations and is based on the eIDAS EU Regulation 2015 / 1502. The EU Regulation sets requirements for, among other things, identifying the consumer, the authentication tools and the use thereof. These requirements have been included in the iDIN Rules & Regulations. This roughly corresponds to the older STORK assurance level LOA3, which is still used in this technical standard. The level of assurance doesn’t relate to interoperability or cross border acceptance of iDIN.

2.3 iDIN process

At the Merchant website the Consumer initiates the process by selecting iDIN for authentication/provisioning of attributes and/or signing of documents, and subsequently selects an Issuer from the Issuer list. The Consumer will then be forwarded to his/her Issuer’s secure environment where he/she can continue with the Issuer’s authentication process (based on the credentials that were issued to the Consumer by the Issuer). After successfully authenticating at the Issuer, the Consumer can approve or cancel the iDIN transaction. The Consumer will then be redirected back to the Merchant website. The Merchant receives the requested authentication/attributes and or the consumers' signature if the Consumer has approved the transaction.

2.4 iDIN transaction

The result of an iDIN transaction can be delegated authentication, provisioning of attributes (including age verification), signing of documents or a combination.

2.4.1 Delegated authentication

In an iDIN transaction, the Merchant can request a unique, Merchant-specific persistent identifier (BIN) of the Consumer. This allows the Merchant to link the Consumer session to an already existing user account at the Merchant’s system that contains the same BIN, or offer the option to create a new account for the Consumer when the BIN is not yet present in the Merchant’s system. By approving the transaction, the Consumer consents to logging in at the Merchant’s website.

2.4.2 Providing consumer attributes

In an iDIN transaction, the Merchant can request attributes, possibly used in the context of signing a document, of the Consumer. To this end, at the Issuer website the Consumer explicitly consents to provide the requested attributes to the Merchant. Attributes cannot be requested (and provided) individually, but only as bundled in one of the three[3] attribute groups that are specified as: name, address and age related. See Section 5.3.1 and Section 5.4 for more details. Consent is always given for all requested attributes as a whole, not per data set or per attribute. However, the Merchant is free to ask the Consumer on its website/application, before initiating the transaction, which attribute groups the Consumer would like to give to the Merchant.

Note: Due to possible movement of Consumers it is advised to Merchant to always check the correctness of the address. Also, when dealing with a delivery, the Consumer might want to deliver to another address then his/her residential address.

Consumer attributes can be requested on a one-time basis, without linking the Consumer session to previous or future sessions, or to an existing user account.  In that case, the Merchant will request and receive a transient identifier (transient meaning temporary), generated by the issuer for this session. In case attribute provisioning is combined with delegated authentication, the Merchant requests and receives the persistent BIN.

The Merchant can easily set up a new account for the Consumer in the Merchant’s domain based on the BIN and attributes provided by the Issuer.

Note that the consumer should always be aware when using iDIN to create a new Consumer account, in order to prevent the Consumer from connecting whilst already having another account at the Merchant. When connecting a Consumer to an existing account, simply matching consumer attributes with the entire database of the Merchant is an erroneous method, because certain Consumers can share the same attributes (e.g. first and last name). First letting the Consumer log in the Consumer to the existing account before connecting the account with iDIN, or connecting with additional unique Consumer information (not provided by Issuer e.g. email address), should counteract this Issue.

2.5 Merchant registration

When registering for iDIN, the Acquirer issues a Merchant.MerchantID and a Merchant.LegalID to the Merchant that is associated with the Merchant.Name. If required, the Merchant also receives a Merchant.SubID to register one or more Merchant.TradeName. This is the case when a Merchant performs iDIN transactions under different trade names. Only the Merchant.MerchantID and Merchant.SubID are relevant to the Merchant, that is, the Merchant only has to use these to fulfil a successful iDIN process. The other identifiers are allocated by the Acquirer and used within the Acquirer-Issuer and Issuer-Consumer domain.

A SSP/DISP must register their Merchants in a specific way. This method is required for four reasons:

  1. To prevent the display of the name of the DISP on the Issuer screens;

  2. To allow a SSP to choose if he is visible to the consumer on the Issuer screens;

  3. To make sure the BIN is different for each Merchant. This is due to reasons of security and enhanced Consumer privacy.

  4. To make sure the SSP is the only entity who can request the serviceID reserved for iDIN signature

To ensure above standing requirements SSP/DISP must register their Merchants at their Acquirer as follows:

  • The MerchantID is registered to the SSP/DISP;

  • Normally, the MerchantName and LegalID are registered to the MerchantID, but in case of a DISP or SSP, who are not visible to the consumer during the transaction process in the Issuer screens, these need to be registered to the SubID;

  • The SSP/DISP must register each Merchant with a new SubID. With the SubID they must be able to have their own MerchantName, LegalID and Tradename (optionally used by Merchants);

  • The MerchantName is registered to the MerchantID of the SSP which is visible to the consumer during the transaction process in the Issuer screens. The TradeName and LegalID are used by Merchants.

  • If the DISP is a contracting DISP (i.e. it does not take care of the technical implementation), the Merchant uses its own iDx signing certificate. The contracting DISP must then also register the certificate of the Merchant for each SubID.

Registration examples are shown in the table below. For SubID 1 through 4 the MerchantID is registered to the Contractual or Full DISP, while the other parameters (LegalID, MerchantName and optional the TradeName) are registered to the SubID. For SubID 5 and 6 the MerchantID is registered to a SSP which is not visible during the transaction process to the consumer in the Issuer screens, the other parameters (LegalID, MerchantName and optional the TradeName) are registered to the SubID. For SubID 7 and 8 the MerchantID and MerchantName are registered to the SSP, which is visible during the transaction process to the consumer in the Issuer screens, only the TradeName and LegalID are registered to the SubID.

MerchantID

subID

Merchant Name

LegalID

Tradename

MerchantID

subID

Merchant Name

LegalID

Tradename

0800123456

1

Energy Inc.

NL69ZZZ123456780000

-

0800123456

2

Insurance GmbH

NL32ZZZ876543210000

Life

0800123456

3

Insurance GmbH

NL32ZZZ876543210000

Car

0800123456

4

PhoneShop B.V.

NL91ZZZ112233440000

-

0900654321

5

Telco B.V.

NL25ZZZ132465870000



0900654321

6

notarissen.com

NL14ZZZ887766550000



0900654321

7

Signing Service B.V.

NL25ZZZ132465870000

Telco B.V.

0900654321

8

Signing Service B.V.

NL14ZZZ887766550000

notarissen.com

Table 3: Registration example for SSPs or DISPs

2.6 Dispute management

In case of a dispute, the Issuer must be able to provide the identity of the Consumer. During such a dispute the following steps must be executed:

  • The Merchant must supply the original SAML iDIN message that holds the Consumer identity to the Merchant’s Acquirer. To ensure the Issuer can read the encrypted attributes, the Merchant must decrypt the AES keys with his private key. The AES keys have to be provided along with the original message;

  • The Acquirer forwards this information to the Issuer, with contact information of the Merchant;

  • The Issuer must use the certificate from the message to verify the electronic signature, thereby establishing the authenticity and integrity of the iDIN message. The Issuer must take into account the need for an application to be able to perform these checks;

  • By using the AES keys provided by the Merchant, it can be easily verified whether these keys are in fact the correct keys;

  • In case a message is authentic, the Issuer must provide Consumer details to the Merchant and/or Consumer directly. This can only be done if the Consumer has given his/her consent;

  • Providing the details has to be done via telephone[4] where:

  • The Acquirer must provide the telephone number of the Merchant to the Issuer;

  • The Issuer must initiate the call to the Merchant/Consumer to prevent misuse.

3 iDIN protocols

This chapter gives a general description of the iDx protocols, which are used as a messaging standard for iDIN.

3.1 Basic technical principles

  • All iDIN processes are initiated on the Merchant website by the Consumer;

  • iDIN uses the iDx standards as a messaging standard. It uses the generic information container in the iDx protocol to embed SAML 2.0 messages for iDIN specific elements;

  • Consumers will be persistently identified using a Bank Identification Number (BIN), see Section 0, which will be Issuer generated (so not shared among Issuers) and unique per Consumer-Merchant combination;

  • A Consumer has only one identity per Issuer, regardless of the number of credentials;

  • Consumer information in messages will be shielded from Acquirers (Routing Service) by means of end-to-end encryption.

3.2 iDx protocols

The iDIN process (request-/response-XML messaging and browser redirects) consists of the following protocols:

  • The Directory protocol: used to retrieve the most recent Issuer list from the Routing Service.

  • The Transaction protocol: the iDIN-transaction process from beginning to end.

  • The Status protocol: used to request the status of a transaction from the Validation Service (via the Routing Service).

  • The Error protocol: used to inform when errors have occurred.

A specific name (letter) has been assigned to identify each message. The following table applies:

Message

Message description

Message

Message description

A

DirectoryReq (Directory Request)

A’

DirectoryRes (Directory Response)

B

AcquirerTrxReq (Transaction Request)

B’

AcquirerTrxRes (Transaction Response)

F

AcquirerStatusReq (Status Request)

F’

AcquirerStatusRes (Status Response)

A’(X),B’(X), F’(X)

AcquirerErrorRes (Error Response)

Redirects:

 

D

Merchant redirects Consumer to Issuer

E

Issuer redirect Consumer to Merchant

Table 4: Message names and description

The sequence of the protocols is shown in Figure 2. In order to retrieve the services provided by iDIN both the Transaction and Status Protocol have to be completed. The Directory protocol is not indicated, because it follows a simple request and response from the Merchant to the Acquirer.

Figure 2: Transaction, Status and Error protocol

3.2.1 Directory protocol

By using the Directory protocol, the Merchant sends a DirectoryReq to the Routing Service. This is a request in XML format to obtain the list of participating Issuer Banks from the Routing Service. The Routing Service will provide this list to the Merchant by sending back the DirectoryRes. The Merchant will show the list of banks, which were sent in the DirectoryRes to the Merchant. The Consumer will choose his bank from this list at the beginning of the iDIN process. The Directory protocol is explained in more detail in Chapter 6.

3.2.2 Transaction protocol

By using the Transaction protocol the Merchant sends an AcquirerTrxReq to the Routing Service, containing the ID of the Issuer Bank chosen by the Consumer, iDIN information (requesting consumer authentication, attributes or age verification) and other transaction details. This message also contains the merchantReturnURL. This URL is used by the Validation Service to redirect the Consumer back to the Merchant’s website when he has completed the iDIN transaction in the Issuer domain. After the Routing Service has received the message from the Merchant the message is send to the Validation Service of the Issuer that was selected by the Consumer (after adding some information which is beyond the scope of the Merchant).

In return, the Validation Service responds with the IssuerTrxRes message that contains amongst others the issuerAuthenticationURL. The Routing Service forwards this issuerAuthenticationURL together with a unique Transaction.TransactionID back to the Merchant in an AcquirerTrxRes.

3.2.2.1  Redirect

The Merchant now redirects the Consumer to the issuerAuthenticationURL, which refers to the page of the online banking portal. This takes the Consumer to his internet-banking environment where he can continue the iDIN transaction (i.e. logging in and approve the transaction).

The Issuer adds Consumer information (consumer authentication, attributes or age verification) to the iDIN transaction which can be later retrieved with the AcquirerStatusReq. The Consumer approves the iDIN request and receives a confirmation from the Issuer. The Consumer is then redirected back to the website of the Merchant via the merchantReturnURL. The entire Transaction protocol and the 2 redirects are described in more detail in Chapter 7.

The Mobile transaction flow is almost identical to the transaction flow in a regular iDIN transaction. The only difference is the redirect to a ‘landing page’ (using the issuerAuthenticationURL) or the Issuers' mobile banking app where the Consumer, using a mobile device, can choose to be redirected to the Issuer’s (mobile) web page or to the Issuer’s mobile banking app (if available). The issuerAuthenticationURL must therefore always be presented to the mobile OS before execution or opened usinSafariViewController or Chrome Custom Tabs.

3.2.3 Status protocol

Finally the Merchant initiates the Status protocol by sending an AcquirerStatusReq message to the Routing Service. The Routing Service will request the transaction status from the appropriate Issuer and returns the status to the Merchant in the AcquirerStatusRes. If all steps in the transaction are successful this status message contains the iDIN consumer authentication, attributes and/or age verification. Chapter 8 contains more detailed information on the Status protocol.

3.2.4 Error protocol

Instead of a regular response to the messages mentioned above, it is also possible that an AcquirerErrorRes is returned. This can be the case if a request (DirectoryReq, AcquirerTrxReq or AcquirerStatusReq) contains an error, or if an error occurs during the processing of the request. The AcquirerErrorRes messages are discussed in Chapter 9.

3.3 SAML V2.0

iDIN uses the iDx standards as a messaging standard. However, it uses the generic information container in the iDx protocol to embed SAML 2.0 messages for iDIN specific elements. This container is only used in the AcquirerTrxReq, AcquirerStatusRes and sometimes in AcquirerErrorRes. For the other messages the container is left empty.

4 iDIN Message format 

4.1 General

This chapter contains a description of the general message structure for the Directory, Transaction, Status, and Error protocol. The subsequent sections will describe the specific fields within the XML messages for each protocol in more detail. A list of the data elements and their format can be found in the data dictionary in Chapter 5.

The following conventions are used to indicate whether a message element is mandatory:

  • Yes The element must occur exactly once;

  • Yes (1..∞) The element must occur one or more (unlimited) times;

  • No The element may be left out or may occur exactly once;

  • No (0..∞)    The element may be left out or may occur more (unlimited) times.

4.2 Character set

  • In all iDIN messages the Unicode character set must be used. Only the MES-2 subset must be supported;

  • Encoding must be used as indicated in the HTTP and XML headers UTF-8 (Unicode Transformation Format);

  • The use of characters that are not part of the Unicode character set will not lead to a refusal of a post, but the character may be changed to a space, question mark or asterisk in transit;

  • The Byte Order Mark (BOM) must not be used. The UTF-8 representation of the BOM is the byte sequence 0xEF,0xBB,0xBF.

4.3 HTTP

  • All messages must comply with the HTTP 1.1 standard, as defined in RFC 2616 of W3C. For more information: http://www.w3.org/Protocols/rfc2616/rfc2616.html;

  • Each XML request message must be sent as the body of a HTTP POST message;

  • Each XML response message must be sent as the body of a HTTP 200 OK message.

The following HTTP header must be used for all messages:

Data element

Mandatory

Explanation

Data element

Mandatory

Explanation

content-type

Yes

Defines how the remainder of the content is to be interpreted.
Must be: text/xml; charset=”utf-8”

Table 5: HTTP header

4.4 XML header

The following XML header must be used for all messages:

Data element

Mandatory

Explanation

Data element

Mandatory

Explanation

version

Yes

Must be: “1.0”

encoding

Yes

Must be: “UTF-8”

Table 6: XML header

4.5 XML namespaces

iDIN uses the iDx standards as a messaging standard. It uses the generic information container (an XML element) in the iDx protocol to embed SAML 2.0 messages for iDIN specific elements. In addition to the namespaces of the iDx messages, several namespaces are declared in the SAML message.

The namespaces for all messages described in this document is as follows:

Namespaces

Namespace declaration in example messages

Namespaces

Namespace declaration in example messages

Namespace for the iDIN iDx messages between the Merchant and Acquirer.

Must be:http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0

xmlns

Namespace for the XML signature syntax.

Must be:http://www.w3.org/2000/09/xmldsig#

xmlns:ds

Namespace for schema related mark-up.

Must be:http://www.w3.org/2001/XMLSchema-instance

xmlns:xsi

Namespace for the SAML 2.0 Assertion which is embedded in the container element of the iDx message.

Must be: “urn:oasis:names:tc:SAML:2.0:assertion”

xmlns:saml

Namespace for the SAML 2.0 Protocol which is embedded in the container element of the iDx message.

Must be: “urn:oasis:names:tc:SAML:2.0:protocol”

xmlns:samlp

Namespace for the XML encryption syntax. This namespace is declared in the container element of the iDx message in, only in the AcquirerStatusReq message for the encrypted XML elements, see 10.3.

Must be:http://www.w3.org/2001/04/xmlenc#

xmlns:xenc

Table 7: iDx namespaces

Namespace declaration can be done in any way allowed by the XML standards (default namespace declaration or namespace qualification/prefixes) with only a few exceptions as discussed in Section 10.3 where all namespace declaration must be present inside the encrypted parts of the message.

4.6 XML Schemas

All messages must be validated against the iDIN, SAML 2.0 and W3C Schemas. The schemas names and locations are shown in the following table:

XML schema

Explanation

XML schema

Explanation

idx.merchant-acquirer.1.0.xsd

Schema for the iDIN iDx messages between the Merchant and Acquirer.

Provided by Acquirer to the Merchant after registration. Also available in chapter 14

xmldsig-core-schema.xsd

Schema for XML signatures.

Available at: http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd#

saml-schema-assertion-2.0.xsd

Schema for the SAML 2.0 assertion which is embedded in the container element of the iDx message.

Available at: http://docs.oasis-open.org/security/saml/v2.0/saml-schema-protocol-2.0.xsd

saml-schema-protocol-2.0.xsd

Schema for the SAML 2.0 protocol which is embedded in the container element of the iDx message.

Available at: http://docs.oasis-open.org/security/saml/v2.0/saml-schema-assertion-2.0.xsd

xenc-schema.xsd

Schema for the XML encryption syntax.

Available at: http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/xenc-schema.xsd

Table 8: XML schemas

5 iDIN data dictionary 

This chapter describes the data elements and ID’s that are used in iDIN.  First, two attributes for all iDx messages are described in Section 5.1. All iDx data elements are described in Section 5.2. Subsequently, in Section 5.3 the iDIN specific data elements are described, which are either located in the SAML message, or differ from the normal iDx formatting. Section 5.4 provides a list of all consumer attributes.

5.1 iDx attributes

The following two attributes are given to the root of each message to ensure proper identification of the correct service and version:

Attribute

Description

Messages

Formatting rules

Attribute

Description

Messages

Formatting rules

version

Indicate the version of the iDIN Service

ALL

Must be: “1.0.0”

productID

Indicates the service used with the iDx format

ALL

Must be: "NL:BVN:BankID:1.0”

Table 9: iDx attributes

5.2 iDx data elements

iDIN relies on the identifiers described in Table 10. If the element must be generated as an input in one of the three request messages (DirectoryReq, AcquirerTrxReq, AcquirerStatusReq) it is indicated in the description in bold.

Name

Description

Messages

Formatting rules

Name

Description

Messages

Formatting rules

Acquirer.AcquirerID

Unique four-digit identifier of the Acquirer within an iDx based product, assigned by the product owner when registering the Acquirer.

A’, B’, F’,

F’(X)

4 digit-number

Country.countryNames

Contains the countryNames in the official languages of the country. Used in presentation of the Merchant to the Consumer on the website, see Section 6.4. In official languages of the country, separated by a ‘/’ symbol (e.g. ‘België/Belgique’)

A’

Max 128 alphanumeric

createDateTimeStamp

The time of creation of a particular request or response. Can also have the form directoryDateTimestamp, statusDateTimestamp and transactionCreateDateTime-stamp but follows the same formatting rules. It is indicated in the messages in Chapter 6-9 which particular time is meant

Generated by Merchant in Requests messages

ALL

ISO 8601

UTC time format (no daylight saving) in format YYYY-MM- DDThh:mm:ss.sssZ e.g. 2015-10-13T14:41:12.123Z

  • Merchants are allowed to use zero to three decimals behind the seconds. DateTimestamp in messages from the Routing Service will always have three decimals after the seconds

  • YYYY is the calendar year

  • hh is 24-hour notation. 12-hour notation must not be used

Error.

consumerMessage

An Acquirer can use this field to include a (standardized) message that the Merchant should show to the Consumer

A’(X), B’(X), F’(X)

See Appendix A: Error codes and cases

 

Error.errorCode

Unique identification of an error occurring within the iDx transaction

A’(X), B’(X), F’(X)

See Appendix A: Error codes and cases

 

Error.errorMessage

Descriptive text accompanying Error.errorCode

A’(X), B’(X), F’(X)

Max 128 alphanumeric

See Appendix A: Error codes and cases

 

Error.errorDetail

Details of the error. The message-generating party is free to determine this information

 

A’(X), B’(X), F’(X)

Max 256 alphanumeric

Error.

suggestedAction

Suggestions aimed at resolving the problem. The message-generating party is free to determine this information

A’(X), B’(X), F’(X)

Max 512 alphanumeric

issuerAuthenticationURL

Contains the issuer authentication URL to which the consumer is sent

B’

Max 512 characters

Issuer.IssuerID

Unique identifier of the Issuer that consists of the international Bank Identifier Code (BIC).

A’, B

ISO 9362

Issuer.Name

Only given in pairs together with the Issuer.IssuerID used in presentation of the Merchant to the Consumer on the website, see Section 9.4

A’

Max 35 alphanumeric

language

This field enables the Issuer’s website or mobile app to select the Consumer’s preferred language (e.g. the language that was selected on the Merchant’s website or mobile app), if the Issuer's website or mobile app supports this.

In case of error, this field enables the Acquirer to select the Error.consumerMessage in the Consumer’s preferred language (see Section 15.2).

If a non-supported or non-existing language is entered, the standard language of the Issuer is used.

e.g. ‘en’ for English, ‘nl’ for Dutch is used

Generated by Merchant

B

ISO 639-1

 

 

Merchant.MerchantID

This is the contract number for iDIN.

The Merchant obtains this ID after registration for iDIN.

A,B,F

10 numeric

Made up of Acquirer.AcquirerID (first four positions) and a unique number of exactly six positions

Merchant.subID

The subID that uniquely defines the name and address of the Merchant to be used for the iDIN. The Merchant obtains the subID from its Acquirer after registration for iDIN.

A Merchant can request permission from the Acquirer to use one or more subIDs. Unless agreed otherwise with the Acquirer, the Merchant has to use 0 (zero) as subID by default (if no subIDs are used).

A,B,F

Max 6 numeric

Number from 0 to and including 999999 in which each value is related to a separate instance registered with the Acquirer. The default value is ‘0’

merchantReturnURL

URL to which the Consumer must be redirected after authentication and/or authorization of the transaction at the Issuer. The URL does not necessarily begins with http:// or https://, it can also start with an app handler e.g. companyname-nl-service://. The protocol part must always be included.

The resource indicated by the URL must be the website or mobile app of the Merchant or a part thereof.

Generated by Merchant

B

Max 512 characters

Merchant.X509

Certificate of the Merchant. Used in the request to express the Merchant’s certificate needed for encryption by the Issuer (excluding the private key)

Never included in the response and placed in the extension element of a SAML AuthnRequest

B

Base64 encoding

Transaction.

entranceCode

An ‘authentication identifier’ created by the Merchant to facilitate continuation of the session between a Merchant and a Consumer, even if the existing session has been lost (e.g. because the cookie expired). It enables the Merchant to recognize the Consumer associated with a (completed) transaction. The entranceCode is sent to the Merchant in the Redirect to Merchant. See Section 10.6 for more information on its use.

Generated by Merchant

B

 

Max 40 alphanumeric

A minimum variation of 1 million is required

Transaction.

TransactionID

Unique 16-digit number within an iDx based product, assigned by an Acquirer. Received in the AcquirerTrxRes. Used to couple a AcquirerStatusReq to a particular response

B’, F, F’

F’(X)

16 numeric

The first four digits of the TransactionID are made up of the AcquirerID

Transaction.status

Status of the transaction: related to whether the transaction has been authenticated/authorized by the Consumer

F’

Contains always one of the following values:

Open: Final status not yet known. This is the initial status value for all parties for all transactions.

Success: the Consumer approved the transaction and the Issuer has confirmed this approval.

Cancelled: the transaction has not been approved; cancelled by the Consumer.

Expired: the transaction has not been approved within the BankID.expirationPeriod set by the Merchant 
or the default BankID.expirationPeriod.

Failure: the transaction has not been approved; unknown reason

Table 10: iDx data elements

5.3  iDIN data elements

These elements are the iDIN specific data elements that are either located in the SAML 2.0 message, or, differ from the normal iDx standard. If the element must be generated as an input in one of the three request messages (DirectoryReq, AcquirerTrxReq, AcquirerStatusReq) it is indicated in the description in bold.

Name

Description

Messages

Formatting rules

Name

Description

Messages

Formatting rules

BankID.

MerchantReference

Unique transaction reference generated by and only for the Merchant (e.g. administration)

Generated by Merchant

B, F’, F’(X)

 

Max 35 text and must

start with a letter (either lower- or upper-case)

BankID.

expirationPeriod

The time in which the consumer has to approve the transaction. Otherwise the status will be set to ‘Expired’.

Minimum is 60 seconds and maximum and default value is 300 seconds.

Generated by Merchant

B

ISO 8601 e.g. PT300S or PT5M

 

BankID.LOA

For a request: the minimum level of assurance required

For a response: the actual level of assurance provided

Generated by Merchant

B, F’

Must be: "nl:bvn:bankid:1.0:loa3”

Note:

nl:bvn:bankid:1.0:loa2” has been deprecated as of 01-05-2018.

BankID.

RequestedServiceID

The number that is used to ask for a particular set of consumer attributes, see Section 0 for more information.

Generated by Merchant

B

Integer as specified in Section 0.

BankID.

DeliveredServiceID

Same structure as RequestedServiceID. Returned to the Merchant in the Response to indicate which requested attributes are delivered conform the minimal set (see Section 15.4).

If the Issuer is unable to determine the DeliveredServiceID a value of ‘0’ must be used.

The DeliveredServiceID is included as unencrypted Attribute in the Assertion

F’

Integer as specified in Section 0.

consumer.bin

BIN is short for Bank identifying Number. It identifies the Consumer. BINs are bank specific and are unique for every Consumer-Merchant-Issuer combination

F’

BIN consists of two parts:

1) Prefix: Two-letter country code of the Issuer (ISO 3166-1) followed by four-letter (alphabetic) bank identifier (ISO 9362)

2) Bank specific identifier. Must be transportable as a string of max 1020 chars

consumer.transientid

Can be asked instead of the Consumer.BIN. Indicates that the content of the element is an identifier with transient semantics and SHOULD be treated as an opaque and temporary value by the Merchant

F’

Max 256 characters and is prefixed with ‘TRANS‘.

Issuer.X509

Used in the SAML Response in the Signature element (see Section 13.6) such that the Merchant can verify the Issuer’s Signature

F’

Base64 encoding

Merchant.LegalID

The Merchant.LegalID is the CreditorID of the Merchant. In the Netherlands this is based on the number of the Chamber of Commerce. See the EPC guidelines for country specific information on provision of the CreditorID which is the same legal identifier as the LegalID (https://www.europeanpaymentscouncil.eu/document-library/guidance-documents/creditor-identifier-overview)It is returned in the Status Response due to SAML compliance but has no particular use for the Merchant in completing an iDIN transaction flow

F’

 

-



Name

Description

Messages

Formatting rules

Name

Description

Messages

Formatting rules

Merchant.DocumentID

A SHA256 hash of the (set of) documents on which an electronic signature will be placed. 

Generated by Merchant

B, F'

Maximum of 256 characters

This data element can only be processed by Issuers who have implemented the product type iDIN Signature.  See 5.3.1. for more information.

Table 11: iDIN data elements in SAML message

5.3.1 iDIN Requested- and DeliveredServiceID

iDIN provides services that can be requested by the Merchant. Each transaction request can only supply one set of data, based on a single RequestedServiceID. The returned consumer attributes can differ per Issuer and request, therefore some of these elements that are part of a group are optional e.g. some consumers do not have a last name prefix. The DeliveredServiceID is used to indicate which attributes are delivered conform the minimal set as defined in Section 8.5. In most cases the RequestedServiceID shall be equal to the DeliveredServiceID. If the Issuer cannot provide all attributes conform the minimal set the DeliveredServiceID is not equal to the RequestedServiceID. This is discussed in more detail in Section 15.4.

The Excel ‘1711289A_ServiceID_Calculator’ provided along this Implementation Guidelines provides an easy method to calculate the ServiceID.

The Requested- and DeliveredServiceID are short integers translated from a binary format. The binary numbers are separated into groups. These groups represent the categories of attributes the Merchant may request. Please be aware that this is a bit pattern instead of a number, and that the first bit is on the left not on the right.

Table 12 provides an overview of which attributes are included and what value it should represent on binary level in order to receive the correct attributes, as defined in Section 8.2.

Bit number

Category

Description

Values

Bit number

Category

Description

Values

1

Reserved (R)

Reserved for reasons of backwards compatibility

0 (must be zero)

3, 5, 7, 11, 16

Reserved (R)

Not assigned; reserved space for future attributes

0 (must be zero)

2

Category 1: ConsumerID

Indicates what ConsumerID is required. See Section 8.2 for all ConsumerIDs

0  Consumer.TransientID

1  Consumer.BIN

4

Category 2: Name

All name related attributes of the Consumer excluding gender. See Section 8.2 for all attributes

0 No Name attributes

1 Provide Name attributes

6

Category 3: Address

All address attributes of the Consumer See Section 8.2 for all address attributes

0 No Address attributes

1 Provide Address Attributes

8..10

Category 4: Age related

Provides Merchant with the requested age verification or date of birth. See Section 8.2 for all age related attributes

000  No age related attribute

001 18orOlder

010 Reserved

011 Reserved

100 Reserved

101 Reserved

110 Reserved

111 Date of Birth

12

Category 5: Gender

Provides the Merchant with requested gender

0 No gender attribute

1 Provide gender attribute

14

Category 7: Telephone

Provides the Merchant with requested telephone number

0 No telephone attribute

1 Provide telephone attribute

15

Category 8: Email

Provides the Merchant with requested email address

0 No email attribute

1 Provide email attribute

 

Bit Number

Category

Description

Values

Bit Number

Category

Description

Values

13

Category 6: Electronic signature

Indicates that the product type for iDIN signature is used.

Only to be used by a Signing Service Provider.

0 Product type for iDIN signature is not used

1 Product type signature is used

The ServiceID containing the Bit Number 13 for the product type Signature can only be requested from an Issuer who has implemented the product type Signature. The Signing Service Provider (SSP) must only send requests containing a ServiceID for placing electronic signatures which minimally contain the data attribute for BIN (bit number 2) and name (bit number 4) to ensure compliancy with regulation (EU) No 910/2014 (eIDAS).

Table 12: Overview of Requested- and DeliveredServiceID

The service IDs are included in the SAML request message to specify part of the Merchant’s request. For example, if the Merchant wishes to do an authentication (by requesting the BIN), only the second bit should be equal to one, which leads to an integer value of 16384.

5.4  Consumer attributes

The consumer attributes are located in the SAML 2.0 message as a result of the requested service with the BankID.RequestedServiceID. The consumer.bin and consumer.transientid are not defined as consumer attributes and are located at a different place in the SAML 2.0 message. iDIN can provide the following attributes about a Consumer in a SAML Response message AttributeStatement. Where possible, the consumer attributes have formatting rules in line with the NEN-ISO 8601 standard. All attributes use the UTF-8 character set.

Nr.

Consumer attribute

Group[5]

Description

Formatting rules[6]

Examples

Nr.

Consumer attribute

Group[5]

Description

Formatting rules[6]

Examples

1.    

consumer.deprecatedbin

-

Same as BIN but is used to sustain continuous usage of consumer BIN. This element can occur for instance when two Merchants fuse, or, for some particular reason the consumer.bin has been reset.

See consumer.bin

See consumer.bin

2.    

consumer.gender

Can be requested individually

Gender of Consumer

0 (= unknown)

1 (= male)

2 (= female)

9 (= not specified)

Matches formatting rules of NEN 1888_2002, section 5.4.9 and NEN-ISO 528.

Allowed values: “0”, “1”, “2” and “9”.

Not allowed: Any other value than the above

3. 

consumer.legallastname

Name

Legal last name of Consumer without prefixes
(from: NEN 1888_2002, section 3.1, “significant deel van de achternaam”)

Maximum of 200 characters without numbers.

Must not include the prefix of the first last name. Prefixes of later sections of the last name must be included.

If the last name consists of multiple sections that are separated by a -, the - must not be lead and followed by a space.

Leading and trailing spaces are not allowed

Matches formatting rules of NEN 1888_2002, section 5.1.1.

For the name “Luana van Oranje-Nassau van Amsberg” the value would be “Oranje-Nassau van Amsberg”.

For the name “Jacques d’Ancona” the value would be “d’Ancona”.

For the name “Jacques d’ Ancona” the value would be “Ancona”.

4.

consumer.preferredlastname

Name

Last name of Consumer as preferred by Consumer.

Analogous to legallastname

Separation of last name from given name and prefix is analogous to legallastname.

Preferred last name can include the partner’s last name

5.

consumer.partnerlastname

Name

Last name of Consumer’s registered partner


Analogous to legallastname

Analogous to legallastname

6.

consumer.legallastnameprefix

Name

Last name prefix of Consumer’s legal last name

(from: NEN 1888_2002, section 3.1, “voorvoegsel”)

Maximum of 10 characters without numbers

A prefix is only a prefix if it was separated from the last name by a space

Only the prefix of the first section of the last name should be included

Leading and trailing spaces are not allowed

Matches formatting rules of NEN 1888_2002, section 5.1.4


For the name “Luana van Oranje-Nassau van Amsberg” the value would be “van”.

For the name “Jacques d’Ancona” there is no prefix.

For the name “Jacques d’ Ancona” the value would be “d’”.

7.

consumer.preferredlastnameprefix

Name

Last name prefix of Consumer’s preferred last name.

(analogous to legallastnameprefix)

Analogous to legallastnameprefix

Analogous to legallastnameprefix

8.

consumer.partnerlastnameprefix

Name

Last name prefix of Consumer’s partner last name
(analogous to legallastnameprefix)

Analogous to legallastnameprefix

Analogous to legallastnameprefix

9.

consumer.initials

Name

The initials of the Consumer, defined as the first letter of each of the Consumer’s first names. 

(from: NEN 1888_2002, section 5.1.7, “voorletters-1”)

Maximum of 24 capitalized letters

Only the first letter of each first name is used which must be capitalized and returned without spaces or dots.

Matches formatting rules of NEN 1888_2002, section 5.1.7 but with an increased character limit.

For the name “Jan-Jaap Christaan Jozefszoon” or “jan-jaap christaan jozefszoon” the value must be “JC”.



10.

consumer.dateofbirth

Can be requested individually

Date of birth of Consumer

Basis format (CCYYMMDD) from NEN-ISO 8601

If the month or day of the date of birth is unknown ‘00’ shall be returned e.g. 19870400

For the birthdate May 14th 1990 the value would be “19900514”.

For the year of birth 1990 with an unknown month and unknown day the value would be “19900000”.

11.

consumer.18orolder

Can be requested individually

Specifies whether the Consumer is 18 or older of age.

Boolean (true/false)

Age verification when the date of birth has an unknown day or month shall be based on the latest day of the month or latest month of the year respectively.

Allowed values are “true” and “false”.

12.

consumer.street

Address

Street name of the Consumer’s residential address
(from: NEN 5825_2002, section 3.3, “straatnaam”)

Used for NL addresses only

Maximum of 43 characters

“Prins Willem Alexanderlaan”

“Mr. J.F. Vietorstraat”

“Steenstr”

“Leidsepln”

13. 

consumer.houseno

Address

House number of the Consumer’s residential address
(from: NEN 5825_2002, section 3.3, “huisnummer”)

Used for NL addresses only

Maximum of 5 numbers
Matches formatting rules of NEN 5825_2002, section 5.3.4

“1”

“12345”

14. 

consumer.housenosuf

Address

House number suffix
(from: NEN 5825_2002, section 3.3, “huisnummertoevoeging”)

Used for NL addresses only

Maximum of 6 characters
Matches formatting rules of NEN 5825_2002, section 5.3.5

“A”, “a”, “Bis A”, “huis”, “A02”, “-2”

15.

consumer.addressextra

Address

Additional address details of Consumer’s residential address
(from: NEN 5825_2002, section 3.3, “locatieomschrijving”)

Used for NL addresses only

Maximum of 70 characters
Matches formatting rules of NEN 5825_2002, section 5.3.1

“Woonboot tegenover de kerk”

“Derde verdieping”

“Groene deur”

“Ingang aan de Kerklaan”

16.

consumer.postalcode

Address

Postal code of the Consumer’s residential address
(from: NEN 5825_2002, section 3.3, “postcode”)

Used for NL addresses only

Numerical part: 4 numbers
Alphabetic part: 2 letters
Matches formatting rules of NEN 5825_2002, section 5.3.11-12

“1234AB”

17.

consumer.city

Address

City of the Consumer’s residential address

Used for NL addresses only

Maximum of 24 characters




18.

consumer.intaddressline1

Address

Used for non-NL addresses only.
The diversity of international address formats, is captured in 3 freetext strings.

Maximum of 70 characters



19.

consumer.intaddressline2

Address

Used for non-NL addresses only
(analogous to consumer.intaddressline1)

Maximum of 70 characters



20.

consumer.intaddressline3

Address

Used for non-NL addresses only
(analogous to consumer.
intaddressline1)

Maximum of 70 characters



21.

consumer.country

Address

Country code of country where Consumer currently resides

2 letter code from ISO 3166-1

For the Netherlands, this has the value “NL”. For Belgium, this has the value “BE”. For Germany, this has the value “DE”.

22.

consumer.telephone

Telephone

Telephone number (mobile or landline) of the consumer

Issuers aspire to return all telephone numbers according to the soft format requirements.

Soft format:

Max 20 in length, using only digits and beginning with a plus sign. The following sequence must be used:

  • ‘+’

  • Country-code

  • National number excluding leading zero

Telephone numbers will always abide to the following hard format requirements.

Hard format:

Max 20 in length with the following allowed characters:

  • digit ‘0-9’

  • space ‘ ‘

  • bracket ‘()’

  • plus ‘+’

  • minus ‘-‘

Soft format examples:

‘+31612345678’ (Dutch mobile)

‘+31203051900’ (Dutch landline)



Hard format examples:

’06-12345678’

‘(020) 3051900’

23.

consumer.email

Email

Email address of the consumer

Maximum of 255 characters

Must contain:

  • One @-symbol

  • At least one character before the @-symbol

  • A dot somewhere after the @-symbol

  • At least one character after the @, before the dot

  • At least one character after the @ and after the dot.

X@Y.Z

Table 13: Consumer attributes

Notes:

  • Consumer attributes are located in the SAML Attribute element. In the @Name attribute the Name indicated above is prefixed with the following “nl:bvn:bankid:1.0:attribute:”. This results in attribute names containing only small-caps letters e.g. “nl:bvn:bankid:1.0:attribute:consumer.city”;

  • If one of the attributes is longer than the NEN-prescribed maximum length, then the name is truncated and the last character is replaced by a dash “-” (NEN 1888_2002, p14);

  • Some of the name or address related attributes might not be available at all Issuers, e.g., Consumer’s partner last name. In that case the Issuer shall not include the attribute in the attribute statement provided. Example of SAML Attribute:

1 2 3 <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.dateofbirth">      <saml:AttributeValue>19850101</saml:AttributeValue> </saml:Attribute>

5.5 Guaranteed minimal set of requested attributes

Table 14 shows the minimal set of attributes that must be provided by the Issuer for the name and address attributes when these are requested by the Merchant. The other categories (Consumer IDs, age related and gender) are requested and provided individually, and therefore must always be delivered to the Merchant upon request conform the specified format (i.e. when the Merchant requests a date of birth the Issuer must provide this, and not some other form of age verification).

If the Issuer is unable to provide the attribute groups conform this minimal set, or cannot provide one or more of the individually requested ID, gender and/or an age related attributes, it fails to respond with a complete success. When this occurs the Issuer returns all attributes and/or an ID it can deliver (which are part of the categories requested by the Merchant), but indicates with a status code that the request could not be performed with a complete success, see Section 15.4 for more detail. For this scenario the DeliveredServiceID is not equal to the RequestedServiceID.

Group

Minimal set of attributes

Name

One of the three options listed below:

1

consumer.legallastname

2

consumer.preferredlastname

3

consumer.partnerlastname

Address

One of the five options listed below:

1

consumer.postalcode AND consumer.houseno

2

consumer.streetname AND consumer.houseno AND consumer.city

3

consumer.postalcode AND consumer.addressextra

(for addresses that don’t have a house number e.g. a ‘woonboot’)

4

consumer.streetname AND consumer.addressextra AND consumer.city

(for addresses that don’t have a house number e.g. a ‘woonboot’)

5

consumer.intaddressline1 AND consumer.country

(for international addresses)

Table  14: Minimal set of attributes provided by Issuer per requested attribute group

5.5.1 Optional deselecting/changing of telephone nr. or email address by the Consumer

Consumers are given the option to deselect and optionally change their email address and/or telephone number when they are approving the transaction at the Issuer. This is only possible for the telephone number and or email and of course only if these attributes are requested by the Merchant.

If the Consumer deselects his/her telephone number and/or email address this is indicated to the Merchant in the DeliveredServiceID and the 2nd SAML StatusCode, see Section 15.4 for more detail.  

If the Consumer changes his/her telephone number and/or email address this is not indicated to the Merchant. However, if Consumers change their telephone number and/or email address the attributes do abide to the formatting requirements as described in Table 13.

6 iDIN Directory protocol 

6.1 General

The Directory protocol allows a Merchant to retrieve an up to date list of participating Consumer Banks (Issuers) from his Routing Service, which can be presented to the Consumer. In case of changes in the list of Issuers, the Directory protocol will supply the Merchant with the update of this list.

It is not allowed to perform the Directory protocol for each transaction. Since the list of Issuers only changes occasionally, it is sufficient to execute the Directory protocol on a weekly basis and check if the list has changed based on the directoryDateTimestamp. If the Issuer list has changed, the latest version has to be saved and used for any subsequent transaction. Routing Services will normally also inform all Merchants (e.g. by email) about changes in their Issuer list. The Directory protocol should at least be executed once a week.

The Directory protocol (like the Transaction protocol and the Status protocol) consists of a HTTP POST request from the Merchant to the Routing Service, followed by a HTTP response. The DirectoryReq is sent to the URL that is provided to the Merchant by the Routing Service for this specific purpose. This URL can be different from the one that is used for the AcquirerTrxReq and the AcquirerStatusReq, but it can also be the same URL.

The Routing Service validates the authenticity of the message sent by the Merchant by verifying the signature in the message. To do this, the Routing Service needs the public part of the Merchant’s Certificate, including the public key. The way in which the Merchant’s certificate is communicated with the Routing Service varies per bank.

Please refer to Chapter 10 for more information on authentication and security. APPENDIX B shows an example of a DirectoryReq and DirectoryRes.

6.2 Directory Request (DirectoryReq)

The DirectoryReq consists of an XML message that is sent to the Routing Service with HTTP POST.

Table 15 shows all elements and attributes of the DirectoryReq:

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

DirectoryReq

Yes

Root of the message

@version

Yes

Must be: “1.0.0”

@productID

Yes

Must be: “NL:BVN:BankID:1.0”

+createDateTimestamp

Yes

Contains DateTime at which this directory request message was created.

+ Merchant

Yes

Contains Merchant sub-elements.

++ MerchantID

Yes

Contains Merchant.MerchantID as supplied to the Merchant by the Acquirer

++ subID

Yes

Contains Merchant.subID as supplied to the Merchant by the Acquirer

+ Signature

Yes

Contains all signature sub-elements.

See Chapter 13 for more information about signing and Section 13.6 for all the elements

Table 15: Elements/attributes of the DirectoryReq

6.3 Directory Response (DirectoryRes)

The Merchant will receive the DirectoryRes as a reply to the DirectoryReq. This XML message contains a list of pairwise Issuer.Name and Issuer.IssuerID. Issuers are grouped by country. The Issuers in the Consumer’s country of choice may be presented at the top in the Issuer selection list, the rest is sorted alphabetically, first by country, then by name. Table 16 shows all elements and attributes that appear in the DirectoryRes message.

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

DirectoryRes

Yes

Root of the message

@version

Yes

Must be: “1.0.0”

@productID

Yes

Must be: “NL:BVN:BankID:1.0”

+createDateTimestamp

Yes

Contains DateTime at which this directory response message was created.

+ Acquirer

Yes

Contains Acquirer sub-elements

++ AcquirerID

Yes

Contains Acquirer.AcquirerID

+ Directory

Yes

Contains all Directory sub-elements

++directoryDateTimestamp

Yes

Contains DateTime at which the list of Issuers was last updated by the Acquirer

++ Country

Yes (1..∞)

Contains al Country sub-elements

+++ countryNames

Yes (1..∞)

Contains all Country.countryNames

+++ Issuer

Yes (1..∞)

Contains pairwise issuerID and issuerName sub-elements

++++ issuerID

Yes

Contains Issuer.IssuerID

++++ issuerName

Yes

Contains Issuer.Name

+ Signature

Yes

Contains all signature sub-elements.

See Chapter 13 for more information about signing and Section 13.6 for all the elements

Table 16: Elements/attributes of the DirectoryRes

6.4 Presentation of the Issuer Bank selection list

The Merchant bears primary responsibility for initiating the iDIN process and for the communication to the Consumer regarding the status of this process. Merchants who offer iDIN to their customers must include iDIN in their lists of authentication methods, methods to log on, age verifications methods and/or methods for signing of documents (if any). iDIN must be presented in the list of methods in such a way that it receives at least the same amount of attention as all other competitors. It must be clear for the Consumer that he is about to authenticate with iDIN. The Merchant must clearly indicate to the Consumer what iDIN service he is about to initiate for the Consumer.

To ensure that the Consumer experience of an iDIN transaction is consistent and recognisable through all Merchant websites; all Merchants have to comply with certain presentation standards.

All Issuers in the DirectoryRes have to be shown in a “dropdown list box”. The first element in this list is “Kies uw bank…” (Eng. “Choose your bank…”), and is selected by default. Subsequently the name of the Consumer’s country of choice is shown (either the Merchant’s own country or the country where the Consumer is expected to be from). The names of all Issuers that belong to the Merchant’s country of choice are presented next in separate elements, in the same (alphabetical) order as they are presented in the DirectoryRes. Following this the names of other available countries are presented alphabetically. Within each country the banks from that country are sorted alphabetically, in the same order as presented in the DirectoryRes. The Merchant should generate an error message whenever one of the elements “Kies uw bank…” and countryNames elements is selected by the Consumer.

It is recommended to configure the HTML “value” field of the items in the list box to be the Issuer.IssuerID (BIC) of the corresponding Issuer, because this value is necessary for subsequent messages. An example of the Issuer selection list is shown in the Figure below.

 

Figure 3: Example of (open) dropdown list box showing the Issuer list

Merchants are not allowed to remove Issuers temporarily from the Issuer selection list or to grey them out. An exception is made for the presentation of the Issuer list in case of iDIN Signing. The SSP may only present to the Consumer Issuers who offer iDIN Signing. A list of Issuers who have implemented the product type Signature can be requested at iDIN B.V. (idin@betaalvereniging.nl). 

If a Merchants learns via the iDIN Notification System (Central Reporting tool for iDIN Validation Services and Routing Services to state system non-availability) or via error messages received from the Acquiring bank that a particular Validation Service is currently not available, the Merchant may display a message on its website informing Consumers that the particular bank is currently not available. In other words, it is permissible to display a message conveying such information but it is not permissible to temporarily remove or grey out the Issuer concerned from the Issuer selection list.

7 iDIN Transaction protocol 

7.1 General

The Transaction protocol initiates the exchange of messages of the actual iDIN process. After the Consumer has chosen iDIN as an identification method and has selected his bank, the Merchant sends a Transaction Request to the Routing Service. Within the iDIN standards this message is referred to as the AcquirerTrxReq. The Routing Service replies to the AcquirerTrxReq with a Transaction Response (AcquirerTrxRes). This AcquirerTrxRes will also (among other fields) contain the issuerAuthenticationURL. This URL will redirect the browser of the Consumer to the Issuer in order to let him authorise the iDIN transaction.

The Transaction protocol consists of a HTTP POST request from the Merchant to the Routing Service, followed by a HTTP response. The AcquirerTrxReq is sent to the URL that is provided to the Merchant by the Routing Service for this specific purpose. This URL can be different from the one that is used for the DirectoryReq and the AcquirerStatusReq, but it can also be the same URL.

The Routing Service validates the authenticity of the message sent by the Merchant by verifying the signature in the message. To do this, the Routing Service needs the public part of the Merchant’s Certificate, including the public key. The way in which the Merchant’s certificate is communicated with the Routing Service varies per bank.

Please refer to Chapter 13 for more information on authentication and security. APPENDIX B shows an example of an AcquirerTrxReq and AcquirerTrxRes.

7.2 Transaction Request (AcquirerTrxReq)

The XML message sent by the Merchant to the Routing Service to initiate the transaction contains the elements and attributes shown in Table 17. The iDIN product specific information (SAML 2.0 message) is put inside the container element in the AcquirerTrxRes in the form of an AuthnRequest, as shown in Table 18.

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

AcquirerTrxReq

Yes

Root of the message

@version

Yes

Must be: “1.0.0”

@productID

Yes

Must be: “NL:BVN:BankID:1.0”

createDateTimestamp

Yes

Contains DateTime at which this Transaction Request message was created

+ Issuer

Yes

Contains Issuer sub-elements

++ IssuerID

Yes

Contains Issuer.IssuerID

+ Merchant

Yes

Contains all Merchant sub-elements

++ merchantID

Yes

Contains Merchant.MerchantID

++ subID

Yes

Contains Merchant.subID

++ merchantReturnURL

Yes

Contains Merchant.returnURL

+ Transaction

Yes

Contains all Transaction sub-elements

++ expirationPeriod

No

Contains expirationPeriod

++ language

Yes

Contains language of Consumer

++ entranceCode

Yes

Contains entranceCode

++ container

Yes

Contains the SAML 2.0 AuthnRequest message, see Table 18

+ Signature

Yes

Contains all signature sub-elements.

See Chapter 13 for more information about signing and Section 13.6 for all the elements

Table 19: Elements/attributes of AcquirerTrxReq

As explained, the SAML 2.0 AuthnRequest message is embedded in the container element. The AuthnRequest message is a standardised message, so it contains elements that are not used in iDIN. This elements and attributes inside the container are shown in Table 18.

Element/attributes (inside container element)

Mandatory

Contents

Element/attributes (inside container element)

Mandatory

Contents

AuthnRequest

Yes

Root of the message (inside container element)

@ID

Yes

Contains BankID.MerchantReference

@Version

Yes

Must be: “2.0”

@IssueInstant

Yes

Contains DateTime at which this Transaction Request message was created. This must be the same value as in createDateTimestamp.

@Destination

   

Shall not be present

@Consent

No

May be present. Shall be ignored. No matter what consent has been provided to the Merchant, the Issuer is always responsible for obtaining the Consumer’s consent

@ForceAuthn

No

May be present. Must be: “true” if present. Explicit authentication shall be enforced for every iDIN service

@IsPassive

No

May be present. Must be: “false” if present. Since explicit authentication is enforced the Issuer cannot be passive

@ProtocolBinding

Yes

Must be: “nl:bvn:bankid:1.0:protocol:iDx”

@AssertionConsumerServiceIndex

 

Shall not be present

@AssertionConsumerServiceURL

Yes

Contains Merchant.merchantReturnURL

@AttributeConsumingServiceIndex

Yes

Contains BankID.RequestedServiceID

@ProviderName



Shall not be present

+ Issuer

Yes

Contains Merchant.MerchantID

+ @NameQualifier

 

Shall not be present

+ @SPNameQualifier

 

Shall not be present

+ @Format

 

Shall not be present

+ @SPProviderID

 

Shall not be present

+ Signature

 

Shall not be present. Relevant signing is done at iDx level. (signature element in table 17)

+Extensions

No

Must be present when the serviceID indicates this transaction is used to place an electronic signature. May not be present in other cases

++ Attribute

No

Contains Attribute sub-elements

++ @Name

No

Must be: “urn:nl:bvn:bankid:1.0:merchant.documentID”

+++ AttributeValue

No

Contains Merchant.DocumentID

This element/attribute can only be processed by Issuers who have implemented the product type Signature. See 5.3.1. for more information.

+ Subject



Shall not be present

+ NameIDPolicy



Shall not be present

+ Conditions

No

May be present

+ RequestedAuthnContext

Yes

Contains RequestedAuthnContext sub-elements

+ @Comparison

Yes

Must be: “minimum”

++ AuthnContextClassRef

Yes

Contains BankID.LOA

++ AuthnContextDecIRef

 

Shall not be present

+ Scoping

No

May be present

Table 18: Elements/attributes inside the container of the AcquirerTrxReq

7.3 Transaction Response (AcquirerTrxRes)

If everything goes well the Routing Service will reply to the AcquirerTrxReq with the AcquirerTrxRes. Table 19 shows all fields of the AcquirerTrxRes message. The AcquirerTrxRes has no container, so there is no SAML 2.0 message in this response (this is different in case of an Error Response, see Chapter 9 on error handling).

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

AcquirerTrxRes

Yes

Root of the message

@version

Yes

Must be: “1.0.0”

@productID

Yes

Must be: “NL:BVN:BankID:1.0”

+ createDateTimestamp

Yes

Contains DateTime at which this Transaction Response message was created

+ Acquirer

Yes

Contains Acquirer sub-elements

++ AcquirerID

Yes

Contains Acquirer.AcquirerID

+ Issuer

Yes

Contains Issuer sub-elements

++ IssuerAuthenticationURL

Yes

Contains issuerAuthenticationURL

+ Transaction

Yes

Contains Transaction sub-elements

++ transactionID

Yes

Contains Transaction.TransactionID

++ transactionCreateDateTimeStamp

Yes

Contains DateTime at which the transaction was first registered by the Routing Service. This time can be used by Merchant, Routing Service and Validation Service for reporting on the transaction.

+ Signature

Yes

Contains all signature sub-elements.

See Chapter 13 for more information about signing and Section 13.6 for all the elements

Table 19: Elements/attributes of AcquirerTrxRes

7.4 Errors when executing Transaction Protocol

A number of errors may occur when executing the iDIN Transaction Protocol. These may be related to unavailability or an error within your own web environment (Merchant), the Routing Service environment or the Validation Service environment.

The following situations may occur:

  • You receive an error response (message B’(X) ) from your Routing Service within the set time-out period;

  • You do not receive any response within the set time-out period.

In all of the above cases, the Transaction protocol cannot be successfully executed. This means it is not possible for the iDIN transaction to take place at that time. Error handling is explained in more detail in Chapter 12.

7.5 Redirect to the online banking environment

After receiving the AcquirerTrxRes the Merchant has to redirect the Consumer to the issuerAuthenticationURL of the selected Issuer, as stated in the AcquirerTrxRes message. If the Merchant’s page contains HTML frames, these will be removed by the Issuer (‘frame busting’). If and when the Consumer returns to the Merchant’s website (with the merchantReturnURL), the Merchant will have to completely rebuild its own page to show confirmation of iDIN reception.

The Merchant needs to redirect the Consumer to the selected Issuer from the browser window or Merchant app. If it is not possible to keep the Consumer in the same browser window then this should be communicated to the Consumer (e.g.: “You will now be redirected to the app or (mobile) website of your bank” or in Dutch “U wordt nu doorverwezen naar de app of (mobiele) website van uw bank”).

In case of a transaction initiated in the mobile Merchant app, it is not allowed to present the Issuer approval screens in a web view component within the Merchant’s own app (in-app browser). The complete transaction flow, up to the redirect back to the Merchant’s app, must take place in an app that is trusted by the Consumer, either the Consumer’s chosen browser or the Issuer’s mobile app. Thus, the issuerAuthenticationURL must, for execution, be offered to the mobile operating system at all times or executed using SafarViewController or Chrome Custom Tabs. During the transaction flow it should not be possible for the Consumer to initiate another transaction through the Merchant’s original app.

Relevant details about the redirect from the Merchant to the Issuer’s mobile channel:

  • The Issuer decides which Consumers to redirect to which channel. For example, some Issuers may treat users of tablet devices the same as mobile users, while others will treat them like PC users;

  • The Merchant should not intervene with the redirect. The issuerAuthenticationURL has also to be used for mobile iDIN transactions.

  • If the Issuer has integrated iDIN mobile in its mobile banking app, the Consumer is offered the option, on a ‘landing page’, to open the app or approve the iDIN transaction via the (mobile) web page. On this ‘landing page’ the Consumer might be offered the option to download the latest version of the mobile banking app, if it is not yet installed on the Consumer’s device.

7.6 Redirect to the Merchant environment

After the Consumer has performed the necessary steps at the Issuer he/she will be presented with a ‘Continue’ button that must redirect him back to the website of the Merchant with the merchantReturnURL as supplied in the AcquirerTrxReq.

Two GET parameters are appended to this URL: the entranceCode (see Table 10) with ‘ec’ as GET parameter name, and the Transaction.TransactionID (see Table 10) with ‘trxid’ as GET parameter name. It is also possible for a Merchant to add additional parameters. For example, if the Merchant defines the merchantReturnURL as follows:

http://www.webshop.nl/processtransaction?producttype=electronics

The final URL will look something like:

http://www.webshop.nl/processtransaction?producttype=electronics&trxid=0010123456789012&ec=4hd7TD9wRn76w6gGwGFDgdL7jEtb

The entranceCode field should contain a unique value, with the object of preventing message ‘sniffing’. Use of the same entranceCode each time would allow malevolent individuals to intercept the data from the merchantReturnURL and make fraudulent use of this information. This is why using unique values for the entranceCode is extremely important.

Note that a Consumer may not always use the redirect back to the Merchant environment that is offered by the Issuer. Also note that in exceptional cases the Issuer may be unable to match the Transaction.TransactionID in its system or another error occurs, which makes it impossible to redirect the Consumer back to the Merchant. In all other cases the Consumer is redirected with the parameters defined above, regardless of the final status of the transaction (success, cancelled, failed). The Merchant must then use the Status protocol (see Chapter 11) to determine the status of the transaction.

After the Consumer has been authenticated in either the mobile or regular channel and has approved the transaction, he is redirected back to the Merchant as normal (using the merchantReturnURL). The merchantReturnURL usually starts with ‘https’, redirecting the Consumer back to a page on the mobile device’s browser. If the Consumer has initiated the transaction from the Merchant’s mobile app, the merchantReturnURL can be an app handler, which will redirect the Consumer directly to the Merchant app. An app handler is a call that can be used to start an app and request it to initiate a specific action. For example a Merchant’s app handler can start with ‘nl.companyname.idin://’ and this will open the Merchant’s app.

The merchantReturnURL should always direct to a web page or app of the Merchant (or party acting on behalf of the Merchant).

The following errors may occur during execution of the redirect to the online banking environment (Issuer), the execution of the iDIN transaction at the Issuer and/or the redirect back to your (Merchant) environment:

  1. The bank page is unavailable, resulting in the Consumer being unable to approve the iDIN request, and thus the Consumer cannot be properly redirected to your confirmation page;

  2. The bank page is available but the Consumer cannot (after approving the iDIN request or otherwise) be properly redirected to your confirmation page.

In both situations the Consumer cannot (as the result of a disturbance) return to your confirmation page in the normal way. In that case the Consumer can return to your website by using the ‘back’ button or entering the URL, for example. Considering the short validity of the Assertion the Merchant would be unable to retrieve the status of the transaction. More precisely, the Merchant is only allowed to request the status when the Consumer is successfully returned to the Merchant’s website using the return URL, see Section 11.5. Therefore, the Merchant has to make a new transaction when something has gone wrong in the redirections.

To give an overview of all the possible process steps and important notes when dealing with iDIN Mobile transactions, we have specified four different scenarios. There are four different scenarios because either the Issuer or the Merchant or both can use a (mobile) web page or a mobile app.

Because these scenarios (could) differ from the regular (non-mobile) iDIN transactions they will be illustrated in the following paragraphs.

Section

Merchant

Issuing Bank

Section

Merchant

Issuing Bank

7.8.1

(Mobile) web page

(Mobile) web page

7.8.2

(Mobile) web page

Mobile banking app

7.8.3

Mobile app

(Mobile) web page

7.8.3

Mobile app

Mobile banking app

Table 20: Different scenarios for the completion of an iDIN mobile transaction

7.8.1 Consumer is redirected from the Merchant’s (mobile) web page to the Issuer’s (mobile) web page.

This is currently the most common iDIN mobile scenario, as it is identical to the regular desktop iDIN transaction flow. As such there are no specific notes for use in a mobile setting, but this scenario has been added for reasons of completeness.

The Consumer starts the transaction on the Merchant’s mobile page and follows these steps:

Step

Description

Important note

Step

Description

Important note

1

The Consumer selects iDIN to provide identification or consumer attributes



2

The Consumer selects his Issuer



3

The Consumer is redirected to the Issuer of his choice

It is mandatory for the Merchant to have the Operating System (OS) of the mobile device handle the issuerAuthenticationURL or use the secure in-app browsing techniques SafariViewController and Chrome Custom Tabs. See section 7.5 for more information.

4

The Issuer presents the Issuer’s ‘landing page’ to the Consumer or redirects the Consumer to it's mobile banking app, which offers the option to complete the iDIN transaction in the Issuer’s mobile banking app or in the Issuer’s (mobile) web page



5

The Consumer selects the (mobile) web page



6

The Consumer is redirected to the Issuer’s (mobile) web page where he can log in and authorize the iDIN transaction. After completion of the transaction the Issuer shows the complete iDIN identification/authentication to the Consumer



7

The Consumer is redirected back by the Issuer, to the Merchant’s (mobile) web page using the merchantReturnURL, which was received from the Merchant

The merchantReturnURL usually starts with https:// and contains two parameters (entranceCode and Transaction.TransactionID) that can be used to correctly identify the Consumer upon his return

8

The Merchant shows the Consumer the result of the iDIN transaction



 Table 21: Scenario: Redirect from Merchant (mobile) web page to the Issuers (mobile) web page

7.8.2 Consumer is redirected from the Merchant’s (mobile) web page to the Issuer’s mobile banking app

The Consumer starts his customer journey on the Merchants (mobile) web page and follows the following steps:

Step

Description

Important note

Step

Description

Important note

1

The Consumer selects iDIN to provide identification or consumer attributes



2

The Consumer selects his Issuing Bank



3

The Consumer is redirected to the Issuer of his choice



4

The Issuer presents the Issuer’s ‘landing page’ to the Consumer, which offers the option to complete the iDIN transaction in the Issuer’s mobile banking app or in the Issuer’s (mobile) web page



5

The Consumer selects the mobile banking app



6

The Consumer is redirected to the Issuer’s banking app where he can log in and authorize the iDIN transaction. After completion of the transaction the Issuer shows the complete iDIN identification/authentication to the Consumer



7

The Consumer is redirected back by the Issuer, to the Merchant’s (mobile) web page using the merchantReturnURL, which was received from the Merchant

Because the transaction takes place in the bank’s app, outside of the web-browser setting, the browser session may be lost. This means the Merchant may not be able to recognize the Consumer using the browser session.

Next to this, when redirecting the Consumer back to the Merchant from the bank-app, the merchantReturnURL is handled by the Operating System of the mobile device. The OS uses the native (default) browser to handle this URL. This discontinues the original browser session if the transaction was initiated in a non-native browser. 

The merchantReturnURL starts with https:// and contains two parameters (entranceCode and Transaction.TransactionID) that can be used to correctly identify the Consumer upon his return

8

The Merchant shows the Consumer the result of the iDIN transaction.



Table 22: Scenario: Redirect form Merchant (mobile) web page to the Issuers mobile banking app

7.8.3 Consumer is redirected from the Merchant’s mobile app to the Issuer’s (mobile) web page

The Consumer starts his customer journey on the Merchants mobile app and follows the following steps:

Step

Description

Important note

Step

Description

Important note

1

The Consumer selects iDIN to provide identification or consumer attributes



2

The Consumer selects his Issuer



3

The Consumer is redirected to the Issuer of his choice

It is mandatory for the Merchant to let the Operating System, which is installed on the Consumer’s mobile device, handle the issuerAuthenticationURL. See Section 8.5.1 for more information

4

The Issuer presents the Issuer’s ‘landing page’ to the Consumer, which offers the option to complete the iDIN transaction in the Issuer’s mobile banking app or in the Issuer’s (mobile) web page



5

The Consumer selects the (mobile) web page



6

The Consumer is redirected to the Issuer’s (mobile) web page where he can log in and authorize the iDIN transaction. After completion of the transaction the Issuer shows the complete iDIN identification/authentication to the Consumer



7

The Consumer is redirected back by the Issuer, to the Merchant’s app using the merchantReturnURL, which was received from the Merchant

The merchantReturnURL contains an app handler and two parameters (merchantReturnURL and Transaction.TransactionID) that can be used to correctly identify the Consumer upon his return. See Section 8.6 for more information

8

The Merchant shows the Consumer the result of the iDIN transaction



Table 23: Scenario: Redirect from the Merchants mobile app to the Issuers (mobile) web page

7.8.4 Consumer is redirected from the Merchant’s mobile app to the Issuer’s mobile banking app

The Consumer starts his customer journey on the Merchants mobile app and follows the following steps:

Step

Description

Important note

Step

Description

Important note

1

The Consumer selects iDIN to provide identification or consumer attributes



2

The Consumer selects his Issuer



3

The Consumer is redirected to the Issuer of his choice

It is mandatory for the Merchant to let the Operating System, which is installed on the Consumer’s mobile device, handle the issuerAuthenticationURL. See Section 8.5.1 for more information

4

The Issuer presents the Issuer’s ‘landing page’ to the Consumer, which offers the option to complete the iDIN transaction in the Issuer’s mobile banking app or in the Issuer’s (mobile) web page



5

The Consumer selects the mobile banking app



6

The Consumer is redirected to the Issuer’s banking app where he can log in and authorize the iDIN transaction. After completion of the transaction the Issuer shows the complete iDIN identification/authentication to the Consumer



7

The Consumer is redirected back by the Issuer, to the Merchant’s app using the merchantReturnURL, which was received from the Merchant

The merchantReturnURL contains an app handler and two parameters (entranceCode and Transaction.TransactionID) that can be used to correctly identify the Consumer upon his return. See Section 8.6 for more information

8

The Merchant shows the Consumer the result of the iDIN transaction



Table 24: Scenario: Redirect from the Merchants mobile app to the Issuers mobile banking app

7.9 Performance and time-out of transaction message

The performance of the Issuer and Routing Service systems has a direct influence on the Consumer’s user experience. Therefore, iDIN sets a target time and time-out for the Transaction Response message. For a Merchant the relevant target time and time-out concerning the communication with its iDIN Routing Service is: 

Communication

Target time (in seconds)

Time-out (in seconds)

Communication

Target time (in seconds)

Time-out (in seconds)

AcquirerTrxReq - AcquirerTrxRes

2.0

7.6

Table 25: Performance requirements (for the 95th percentile[7])

The target time is the time (in seconds) in which the Merchant should receive a AcquirerTrxRes message after sending a AcquirerTrxReq. The time-out is the length of time after which the Merchant should no longer expect a response (most likely an error has occurred) and should act accordingly (for example by displaying an appropriate error message to the Consumer).

8 iDIN Status protocol

8.1 General

To verify whether an iDIN transaction was successful the Merchant will start the Status protocol by sending a Status Request to the Routing Service. Within the iDIN standards this message is referred to as the AcquirerStatusReq.

To avoid unnecessary system load status requests should not be made unnecessarily, see Section 11.5 for more details on what is allowed. The AcquirerStatusReq message can be sent after the return of the Consumer to the Merchant’s website (after the redirect from the Issuer).

Status protocol consists of a HTTP POST request from the Merchant to the Routing Service, followed by a HTTP response. The AcquirerStatusReq is sent to the URL that is provided to the Merchant by the Routing Service for this specific purpose. This URL can be different from the one that is used for the DirectoryReq and the AcquirerTrxReq, but it can also be the same URL.

The Routing Service validates the authenticity of the message sent by the Merchant by verifying the signature in the message. To do this, the Routing Service needs the public part of the Merchant’s Certificate, including the public key. The way in which the Merchant’s certificate is communicated with the Routing Service varies per bank.

Please refer to Chapter 13 for more information on authentication and security. Appendix B shows an example of an AcquirerStatusReq and AcquirerStatusRes.

8.2 Status Request (AcquirerStatusReq)

Table 26 contains all fields that are part of the AcquirerStatusReq XML message. The Merchant sends this message to the Routing Service. The AcquirerStatusReq does not contain a container with a SAML 2.0 message.  

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

AcquirerStatusReq

Yes

Root of the message

@version

Yes

Must be: “1.0.0”

@productID

Yes

Must be: “NL:BVN:BankID:1.0”

+createDateTimestamp

Yes

Contains DateTime at which this Status Request message was created

+ Merchant

Yes

Contains Merchant sub-elements

++ merchantID

Yes

Contains Merchant.MerchantID

++ subID

Yes

Contains Merchant.subID

+ Transaction

Yes

Contains Transaction sub-elements

++ transactionID

Yes

Contains Transaction.TransactionID

+ Signature

Yes

Contains all signature sub-elements.

See Chapter 13 for more information about signing and Section 13.6 for all the elements

Table 26: Elements/attributes of AcquirerStatusReq

8.3 Status Response (AcquirerStatusRes)

The reply to the AcquirerStatusReq is the AcquirerStatusRes. This message and the SAML Response inside the container are created by the Validation Service and sent to the Merchant via the Routing Service. The AcquirerStatusRes contains the elements and attributes as listed in Table 27. This message communicates the status of the transaction (related to the Transaction.TransactionID which was sent in the AcquirerStatusReq) to the Merchant. If the status equals “Success”, the container element is included in the response. Inside the container element is the SAML 2.0 message containing the consumer data elements. The elements and attributes in the optional container are shown in Table 28.

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

AcquirerStatusRes

Yes

Root of the message

@version

Yes

Must be: “1.0.0”

@productID

Yes

Must be: “NL:BVN:BankID:1.0”

+ createDateTimestamp

Yes

Contains DateTime at which this Status Response message was created

+ Acquirer

Yes

Contains Acquirer sub-elements

++ acquirerID

Yes

Contains Acquirer.AcquirerID

+ Transaction

Yes

Contains Transaction sub-elements

++ transactionID

Yes

Contains Transaction.TransactionID

++ status

Yes

Contains Transaction.status

++ statusDateTimeStamp

No

Present only If: Transaction.status = “Success”, “Cancelled”, “Expired” or “Failure” (not present when Transaction.status = “Open” or “Pending”). Contains DateTime at which the Issuer established the Transaction.status for this transaction and recorded it as part of the transaction details

++ container

No

Present only if: Transaction.status = “Success”

Contains the SAML 2.0 Response message, see Table 28

+ Signature

Yes

Contains all signature sub-elements.

See Chapter 13 for more information about signing and Section 13.6 for all the elements

Table 27: Elements/attributes of AcquirerStatusRes

As explained, the SAML 2.0 Response message is embedded in the container element. The Response message is a standardised message, and therefore it contains elements that are not used in iDIN. However, because it is up the Validation Service to omit these values it is not indicated in Table 28. The elements and attributes inside the container are shown in Table 28.

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

Response

Yes

Root of this message inside the container element

@ID

Yes

Contains Transaction.TransactionID prefixed with ‘RES-‘

@InResponseTo

Yes

Contains Merchant.MerchantReference

@version

Yes

Must be: “2.0”

@IssueInstant

Yes

Contains DateTime at which this SAML Response message was created

+ Issuer

Yes

Contains Acquirer.AcquirerID

NB: Issuer in this context is reserved SAML terminology and not related to the iDIN Issuer

+ Status

Yes

Contains the status of SAML Response in attribute

++ StatusCode

Yes

Contains StatusCode sub-elements

+++@Value

Yes

Must be: “urn:oasis:names:tc:SAML:2.0:status:Success”

+++ StatusCode

Yes

StatusCode one level deeper

++++ @Value

Yes

Has one of the two values:

“urn:nl:bvn:bankid:1.0:status:Success”

or, if some attributes are not delivered conform the minimal set:

“urn:nl:bvn:bankid:1.0:status:IncompleteAttributeSet”

The use of this status code is explained in more detail in Section 15.4

+ Assertion

Yes

Contains Assertion sub-elements

+ @Version

Yes

Must be: “2.0”

+ @ID

Yes

Contains unique identifier created by the Validation Service

+ @IssueInstant

Yes

Contains DateTime at which this Assertion element was created. Different from the DateTime at which this Status Response message was created

++ Issuer

Yes

Contains Issuer.IssuerID

++ Signature

Yes

Contains the Signature sub-elements for the SAML signature created by the Validation Service.

See Chapter 13 for more information about signing and Section 13.6 for all the elements. Section 10.2.1. deals with the signing of the SAML Assertion in particular.

++ Subject

Yes

Contains Subject sub-elements

+++ EncryptedID

Yes

Contains the encrypted element NameID which in turn contains the consumer.bin or consumer.transientid. See Section 13.3

++ Conditions

Yes

Contains Conditions sub-elements

++ @NotBefore

Yes

Contains DateTime at which the transaction request was created

++ @NotOnOrAfter

Yes

Contains DateTime 30 seconds after the Assertion@IssueInstant

+++ AudienceRestriction

Yes

Contains AudienceRestriction sub-elements

++++ Audience

Yes

Contains the Merchant.LegalID

++++ OneTimeUse

Yes

Is present but is left empty

++ AuthnStatement

Yes

Contains AuthnStatement sub-elements

++ @AuthnInstant

Yes

Contains DateTime at which the authentication took place

+++ AuthnContext

Yes

Contains AuthnContext sub-elements

++++AuthnContextClassRef

Yes

Contains BankID.LOA

++++AuthenticationAuthority

Yes

Contains Issuer.IssuerID

++AttributeStatement

Yes

Contains AttributeStatement sub-elements

+++Attribute

Yes

 

++++@Name

Yes

Must be: “urn:nl:bvn:bankid:1.0:bankid.deliveredserviceid”

++++AttributeValue

Yes

 

+++<Attribute>

No

Must be present when the serviceID indicates the product type for signing is used. Only to be used by a Signing Service Provider

++++@Name

No

Must be: “urn:nl:bvn:bankid:1.0:merchant.documentID”

++++<AttributeValue>

No

Contains Merchant.DocumentID

This element/attribute can only be processed by Issuers who have implemented the product type Signature. See 5.3.1. for more information.

+++ EncryptedAttribute

No (0..∞)

Contains encrypted consumer attributes. One for each consumer attribute. See Section 13.3

Table 28: Elements/attributes inside the container of AcquirerStatusRes

8.4 Errors during execution of Status Protocol

When using the Status Protocol to request an iDIN transaction status, errors can occur which can lead to the Merchant not obtaining the status of the transaction at that moment. It is therefore not possible to show the Consumer the final status of the transaction at that moment. Recommended messages to show to Consumers are defined further on in this document.

8.5 Restrictions on AcquirerStatusReq

A Merchant may only initiate an AcquirerStatusReq in the following case:

  • It is triggered by a Redirect to Merchant (E) as part of the Transaction protocol.

The SAML Assertion issued by the Validation Service is only valid for 30 seconds. From the moment the Consumer has been successfully redirected to the Merchant up to the time the Assertion is expired, the Merchant can make status requests. However, the Merchant should only perform more than one status request if it has received a timeout from the Routing Service. The Merchant is not allowed to perform any more status requests once it received notification from the Validation Service that the Assertion is expired, see Chapter 12 for the details.

Merchants will be perceived as committing undesirable actions if they use the Status Request more than the above described limitation, as doing so places unnecessarily heavy demands on the Acquirer’s and Issuer’s system.

8.6 Performance and time-out of status messages

The performance of the Issuer/Validation Service and Routing Service systems has a direct influence on the Consumer’s user experience. Therefore iDIN sets a target time and time-out for the status response message. For a Merchant the relevant target time and time-out concern the communication with its iDIN Routing Service is:

Communication

Target time (in seconds)

Time-out (in seconds)

Communication

Target time (in seconds)

Time-out (in seconds)

AcquirerStatusReq - AcquirerStatusRes

2.0

7.6

Table 29: Performance requirements (for the 95th percentile[8])

The target time is the time (in seconds) in which the Merchant should receive a AcquirerStatusRes after sending a AcquirerStatusReq. The time-out is the length of time after which the Merchant should no longer expect a response (most likely an error has occurred) and should act accordingly (for example by displaying an appropriate error message to the Consumer).

9 Error handling

9.1 General

If an error occurs while processing a DirectoryReq, AcquirerTrxReq or AcquirerStatusReq, for example because a request contains an invalid value, an AcquirerErrorRes will be returned instead of the regular response. Also, for certain special cases an error is returned to the Merchant e.g. when the Assertion is expired. This is discussed in more detail in Appendix A.

The AcquirerErrorRes has the same main structure as indicated in Table 30 for all three types of requests. The container is only present when receiving an error after an AcquirerStatusReq. Appendix B shows an example of an AcquirerErrorRes.

9.2 Error Response (AcquirerErrorRes)

Instead of the regular response (DirectoryRes, AcquirerTrxRes or AcquirerStatusRes) the Routing Service will return an AcquirerErrorRes if an error occurs during the reception or processing of the request, or if the request contains values that are not allowed or do not comply with the required format. Table 30 lists the fields that appear in the AcquirerErrorRes and Table 31 lists the elements and attributes that appear inside the container.

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

AcquirerErrorRes

Yes

Root of the message

@version

Yes

Must be: “1.0.0”

@productID

Yes

Must be: “NL:BVN:BankID:1.0”

+createDateTimestamp

Yes

Contains DateTime at which this Error Response message was created

+Error

Yes

Contains Error sub-elements

++errorCode

Yes

Contains Error.errorCode see Appendix A

++errorMessage

Yes

Contains Error.errorMessage see Appendix A

++errorDetail

No

Contains Error.errorDetail

++suggestedAction

No

Contains Error.suggestedAction

++consumerMessage

No

Contains Error.consumerMessage see Appendix A

++container

No

Contains the SAML 2.0 Response message, see Table 32

+Signature

Yes

Contains all signature sub-elements. See Chapter 13 for more information about signing and Section 13.6 for all the elements

Table 30: Elements/attributes of the AcquirerErrorRes

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

Response

No

Root of the message inside the container

@ID

Yes

Contains Transaction.TransactionID prefixed with ‘RES-‘

@InResponseTo

Yes

Contains BankID.MerchantReference

@Version

Yes

Must be: “2.0”

@IssueInstant

Yes

Contains DateTime at which this Error Response message was created

+ Issuer

Yes

Contains Acquirer.AcquirerID

+ Status

Yes

Contains Status sub-elements

++ StatusCode

Yes

Contains StatusCode sub-elements.

++ @Value

Yes



Contains a first level SAML status code equal to:

“urn:oasis:names:tc:SAML:2.0:status:Requester” which means the request could not be performed due to an error on the part of the requester

+++ StatusCode

Yes

Contains StatusCode sub-elements.

+++ @Value

Yes

Contains the second level status code. See Appendix  A for which status code is returned when

++ StatusMessage

Yes

Provides a human readable hint to which field caused the error

Table 31: Elements/attributes inside the container of AcquirerErrorRes

9.3 Non-availability

It might be possible that one of the Issuers is temporarily unavailable. In this case, transactions that have to be processed by this Issuer will generate an AcquirerErrorRes. When the Routing Service has determined unavailability of an Issuer it will communicate this to the Issuer immediately. This means that Merchant will never have to contact the Issuer directly.

It might also be possible that the Routing Service itself is temporarily unavailable. In this case, unless the Merchant has more than one Routing Service, no iDIN transactions can be processed and the Routing Service will generate an AcquirerErrorRes or time-out.

Lastly, the Merchant return-webpage might not be working properly.

For all three cases we recommend displaying a clear error message to the Consumer.

10 Security and certificates 

10.1 General principles of certificates

For asymmetric encryption two keys are used: one public key and one private key. The public key is linked to the certificate and can be shared with anyone. The owner of the certificate must keep the private key confidential at all times. The specific characteristics of the private and public part of the certificates will allow the encryption of a message with the public part while the result can be decrypted with the private part, and vice versa. The certificates should have RSA keys of 2048 bit long. It is not possible to decrypt a text with the same key that was used to encrypt it.

These specific characteristics enable two applications of a certificate:

  • Encryption of a message. By encrypting a message with the public key of the receiving party the information can only be read by the recipient (who has sole knowledge of the private key);

  • Creating an electronic signature of a message. By encrypting the (hash) message with the private key, the recipient can determine the authenticity of the (sender of the) message by verifying the signature with the public part of the certificate. The recipient will also verify the integrity of the message to make sure the contents of the message was not changed by a third party.

The TLS connection that is used within iDIN between the Merchant and the Routing Service is based on the first application. The TLS connection uses at least 128-bit encryption based on a server side certificate of the Routing Service.

Merchant MUST use a minimum TLS version of 1.2. Earlier versions have become out-dated.

Since iDIN does not put any constraints on the communication between the Consumer and the Merchant, this can be either with or without a TLS connection. Merchants are however strongly advised to always use TLS on the transaction pages of their website. The iDIN standard also uses electronic signatures to ensure the authenticity, integrity and non- repudiation of all messages with the exception of redirects. The electronic signature of the Routing Service in the AcquirerStatusRes message, for example, enables the Merchant to verify the authenticity of the transaction confirmation.

10.2 Signing iDIN messages

All messages that are sent by the Merchant to the Routing Service (DirectoryReq, AcquirerTrxReq and AcquirerStatusReq) have to be signed by the Merchant. Messages are signed in accordance with the "XML Signature Syntax and Processing”, with the following settings and restrictions applied:

  • The entire XML message[10] must be signed;

  • For the purpose of generating the digest, the exclusive[11] canonicalization algorithm must be used;

  • For the purpose of generating the signature value, the exclusive[12] canonicalization algorithm must be used;

  • The syntax for an enveloped[13] signature must be used. The signature itself must be removed from the XML message using the default transformation prescribed for this purpose;

  • For hashing purposes the SHA-256[14] algorithm must be used;

  • For signature purposes the RSAWithSHA256[15] algorithm must be used. RSA keys must be 2,048 bits long;

  • The public key must be referenced using a fingerprint of an X.509 certificate. The fingerprint must be calculated according to the following formula HEX(SHA-1(DER certificate)) [16].

In general Merchants don’t need to have extensive knowledge of RSA since most programming languages have libraries with functionalities that implements XML Digital Signature processing. It is strongly recommended to use these standard libraries.

Standard functionality for creation and verification of RSAWithSHA256 digital signatures is available in commonly used software platforms, from the following versions and higher:

  • PHP 5.5;

  • Microsoft .NET 4,5;

  • Java SE 7.

This functionality may also be available in earlier versions of these platforms and in other platforms (e.g. Python, Ruby).

To further support Merchants, software libraries have been developed for iDIN in .NET, PHP and Java. Please contact your bank about this for more information.

For information about creating the public and private key pair please refer to paragraph 13.5.

10.2.1 Signing of the SAML 2.0 Assertion

Next to the regular signing of the entire XML message in the iDx protocol, the Validation Service signs the SAML Assertion separately. This Assertion is passed along the Merchant via the Routing Service in the AcquirerStatusRes (only for the Transaction.status ‘Success’). This signing in the SAML Assertion follows the same requirements that apply to signing as discussed before except for the following:

  • Instead of referring to the certificate of the Issuer to be used for verifying the signature by fingerprint, the entire certificate is included. The KeyName element is replaced by an X509Data element containing an X509Certificate element containing the entire X509 certificate of the Validation Service, See Table 33. The X509SubjectName element may be included inside the X509Data element. Other elements in KeyInfo shall not be used. This is done to guarantee availability of the certificate of the Validation Service for the Merchant in an easy manner, without synchronization with a scheme directory for example;

  • The attribute Reference@URI must contain the value of the of @ID attribute of Assertion to make the reference to the object being signed;

  • Merchants shall only trust and process SAML Assertions signed with a valid Validation Service certificate issued under the trusted root for iDIN Issuers.

10.3 SAML EncryptedID and EncryptedAttribute

For privacy reasons the Routing Service is prevented to see the consumer attributes in readable form. Hence, all consumer data inside the SAML 2.0 assertion are encrypted. Note that the Merchant is allowed to use a different certificate to sign the messages than it uses to decrypt the attributes. For the encryption of both the EncryptedID element and the EncryptedAttribute elements within the SAML Assertion the following requirements apply:

  • Encryption of the attributes will be based on a 256 bit AES key;

  • A Validation Service generates a new AES key for each EncryptedAttribute and EncryptedID elements;

  • The AES keys are encrypted with the public key of the Merchant, which the Validation Service received from the Routing Service. Encryption of the AES keys is done with RSA in combination with OAEP: http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p;

  • XML contents in the encrypted element have all relevant namespace definitions;

  • xsi:type definitions MAY be included in the AttributeValue element e.g. <saml:AttributeValue xsi:type=”xs:int>.

The NameID element containing either the Consumer.BIN or Consumer.TransientID is entirely encrypted (for the corresponding namespaces see Table 7). The following element containing the Consumer.BIN is encrypted:

1 <saml:NameID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">%Consumer.BIN%</saml:NameID>

Encrypting the NameID element yields an EncryptedID in the following fashion. The placeholders (between % signs) indicate where the encrypted AES key and where the encrypted NameID can be found. The EncryptedKey element is embedded inside the EncryptedData element.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 <saml:EncryptedID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/> <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <xenc:EncryptedKey Recipient=%Merchant.LegalID%> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> </xenc:EncryptionMethod> <xenc:CipherData> <xenc:CipherValue>%AESKey_Encrypted_With_Public_Key_Merchant%</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedKey> </ds:KeyInfo> <xenc:CipherData> <xenc:CipherValue>%NameID_Encrypted_With_AESKey%</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </saml:EncryptedID>

In a similar fashion the consumer attributes in the SAML Assertion are encrypted. An example below shows how the consumer.dateofbirth is encrypted. Depending on the request of the Merchant, zero or more EncryptedAttributes are returned in the SAML Assertion.

1 2 3 4 <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.dateofbirth"> <saml:AttributeValue>19850101</saml:AttributeValue> </saml:Attribute>

The entire attribute is encrypted which yields the following:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 <saml:EncryptedAttribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/> <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <xenc:EncryptedKey Recipient=%Merchant.LegalID%> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> </xenc:EncryptionMethod> <xenc:CipherData> <xenc:CipherValue>%AESKey_Encrypted_With_Public_Key_Merchant%</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedKey> </ds:KeyInfo> <xenc:CipherData> <xenc:CipherValue>%Attribute_Encrypted_With_AES_Key%</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </saml:EncryptedAttribute>

10.4 Authentication of iDIN messages

To ensure the status of a transaction, the Merchant has to verify the signature of the Routing Service in all Response messages. Furthermore it has to verify the signature of the Validation Service on the Assertion. To verify the signature in the SignatureValue field, it is recommended that Merchants use standard XML Digital Signature libraries, which are available in most (web) programming languages.

10.5 Creating a key pair

If you want to use a so-called “self signed certificate” this paragraph will explain how to do so. It is also possible to purchase a certificate at a company specialized in this field (Certificate Authority), see paragraph 0.

In order to create a public and a private key execute the following steps:

  1. Download the “OpenSSL Library” from http://www.openssl.org. You can find more information on the “certificate generating utility” at: http://www.openssl.org/docs/apps/req.html. You may also generate the key pair using other software. If so please use the manual that comes with your software.

  2. Generate an “RSA private key” using the following command
    (choose your own password for the field [privateKeyPass]): 
    openssl genrsa –aes128 –out priv.pem –passout pass:[privateKeyPass] 2048

  3. Create a certificate based on the “RSA private key”
    (use the same password as in the previous step for the field [privateKeyPass]): 
    openssl req –x509 –sha256 –new –key priv.pem –passin pass:[privateKeyPass]
    -days 1825 –out cert.cer

  4. The previous OpenSSL command will generate a certificate in X.509 format, with a validity period of 5 years (1825 days), the maximum for iDIN signing certificates.

  5. The file priv.pem contains the private key. The file cert.cer contains the certificate with the public key. The Merchant has to keep the priv.pem file private, which is used in the RSA encryption. The cert.cer file has to be communicated to the Routing Service. The method of communication will depend on the Routing Service.

10.5.1 Buying a certificate from a Certificate Authority

When buying a certificate from a Certificate Authority (CA), rather than generating the certificate yourself, it is important to note the following: the CA signing certificate (and the rest of the certificate chain) must use hashing algorithms and key lengths that are at least as secure or better than those of the Merchant certificate. Therefore CA-certificates used to sign certificates for electronic signatures must use at least SHA-256 for hashing and 2,048 bits for RSA keys.

Signing certificates should also have a maximum validity period of 5 years.

10.6 Signature data elements

All messages, including the error messages, with the exception of redirects, are signed using an electronic signature. The electronic signature guarantees the authenticity of the sender, non-repudiation and the integrity of the message. The digital signature is an XML Signature data element that is defined in the XML-Signature Syntax and Processing W3C Recommendation 12 February 2002. See Table 8 for the Schema location. All attributes and elements of the Signature element are listed in the Table 32. The elements and attributes relevant for creating the signature in all iDx messages and SAML Signature are described below; other elements should not be used.

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

Signature

Yes

Root

+ SignedInfo

Yes

Contains SignedInfo sub-elements

++ CanonicalizationMethod

Yes

Must have one attribute

++ @algorithm

Yes

The XML content that will be signed has to be canonicalized. Canonicalization (c14n) is a process for converting data that has more than one possible representation into a canonical form.

Must be: http://www.w3.org/2001/10/xml-exc-c14n#"

++ SignatureMethod

Yes

Must have one attribute

++ @algorithm



For all signing RSA with SHA256 must be used as signature algorithm.

Must be: "http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"

++ Reference

Yes

Contains Reference sub-elements

++ Reference@URI

Yes

Attribute of Reference which must be empty.

This indicates that the entire XML document will be signed.

must be: “”

+++ Transforms

Yes

Contains Transforms sub-elements. This is a list of Transform elements, each of which specifies a processing step before feeding the document to the digest algorithm. All messages use an enveloped signature: the signature is contained within the signed document. A transform is required to remove the signature from the signed data

++++ Transform

 

Must have one attribute

++++ Transform@algorithm



Must be: http://www.w3.org/2000/09/xmldsig#enveloped-signature

++++ Transform

 

Must have one attribute

++++ Transform@algorithm



Must be:http://www.w3.org/2001/10/xml-exc-c14n#"

+++ DigestMethod

 

Must have one attribute

+++ @algorithm

 

This element specifies the hashing algorithm used (SHA256).

Must be: "http://www.w3.org/2001/04/xmldsig-more#rsa-sha256

+++ DigestValue

Yes

The base64 value of the hash of the entire document

+ SignatureValue

Yes

The value of the electronic signature of the Merchant

+ KeyInfo

Yes

Contains KeyInfo sub-elements

++ KeyName

Yes

This value holds the fingerprint which indicates the certificate to be used for validating the signature.

The certificate must be referenced using a fingerprint of the X.509 certificate of the Merchant, Acquirer or Issuer alike. The fingerprint must be calculated according to the following formula HEX(SHA-1(DER certificate))

Table 32: Elements/attributes of the Signature

The signing of the SAML 2.0 Assertion is different that instead of the fingerprint of the X.509 certificate the entire certificate of the Issuer is added. Also the @URI attribute of the Reference element should reference to the @ID attribute of the Assertion. This yields to the following change with respect to the Signature, while all other elements and attributes are the same as in Table 32:

Element/attributes

Mandatory

Contents

Element/attributes

Mandatory

Contents

Signature

Yes

Root

+ SignedInfo/Reference@URI

Yes

Must reference to the Assertion element.

Must be: The value of the @ID attribute of the Assertion.

+ KeyInfo

Yes

Contains KeyInfo sub-elements

++ X509Data

Yes

Contains X509Data sub-elements

+++ X509SubjectName

No

Contains the name of the certificate holder

+++ X509Certificate

Yes

Contains entire X.509 certificate of the Validation Service.

Table 34: Signature changes with respect to signing the SAML Assertion

11 Presentation of iDIN 

11.1 General

There are some requirements regarding the presentation of iDIN on the Merchant’s website. The main purpose of these requirements is to create a uniform user experience for Consumers whenever they use iDIN, regardless of which Merchant’s website they use. The requirements are further explained in the following paragraphs.

The Merchant bears primary responsibility for initiating the iDIN process and for the communication to the Consumer regarding the status of this process. Merchants who offer iDIN to their customers must include iDIN in their lists of authentication methods (if any). iDIN must be presented in the list of methods in such a way that it receives at least the same amount of attention as all other competitors.

In addition, an iDIN transaction (of any kind) must always be recognisable as such to the Consumer. This means that a Merchant must make sure in the design of their implementation of iDIN that iDIN and the start of an iDIN process are recognisable as such. The Merchant must also distinguish clearly between the processes (authentication, gather attributes or age verification) of different iDIN services. If a Merchant offers iDIN to Consumers to sign, the Merchant must indicate this clearly to the Consumer.

11.2 Transaction flow

When the Consumer chooses to use iDIN, the Consumer should immediately be presented with the Issuer selection list without any intermediate screens being displayed by the Merchant (e.g. Consumer login and/or registration screens). And when the Consumer has selected the required Issuer, he or she should be immediately redirected to the online bank environment of the selected Issuer (based on the issuerAuthenticationURL the Merchant has received in the AcquirerTrxRes).

11.3 Redirect to Issuer

The Merchant needs to perform the redirect to the Issuer, from the browser window where the Consumer selected the Issuer. The complete page of the Merchant will be replaced by the complete page of the selected bank. Therefore it is not allowed to open the redirect to the Issuer in a new browser window. However, it is allowed to open a new window, with visible address bar, before the Consumer selects his bank from the Issuer list.

11.4 Frames

Frames used on the Merchant’s site are allowed. The page of the Issuer will remove these frames using a frame busting technique. This will allow the Consumer to verify whether the transaction is really taking place at the bank chosen from the Issuer list. After the redirect to the Merchant, the Merchant must completely rebuild the Merchant page to show the Merchant’s confirmation of reception of the iDIN Authentication/attributes.

11.5 New Window

The iDIN authentication may take place in a new browser window, as long as the Merchant makes this window appear at (or before) the moment the Consumer chooses the authentication method. A new window is only allowed if initiated by the Consumer (no pop-ups are allowed). The complete transaction flow must take place in this window, including the Merchant’s confirmation of receiving the iDIN authentication/attributes. The new window must also contain an address bar that allows the Consumer to check the Internet address URL and SSL-certificate of the Issuer. During the transaction flow it should not be possible for the Consumer to initiate another transaction through the Merchant’s original browser window.

The Mobile iDIN process may redirect the Consumer to a different mobile page or app as part of the transaction. The Merchant should strive to keep the Consumer on one browser page as much as possible but it is not allowed to make use of an in-app browser in the Merchant app (see Chapter 10 for more details). In those cases where changing to another app or window is necessary (such as the redirect to the Issuer) the Consumer should be informed beforehand in order to avoid confusion (e.g.: “You are being redirected to the (mobile) website or the app of your bank” or in Dutch “U wordt doorverwezen naar de (mobiele) website of app van uw bank”).

11.6 Issuer list

The Issuer list has to be presented as described in Section 9.4.

11.7 Banners and logo's

This information shall be made available on idin.nl.

11.8 Requirements and recommendation for Merchant screens

This section describes requirements and recommendations for iDIN related texts on the Merchant website. Note that some information is only available in Dutch.

11.8.1 Display last login

If a Consumer logs into the website of the Merchant using iDIN, the Merchant is strongly recommended to show the date and time of the previous login (in general, so not specifically the last iDIN login), e.g. ‘Welcome, the last time you were logged in was on October 5 2015 at 15:41’. The Merchant may determine the exact text. This makes it possible for the Consumer to verify if this matches the moment of his/her last visit.

11.8.2 Explaining iDIN to Consumers

Merchants can use the following texts to explain iDIN to their users. These texts are only available in Dutch.

Explanation of iDIN to the Consumer

  • Short version: Makkelijk en veilig online identificeren met uw bank.
    Long version (preferred): Met iDIN kunt u zich online identificeren bij een bedrijf of instelling. Gemakkelijk, vertrouwd en veilig met de inlogmethode van uw bank.

Explanation of the advantages of iDIN

  1. Makkelijk en veilig online identificeren.

  2. Met de vertrouwde inlogmethode van uw bank.

  3. Eén manier van inloggen bij bedrijven en instellingen.

  4. Geen aparte gebruikersnamen en wachtwoorden meer onthouden.

  5. Zelf invullen van persoonlijke gegevens is niet meer nodig.

iDIN provides different types of services, which have been divided into the following three product types:

  1. Gegevens verstrekken: The Consumer chooses iDIN to provide attributes and/or an ID to the Merchant, with or without the creation of a user account. The Merchant requests this service, either with or without the BIN. This also includes for example the provisioning of the date of birth or name/address attributes with/without BIN;

  2. Inloggen: The Consumer uses iDIN to login. No attributes are provided to the Merchant, just the BIN;

  3. Leeftijd bevestigen: Verification that the age is above 18 year (the attribute 18orOlder is requested, with or without the BIN). This can also be used for verification of the age below 18 years.

  4. Ondertekenen: The Consumer chooses iDIN to sign documents using Issuer issued credentials. 

Table 34 shows the recommended texts for the Merchant website. The referral page is the webpage where the Consumer chooses to use iDIN. The returnpage is the webpage to which the Consumer returns, after he has approved the iDIN transaction at his own bank.

Product type

Recommended text for referral webpage Merchant

Recommended text for returnpage Merchant

Product type

Recommended text for referral webpage Merchant

Recommended text for returnpage Merchant

1  Gegevens verstrekken

  • Maak uw account aan met iDIN

  • Gegevens verstrekken/versturen met iDIN

  • Uw gegevens zijn succesvol ontvangen

  • Wij hebben de volgende gegevens ontvangen: [overzicht gegevens]

2  Inloggen

  • Inloggen met iDIN



  • U bent ingelogd met iDIN

  • Tonen laatste inlog (verplicht)

3 Leeftijd bevestigen

Leeftijd bevestigen met iDIN



  • Bedankt voor het bevestigen van uw leeftijd

  • Direct toegang tot de site



4 Ondertekenen

  • Onderteken uw documenten met iDIN

  • Gegevens verstrekken/versturen met iDIN

  • Uw documenten zijn succesvol ondertekend

  • Wij hebben de volgende gegevens ontvangen: [overzicht gegevens]

Table 34: Recommendation Merchant texts per product type

11.9 Validation Service front-end

The following described process is outside the scope of the Merchant implementation. It is provided in this document to give insight in the Consumer’s experience of iDIN.

The Issuer (Validation Service) bears primary responsibility for handling the iDIN process and for communicating with the Consumer regarding the status of the process of the iDIN transaction. The page sequence and layout (from redirect from Merchant to Issuer until redirect back to Merchant) are determined by the Validation Service. The following conditions must be met:

  • After selecting his Issuer at the Merchant website, the Consumer is redirected to the selected Issuer’s Validation Service website. In the active browser window, the complete page of the Merchant is replaced by the complete page of the selected Validation Service. Alternatively the Validation Service can choose, based on the header information received from the Consumer, to automatically redirect the Consumer to its mobile payment website or mobile payment app. Criteria for choosing which Consumers/devices are redirected to which channels are left to the Validation Service;

  • Optionally, the Validation Service may allow the Consumer to choose a different channel from the one chosen automatically, if the Validation Service offers multiple channels available to the Consumer. If this option is offered and used by the Consumer a second redirect takes place to the authentication website or application of choice;

  • At all times during an iDIN process, it must be clear to the Consumer that he is about to start an iDIN transaction. Therefore, the Validation Service must display the iDIN logo on every Validation Service web/mobile application page shown in the iDIN process;

  • The Validation Service will not display any information unrelated and irrelevant to the iDIN transaction, that could distract the Consumer from completing the process on the website or in the mobile application. Information that is considered relevant is:

    • A help function offered by the Validation Service, providing the Consumer with an explanation or additional information regarding the iDIN service(s);

    • If the Issuer has a mobile application available then this may be offered for immediate download and activation during the iDIN process to Consumers that have been detected as using a mobile device but who have not yet downloaded the app. Note: downloading an application during the iDIN process may very well result in the process expiring if it exceeds the expiration period set by the Merchant;

  • The Validation Service facilitates all services of iDIN. The Validation Service must clearly indicate to the Consumer what iDIN service the Consumer is about to consent to;

  • The Validation Service will guarantee that the integrity and layout of the Validation Service website/mobile application is not altered when displaying the contents of textual fields (e.g. due to possible malicious content of the transaction information provided by a malicious Merchant);

  • All iDIN transaction related information (i.e. Transaction information, Consumer information and Merchant information, must be presented to the Consumer for approval;

  • During the iDIN transaction process, the Consumer can either consent to the provision of all attributes (so not per attribute set or individual attribute) or reject the entire request, with the exception of the telephone and email attributes which may be deselected by the Consumer, see Section 0;

  • During the iDIN transaction process, the Consumer is not allowed to change any of the information in the transaction details nor is he/she allowed to give partial consent, with the exception of the telephone and email attributes which may be deselected by the Consumer, see Section 0;

  • The Validation Service indicates clearly how the Consumer can approve and give his/her consent for the iDIN transaction;

  • The Consumer must be able to see all attributes and their values in order to give informed consent for providing the attributes to the Merchant. In order to retrieve this information, the Consumer must first be logged into Validation Service system. This enables the Validation Service to identify the Consumer and retrieve the right information;

  • The Validation Service indicates clearly how the Consumer can cancel the iDIN process;

  • As an option, the Validation Service iDIN application may show a message to the Consumer when he/she tries to cancel the iDIN transaction by using the browser close button or tries to navigate backwards or forwards by using the browser arrow buttons. The message may be shown because this can be considered undesired Consumer behaviour. In this message, the Consumer can be advised to cancel or complete the iDIN transaction in a proper way, using the cancel or confirmation facilities of the Validation Service iDIN application;

  • In case the Validation Service cannot suffice to the minimal requested attribute set, it may state to the Consumer what attributes are missing that are required to successfully complete the transaction and shorty explains which procedure must be followed to add in the missing information. The Validation Service is free, in choice and implementation, to provide instructions on how the Consumer can change his/her attributes;

  • After approval of the iDIN transaction, the Consumer must have the opportunity to instantaneously return to the Merchant where the iDIN transaction was initiated. This is achieved by incorporating a ‘Continue’ button. Clicking on this button takes the Consumer to the Merchant’s return URL provided during transaction initiation by the Merchant.

11.9.1 Approval information

iDIN offers different services that can be requested by the Merchant with the RequestedServiceID. Each service is coupled to one of three product types. Depending on the requested service, the Issuer presents a different text to the Consumer. Table 35 shows these texts, with the following remarks:

  • Texts and elements that are always shown are indicated in bold. For illustrative purposes an example is given, however the exact formulation of the sentences can be different for each Issuer;

  • ‘Voor/Inzake TradeName’ is only shown when the trade name is present;

  • The mandatory texts and elements are shown before and/or after the Consumer has logged into the Issuer domain;

  • The Validation Service shows all Consumer attributes (for product type 1 and 3) that are requested by the Merchant. Subsequently, the Consumer can approve that the Issuer provides these attributes to the Merchant. The TransientID, Consumer.BIN and Consumer.DeprecatedBIN shall not be presented to the Consumer. All other Consumer attributes are always shown.

Product type

Issuer terms that are always shown

Example

Product type

Issuer terms that are always shown

Example

1  Gegevens verstrekken

  • Gegevens verstrekken/versturen

  • Merchant.Name (voor/inzake Merchant.TradeName)



U gaat de volgende gegevens verstrekken aan Merchant.Name (inzake Merchant.TradeName):

[overzicht gegevens] bijvoorbeeld:

Naam: Pietje Puk

Adres: Dorpstraat 1 1234AB Ons dorp

2  Inloggen

  • Inloggen

  • Merchant.Name (voor/inzake Merchant.TradeName)



U gaat inloggen bij Merchant.Name (inzake Merchant.TradeName)

3 Leeftijd bevestigen

  • Leeftijd bevestigen

  • Merchant.Name (voor/inzake Merchant.TradeName)

U bevestigt uw leeftijd aan Merchant.Name (inzake Merchant.TradeName)

[overzicht gegevens] bijvoorbeeld:

18 jaar of ouder: JA



4 Ondertekenen

  • Gegevens verstrekken/versturen

  • Ondertekening/ondertekenen

  • Merchant.Name (voor/inzake Merchant.TradeName)

U gaat de volgende gegevens verstrekken aan Merchant.Name (voor/inzake Merchant.TradeName) in het kader van ondertekening van een document:

[overview attributes] (for example):

Naam: Pietje Puk

Adres: Dorpstraat 1 1234AB Ons dorp

Table 35: Mandatory texts on the Issuer screens per product type

The following screenshot provides an example of the iDIN approval website or mobile application screen for authentication service plus providing attributes.

Figure 4: Example of transaction approval or mobile app screen

12 Appendix A: Error codes and cases 

In case something goes wrong on iDx level an AcquirerErrorRes with the appropriate errorCode is returned to the Merchant. If there is an error within the SAML messages an iDx errorCode AP3000 is return and a container is present with an SAML (error) Response, as outlined in Section 12.2.

12.1 iDx error codes

The Error.errorCode is composed of:

  • A category (two letters)

  • A number (four digits)

The following categories are distinguished:

Category

Meaning

Category

Meaning

IX

Invalid XML and all related problems.
Such as incorrect encoding, invalid version, otherwise unreadable.

SO

System maintenance.
The errors that are communicated in the event of system maintenance or system failure. Also covers the situation where new requests are no longer being accepted but requests already submitted will be dealt with (until a certain time).

SE

Security and authentication errors.
Incorrect authentication methods and expired certificates.

BR

Field errors.
Additional information on incorrect fields.

AP

Application errors.
Errors relating to IDs, transaction, expiration period and iDIN specific errors

Table 36: Error code categories

The following iDx error codes exist:

errorCode

errorMessage

errorDetail

Occurs in

errorCode

errorMessage

errorDetail

Occurs in

IX1100

Received XML not valid

See 1)

A’(X), B’(X), F’(X)

IX1200

Encoding type not UTF-8

See 1)

A’(X), B’(X), F’(X)

IX1300

XML version number invalid

See 1)

A’(X), B’(X), F’(X)

IX1600

Mandatory value missing

See 1)

A’(X), B’(X), F’(X)

 

 

 

 

SO1000

Failure in system

See 2)

A’(X), B’(X), F’(X)

SO1100

Issuer unavailable

See 3)

B’(X), F’(X)

SO1200

System busy. Try again later

See 2)

A’(X), B’(X), F’(X)

SO1400

Unavailable due to maintenance

See 2)

A’(X), B’(X), F’(X)

 

 

 

 

SE2700

Invalid electronic signature

See 1)

A’(X), B’(X), F’(X)

 

 

 

 

BR1200

Version number invalid

See 1)

A’(X), B’(X), F’(X)

BR1205

ProductID invalid

See 1)

A’(X), B’(X), F’(X)

BR1210

Value contains non-permitted character

See 1)

A’(X), B’(X), F’(X)

BR1220

Value too long

See 1)

A’(X), B’(X), F’(X)

BR1230

Value too short

See 1)

A’(X), B’(X), F’(X)

BR1270

Invalid date/time

See 1)

A’(X), B’(X), F’(X)

BR1280

Invalid URL

See 1)

B’(X)

 

 

 

 

AP1100

Merchant.MerchantID unknown

See 1)

A’(X), B’(X), F’(X)

AP1200

Issuer.IssuerID unknown

See 1)

B’(X)

AP1300

Merchant.subID unknown

See 1)

A’(X), B’(X), F’(X)

AP1500

Merchant.MerchantID not active

See 1)

A’(X), B’(X), F’(X)

 

 

 

 

AP2600

Transaction does not exist

See 1)

F’(X)

AP2920

Expiration period is not valid

See 1)

B’(X)

AP3000

iDIN specific error

 

See 1)

A’(X), B’(X), F’(X)

Table 37: Error codes

The field errorDetail in the table above contains one of the values shown in the table below.  The italic printed words will be replaced by actual values, as indicated.

Indication

errorDetail

Indication

errorDetail

1)

Field generating error: location-reference in XML message

2)

System generating error: Issuer/Acquirer

3)

System generating error: Name of Issuer

Table 38: errorDetail

12.2 SAML error codes

To communicate to the Merchant that an error has occurred in the SAML message, the SAML Status element is used which has the following structure:

1 2 3 4 5 6 <samlp:Status xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">> <samlp:StatusCode Name=%First level status code%> <samlp:StatusCode Name=%Second level status code% /></samlp:StatusCode> <samlp:StatusMessage>Text determined by Routing or Validation Service</samlp:StatusMessage> </samlp:Status>

AML defines two level of status codes. The first level status code can have the values as shown in the Table below.

StatusCode@Value

Description

StatusCode@Value

Description

urn:oasis:names:tc:SAML:2.0:status:Success

The request succeeded.

Not used in case an error has occured

urn:oasis:names:tc:SAML:2.0:status:Requester

The request could not be performed due to an error on the part of the requester.

Table 39: First level SAML status codes

The second level status code is present for the cases as discussed in Section 12.2. There are several standard values for the SAML second level status code, and some defined values that are only used within the iDIN domain. The possible values for the second level status code within iDIN are listed in the Table below.

StatusCode@Value

Description

StatusCode@Value

Description

urn:oasis:names:tc:SAML:2.0:status:

RequestUnsupported

The request could not be executed because the requested BankID.ServiceID or BankID.LOA is not supported.

This value is only used in combination with the first level status code value urn:oasis:names:tc:SAML:2.0:status:Requester

urn:oasis:names:tc:SAML:2.0:status:

InvalidAttrNameOrValue

The request could not be executed because unexpected or invalid content was encountered within a SAML element.

It is used when the contents or attribute value of a SAML element is not in line with the iDIN specifications, other than BankID.ServiceID or BankID.LOA. E.g. wrong formatting, incorrect version etc.

This value is only used in combination with the first level status code value urn:oasis:names:tc:SAML:2.0:status:Requester

urn:nl:bvn:bankid:1.0:status:

MismatchWithIDx



This status code is made specifically for iDIN

The request could not be executed because one or more fields inside the SAML AuthnRequest do not match the fields in the iDx message as required by the iDIN specifications. E.g. the MerchantID in the SAML AuthnRequest does not correspond to that in the iDx message.

This value is only used in combination with the first level status code value urn:oasis:names:tc:SAML:2.0:status:Requester

urn:oasis:names:tc:SAML:2.0:status:

RequestDenied

The request is denied because the Assertion is expired.

See next section for the correct use.

This value is only used in combination with the first level status code value urn:oasis:names:tc:SAML:2.0:status:Requester

urn:nl:bvn:bankid:1.0:status:Success

This status code is made specifically for iDIN

Present when the Validation Service has delivered all attributes conform the minimal set as defined in Section 8.5

urn:nl:bvn:bankid:1.0:status:

IncompleteAttributeSet

This status code is made specifically for iDIN

The request has been delivered, however not all of the requested Consumer attributes could be delivered according to the minimal set as defined in Section 8.5, or the telephone and/or email address are deselected by the Consumer, see Section 0. The element DeliveredServiceID either indicates which attributes are delivered conform the minimal set, or is equal to ‘0’ if the Issuer was unable to determine this. In both cases it is not equal to the RequestedServiceID

Table 40: Second level SAML status codes

12.3   SAML error cases

There are two cases where a SAML Response is returned with a first level status code not equal to “urn:oasis:names:tc:SAML:2.0:Success” but equal to “urn:oasis:names:tc:SAML:2.0:Requester”.

  1. There is some type of error in the AuthnRequest between the Merchant and the Routing Service. This AuthnRequest is embedded inside the container of the AcquirerTrxReq (B):
    For this case on iDx level an AcquirerErrorRes (B’(X)) is returned to the Merchant with a SAML Response in the container. The iDx errorCode equals AP3000 with an errorMessage ‘Product specific error’. The second level status code depends on the type of error that has occurred, see above table.

  2. The Merchant has requested the Status, however the Assertion is expired. This can occur when the Consumer has successfully authenticated and approved the transaction, however the Merchant has not succeeded in requesting the status within 30 seconds from the moment the Consumer has returned to the website of the Merchant.
    For this case a normal AcquirerStatusRes is returned to the Merchant. The iDx Transaction.status of this message equals “Success”. However the SAML Response does not contain an Assertion, but has the structure as discussed in Table 28: Elements/attributes inside the container of AcquirerErrorRes. It has a second level status code value of “urn:oasis:names:tc:SAML:2.0:status:RequestDenied”.

12.4 Issuer cannot provide all attributes conform minimal set or deselection of telephone or email

When the Issuer cannot deliver all requested attributes conform the minimal set (or the telephone and or email address are deselected by the Consumer), the following shall be done:

  • A normal SAML Response is returned. The first level status code is “urn:oasis:names:tc:SAML:2.0:Success”;

  • If the Consumer de-selects his/her telephone number and/or email address, then these are not returned to the Merchant;

  • The Issuer returns all other attributes that are available in the requested categories;

  • Instead of the second SAML status code “urn:nl:bvn:bankid:1.0:status:Success” the second SAML status code “urn:nl:bvn:bankid:1.0:status:IncompleteAttributeSet” is used;

  • The DeliveredServiceID shall indicate which attribute categories are delivered conform the minimal set as defined in Section 5. If the Issuer cannot determine the DeliveredServiceID it must use the value ‘0’.

Example:

  • The Merchant has requested the date of birth and all address attributes of a Consumer with RequestedServiceID 1472;

  • When the Issuer processes the request, its systems detects the address attributes cannot be delivered conform the minimal set as defined in Section 5 (it has the consumer.postalcode, consumer.city, consumer.streetname but is missing the consumer.houseno. Therefore, it cannot match any of the five possible options as defined in Section 8.5.

  • The Issuer calculates the DeliveredServiceID that corresponds to the requested attributes categories it can deliver conform the minimal set (in this case 448 which indicates the date of birth is delivered conform the minimal set);

  • The Issuer returns all requested attributes (date of birth and all attributes in the incomplete address category), and uses the second SAML status code “urn:nl:bvn:bankid:1.0:status:IncompleteAttributeSet” and the DeliveredServiceID equal to 448.

12.5 Consumer message

The Error.consumerMessage can contain one of four different standardised texts that are sent to the Merchant by the Routing Service, see Table 41. The Merchant must show the Error.consumerMessage to the Consumer on his website. The value of Error.consumerMessage is specified in the AcquirerErrorRes by the Acquirer.

Situation

Message to be shown to Consumer (English)

Message to be shown to Consumer  (Dutch)

Situation

Message to be shown to Consumer (English)

Message to be shown to Consumer  (Dutch)

Error occurred in sending or receiving message A, A’, B, B’

It is currently not possible to use iDIN. Please try again later.

Het is op dit moment niet mogelijk om iDIN te gebruiken. Probeer het later nog een keer.

Error occurred in sending or receiving message F, F’’

It is currently not possible to use iDIN. Please try again later.

Het is op dit moment niet mogelijk om iDIN te gebruiken. Probeer het later nog een keer.

Error occurred because of unavailability of Validation Service (SO1000, SO1100, SO1200 , SO1400 or no response received from Validation Service by Routing Service after sending message C)

The selected bank is currently unavailable. Please try again later.

De geselecteerde bank is op dit moment niet beschikbaar. Probeer het later nog een keer.

Error occurred because of unavailability of Validation Service (see above) AND additional information is available from the Notification System

The selected bank is currently unavailable due to maintenance until projected time of [DateTime received from the Notification System].

Please try again later.

De geselecteerde bank is op dit moment niet beschikbaar i.v.m. onderhoud tot naar verwachting [DateTime ontvangen van Notification System].

Probeer het later nog een keer.

Table 41: Consumer messages

13   Appendix B: Message examples

Most of the example messages given here only use the default method of namespace declaration. At the end of the appendix one example is given of a message with namespace prefixes (this message does not contain an information container, it is merely meant to signify the use of namespace prefixes). NB:

  • Signatures are examples and don’t validate against the messages;

  • The examples are not necessarily related to each other.

13.1 DirectoryReq (A)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 <?xml version="1.0" encoding="UTF-8"?> <DirectoryReq version="1.0.0" productID="NL:BVN:BankID:1.0" xmlns=" http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <createDateTimestamp>2001-12-17T09:30:47.123Z</createDateTimestamp> <Merchant> <merchantID>1234123456</merchantID> <subID>1</subID> </Merchant> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <Reference URI=""> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <DigestValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</DigestValue> </Reference> </SignedInfo> <SignatureValue> IELLwKSGFMk64US23YrpZ8//hJ8DeJEtYht5knlxJvBOr8dcI+aJTBq+YtyzP9ClcK62Obs5aynHBE/GPHZShuMw+8WHq4fCMInOwKURgwjDOz8UYaIMqG0Ojiz8dFYGn+dH2lL0QVss4jmIIAD8MCijb27oqij6PclXw9Y9veI= </SignatureValue> <KeyInfo> <KeyName>7D665C81ABBE1A7D0E525BFC171F04D276F07BF2</KeyName> </KeyInfo> </Signature> </DirectoryReq>

13.2 DirectoryRes (A’)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 <?xml version="1.0" encoding="UTF-8"?> <DirectoryRes version="1.0.0" productID=" NL:BVN:BankID:1.0" xmlns=" http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <createDateTimestamp>2001-12-17T09:30:47.123Z</createDateTimestamp> <Acquirer> <acquirerID>1234</acquirerID> </Acquirer> <Directory> <directoryDateTimestamp>2004-11-10T10:15:12.123Z</directoryDateTimestamp> <Country> <countryNames>Nederland</countryNames> <Issuer> <issuerID>BANKNL2U</issuerID> <issuerName>Bank 1</issuerName> </Issuer> <Issuer> <issuerID>BANANL2U</issuerID> <issuerName>Bank 2</issuerName> </Issuer> <Issuer> <issuerID>BANBNL2UXXX</issuerID> <issuerName>Bank 3</issuerName> </Issuer> <Issuer> <issuerID>BANCNL2U</issuerID> <issuerName>Bank 4</issuerName> </Issuer> </Country> <Country> <countryNames>België/Belgique</countryNames> <Issuer> <issuerID>BANKBE2U</issuerID> <issuerName>Banque 1</issuerName> </Issuer> </Country> </Directory> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256" /> <Reference URI=""> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" /> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256" /> <DigestValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</DigestValue> </Reference> </SignedInfo> <SignatureValue> IELLwKSGFMk64US23YrpZ8//hJ8DeJEtYht5knlxJvBOr8dcI+aJTBq+YtyzP9ClcK62Obs5aynHBE/GPHZShuMw+8WHq4fCMInOwKURgwjDOz8UYaIMqG0Ojiz8dFYGn+dH2lL0QVss4jmIIAD8MCijb27oqij6PclXw9Y9veI= </SignatureValue> <KeyInfo> <KeyName>7D665C81ABBE1A7D0E525BFC171F04D276F07BF2</KeyName> </KeyInfo> </Signature> </DirectoryRes>

13.3 AcquirerTrxReq (B)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 <?xml version="1.0" encoding="UTF-8"?> <AcquirerTrxReq version="1.0.0" productID="NL:BVN:BankID:1.0" xmlns="http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <createDateTimestamp>2015-01-01T09:30:00.123Z</createDateTimestamp> <Issuer> <issuerID>BANKNL2U</issuerID> </Issuer> <Merchant> <merchantID>1234123456</merchantID> <subID>1</subID> <merchantReturnURL>https://merchantwebsite.nl/returnPage.php?param1=true&param2=3</merchantReturnURL> </Merchant> <Transaction> <expirationPeriod>PT5M</expirationPeriod> <language>nl</language> <entranceCode>1234567890abcdefghijABCDEFGHIJ1234567890</entranceCode> <container> <samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" AttributeConsumingServiceIndex="21952" ID="REF1234567890" IssueInstant="2015-01-01T09:30:00Z" Version="2.0" ProtocolBinding="nl:bvn:bankid:1.0:protocol:iDx" AssertionConsumerServiceURL="https://merchantwebsite.nl/returnPage.php?param1=true&param2=3"> <saml:Issuer>1234123456</saml:Issuer> <samlp:RequestedAuthnContext Comparison="minimum"> <saml:AuthnContextClassRef>nl:bvn:bankid:1.0:loa3</saml:AuthnContextClassRef> </samlp:RequestedAuthnContext> </samlp:AuthnRequest> </container> </Transaction> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <Reference URI=""> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <DigestValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</DigestValue> </Reference> </SignedInfo> <SignatureValue>IELLwKSGFMk64US23YrpZ8//hJ8DeJEtYht5knlxJvBOr8dcI+aJTBq+YtyzP9ClcK62Obs5aynHBE/GPHZShuMw+8WHq4fCMInOwKURgwjDOz8UYaIMqG0Ojiz8dFYGn+dH2lL0QVss4jmIIAD8MCijb27oqij6PclXw9Y9veI=</SignatureValue> <KeyInfo> <KeyName>7D665C81ABBE1A7D0E525BFC171F04D276F07BF2</KeyName> </KeyInfo> </Signature> </AcquirerTrxReq>

13.4 AcquirerTrxRes (B’)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 <?xml version="1.0" encoding="UTF-8"?> <AcquirerTrxRes version="1.0.0" productID="NL:BVN:BankID:1.0" xmlns=" http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <createDateTimestamp>2001-12-17T09:30:47.123Z</createDateTimestamp> <Acquirer> <acquirerID>1234</acquirerID> </Acquirer> <Issuer> <issuerAuthenticationURL>https://issuer.nl?param=true&paramRandom=123456789012345678901234567890</issuerAuthenticationURL> </Issuer> <Transaction> <transactionID>1234123456789012</transactionID> <transactionCreateDateTimestamp>2001-12-17T09:30:47.123Z</transactionCreateDateTimestamp> </Transaction> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <Reference URI=""> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <DigestValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</DigestValue> </Reference> </SignedInfo> <SignatureValue> IELLwKSGFMk64US23YrpZ8//hJ8DeJEtYht5knlxJvBOr8dcI+aJTBq+YtyzP9ClcK62Obs5aynHBE/GPHZShuMw+8WHq4fCMInOwKURgwjDOz8UYaIMqG0Ojiz8dFYGn+dH2lL0QVss4jmIIAD8MCijb27oqij6PclXw9Y9veI= </SignatureValue> <KeyInfo> <KeyName>7D665C81ABBE1A7D0E525BFC171F04D276F07BF2</KeyName> </KeyInfo> </Signature> </AcquirerTrxRes>

13.5 AcquirerStatusReq (F)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 <?xml version="1.0" encoding="UTF-8"?> <AcquirerStatusReq version="1.0.0" productID="NL:BVN:BankID:1.0" xmlns=" http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <createDateTimestamp>2001-12-17T09:30:47.123Z</createDateTimestamp> <Merchant> <merchantID>1234123456</merchantID> <subID>1</subID> </Merchant> <Transaction> <transactionID>1234123456789012</transactionID> </Transaction> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <Reference URI=""> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <DigestValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</DigestValue> </Reference> </SignedInfo> <SignatureValue> IELLwKSGFMk64US23YrpZ8//hJ8DeJEtYht5knlxJvBOr8dcI+aJTBq+YtyzP9ClcK62Obs5aynHBE/GPHZShuMw+8WHq4fCMInOwKURgwjDOz8UYaIMqG0Ojiz8dFYGn+dH2lL0QVss4jmIIAD8MCijb27oqij6PclXw9Y9veI= </SignatureValue> <KeyInfo> <KeyName>7D665C81ABBE1A7D0E525BFC171F04D276F07BF2</KeyName> </KeyInfo> </Signature> </AcquirerStatusReq>

13.6 AcquirerStatusRes (F’) Unencrypted

Note

Note: this message will never be sent/received, but is provided for illustrative purposes only.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 <?xml version="1.0" encoding="UTF-8"?> <AcquirerStatusRes version="1.0.0" productID="NL:BVN:BankID:1.0" xmlns="http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <createDateTimestamp>2015-01-01T09:30:47.123Z</createDateTimestamp> <Acquirer> <acquirerID>1234</acquirerID> </Acquirer> <Transaction> <transactionID>1234123456789012</transactionID> <status>Success</status> <statusDateTimestamp>2015-01-01T09:30:47.123Z</statusDateTimestamp> <container> <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="RES-1234123456789012" InResponseTo="REF1234567890" Version="2.0" IssueInstant="2015-01-01T09:30:47.123Z”> <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">1234 </saml:Issuer> <samlp:Status> <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"> <samlp:StatusCode Value=”urn:nl:bvn:bankid:1.0:status:Success”/></samlp:StatusCode> </samlp:Status> <saml:Assertion xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Version="2.0" ID="_a75adf55-01d7-40cc-929f-dbd8372ebdfc" IssueInstant="2015-01-01T09:30:47.123Z”> <saml:Issuer>BANKNL2U</saml:Issuer> <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <ds:SignedInfo> <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <ds:Reference URI="#_a75adf55-01d7-40cc-929f-dbd8372ebdfc"> <ds:Transforms> <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> </ds:Transforms> <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <ds:DigestValue>AA+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</ds:DigestValue> </ds:Reference> </ds:SignedInfo> <ds:SignatureValue>AAAAwKSGFMk64US23YrpZ8//hJ8DeJEtYht5knlxJvBOr8dcI+aJTBq+YtyzP9ClcK62Obs5aynHBE/GPHZShuMw+8WHq4fCMInOwKURgwjDOz8UYaIMqG0Ojiz8dFYGn+dH2lL0QVss4jmIIAD8MCijb27oqij6PclXw9Y9veI=</ds:SignatureValue> <ds:KeyInfo> <ds:X509Data> <ds:X509Certificate>MIICyjCCAjOgAwIBAgICAnUwDQYJKoZIhvcNAQEEBQAwgakxCzAJBgNVBAYTAlVTMRIwEAYDVQQIEwlXaXNjb25zaW4xEDAOBgNVBAcTB01hZGlzb24xIDAeBgNVBAoTF1VuaXZlcnNpdHkgb2YgV2lzY29uc2luMSswKQYDVQQLEyJEaXZpc2lvbiBvZiBJbmZvcm1hdGlvbiBUZWNobm9sb2d5MSUwIwYDVQQDExxIRVBLSSBTZXJ2ZXIgQ0EgLS0gMjAwMjA3MDFBMB4XDTAyMDcyNjA3Mjc1MVoXDTA2MDkwNDA3Mjc1MVowgYsxCzAJBgNVBAYTAlVTMREwDwYDVQQIEwhNaWNoaWdhbjESMBAGA1UEBxMJQW5uIEFyYm9yMQ4wDAYDVQQKEwVVQ0FJRDEcMBoGA1UEAxMTc2hpYjEuaW50ZXJuZXQyLmVkdTEnMCUGCSqGSIb3DQEJARYYcm9vdEBzaGliMS5pbnRlcm5ldDIuZWR1MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDZSAb2sxvhAXnXVIVTx8vuRay+x50z7GJjIHRYQgIv6IqaGG04eTcyVMhoekE0b45QgvBIaOAPSZBl13R6+KYiE7x4XAWIrCP+ c2MZVeXeTgV3Yz+USLg2Y+Jh4HxwkPFmZBctyXiUr6DxF8rvoP9W7O27rhRjE pmqOIfGTWQIDAQABox0wGzAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIFoDANBgkq hkiG9w0BAQQFAAOBgQBfDqEW+OI3jqBQHIBzhujN/PizdN7s/z4D5d3pptWDJf2n qgi7lFV6MDkhmTvTqBtjmNk3No7v/dnP6Hr7wHxvCCRwubnmIfZ6QZAv2FU78pLX8I3bsbmRAUg4UP9hH6ABVq4KQKMknxu1xQxLhpR1ylGPdiowMNTrEG8cCx3w/w==</ds:X509Certificate> </ds:X509Data> </ds:KeyInfo> </ds:Signature> <saml:Subject> <saml:NameID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">NLBANKsd45232432663dd34ja8sjsah439h28834HSh23h192h3 </saml:NameID> </saml:Subject> <saml:Conditions NotBefore="2015-01-01T09:30:47Z" NotOnOrAfter="2015-01-01T09:31:17.123Z”> <saml:AudienceRestriction> <saml:Audience>NL69ZZZ123456780000</saml:Audience> </saml:AudienceRestriction> <saml:OneTimeUse></saml:OneTimeUse> </saml:Conditions> <saml:AuthnStatement AuthnInstant="2015-01-01T09:30:47.123Z”> <saml:AuthnContext> <saml:AuthnContextClassRef>nl:bvn:bankid:1.0:loa3</saml:AuthnContextClassRef> <saml:AuthenticatingAuthority>BANKNL2U</saml:AuthenticatingAuthority> </saml:AuthnContext> </saml:AuthnStatement> <saml:AttributeStatement> <saml:Attribute Name=”urn:nl:bvn:bankid:1.0:bankid.deliveredserviceid"> <saml:AttributeValue>21952</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.gender"> <saml:AttributeValue>1</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.legallastname"> <saml:AttributeValue>Vries</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.preferredlastname"> <saml:AttributeValue>Vries-Jansen</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.partnerlastname"> <saml:AttributeValue>Jansen</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.legallastnameprefix"> <saml:AttributeValue>de</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.preferredlastnameprefix"> <saml:AttributeValue>de</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.initials"> <saml:AttributeValue>JV</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.dateofbirth"> <saml:AttributeValue>19850101</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.street"> <saml:AttributeValue>Gustav Mahlerplein</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.houseno"> <saml:AttributeValue>33</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.housenosuf"> <saml:AttributeValue>bis</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.addressextra"> <saml:AttributeValue>woonboot t.o. de Albert Heijn</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.postalcode"> <saml:AttributeValue>1082MS</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.city"> <saml:AttributeValue>Amsterdam</saml:AttributeValue> </saml:Attribute> <saml:Attribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Name="urn:nl:bvn:bankid:1.0:consumer.country"> <saml:AttributeValue>NL</saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement> </saml:Assertion> </samlp:Response> </container> </Transaction> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <Reference URI=""> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <DigestValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</DigestValue> </Reference> </SignedInfo> <SignatureValue>IELLwKSGFMk64US23YrpZ8//hJ8DeJEtYht5knlxJvBOr8dcI+aJTBq+YtyzP9ClcK62Obs5aynHBE/GPHZShuMw+8WHq4fCMInOwKURgwjDOz8UYaIMqG0Ojiz8dFYGn+dH2lL0QVss4jmIIAD8MCijb27oqij6PclXw9Y9veI=</SignatureValue> <KeyInfo> <KeyName>7D665C81ABBE1A7D0E525BFC171F04D276F07BF2</KeyName> </KeyInfo> </Signature> </AcquirerStatusRes>

13.7 AcquirerStatusRes (F’) Encrypted

Note

Note: this example only shows the first two encrypted attributes.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 ?xml version="1.0" encoding="UTF-8"?> <AcquirerStatusRes version="1.0.0" productID="NL:BVN:BankID:1.0" xmlns="http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <createDateTimestamp>2015-01-01T09:30:47.123Z</createDateTimestamp> <Acquirer> <acquirerID>1234</acquirerID> </Acquirer> <Transaction> <transactionID>1234123456789012</transactionID> <status>Success</status> <statusDateTimestamp>2015-01-01T09:30:47.123Z</statusDateTimestamp> <container> <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="RES-1234123456789012" InResponseTo="REF1234567890" Version="2.0" IssueInstant="2015-01-01T09:30:47.123Z”> <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">1234 </saml:Issuer> <samlp:Status> <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"> <samlp:StatusCode Value=”urn:nl:bvn:bankid:1.0:status:Success”/></samlp:StatusCode> </samlp:Status> <saml:Assertion xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Version="2.0" ID="_a75adf55-01d7-40cc-929f-dbd8372ebdfc" IssueInstant="2015-01-01T09:30:47.123Z”> <saml:Issuer>BANKNL2U</saml:Issuer> <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <ds:SignedInfo> <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <ds:Reference URI="#_a75adf55-01d7-40cc-929f-dbd8372ebdfc"> <ds:Transforms> <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> </ds:Transforms> <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <ds:DigestValue>AA+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</ds:DigestValue> </ds:Reference> </ds:SignedInfo> <ds:SignatureValue>VGhpcyBpcyBhIHRlc3QgbWVzc2FnZSE=</ds:SignatureValue> <ds:KeyInfo> <ds:X509Data> <ds:X509Certificate>MIICyjCCAjOgAwIBAgICAnUwDQYJKoZIhvcNAQEEBQAwgakxCzAJBgNVBAYTAlVTMRIwEAYDVQQIEwlXaXNjb25zaW4xEDAOBgNVBAcTB01hZGlzb24xIDAeBgNVBAoTF1VuaXZlcnNpdHkgb2YgV2lzY29uc2luMSswKQYDVQQLEyJEaXZpc2lvbiBvZiBJbmZvcm1hdGlvbiBUZWNobm9sb2d5MSUwIwYDVQQDExxIRVBLSSBTZXJ2ZXIgQ0EgLS0gMjAwMjA3MDFBMB4XDTAyMDcyNjA3Mjc1MVoXDTA2MDkwNDA3Mjc1MVowgYsxCzAJBgNVBAYTAlVTMREwDwYDVQQIEwhNaWNoaWdhbjESMBAGA1UEBxMJQW5uIEFyYm9yMQ4wDAYDVQQKEwVVQ0FJRDEcMBoGA1UEAxMTc2hpYjEuaW50ZXJuZXQyLmVkdTEnMCUGCSqGSIb3DQEJARYYcm9vdEBzaGliMS5pbnRlcm5ldDIuZWR1MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDZSAb2sxvhAXnXVIVTx8vuRay+x50z7GJjIHRYQgIv6IqaGG04eTcyVMhoekE0b45QgvBIaOAPSZBl13R6+KYiE7x4XAWIrCP+c2MZVeXeTgV3Yz+USLg2Y1on+Jh4HxwkPFmZBctyXiUr6DxF8rvoP9W7O27rhRjE pmqOIfGTWQIDAQABox0wGzAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIFoDANBgkqhkiG9w0BAQQFAAOBgQBfDqEW+OI3jqBQHIBzhujN/PizdN7s/z4D5d3pptWDJf2nqgi7lFV6MDkhmTvTqBtjmNk3No7v/dnP6Hr7wHxvCCRwubnmIfZ6QZAv2FU78pLX8I3bsbmRAUg4UP9hH6ABVq4KQKMknxu1xQxLhpR1ylGPdiowMNTrEG8cCx3w/w==</ds:X509Certificate> </ds:X509Data> </ds:KeyInfo> </ds:Signature> <saml:Subject> <saml:EncryptedID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/> <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <xenc:EncryptedKey Recipient="NL69ZZZ123456780000"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> </xenc:EncryptionMethod> <xenc:CipherData> <xenc:CipherValue>jenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBsVW+V=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedKey> </ds:KeyInfo> <xenc:CipherData> <xenc:CipherValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </saml:EncryptedID> </saml:Subject> <saml:Conditions NotBefore="2015-01-01T09:30:47Z" NotOnOrAfter="2015-01-01T09:31:17.123Z”> <saml:AudienceRestriction> <saml:Audience>NL69ZZZ123456780000</saml:Audience> </saml:AudienceRestriction> <saml:OneTimeUse></saml:OneTimeUse> </saml:Conditions> <saml:AuthnStatement AuthnInstant="2015-01-01T09:30:47.123Z”> <saml:AuthnContext> <saml:AuthnContextClassRef>nl:bvn:bankid:1.0:loa3</saml:AuthnContextClassRef> <saml:AuthenticatingAuthority>BANKNL2U</saml:AuthenticatingAuthority> </saml:AuthnContext> </saml:AuthnStatement> <saml:AttributeStatement> <saml:Attribute Name=”urn:nl:bvn:bankid:1.0:bankid.deliveredserviceid"> <saml:AttributeValue>21952</saml:AttributeValue> </saml:Attribute> <saml:EncryptedAttribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/> <ds:KeyInfo > <xenc:EncryptedKey Recipient="NL69ZZZ123456780000"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> </xenc:EncryptionMethod> <xenc:CipherData> <xenc:CipherValue>jenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBsVW+V=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedKey> </ds:KeyInfo> <xenc:CipherData> <xenc:CipherValue>BTeoxDflQ4yfR8KYFvwPVinVPqBsVW+VjenRyZVFCNf=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </saml:EncryptedAttribute> <saml:EncryptedAttribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/> <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <xenc:EncryptedKey Recipient="NL69ZZZ123456780000"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> </xenc:EncryptionMethod> <xenc:CipherData> <xenc:CipherValue>jenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBsVW+V=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedKey> </ds:KeyInfo> <xenc:CipherData> <xenc:CipherValue>nVPqBsVW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVi=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </saml:EncryptedAttribute> </saml:AttributeStatement> </saml:Assertion> </samlp:Response> </container> </Transaction> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <Reference URI=""> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <DigestValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</DigestValue> </Reference> </SignedInfo> <SignatureValue>IELLwKSGFMk64US23YrpZ8//hJ8DeJEtYht5knlxJvBOr8dcI+aJTBq+YtyzP9ClcK62Obs5aynHBE/GPHZShuMw+8WHq4fCMInOwKURgwjDOz8UYaIMqG0Ojiz8dFYGn+dH2lL0QVss4jmIIAD8MCijb27oqij6PclXw9Y9veI=</SignatureValue> <KeyInfo> <KeyName>7D665C81ABBE1A7D0E525BFC171F04D276F07BF2</KeyName> </KeyInfo> </Signature> </AcquirerStatusRes>

3.8 AcquirerErrorRes (B’(X))

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 ?xml version="1.0" encoding="UTF-8"?> <AcquirerStatusRes version="1.0.0" productID="NL:BVN:BankID:1.0" xmlns="http://www.betaalvereniging.nl/iDx/messages/Merchant-Acquirer/1.0.0" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <createDateTimestamp>2015-01-01T09:30:47.123Z</createDateTimestamp> <Acquirer> <acquirerID>1234</acquirerID> </Acquirer> <Transaction> <transactionID>1234123456789012</transactionID> <status>Success</status> <statusDateTimestamp>2015-01-01T09:30:47.123Z</statusDateTimestamp> <container> <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="RES-1234123456789012" InResponseTo="REF1234567890" Version="2.0" IssueInstant="2015-01-01T09:30:47.123Z”> <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">1234 </saml:Issuer> <samlp:Status> <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"> <samlp:StatusCode Value=”urn:nl:bvn:bankid:1.0:status:Success”/></samlp:StatusCode> </samlp:Status> <saml:Assertion xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Version="2.0" ID="_a75adf55-01d7-40cc-929f-dbd8372ebdfc" IssueInstant="2015-01-01T09:30:47.123Z”> <saml:Issuer>BANKNL2U</saml:Issuer> <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <ds:SignedInfo> <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <ds:Reference URI="#_a75adf55-01d7-40cc-929f-dbd8372ebdfc"> <ds:Transforms> <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> </ds:Transforms> <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <ds:DigestValue>AA+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</ds:DigestValue> </ds:Reference> </ds:SignedInfo> <ds:SignatureValue>VGhpcyBpcyBhIHRlc3QgbWVzc2FnZSE=</ds:SignatureValue> <ds:KeyInfo> <ds:X509Data> <ds:X509Certificate>MIICyjCCAjOgAwIBAgICAnUwDQYJKoZIhvcNAQEEBQAwgakxCzAJBgNVBAYTAlVTMRIwEAYDVQQIEwlXaXNjb25zaW4xEDAOBgNVBAcTB01hZGlzb24xIDAeBgNVBAoTF1VuaXZlcnNpdHkgb2YgV2lzY29uc2luMSswKQYDVQQLEyJEaXZpc2lvbiBvZiBJbmZvcm1hdGlvbiBUZWNobm9sb2d5MSUwIwYDVQQDExxIRVBLSSBTZXJ2ZXIgQ0EgLS0gMjAwMjA3MDFBMB4XDTAyMDcyNjA3Mjc1MVoXDTA2MDkwNDA3Mjc1MVowgYsxCzAJBgNVBAYTAlVTMREwDwYDVQQIEwhNaWNoaWdhbjESMBAGA1UEBxMJQW5uIEFyYm9yMQ4wDAYDVQQKEwVVQ0FJRDEcMBoGA1UEAxMTc2hpYjEuaW50ZXJuZXQyLmVkdTEnMCUGCSqGSIb3DQEJARYYcm9vdEBzaGliMS5pbnRlcm5ldDIuZWR1MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDZSAb2sxvhAXnXVIVTx8vuRay+x50z7GJjIHRYQgIv6IqaGG04eTcyVMhoekE0b45QgvBIaOAPSZBl13R6+KYiE7x4XAWIrCP+c2MZVeXeTgV3Yz+USLg2Y1on+Jh4HxwkPFmZBctyXiUr6DxF8rvoP9W7O27rhRjE pmqOIfGTWQIDAQABox0wGzAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIFoDANBgkqhkiG9w0BAQQFAAOBgQBfDqEW+OI3jqBQHIBzhujN/PizdN7s/z4D5d3pptWDJf2nqgi7lFV6MDkhmTvTqBtjmNk3No7v/dnP6Hr7wHxvCCRwubnmIfZ6QZAv2FU78pLX8I3bsbmRAUg4UP9hH6ABVq4KQKMknxu1xQxLhpR1ylGPdiowMNTrEG8cCx3w/w==</ds:X509Certificate> </ds:X509Data> </ds:KeyInfo> </ds:Signature> <saml:Subject> <saml:EncryptedID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/> <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <xenc:EncryptedKey Recipient="NL69ZZZ123456780000"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> </xenc:EncryptionMethod> <xenc:CipherData> <xenc:CipherValue>jenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBsVW+V=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedKey> </ds:KeyInfo> <xenc:CipherData> <xenc:CipherValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </saml:EncryptedID> </saml:Subject> <saml:Conditions NotBefore="2015-01-01T09:30:47Z" NotOnOrAfter="2015-01-01T09:31:17.123Z”> <saml:AudienceRestriction> <saml:Audience>NL69ZZZ123456780000</saml:Audience> </saml:AudienceRestriction> <saml:OneTimeUse></saml:OneTimeUse> </saml:Conditions> <saml:AuthnStatement AuthnInstant="2015-01-01T09:30:47.123Z”> <saml:AuthnContext> <saml:AuthnContextClassRef>nl:bvn:bankid:1.0:loa3</saml:AuthnContextClassRef> <saml:AuthenticatingAuthority>BANKNL2U</saml:AuthenticatingAuthority> </saml:AuthnContext> </saml:AuthnStatement> <saml:AttributeStatement> <saml:Attribute Name=”urn:nl:bvn:bankid:1.0:bankid.deliveredserviceid"> <saml:AttributeValue>21952</saml:AttributeValue> </saml:Attribute> <saml:EncryptedAttribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/> <ds:KeyInfo > <xenc:EncryptedKey Recipient="NL69ZZZ123456780000"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> </xenc:EncryptionMethod> <xenc:CipherData> <xenc:CipherValue>jenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBsVW+V=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedKey> </ds:KeyInfo> <xenc:CipherData> <xenc:CipherValue>BTeoxDflQ4yfR8KYFvwPVinVPqBsVW+VjenRyZVFCNf=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </saml:EncryptedAttribute> <saml:EncryptedAttribute xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Element"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/> <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <xenc:EncryptedKey Recipient="NL69ZZZ123456780000"> <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> </xenc:EncryptionMethod> <xenc:CipherData> <xenc:CipherValue>jenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBsVW+V=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedKey> </ds:KeyInfo> <xenc:CipherData> <xenc:CipherValue>nVPqBsVW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVi=</xenc:CipherValue> </xenc:CipherData> </xenc:EncryptedData> </saml:EncryptedAttribute> </saml:AttributeStatement> </saml:Assertion> </samlp:Response> </container> </Transaction> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> <Reference URI=""> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> <DigestValue>VW+VjenRyZVFCNfBTeoxDflQ4yfR8KYFvwPVinVPqBs=</DigestValue> </Reference> </SignedInfo> <SignatureValue>IELLwKSGFMk64US23YrpZ8//hJ8DeJEtYht5knlxJvBOr8dcI+aJTBq+YtyzP9ClcK62Obs5aynHBE/GPHZShuMw+8WHq4fCMInOwKURgwjDOz8UYaIMqG0Ojiz8dFYGn+dH2lL0QVss4jmIIAD8MCijb27oqij6PclXw9Y9veI=</SignatureValue> <KeyInfo> <KeyName>7D665C81ABBE1A7D0E525BFC171F04D276F07BF2</KeyName> </KeyInfo> </Signature> </AcquirerStatusRes>

14 Appendix C: iDx Merchant-Acquirer Schema

1 2 3 4