iDIN is being replaced by itsme

In the coming years, the way people identify themselves online will change. Today, we know iDIN as the method that allows users to identify via their bank. This system will be replaced by itsme. This means that organizations using iDIN on their website, in their customer portal, or in the checkout will need to replace the integration with an itsme integration. Of course, we are closely monitoring all developments. As soon as there’s a clear upgrade path and concrete technical options available, we will proactively communicate this to our customers. We are happy to make sure the itsme implementation is technically sound and to provide guidance for a smooth transition to the new system. In this article, we explain the transition from iDIN to itsme.

What exactly is iDIN?

At the moment, we still use iDIN. It’s a service for login and online identification, with the user’s bank acting as a trusted source. When someone opens a bank account, the bank has already verified that person’s identity. With iDIN, that verification can, in a sense, be reused by the customer to identify themselves with other organizations. iDIN is an attractive solution. It reduces friction for organizations and provides more certainty about details such as a person’s name, address, and date of birth. It also offers benefits for customers, as they need to enter fewer details manually. iDIN is currently used by, among others, online stores, service providers, insurers, and online casinos.

How does iDIN work in practice?

If you currently use iDIN in your webshop, the process is quite simple. A customer can choose “identify with iDIN,” after which they select their bank and confirm the identification in the bank environment. In other words, the customer logs in to their online banking environment, and their identity is then confirmed to the webshop. The data is shared with the organization via iDIN. Only the data that’s relevant for identifying the person is shared. Information about transactions and balances is therefore not shared. In this way, iDIN makes online processes easier and more secure.

Why is iDIN being replaced by itsme?

iDIN has been acquired by itsme, and the choice has been made to build a future-proof platform. Digital identity is no longer intended to remain a solution tied to banks, but is shifting toward a broadly applicable and reusable identity system for the entire EU. The underlying reason is therefore roughly the same as why iDEAL is being replaced by Wero. This doesn’t mean that iDIN will stop existing overnight. Step by step, the transition will be introduced, so that iDIN will eventually be fully integrated into itsme.

What exactly is itsme?

itsme is not a new system. It has been used on a large scale in Belgium for many years. By far most adults in the country already use itsme. The app was developed by Belgian banks and telecom providers. In Belgium, it’s mainly used for public services and commercial services. In the Netherlands, itsme is not yet widely known, but that’s about to change. itsme ensures that, for online identification, you are less dependent on your banking app. With itsme, there will be a separate identification app that can be used in many different situations.

When will iDIN be replaced by itsme?

At this moment, there’s already a timeline for what is expected to happen when. For now, the transition from iDIN to itsme is set to start in the spring of 2026. From June 2026, it will be possible to use both iDIN and itsme with participating services. After that, iDIN will remain available for a period, so people can easily get used to itsme. The ultimate goal is for iDIN to be fully replaced by itsme in 2028. For organizations, it’s wise to make the necessary preparations well in advance. This prevents last-minute rebuilding under time pressure, which can lead to errors.

What will consumers notice?

For end users, the change is not extremely large. The main difference is where they confirm their identity. Instead of confirming in the banking app, they will increasingly confirm in the itsme app. This can be done easily via app prompts, but also by scanning a QR code when using a desktop. For end users, it’s important to activate itsme once. This is done using an identity document and a phone number. In addition, extra verification takes place, for example through a selfie, and the user sets up biometrics or a PIN code to confirm actions.

What does the transition mean for webshops using iDIN?

Many websites and webshops currently use iDIN for purposes such as address and age verification, customer onboarding, faster entry of customer details, or login. Naturally, something will change for these websites and webshops as well. The process itself will not change dramatically, but the technology will. In most cases, iDIN is embedded in your platform. Think of a step in your checkout, an integration in your account environment, or an integration via an external service provider or identity provider. This means the relevant integration must be adjusted or replaced as part of the transition to itsme. After that, all customer flows need to be thoroughly tested.

Start replacing iDIN in time

In many cases, iDIN is seen as just a “button,” which makes it easy to assume the technical migration will be small and simple. That’s a misconception, and therefore it’s not recommended to wait until the last moment to replace iDIN with itsme. There’s a lot involved. Both your front end and back end will change. Your processes will change as well, including logging, support questions, audits, and fallback options for customers who don’t yet have it. If you wait too long to migrate, you risk having to implement updates under time pressure, or you may find that an integration becomes outdated. If you start in time, you can prepare in a controlled way and make the identification flow much more user-friendly.

Running iDIN and itsme side by side

There will be a transition period during which iDIN will be replaced by itsme step by step. This means the two systems can coexist for some time. That gives organizations the space to roll out in phases and gives customers the opportunity to get used to itsme. You can introduce itsme gradually. For example, you can first implement itsme for a specific flow, such as registration, and later apply it to other flows as well. It’s also very important to keep customers well informed. Communicate the changes and provide explanation. This can prevent many questions.

What about security and privacy?

Security and privacy always deserve full attention. For both iDIN and itsme, the principle of data minimization applies. You should only request the attributes that are truly necessary for the process. You should also clearly explain what the relevant data will be used for. Make sure your logging, processing agreements, and retention periods are correct. Also review your internal processes. How do you handle support questions, and which parties are authorized to view identification data? How can you demonstrate afterwards that an identification took place without storing more personal data than is strictly necessary? Give this sufficient attention to ensure everything is in order.

What can you already do as an organization?

For organizations, it’s important to prepare well in advance. Start with an inventory. Clearly identify where and in which customer flows you use iDIN, and through which module or supplier. Also check which dependencies exist, such as identity providers, PSPs, or plugins. Once you have this clear, you can map out your migration path. Decide when you want to offer itsme as an additional option and when you ultimately want to switch off iDIN completely. You can prevent ad hoc decisions later by making all of this clear now.

What can we do for you during the move from iDIN to itsme?

We closely monitor all developments related to the transition from iDIN to itsme. When an upgrade path becomes available, we will immediately communicate this clearly. We can ensure the itsme implementation is set up properly from a technical perspective. This can include adjusting or building the integration, checking data flows, updating customer flow texts, and testing all scenarios. We also provide guidance throughout the transition, so your identification process remains reliable and customers experience as little disruption as possible. We will keep you informed of all developments. Are you concerned, or would you like more information now about what we will be able to do for you during the transition from iDIN to itsme? Please feel free to contact us.