Research manuscript · Summary and implementation guide

European Business Wallets: Regulation, Roadmap and Business Value

A conditional roadmap for the Single Market, cyber-resilience and accountable automation—with practical guidance for starting now.

First page of the European Business Wallets research manuscript, with title, author, date and abstract.

New research · 31 October 2026

A practical decision framework for European business identity. Read the legal comparison, six readiness gates and Section 19’s implementation guide.

Dr. Carsten Stöcker · Spherity GmbH
26 pages · Research manuscript · CC BY 4.0

Planned launch: Q1 2027. Spherity’s EBW-ready Business Wallet, developed with Bundesanzeiger Verlag and tested in WE BUILD, is planned for general availability on BSI-certified infrastructure. Read the launch plan.

Research record and version details
Author
Affiliation
Dr. Carsten Stöcker — Spherity GmbH
Published
Updated
Research cut-off
· Legal and technical evidence; product plans labelled separately
Browse this paper

In brief

What does this research establish?

European Business Wallets connect organisational identity, verifiable evidence and bounded authority to business transactions. Spherity plans general availability of its EBW-ready Business Wallet in Q1 2027 on BSI-certified infrastructure, building on work developed with Bundesanzeiger Verlag and tested in WE BUILD. This product plan is separate from the EBW regulation, which remained under negotiation at the 31 October 2026 cut-off: the paper’s 2029–2031 acceptance examples are conditional calculations, not adopted deadlines.

Key takeaways

  • The Commission, Parliament ITRE and Council texts use different proposed triggers for public-sector acceptance; political agreement is not the same as entry into force or application.
  • EUDI Wallets and business wallets are complementary: personal identity and user-controlled disclosure can connect with organisational evidence, mandates and enterprise processes.
  • Readiness requires six transaction gates: legal basis, technical profile, credentials, mandates, receiving service and operations.
  • Section 19 recommends a minimum viable ecosystem, a value-realisation plan, controlled pilots and a funded approach to changing standards.
  • Identity and bounded authority can support cyber-resilience and Trusted AI; they do not establish safe AI decisions or guaranteed economic gains.
  • Spherity’s EBW-ready Business Wallet, developed with Bundesanzeiger Verlag and tested in WE BUILD, has general availability planned for Q1 2027 on BSI-certified infrastructure; the exact launch day is not announced.

European Business Wallets: from identity to completed transactions

European Business Wallets (EBWs) are proposed digital infrastructure for economic operators and public bodies to identify themselves, exchange verifiable business evidence and demonstrate authority across borders. The practical objective is a completed business transaction: a supplier onboarded, a filing accepted or an authorised agent action recorded. Owning a wallet alone does not deliver that outcome.

This page summarises the 26-page research manuscript prepared on 31 October 2026 and adds an implementation perspective, an EUDI Wallet comparison and Spherity’s product outlook. The full PDF contains the method, article-level legal comparison, worked example and 46 references. The economic and security benefits discussed in the paper are hypotheses to test in deployments.

What changed: the earlier 2028–2029 forecast is replaced by three proposed legal clocks and explicit 2029, 2030 and 2031 scenarios. The paper introduces six transaction-readiness gates and practical implementation guidance in Section 19. The original page was published on 18 May 2026; this edition retains its URL.

Product launch outlook · Planned general availability

Spherity EBW-ready Business Wallet with Bundesanzeiger Verlag: planned Q1 2027 launch

Spherity plans general availability of its EBW-ready Business Wallet in Q1 2027 on BSI-certified infrastructure, building on a European Business Wallet developed with Bundesanzeiger Verlag and tested in WE BUILD. The exact launch day has not been announced.

Planned launch
Q1 2027 — January–March 2027; exact launch day to be announced.
Development partner
Bundesanzeiger Verlag
Pilot experience
Developed and tested in the WE BUILD context.
Planned hosting
BSI-certified infrastructure

Build the business case now: identify one recurring transaction, involve its receiving partner and measure onboarding effort, delegated-authority checks and recovery. This connects the planned launch to business value, cyber-resilience and accountable AI automation.

Plan your Q1 2027 Business Wallet use case

Company plan stated on 31 October 2026. Q1 means January–March; no specific release day is announced. Infrastructure certification concerns the hosting environment and does not itself establish final EBW product conformity. Partnership and WE BUILD context.

The updated European Business Wallet roadmap

The roadmap separates recorded events, political or programme targets, calculated acceptance examples and continuing implementation work. The timeline extends to 2031 to make the consequences of different assumptions visible. It does not promise a final rollout date. Open the SVG for readable detail or download it for reuse with attribution.

Timeline separating recorded EBW legislative events from hypothetical 2029, 2030 and 2031 acceptance calculations, continuing implementation work and separate post-quantum policy targets.
Figure 1. Legislative and implementation timeline at 31 October 2026. Filled markers show recorded events or published baselines; diamonds show targets or plans; open circles show calculated acceptance examples. Continuing bars do not assign completion deadlines. E, I and A are different legal triggers. The EUDI and authentic-source dates are enacted milestones; PQC targets are policy recommendations. Reference numbers follow the full paper. Source: Dr. Carsten Stöcker / Spherity GmbH; supplied roadmap with added white margin and embedded fonts.

Reference numbers inside the figure follow the paper’s bibliography.

Regulatory status: three proposed acceptance clocks

At the 31 October 2026 evidence cut-off, the official record did not establish an adopted final EBW regulation or its publication in the Official Journal. The Commission proposal dates from 19 November 2025; the Council adopted its negotiating position on 9 June 2026; Parliament’s negotiating mandate was confirmed on 7 October; the first trilogue was recorded on 14 October. The end-of-2026 agreement objective is a political target. [1, 2, 3, 4]

When could public-sector acceptance become mandatory?

The answer depends on the final legal trigger, not simply the date of political agreement. Define E as the regulation’s entry into force, I as entry into force of the implementing acts referenced by ITRE Article 16, and A as application of the last implementing act listed in Council Article 22.

Negotiating text General application Proposed public-sector acceptance
Commission proposal E + 12 months E + 24 months, Article 16
Parliament ITRE report E + 12 months, with the Article 20 exception I + 24 months, Article 16
Council general approach A + 12 months, with specified early provisions A + 24 months, Article 22(1c)

The Council’s acceptance period runs directly from A. Adding it after general application to produce A + 36 months would misread the text. Conditional registered-delivery transition provisions also need separate treatment; they are not universal wallet go-live dates. See the full legal analysis in paper Sections 4–6.

Illustrative calendar scenarios, not deadlines

Explicit assumptions Commission calculation ITRE / Council calculations
E = 1 April 2027; I and A = 1 April 2028 1 April 2029 1 April 2030
E = 1 April 2027; I and A = 1 April 2029 1 April 2029 1 April 2031

I and A remain different legal events even when an example assigns them the same date. No probability is assigned to these scenarios. Council presidencies can influence political progress, but do not start the proposed acceptance clocks. EUDI Wallet provision, authentic-source rules and post-quantum policy milestones have their own calendars and must not be substituted for an EBW deadline. [5, 6, 7]

EUDI Wallet vs European Business Wallet: complementary roles

The European Digital Identity Wallet (EUDI Wallet or EUDIW) provides a common framework for digital identity and attestations under eIDAS. European Business Wallets add a proposed organisational operating framework for business evidence, representation and cross-border processes. The table compares a typical personal EUDI Wallet experience with an industrial business-wallet profile. These are usage emphases, not hard technology boundaries: the EUDI framework also addresses legal persons, and personal wallets can carry professional attributes. Privacy and access protection apply to both. [5, 1, 8]

Dimension EUDI Wallet: typical personal use European Business Wallet: industrial profile
Trust and privacy User control, data minimisation and privacy-preserving disclosure; unlinkability where supported by the transaction and design. Verifiable organisational authority and auditable actions, with protected access and proportionate logs. Personal data still requires protection.
Evidence and data Identity attributes and other personal or professional attestations. Company identity, licences, representation and business evidence; integration with semantic data, knowledge graphs and Digital Product Passports where the use case requires it.
Approval and delegation User-mediated disclosure and strong authentication, for example a device plus PIN or biometrics. Scoped mandates and policy checks can support automation, with approval or escalation for exceptions. A login is not an unlimited mandate.
Operation Commonly a personal smartphone application, with the user initiating an interaction. Cloud services and APIs, multiple users and roles, enterprise integrations and business-continuity requirements. Availability must be demonstrated.
Actors People demonstrate identity and attributes, including professional roles. Organisations delegate bounded actions to people, software and machines; AI-agent actions remain attributable to responsible organisations and persons.
Legal status and timing Based on the enacted European Digital Identity Framework and applicable implementing rules. Separate EBW legislation remained under negotiation at the research cut-off; final obligations and acceptance dates were unsettled.

They work together: a person can establish identity through an EUDI Wallet while a business wallet supplies company evidence and the authority to act for that company. Germany’s d-you is one national EUDI Wallet example, not a synonym for all EUDI Wallets. Its official project describes a user-centred personal wallet and a planned initial release in early 2027. See the d-you / EUDI Wallet FAQ and official naming announcement. [9]

Start with business value, cyber-resilience and Trusted AI

Organisations can assess and pilot bounded, lawful use cases before mandatory acceptance. The case for starting is the work that can be improved today: repeated evidence collection, slow onboarding, unclear authority and fragile recovery. Commit to expansion when a real counterparty, a lawful process and measured outcomes support it.

Where to look for an initial business case

Use case Practical value to test Evidence of success
Supplier onboarding: know your business (KYB) / know your supplier (KYS) Reuse current company evidence instead of repeatedly collecting and rekeying it. Completion time, cost per accepted supplier, freshness and exception rates.
Public procurement and business-to-government (B2G) filings Combine company evidence with the representative’s current, limited authority. A submission associated with the correct case, an explicit receipt or outcome, fewer correction cycles.
Government-to-government evidence exchange Obtain evidence from a competent authority through an authorised route. Less reconciliation, lawful access, source-response times and complete case records.
Data spaces and Digital Product Passports Establish which company may access or update a shared record. Appropriate access decisions, provenance and revocation performance.
Industrial AI agents Bind a software action to an organisation, a mandate and an enforced policy. Rejection of out-of-scope actions, human escalation and a reconstructable action record.

Cyber-resilience: test impersonation resistance, revoked authority, replay, stale evidence, compromised endpoints and recovery. The wallet supplies evidence to an access decision; endpoint protection, incident response, privacy controls and continuity remain necessary. Start a cryptographic inventory and a risk-based post-quantum migration plan alongside wallet integration. [7, 12]

Europe’s Trusted AI opportunity: interoperable business identity and bounded delegation can support accountable automation across the Single Market. Enforce permissions outside the generative model and bind them to the action actually executed. For physical AI, retain local safety controls and safe failure paths. A valid identity or mandate does not prove that an AI decision is correct, a product claim is true or a machine action is safe. These are implementation opportunities described in paper Sections 9–14, not demonstrated economy-wide benefits. [4, 13]

Six readiness gates: what “EBW-ready” should mean

The paper’s framework evaluates a specified transaction, not a whole country or product in the abstract. A working credential exchange cannot compensate for an absent legal basis or an unprepared receiving service. All six gates need documented evidence before the selected production use. This is a research framework, not a certification scheme. See Section 15.

Gate Evidence to request
L — Legal basis Applicable procedure, recognition scope and lawful use of the required evidence.
P — Technical profile A versioned specification manifest and exchange tests between independent providers.
C — Credentials A competent source for each required attribute, correct identifiers, coverage and freshness/status checks.
M — Mandates Action-specific authority, delegation limits and successful revocation tests.
S — Receiving service End-to-end case integration and an explicit submission or service outcome.
O — Operations Security, privacy, recovery, provider exit and an appropriate post-quantum migration plan.

The tender example in Section 16 exercises these gates with a manufacturer, its representative, evidence issuers and a receiving authority. Test successful submission alongside revoked mandates, missing evidence, unsupported profiles, interrupted delivery and duplicate requests.

Practical implementation guidance from Section 19

  1. Choose one recurring transaction and its owner. Record manual steps, required evidence, volume, delays and failure modes. Define a completed business outcome and a cost threshold before selecting technology.
  2. Assemble a minimum viable ecosystem. Include the business, a competent source or issuer, a real receiving counterparty, and wallet, verification and operational services. Agree semantics, evidence acceptance, support and responsibility for disputed outcomes. A demonstration within one vendor’s stack does not establish independent interoperability.
  3. Set a value-realisation plan. Name a benefit owner, baseline, target, measurement method and review date. Include costs across the business, issuer and receiver, plus support, parallel channels and migration. Distinguish time released from cash expenditure avoided.
  4. Run a controlled pilot and test failures. Apply the six gates. Test revoked authority, missing or stale evidence, outages, retries and recovery. Decide in advance what evidence would justify expansion, adjustment or stopping; record manual intervention.
  5. Design and budget for change. Separate business workflows from credential formats, protocols, trust services and cryptography. Use versioned interfaces, portable records and replaceable adapters. Assign a migration owner and rerun affected interoperability, authorisation and recovery checks when requirements change.

An illustrative first cycle is one month for design, one for integration and one for measurement. This is a planning option from the paper, dependent on procurement, source availability and participant capacity, not a delivery promise.

Measure value per completed transaction

The paper proposes a transparent annual accounting model:

Net benefit = eligible annual transactions × completion share × (effort avoided per completion − variable cost) − annual fixed costs − exception and parallel-channel costs.

Its illustrative inputs are 1,200 transactions, 60% completion, €18 avoided effort, €3 variable cost, €7,000 fixed cost and €1,500 exception/parallel-channel cost. They yield €2,300 annual net benefit, with break-even completion around 47.2%. At 40% completion the same case loses €1,300. These are invented management inputs, not benchmarks or a savings forecast. Pair the financial assessment with revocation, recovery, error and support measurements. Sections 14 and 19.

From WE BUILD testing to an EBW-ready Business Wallet

Spherity and Bundesanzeiger Verlag have developed a European Business Wallet and tested it in WE BUILD. The collaboration connects wallet capabilities with verified business information, representation and enterprise processes. Spherity’s EIDA Business Wallet overview describes the partnership and pilot use cases, including KYC/KYS/KYB, representative rights, corporate banking and data-space access. WE BUILD provides the wider European pilot and interoperability setting. [10, 8]

Spherity is productising this work as an EBW-ready Business Wallet. See the standalone Q1 2027 launch plan for the planned general-availability window, Bundesanzeiger Verlag partnership and infrastructure scope.

For procurement, ask for the tested profile versions, participating counterparties, supported credentials, mandate lifecycle, service commitments, infrastructure certification scope and migration responsibilities. Pilot participation is useful implementation experience; final EBW conformity remains a separate matter.

Your next step · from 1 November 2026

Don’t wait to build business value.

Put business value, cyber-resilience and Europe’s Trusted AI opportunity on the same implementation agenda. Start with one recurring transaction, one receiving partner and a measurable outcome. Use the assessment to decide whether a controlled pilot is justified, then scale what works.

Bring your onboarding, procurement, compliance or AI-agent use case to Spherity. Define the minimum ecosystem, evidence requirements, delegated authority and recovery tests—and a practical path towards the planned Q1 2027 Business Wallet release.

Discuss your Business Wallet use case

1 November is a recommended action date, not a regulatory deadline or a general-availability announcement.

Research scope and limitations

This is a comparative legal and technical policy analysis with a fixed evidence cut-off. It proposes a readiness framework and evaluation model; it does not report independently measured deployment savings or security outcomes. Specifications, negotiating positions, enacted requirements and product plans have different evidentiary status. Check the official procedure record for subsequent developments.

The author is affiliated with Spherity GmbH, which has commercial interests in digital identity and credential infrastructure. The product outlook above is additional company information supplied for this page; it is distinct from the manuscript’s documentary findings. The PDF preserves the supplied manuscript content and publication date; its descriptive metadata has been corrected.

Selected references and further reading

The full paper contains 46 references. The numbered references below support this page; numbering inside the roadmap follows the PDF.

  1. European Commission. Proposal establishing European Business Wallets, COM(2025) 838, 19 November 2025. Proposed functions and legal baseline; Articles 16 and 22 govern the Commission’s timing model.
  2. European Parliament. Legislative Observatory: 2025/0358(COD) and first-trilogue event record, 14 October 2026.
  3. Council of the European Union. General approach, ST 9684/26, 2 June 2026; negotiating position adopted 9 June 2026.
  4. European Parliament, ITRE. Report A10-0240/2026, September 2026. Consolidated negotiating text, particularly Articles 6, 16 and 22.
  5. European Parliament and Council. Regulation (EU) 2024/1183: European Digital Identity Framework. Enacted EUDI framework, distinct from the EBW proposal.
  6. European Commission. Implementing Regulation (EU) 2026/1735, amending attestation and authentic-source specifications. Article 1(3) applies from 1 January 2027.
  7. NIS Cooperation Group. Coordinated implementation roadmap for the transition to post-quantum cryptography, June 2025. Risk-based policy recommendations, not EBW acceptance law.
  8. WE BUILD Consortium. About WE BUILD. Business and payment use cases, technical foundations and interoperability testing.
  9. German EUDI Wallet project. Frequently asked questions and d-you name and logo announcement. National personal-wallet example; consult the project for current availability.
  10. Spherity. EIDA European Business Wallet. Company source for the Bundesanzeiger Verlag partnership and WE BUILD pilot use cases; product claims are not independent conformity evidence.
  11. European Commission. EUDI Architecture and Reference Framework 3.0.0. W3C. Verifiable Credentials Data Model v2.0. Technical foundations; they do not alone establish final EBW compliance.
  12. NIST. Zero Trust Architecture, SP 800-207, 2020. Authentication, authorisation and resource-specific policy decisions.
  13. NIST. AI Risk Management Framework 1.0, 2023. Trustworthiness includes validity, safety, security and accountability beyond identity.
Creative Commons Attribution 4.0 International

Open research

License and citation

This research publication (including the page, linked manuscript and original roadmap) is licensed by its named author under the Creative Commons Attribution 4.0 International License (CC BY 4.0), except for the third-party material identified below. Reuse must credit every named author, link to this canonical version and the license, and indicate whether changes were made.

Third-party rights: Logos and trademarks are excluded from the CC BY grant. Third-party sources retain their own terms. Embedded Liberation Sans font software retains its accompanying font licence.

How to cite this work

Dr. Carsten Stöcker (2026-10-31). “European Business Wallets: A Conditional Roadmap for the Single Market, Cyber-Resilience and Accountable Automation.” Spherity GmbH. https://spherity.github.io/spherity-research/ebw-roadmap.html. Licensed CC BY 4.0.

Direct answers

Questions this research answers

What is the European Business Wallet?

European Business Wallets are proposed digital infrastructure for economic operators and public bodies to identify themselves, exchange verifiable business evidence and demonstrate authority across borders. The practical goal is a completed, accountable transaction. The final EBW regulation had not been established in the official record reviewed on 31 October 2026.

When will European Business Wallet acceptance become mandatory?

There was no adopted final EBW acceptance date at the 31 October 2026 evidence cut-off. The Commission proposal uses regulation entry into force plus 24 months; the Parliament ITRE and Council positions use different implementing-act triggers plus 24 months. The paper’s 2029, 2030 and 2031 examples are conditional calculations, not forecasts or legal deadlines.

What is the difference between an EUDI Wallet and a European Business Wallet?

Typical personal EUDI Wallet use emphasises user-controlled identity and attribute disclosure. A business-wallet operating profile adds organisational evidence, scoped mandates, multiple roles, APIs and process automation. They complement each other; this is not an exclusive legal or technical division, and the EUDI framework also addresses legal persons. Privacy and access protection matter to both.

Is d-you the European Business Wallet?

No. d-you is Germany’s national EUDI Wallet example for personal digital identity and attestations. European Business Wallets follow a separate proposed framework for economic operators and public bodies. A person’s EUDI Wallet can work alongside a company’s business wallet to establish identity and authority.

How can companies start before final EBW legislation?

Choose one lawful recurring transaction, name the process and benefit owners, involve a real receiver and a competent source, and set cost and resilience baselines. Section 19 recommends a controlled pilot, explicit expand/adjust/stop criteria and modular technology with a migration budget. Earlier bounded use does not establish conformity with future EBW rules.

How do business wallets support Trusted AI and cyber-resilience?

They can supply verifiable organisational identity and bounded authority to policy enforcement, helping make automated actions attributable and revocable. Test replay, stale evidence, compromised endpoints and recovery. Wallets do not prove the correctness of AI outputs or the safety of physical actions; separate model, runtime and safety controls remain necessary.

When is the Spherity EBW-ready Business Wallet launch with Bundesanzeiger Verlag planned?

Spherity plans general availability of its EBW-ready Business Wallet in Q1 2027 (January–March 2027) on BSI-certified infrastructure. The wallet builds on work developed with Bundesanzeiger Verlag and tested in WE BUILD. The exact launch day has not been announced. This company plan, stated on 31 October 2026, is separate from final EBW regulatory conformity.

What is Bundesanzeiger Verlag’s role in Spherity’s EBW-ready Business Wallet?

Spherity and Bundesanzeiger Verlag developed a European Business Wallet and tested it in WE BUILD. Bundesanzeiger Verlag contributes verified business information for company identity, representation and related enterprise processes. Spherity is productising this work as an EBW-ready Business Wallet, with general availability planned for Q1 2027 on BSI-certified infrastructure.