Identity Without Another Form: What Digital Wallets Could Change for Customer Journeys

Digital businesses have spent years removing friction from customer journeys. Checkout pages became shorter, passwords began giving way to passkeys, payments moved into mobile wallets and forms increasingly pre-fill information users once had to type manually.

Identity verification remains one of the stubborn exceptions.

A customer can move smoothly through a website until the moment a business needs to know who they are, how old they are or whether they hold a particular credential. Suddenly the journey may involve another form, an ID upload, a selfie, a document scan or a separate verification service.

The EU Digital Identity Wallet could begin to change that experience. Instead of repeatedly asking customers to enter and prove the same information, businesses may increasingly be able to request verified attributes directly from a wallet, while the user remains in control of what is shared.

For marketers and customer-experience teams, the interesting question is therefore not simply whether identity becomes digital. It is what happens to the digital identity customer journey when verification itself becomes easier to embed into the experience.

Identity verification is still one of the least elegant parts of digital UX

Modern digital journeys are designed around momentum.

A user discovers a product, compares options, reaches a landing page and begins taking the action the business wants. Every unnecessary step introduces another opportunity for abandonment.

Identity-heavy journeys often interrupt that momentum.

Opening a financial account, renting a vehicle, accessing an age-restricted service, proving eligibility or completing certain regulated transactions may require additional information and stronger verification. Those requirements cannot simply be removed in the name of conversion optimisation.

The challenge is therefore different from ordinary form optimisation.

The business still needs trustworthy information, but it needs to collect or verify it without making the customer feel as though they have left the journey and entered an administrative process.

That is where digital identity wallets become particularly relevant.

The form itself may stop being the default way to establish identity

Most online forms still operate on a simple assumption: the customer tells the business something about themselves and the business then decides how much it trusts that information.

The user types a name, address or date of birth. If stronger proof is required, another verification layer follows.

A wallet changes that model.

EU Digital Identity Wallets are designed to allow users to present person-identification data and electronic attestations of attributes to public and private services. The framework also supports selective disclosure, meaning the user can share the specific information required rather than automatically revealing an entire identity record.

That creates a very different UX possibility.

Instead of:

enter information → upload proof → wait for verification

a journey may increasingly become:

request attribute → user approves → attribute is verified

The legal and technical requirements behind that process are complex, but from the customer-facing side the interaction could eventually feel remarkably simple.

Age verification shows why this matters

Age checks are a particularly useful example because many services do not actually need to know a customer’s complete identity.

They only need an answer to a specific question:

Is this person above the required age threshold?

A traditional identity document may disclose considerably more information than necessary. The EU wallet framework supports selective disclosure, while Europe’s separate age-verification work is designed around proving an age threshold without unnecessarily exposing the user’s identity or exact age.

From a customer-experience perspective, that changes the design problem.

The brand does not necessarily need another form asking for a date of birth, followed by another process asking the user to prove it.

It may instead request the minimum verified attribute necessary to complete the interaction.

That can improve privacy and usability at the same time rather than treating them as competing objectives.

Asking for less information may become a conversion advantage

Digital marketing has often operated under a simple temptation: if a customer is already filling in a form, collect as much useful information as possible.

Digital identity introduces pressure in the opposite direction.

The European framework explicitly embeds data minimisation into wallet interactions. Relying parties are expected to request information that is necessary and proportionate for the intended use, while selective disclosure allows users to share specific attributes rather than larger data sets.

That matters beyond compliance.

Customers have become accustomed to wondering why a company needs a particular piece of information. A process that clearly asks only for what is necessary can communicate something valuable about the brand itself.

“Prove you are over 18” feels different from “give us your full identity document.”

The conversion advantage may therefore come not from collecting more customer data, but from making the request feel more proportionate, understandable and trustworthy.

The permission screen could become part of the brand experience

If wallet-based identity becomes common, businesses will need to think carefully about a new moment in the customer journey: the request for verified information.

A service cannot simply think about whether technically it can request a credential.

It needs to consider how that request appears to the customer.

Why is this information needed?

What exactly is being requested?

What will happen after the user approves it?

Does the request feel proportionate to what the customer is trying to do?

The regulation requires wallet-relying parties to register and provide information about the intended use of the wallet, including the data they plan to request. The framework is deliberately designed so relying parties can be authenticated and users can understand who is asking for their information.

That makes identity permission part of UX.

A badly explained request could create suspicion.

A clear request at an obvious point in the journey could feel almost invisible.

Trust may become something the interface has to demonstrate

Brands often talk about trust as something created through reputation, reviews, design and communication.

Digital identity adds another layer: technical trust at the moment of interaction.

The customer needs to know that the organisation requesting information is legitimate. The business needs confidence that the credential it receives is authentic. The system needs to establish both without forcing either side into a complicated manual verification process.

The EUDI framework therefore includes mechanisms for identifying and authenticating relying parties as well as validating wallet credentials.

That creates an interesting shift for customer experience.

Trust is no longer communicated only through what a brand says.

Part of it can be embedded in the infrastructure through which the interaction happens.

For the wider digital-marketing conversation at Targeted.gr, this is an important development: conversion increasingly depends not only on persuasive messaging and interface design, but on whether the systems underneath the journey can establish trust with as little friction as possible.

Faster onboarding does not mean removing necessary checks

There is an important distinction here.

A smoother identity process does not mean businesses can bypass KYC, age-verification, eligibility or other legal requirements.

The wallet is potentially valuable because it can change how information is presented and verified, not because it eliminates the obligation to verify it.

The European Commission explicitly identifies areas such as banking, loans, education and other public and private services as potential wallet use cases. It also notes that certain private services that are legally or contractually required to use strong user authentication will be required, under the conditions and timelines in the regulation, to accept compliant EU Digital Identity Wallets when users choose to use them.

For businesses in regulated journeys, the opportunity is therefore not “less verification”.

It is better-integrated verification.

Customer acquisition does not end when someone clicks “Sign up”

This matters particularly for performance marketing.

A campaign can produce an excellent click-through rate and still fail commercially if too many people abandon the process that follows.

Marketers already understand this at checkout. They increasingly need to apply the same thinking to identity-heavy onboarding.

Suppose paid media sends 10,000 qualified visitors to a financial service. The campaign may look efficient at the acquisition layer, but if a large proportion of prospective customers abandon during document verification, part of the apparent media performance disappears further down the funnel.

Digital identity could make this boundary less visible.

If verification becomes faster, more understandable and more integrated, some businesses may see value not by generating additional traffic but by losing fewer qualified users after acquisition has already succeeded.

That makes identity infrastructure relevant to marketing even though it sits well beyond the ad itself.

Conversion optimisation may move deeper into regulated journeys

Traditional CRO tends to focus on visible interface elements: page layout, copy, calls to action, number of fields and checkout steps.

Wallet-based verification creates another layer of optimisation.

Where should an identity request happen?

Should a business explain the requirement before triggering the wallet?

Which attributes are truly necessary?

Can some information be requested later rather than before the user experiences value?

What happens if someone chooses not to use the wallet?

These are not purely technical questions. They influence completion rates, confidence and perceived friction.

Importantly, the European framework makes wallet use voluntary for the individual. Access to public and private services cannot simply be made disadvantageous because someone does not use an EU Digital Identity Wallet, and existing identification or authentication routes must remain available where the regulation applies.

That means businesses may eventually need to optimise parallel identity journeys rather than replacing every existing flow overnight.

The alternative path matters almost as much as the wallet path

This is easy to overlook.

A company may create an excellent wallet-based onboarding experience and still serve many customers who continue using conventional verification.

That can happen because a national wallet has not yet been adopted by the user, a particular credential is unavailable or the customer simply prefers another method.

So the design challenge becomes:

How do you introduce a faster path without making the existing path feel like punishment?

That is especially important during the transition period.

A prominent “Verify with your digital identity wallet” option may become similar to the role Apple Pay or Google Pay plays at checkout: a shorter path for customers who already have the required infrastructure, while conventional methods remain available.

The analogy is not technically exact, but from a UX perspective it is useful. Adoption grows when a new mechanism creates an obvious shortcut without making people who cannot use it feel excluded.

Identity could become another reusable layer across the customer lifecycle

The impact may extend beyond first-time onboarding.

A trusted digital credential could potentially be relevant whenever a business needs to confirm something again during the relationship.

That may include account changes, access to restricted features, contract signing or other interactions requiring a stronger level of assurance.

This creates the possibility of treating identity less like a one-time hurdle at registration and more like a reusable trust layer that can appear only when needed.

That is a much more customer-friendly model than front-loading every possible verification step simply because the organisation might need the information later.

It also fits the wider movement toward progressive customer journeys: ask for what is necessary at the moment it becomes necessary rather than demanding everything upfront.

Identity data should not become another excuse for unnecessary profiling

Marketers may look at digitally verified attributes and immediately see richer segmentation opportunities.

That needs restraint.

A credential existing in a wallet does not mean a brand should request it, and a user proving one fact does not automatically create permission to use that information for unrelated marketing purposes.

The regulation places strong emphasis on necessity, proportionality, transparency and data minimisation. It also requires privacy-preserving design intended to prevent wallet usage from becoming a mechanism for tracking users across relying parties without appropriate authorisation.

This is important strategically as well as legally.

If consumers begin to associate digital identity with excessive data collection, the convenience advantage can quickly become a trust problem.

The strongest customer experience may therefore be the one where the brand learns exactly what it needs to complete the interaction — and nothing more.

The wallet may compete with familiar identity platforms

Another business implication is less visible to consumers.

For years, many digital journeys have relied on identity layers operated by large technology platforms: social login, device accounts and other third-party authentication services.

The European Commission explicitly presents reduced reliance on large competing identity platforms as one potential benefit for service providers adopting EU Digital Identity Wallets. It also argues that wallets could lower authentication costs by simplifying and automating identity-verification processes.

That does not mean “Sign in with Google” or similar systems suddenly disappear.

But businesses may gain another recognised identity route that is built around public European standards rather than a single commercial platform.

From a marketing perspective, that matters because who owns the login layer can influence the customer relationship.

This is where a seemingly simple onboarding feature starts becoming a much larger infrastructure question.

Not every business will be interacting with the wallet in the same way

It is also important not to describe the EU wallet as a universal requirement for every website.

The regulatory obligations are more specific.

Public bodies that require electronic identification for online services must accept compliant wallets. Certain private relying parties — excluding micro and small enterprises under the relevant provision — must accept them where strong online authentication is required by law or contract, including in sectors such as banking, financial services, transport, health, education and telecommunications. Very large online platforms that require authentication must also facilitate wallet use when the user voluntarily requests it.

Other businesses may choose to integrate wallet functionality because it improves their service rather than because they are legally required to do so.

That distinction matters for marketers.

The relevant question is not “Does every company need a wallet button?”

It is “Does verified identity solve a meaningful point of friction in this particular customer journey?”

Businesses will need to become relying parties, not simply add another plugin

From the outside, wallet integration may eventually look like another button in an interface.

Behind that button sits considerably more structure.

Under the regulation, an organisation that intends to rely on EU Digital Identity Wallets for a public or private digital service must register as a wallet-relying party in the Member State where it is established. Registration includes identifying the organisation and declaring the intended use of the wallet and the data it plans to request.

This is one reason the wallet should not be treated as another superficial UX feature.

The customer may see a simple request.

Behind it are trust registries, credential issuers, wallet providers, verification mechanisms and rules governing the relationship between them.

That wider system is where our forthcoming Market Insiders article, “The New Identity Layer: How Europe Is Rebuilding Digital Verification,” will pick up the story.

Consumer adoption comes before the marketing impact

The already published Athens Pulse article, “Your ID Is Moving Into Your Phone: What Europe’s Digital Wallet Changes” looks at this transition from the individual’s perspective: what happens when identity, age proofs and other credentials begin moving into the same device people already use for payments, tickets and everyday digital interactions.

That behavioural shift has to happen before the marketing implications become meaningful.

A wallet that technically exists but nobody uses changes very little.

A wallet that consumers recognise, trust and routinely reach for begins changing expectations around how much effort identity verification should require.

And once a faster interaction becomes familiar in one category, customers may start noticing the friction elsewhere.

Convenience can reset expectations surprisingly quickly

This has happened repeatedly in digital services.

One-click checkout made long payment flows feel worse.

Biometric login made repeated password entry feel outdated.

Real-time delivery tracking made vague delivery windows less acceptable.

Digital identity could eventually create the same type of expectation.

If someone can prove their age in seconds on one service, uploading a full identity document elsewhere may suddenly feel disproportionately cumbersome.

If a bank accepts a verified credential directly from a wallet, manually retyping the same information on another financial service becomes more noticeable.

Customer expectations rarely remain confined to the industry where a better experience first appears.

They spread.

That means businesses should pay attention to the wallet even before it becomes a dominant identity method in their own category.

The biggest opportunity may be invisible conversion improvement

Digital identity is unlikely to become a glamorous marketing channel.

There will probably be no “EUDI Wallet campaign strategy” comparable to social advertising, search or email.

Its marketing value is more structural.

It could reduce abandonment.

Shorten onboarding.

Make age checks less intrusive.

Reduce repetitive data entry.

Clarify why information is being requested.

Strengthen trust at moments where customers are asked to prove something sensitive.

Those changes may never appear in a campaign creative, yet they can influence how efficiently marketing investment converts into actual customers.

This is an important distinction.

Sometimes the next improvement in marketing performance does not come from better acquisition.

It comes from fixing what happens after the customer has already arrived.

Brands should not design for the wallet before understanding the need

There is also a danger in reacting too early.

A new technical standard can encourage businesses to create a “digital identity strategy” before they have identified any genuine customer problem.

The better starting point is the existing journey.

Where do users currently have to prove something?

Where do they abandon?

What information is actually required?

Which steps exist because of regulation, and which survive simply because nobody has redesigned the process?

Could a verified credential remove one of those steps?

Only then does wallet integration become strategically meaningful.

The objective is not to put another technology logo on the login page.

It is to make a difficult interaction noticeably easier.

What users actually see will matter more than the infrastructure underneath

For most customers, terms such as electronic attestation of attributes, relying party and selective disclosure will never need to become familiar.

They will judge the system through much simpler questions.

What is the business asking me for?

Why does it need it?

Can I approve this quickly?

Do I understand what I am sharing?

Does the process work?

That is why the final article in this cluster will move to Techrow.gr with “EU Digital Identity Wallet Explained: What It Can Store and How It Will Work”

There we can leave the marketing layer behind and look directly at the practical interaction: what can sit inside the wallet, how a credential is presented and what the user should expect to happen on the phone.

Identity could become part of conversion architecture

The most important marketing change may ultimately be conceptual.

Brands have traditionally treated identity verification as something that happens outside marketing: a compliance requirement, security process or backend function that begins after acquisition.

That distinction becomes harder to maintain when verification sits directly inside the customer journey.

If a user abandons during identity checks, it affects conversion.

If the information request creates distrust, it affects the brand.

If verification requires unnecessary steps, it affects customer acquisition efficiency.

And if a better identity flow allows more qualified customers to complete onboarding, the infrastructure underneath it has influenced marketing performance even though no ad changed.

The digital identity customer journey therefore forces marketers to look beyond the point where someone clicks the CTA.

The future of conversion may depend increasingly on what happens after persuasion has already worked.

And in some customer journeys, the most effective form may eventually be the one the user no longer has to fill in at all.

Frequently Asked Questions

How could the EU Digital Identity Wallet affect customer journeys?

It could allow customers to present verified identity information or specific attributes directly from a wallet instead of repeatedly typing information or uploading documents. This may reduce friction in journeys that require identity, age or credential verification.

Could digital identity wallets improve conversion rates?

Potentially, but the impact will depend on implementation and the customer journey. A faster verification process can remove friction, although there is not yet a universal conversion uplift that should be assumed for every business.

Can a business request any information stored in the wallet?

No. The European framework emphasises necessity, proportionality and data minimisation. Selective disclosure is specifically designed so users can share only the information needed for a particular interaction.

What is a wallet-relying party?

A wallet-relying party is an organisation that relies on an EU Digital Identity Wallet to provide a public or private digital service. Relying parties must register and declare information including their intended wallet use and the data they intend to request.

Will every business have to accept the EU Digital Identity Wallet?

No. Acceptance obligations apply in specific circumstances. They include public online services requiring electronic identification, certain private services requiring strong authentication and very large online platforms in circumstances defined by the regulation. Other businesses may choose to support the wallet voluntarily.

Will customers be forced to use a digital identity wallet?

No. Use of EU Digital Identity Wallets is voluntary, and the regulation states that people should not be disadvantaged in accessing services because they do not use one.

How could the wallet change age verification?

It can support selective disclosure so a person can prove a required attribute, such as meeting an age threshold, without necessarily revealing their complete identity or unrelated information.

Is an EU Digital Identity Wallet the same as social login?

No. Social login typically authenticates a user through an account operated by a technology platform. The EU Digital Identity Wallet is designed around recognised digital identity and verifiable credentials provided within a regulated European trust framework.

Why should marketers care about digital identity?

Because identity verification can sit directly inside acquisition, onboarding and conversion journeys. Even when marketers do not manage the underlying identity infrastructure, unnecessary verification friction can reduce completion rates and weaken the customer experience.

When will EU Digital Identity Wallets become available?

Member States are required to make compliant EU Digital Identity Wallets available by the end of 2026, although national rollout details and the availability of individual credentials can vary.