Switzerland’s e-ID and the Swiyu Wallet: What Businesses Need to Know Before the 2026 Launch

Key Takeaways

• Swiss voters approved the eID Act by 50.39% on 28 September 2025, a margin that continues to shape how cautiously the rollout is handled.
• The Swiss e-ID is voluntary and free of charge and complements rather than replaces physical identity documents.
• Go live moved from summer 2026 to 1 December 2026 after a federal audit found unfinished work on data encryption and trust infrastructure.
• Credentials use SD-JWT with selective disclosure, so a user can prove one attribute without revealing the rest.
• Businesses accepting the credential must register their intended data requests and purpose in a public federal register beforehand.

Picture this: your son wants to buy an age-restricted game online. The platform checks age by examining his physical ID card. That card discloses his full name, exact date of birth, address in some cases, ID number, nationality and photograph. The platform only needs to ensure age; a proof he’s over 18. As it stands today, it receives roughly a dozen. Anything retained becomes a data protection liability, and if breached, that ID image is exactly what ends up on the darknet. 

Governments around the world are aware of the risks this compliance issue bring forth and are establishing digital identification mechanisms as a solution. Switzerland activates its national electronic identity on 1 December 2026. For organizations verifying customers in Switzerland, from banks and insurers to marketplaces and platforms selling age restricted goods, the Swiss digital ID introduces a new way for users to prove who they are, plus obligations for businesses that accept it. 

Here is what the framework does, how the wallet works, and what integrating as a relying party involves.

What Is Switzerland’s e-ID Act?

The Federal Act on Electronic Identity and Other Electronic Evidence, known as the e-ID Act or BGEID, creates the legal basis for a state issued digital identity. The Confederation issues the credential directly, and use is optional and free.

That design responds to history. In 2021, voters rejected an earlier proposal by more than 64%, largely because private companies would have controlled issuance. The revised law puts the federal government in that role. Even so, the 2025 referendum passed by roughly 3,000 votes, and privacy concerns from that campaign have driven several subsequent design changes.

After the vote, the Federal Office of Justice was instructed to address the main criticisms before launch. The resulting safeguards affect businesses directly:

• Only legally authorized providers may request a user’s AHV social security number, and unauthorized attempts are blocked automatically.
• Providers must register intended data queries and purposes in advance in a publicly accessible federal register.
• If a provider requests more than it registered, or does not appear in the register, the app warns the user, who can report the abuse to the Federal Office of Justice.
• As a final measure, the FOJ can revoke a provider’s access entirely.

If you are new to the underlying concepts, our overview of what identity verification involves is a useful starting point.

The Swiyu Wallet: Architecture and Key Features

Swiyu is not a companion app to the e-ID. It is the delivery mechanism. Users receive, store, and present their credential through it, making this a mobile first national rollout.

Several technical choices matter for businesses:

• Credential format. Credentials follow the IETF SD-JWT VC specification, signed with ECDSA on the NIST P-256 curve, applied per the Swiss Profile for Verifiable Credentials.
• Selective disclosure. Each identity statement is encoded as a hash of the raw claim combined with a random nonce, with all hashes and metadata cryptographically signed. A holder can reveal individual claims while keeping the rest private, and the verifier still confirms authenticity and integrity.
• Base and Trust Registries. The Confederation operates a central Base Registry holding decentralized identifiers and their DID documents, letting issuers publish lifecycle status so verifiers can check whether a credential has been revoked or suspended. A separate Trust Management System issues signed trust statements about entities. The ecosystem currently supports the did:webvh (Decentralized Identifier Web with Verifiable History) method.
• Linkability protections. The Federal Council states each holder will receive multiple technically distinct credentials, each usable once, so transactions cannot be cross referenced. The published interoperability profile notes batch issuance supporting this is planned for a future release, so treat it as a roadmap item rather than a shipped feature.

What the 1 December 2026 Launch Means

The original target was summer 2026. A February 2026 audit by the Swiss Federal Audit Office found several tasks around issuance and trust infrastructure incomplete, including a finalized concept for end-to-end encryption of user data that had been due at the end of 2025. The Federal Council then delayed go live to 1 December.

Two implications follow. Treat the date as a plan rather than a certainty, since it has already moved once for technical reasons. And note that parliament cut the e-ID budget by CHF 1.7 million for 2026, suspending development tracks including international interoperability, a federal backup service, and issuance of e-IDs in third party wallets. Officials say security is unaffected, but scope is.

Through 2026, the Public Beta Trust Infrastructure is intended to mirror production, giving developers somewhere to test before deploying changes.

How Businesses Can Integrate with Swiyu as a Relying Party

Organizations accepting the credential act as verifiers. The Confederation publishes an open-source generic verifier alongside documentation. The onboarding path involves:

1. Register on the Swiyu Trust Infrastructure portal and the API self service portal.
2. Generate signing keys, using the provided DID Toolbox or an equivalent.
3. Create and register a DID on the identifier registry, following the Base and Trust Registry documentation.
4. Deploy a verifier service and publish verifier metadata at a dedicated endpoint. Presentation requests follow OpenID for Verifiable Presentations, with DIF Presentation Exchange expressing what is requested.
5. Apply for recognition as a trusted verifier through the official request process.
6. Register your data queries and purposes in the public federal register before going live.

Sample configurations are built for experimentation rather than production, with separate guidance for live environments. For regulated firms, reconcile the request scope you register against existing obligations under KYC regulations, so you do not register broader access than your legal basis supports.

Swiyu vs. EUDI Wallet: Key Similarities and Differences

The similarities are substantial. Both are voluntary, both use verifiable credentials with selective disclosure, both support online and offline identification, and both target portable proof of identity. Our analysis of the EU Digital Identity Wallet under eIDAS 2.0 covers the European side.

The differences matter more for planning:

• Legal basis. As a non-EU state, Switzerland is not bound by eIDAS 2.0. It legislated independently and pursues conceptual alignment by choice, not obligation.
• Acceptance obligations. The EU regulation imposes acceptance duties on certain sectors. Swiss law does not replicate that, so accepting the credential is largely a commercial decision.
• Interoperability. Full technical interoperability did not exist as of spring 2026, and the Swiss interoperability track was among the items suspended by the budget reduction.
• Timing. Switzerland aims for December 2026, while EUDI wallet rollout is expected to extend into 2027 and beyond.

For multinationals tracking Switzerland digital identity alongside the EU rollout, eIDAS compliance work and Swiss integration are related but separate programs. Architecture built on shared standards transfers reasonably well. Legal analysis, registration, and trust onboarding do not.

FAQ