For banks, card issuers and insurers in Germany, Austria and Switzerland
EUDI Wallet: mandatory by December 2027.
An advantage today.
✓
Timeline and relying-party tasks, factual and dated
✓
Verified attributes as consent-based signals in the CDP
✓
Swiss e-ID in the same model
Readiness conversation in 30 minutes. Last updated: October 20, 2026
Wallet attributes
Example
Wallet
Identity, residence Mannheim, over 18: confirmed. Frequent flyer status: shared with consent.
PID + attestation
Moment
“Your flight to Lisbon: activate a Portugal eSIM? One tap, no documents needed.”
Eligibility checked ✓ · logged
○
Illustrative concept
Your rules
Personal Finance Management
Next Best Action
Top of Wallet
Transaction data
EUDI Wallet
Virtual advisor
Customer Data Platform
Hosted in Frankfurt
Consent first
Timeline 2025–2027
EUDI Wallet timeline for banks: what applies when.
As of October 20, 2026. Dates come from the linked sources; we review the timeline quarterly. The legal assessment for your institution is made by your compliance team.
EUDI Wallet sandbox in Germany
The official sandbox is open to organizations for tests with test data. According to eudi-wallet.gov.de, participation is a prerequisite for later productive use.
Switzerland: yes to the e-ID Act, new timetable
Voters approved the e-ID Act. According to eid.admin.ch (June 2026), the e-ID and trust infrastructure will be introduced in 2027, with the federal swiyu wallet.
EU member states provide wallets
Under Article 5a of Regulation (EU) 2024/1183, every member state must offer at least one EUDI Wallet by this date. Germany opts for a state wallet, which follows in early 2027.
German EUDI Wallet, version 1
Smartphone app with identity function (PID from ID card or eAT) and digital credentials. Namirial names January 2, 2027 as the launch date. Further functions such as QES and payment confirmation follow in stages.
Acceptance obligation for banks
Under Article 5a of Regulation (EU) 2024/1183, banks as well as payment and e-money institutions subject to strong customer authentication must accept the wallet at the user's request from this date; Namirial and Fincite (2026) also name insurers. Example: account opening under anti-money-laundering rules.
Sources: eudi-wallet.gov.de, Namirial, Fincite and eid.admin.ch (as of October 20, 2026).
Relying party
What banks prepare as a relying party.
Summarized factually from public sources, without legal advice. The five points are also the prerequisite for using wallet data for personalization later.
Registration as a relying party
Anyone requesting wallet credentials registers in the respective member state and discloses which attributes are requested for which purpose. Requests are limited to what is necessary.
Acceptance of all certified wallets
A non-discrimination requirement applies: credentials from every recognized EUDI Wallet must be accepted, not only from the German state app.
Adapting processes with identification duties
Account opening under anti-money-laundering rules, re-identification, proof of authority: wherever video identification or document upload stands today, the wallet becomes an accepted option.
Consent and purpose limitation per attribute
Identity for onboarding is a different purpose than residence for a travel offer. Each request needs its own basis and its own entry in the log.
Testing in the sandbox
Use cases are tested with test data in the official sandbox before going live. ACCELERAID supports the integration into CDP and processes.
From identity to personalization
Signal, profile, catalog, decision, moment.
The obligation ends at identification. The opportunity begins afterwards: with the customer's consent, verified attributes become signals in the Customer Data Platform, and Next Best Product moves from segment to individual.
Five steps from verified identity to the fitting offer, each with consent and a log.
Signal
a booking, a move, a border crossing, a new credential in the wallet
Profile
card data plus verified attributes: age, residence, income, household, memberships
Decision and moment
eligibility, value, timing and your rules decide; delivered in app, push or advisor
Use cases
Six applications with wallet attributes.
From the mandatory task to the beyond-banking offer. Each uses the same CDP and the same consent model.
Onboarding without document upload
Identity and address come state-signed from the wallet. No video identification, no scan. The application ends where it starts: in your app.
KPI: completion rate
Re-identification and step-up
For new products, proof of authority or sensitive changes, identity is confirmed again in seconds, with a log.
KPI: turnaround time
Eligibility and age
“Over 18”, residence in the sales territory or student status are shown selectively, without disclosing further data.
KPI: failed applications
Keeping master data current
Instead of letters, uploads and follow-ups, the customer confirms their data in the app. Master data stays current, and the obligation becomes a contact moment.
KPI: refresh rate
Address change as a life event
A new address in the wallet is a moving signal: home insurance, electricity, standing orders, branch. With consent, it becomes a moment.
KPI: products per customer
Beyond banking around the card
Trip detected, residence known, status in the wallet: eSIM, travel cover, loyalty or hotel offer, timed to the booking.
KPI: partner revenue
A moment from the card
Example
Flight to Lisbon paid with the card.
One message, one tap: Portugal eSIM, reminder of travel cover, hotel offer with travel credit.
Trigger, mix and timing are unique to this customer. Partners and offers are defined with you.
✓
Illustrative example
Beyond-banking example
Lisbon, one flight, three offers, one tap.
This is what hyper-personalization with wallet attributes looks like in everyday life. Illustrative; partners and offers are defined with you.
Signal
Flight to Lisbon paid with the card.
Transaction
airline, travel date, destination country
Wallet
residence Germany, over 18, frequent-flyer status attested
Consent
travel offers: granted. Insurance: granted. Partner advertising: not granted.
Decision
Three offers pass the check.
Portugal eSIM
eligible, partner offer from the travel catalog
Travel cover reminder
own product, already included, information only
Hotel with travel credit
loyalty partner, status from the wallet taken into account
Moment
One message, two days before departure.
Channel
app card plus push, no email newsletter
Tone
short, useful, no advertising for anything not permitted
Log
signal, attributes, rules and reaction in the decision record
Comparison
Today vs. with the EUDI Wallet: four processes.
What changes in the processes banks run anyway, and which data arises with consent for personalization.
Video or postal identification, minutes to days
PID from the wallet, seconds
Verified identity, address, age
Master data refresh
Letter, upload, follow-up
Re-confirmation in the app
Up-to-date master data
Form, proof, manual check
New credential from the wallet
Moving signal, life event
Copy of ID
“Over 18” disclosed selectively
Eligibility without date of birth
The Swiss e-ID follows the same pattern with the swiyu wallet; ACCELERAID handles both wallets in one attribute and consent model.
Consent-first governance
What the customer does not allow does not happen.
Wallet attributes are the most trustworthy data a bank will ever receive. They stay that way only if the handling is visibly clean.
Per attribute · Purpose, basis, status
Every attribute in the CDP carries its purpose, its legal basis and the consent status. Identity for onboarding and residence for offers are separate entries.
Selective · Request only what is needed
The wallet allows selective disclosure. Whoever only needs “over 18” does not request a date of birth. The request profile is defined with data protection and compliance.
Revocable · Withdrawal takes effect immediately
If the customer withdraws consent, the attribute disappears from decisions and offers. The withdrawal is logged like the grant.
Traceable · Log per decision
Which attributes fed into which decision is in the decision record. That answers questions from customers, data protection and supervisors.
Data protection & security
Privacy is architecture. Built for regulated banking.
Data protection is architecture, not a feature. The platform connects to core banking, card processor, CRM and app and runs where your supervisor expects it to.
Privacy by design
✓
Consent per purpose
✓
Hosted in Frankfurt
✓
PII filter before the model
✓
No cross-tenant training
01
GDPR & DPA
A data processing agreement, purpose limitation and deletion concepts are part of every project, with a joint data protection impact assessment on request. Every use of customer data is tied to a documented purpose and a consent.
02
Hosted in Frankfurt
Private cloud in the ISO 27001 certified data center in Frankfurt, on-premise optional. Data stays in Germany.
03
PII filter before the model call
Personal data is detected and masked before a language model sees a request. No cross-tenant training: customer data only trains the bank's own models.
04
Tenant separation
Each bank runs in its own logically separated environment with its own keys, roles and logs.
05
SOC 2 Type I certified
ACCELERAID is SOC 2 Type I certified; the report is available under NDA. Audit-proof logging is standard.
06
Enterprise hosting
Enterprise hosting in the PCI DSS certified data center. The ISO 27001 and PCI DSS certifications apply to the data center.
Wallet attributes are only used with consent and for the approved purpose. Automated individual decisions within the meaning of Art. 22 GDPR are not intended; assessing individual processing activities is up to your data protection officer.
The agreed configuration, the contract and the related evidence, such as the SOC 2 Type I report, are authoritative.
FAQ
Frequently asked questions about the EUDI Wallet.
What banks want to know before they start.
How is data protection preserved when wallet attributes flow into the CDP?
What is the EUDI Wallet?
From when must banks accept the EUDI Wallet?
What does relying party mean?
Which attributes can a bank use from the wallet?
May the bank use wallet data for personalization?
How does the Swiss e-ID fit in?
What is beyond banking, and what does it have to do with the wallet?
How do we start, and what does ACCELERAID do?
Read on
Where to go next.
From the blog
EUDI Wallet readiness conversation.
30 minutes: which processes are affected, which attributes you need, and which consent-based use cases generate revenue before the obligation applies.