3 min read

eIDAS – Digitisation of the on-boarding process Part 2 - The Process

eIDAS – Digitisation of the on-boarding process Part 2 - The Process

In Part 1 of this series, we looked at the objectives or motives behind having an eIDAS-enabled digital onboarding process. In Part 2, we look at the actual process that is followed currently and a few examples of the nifty tools and tricks that some banks, financial institutions, and even independent app developers are using to digitize the customer onboarding process. The process can be further simplified using tools provided by eIDAS for electronic identification and authentication.

The process of on-boarding is broadly divided into four main categories, as follows:


This is the initial phase of the onboarding process, where a person or legal entity applies to become a customer. This involves the submission of documents that contain the various KYC attributes that are necessary for onboarding along with the application.



The submitted documents containing the KYC attributes are verified in this second phase. This involves verifying the document's authenticity and ensuring that it comes from a reliable source. It also includes an identity check, which means that the identity of the applicant is compared with the document submitted. Lastly, anti-fraud checks are performed to confirm that the person is not on any watchlists or other anti-fraud databases.

New Call-to-actionAn example of verification using an eIDAS-enabled process might go like this: The customer gets the link to a mobile application from the financial institution that (s)he has applied to. The procedure for submitting the ID proof is simple – just take a picture of your national ID card or passport along with a selfie of yourself via the app provided. The image then makes its way through the verification cycle. It may be compared against various databases that check the document number or customer name against criminal or watchlist databases, etc.

This process might also be performed with a laptop or a computer with a webcam. Some developers are also experimenting with a video format to provide an even higher level of security.



This is the process of recording and documenting the information in relevant formats.

Continuing our example of a mobile-based app, the collection process would involve the mobile app verifying the submitted ID proof and then storing the information in an encrypted format on its cloud-based storage. The customer can then send that information along with his profile to the financial institution. The saved information serves as a sort of verified digital ID containing all the relevant KYC information that is ready to be shared with any financial institution.



This is the on-going maintenance of the information. The KYC attributes may need to be updated in case of any changes. In accordance with applicable laws, periodic re-verification is also necessary.

For a mobile-based application, this process might involve the user updating any changes to it and the application and then submit it to the financial institution. This system has the advantage that the same verified and encrypted user information can be used to apply to multiple financial institutions by sending it along with the digital application.


Download white paper



References and Further Reading

Image: Onboarding, courtesy of Jane Quiglay, Flickr (CC BY 2.0)