EUDI Wallet and KYC: how the wallet transforms bank onboarding

In short: the European Digital Identity Wallet (EUDI Wallet) will change the way you verify your customers at the start of the relationship. The customer presents an identity attribute already verified by a trusted issuer, your system checks its signature cryptographically in real time, and you no longer have to manually review a scanned document. The eIDAS 2.0 regulation (EU Regulation 2024/1183) requires regulated players to accept this wallet by 24 December 2027.

‍

The expected result: faster, cheaper and smoother onboarding. Be careful, though, the wallet certifies an identity at a point in time. It says nothing about creditworthiness, it covers neither dynamic fraud after the account is opened nor KYB, and it does not concern your customers outside the European Union. So you need to plug it in intelligently, with a fallback journey and complementary building blocks.

‍

For a regulated player, the topic is no longer theoretical. The question is no longer whether the wallet is coming, but how it will fit into an already well-honed KYC journey, and what you need to plan around it so that verification remains solid. Here is what the wallet concretely changes for your onboarding.

‍

What the wallet brings to KYC

‍

The principle of the European wallet rests on a simple idea. Trusted issuers, such as states, public administrations, banks or certified companies, produce already-verified data and attestations. These elements are stored in the customer's wallet, under their control.

‍

We distinguish two main families of data. On one side the PID, that is to say the person's identity data (surname, first name, date of birth, nationality). On the other side attestations, which cover a variety of supporting documents such as proof of address, a diploma, a business registration extract or proof of age.

‍

The fundamental difference with a classic KYC journey lies in the origin of trust. Today, your customer sends you a photo of their ID and a supporting document, and your system has to prove that this document is authentic and not falsified. With the wallet, the data arrives already signed by a trusted issuer. You are no longer verifying a document, you are verifying a cryptographic signature.

‍

Another major benefit, selective disclosure. The customer shares only the attributes strictly requested. If you only need to prove that they are of legal age, they transmit that information without revealing their exact date of birth or their address. This is a data minimisation logic consistent with the spirit of the GDPR, applied from the design of the journey onwards.

‍

How onboarding works with the wallet

‍

Concretely, the start of the relationship boils down to a short, structured sequence. Here are the steps.

‍

1. The attribute request

‍

At the time of onboarding, your system asks the customer for the attributes you need in order to meet your verification obligation. For example verified identity and proof of address.

‍

2. Presentation by the customer

‍

The customer opens their wallet and chooses to share only the requested attributes. They keep control over what they transmit, nothing more.

‍

3. Cryptographic verification in real time

‍

Your system automatically checks the authenticity of the issuer's signature. If the signature is valid, the data is deemed reliable, without manual review of the document. This verification happens in real time.

‍

4. The onboarding decision

‍

You have an identity verified at the source. The identity building block of your KYC is processed almost instantly, which frees up time for the checks that really matter.

‍

What this changes for your costs and your conversion

‍

The most visible impact is on three fronts.

First the onboarding time. Verifying a classic document often involves a queue, sometimes a human review and back-and-forth with the customer. Verifying a signature is immediate. You reduce the length of the journey and you smooth the experience at the point where many customers drop off.

Next the cost. Less manual review means fewer resources mobilised on document control tasks. Data verified at the source also reduces re-verifications, those moments when you ask again for a document because the first one was blurry or doubtful.

‍

Finally conversion. A shorter and less friction-heavy journey at the sensitive moment of entering the relationship mechanically translates into fewer drop-offs. For a player who acquires customers at a high cost, every point of conversion recovered at onboarding has direct value.

‍

What the wallet does not replace

‍

This is the most important point to take on board, and it needs to be said honestly. The wallet is a genuine step forward, but it addresses a single building block of risk, identity, and at a precise point in time. It leaves aside several areas that you must continue to cover.

‍

Creditworthiness

‍

The wallet confirms who the customer is. It tells you nothing about their capacity to repay. For a credit subscription or any product exposed to default risk, you still need a creditworthiness analysis based on real financial data.

‍

Dynamic fraud after onboarding

‍

The wallet certifies an identity at the moment of entering the relationship. It does not protect against fraud that occurs afterwards, such as mule accounts or account takeover. A customer perfectly identified today may see their account hijacked tomorrow, or may have been enrolled to serve as a relay. Continuous fraud detection, which analyses behaviour, device and numerous signals throughout the life of the account, remains indispensable.

‍

KYB and beneficial owners

‍

The wallet is designed for natural persons. It does not cover the verification of legal entities or the identification of beneficial owners, which remain at the heart of your obligations when you enter into a relationship with a company.

‍

Customers outside the European Union

‍

The wallet is a European scheme. Your customers located outside the Union will not have a wallet. Your classic verification journey must therefore remain fully operational for them.

‍

The fallback journey

‍

Not all eligible customers will necessarily have adopted the wallet by the time they reach you. You absolutely must plan a robust fallback journey to verify identity by the usual means when the customer does not have a wallet, or you risk blocking a portion of your new relationships.

‍

How to plug the wallet in intelligently

‍

The right approach is to treat the wallet as one verification source among others, and not as the sole foundation of your KYC. A few concrete principles.

‍

Place the wallet at the entry of the journey to speed up the identity building block when the customer has one, and automatically switch to your fallback journey otherwise. The experience must remain continuous whatever the case.

‍

Keep your complementary checks where the wallet says nothing. An identity verified at the source does not exempt you from assessing creditworthiness, monitoring fraud over time or handling legal entities. These building blocks are orchestrated around the wallet, not in its place.

‍

Finally, keep a documented and auditable trail of every decision. The fact that the data is signed by a trusted issuer simplifies your justification, but your regulator still expects to understand how and why you accepted or refused a new relationship. For a broader overview of the eIDAS 2.0 framework, our article on the European Digital Identity Wallet details the timeline and the mechanisms.

‍

In conclusion

‍

The European Digital Identity Wallet will transform the identity building block of your onboarding, with the payoff of a faster, cheaper and more data-respectful journey for your customers.

‍

That is genuinely good news for conversion and for the experience. But you must not confuse an identity verified at a point in time with a complete verification of risk. Creditworthiness, dynamic fraud, KYB and customers outside the Union remain entirely your responsibility.

‍

The challenge, ahead of the 24 December 2027 deadline, is therefore not only to accept the wallet, but to orchestrate it with the building blocks that truly secure your entire journey.

‍

Sources: Regulation (EU) 2024/1183 (eIDAS 2.0), European Commission on the European Digital Identity Wallet, GDPR framework on data minimisation.

‍