swiyu Public Beta – Test services and integration in advance

With swiyu, you accelerate workflows and reduce risks as well as efforts in the areas of data security and compliance by integrating the e-ID, driving licences and other digital credentials of the Swiss Confederation into your processes or by developing tailored solutions for your organisation.

As part of the Public Beta, you test the integration of digital credentials into existing processes within the Confederation’s publicly accessible trust infrastructure and gain experience with the technology, organisation and processes of this infrastructure before it goes live.

Benefits of swiyu

Participation in the Public Beta

By participating, you gain the opportunity to develop tailored concepts and solutions for the planned swiyu ecosystem at an early stage and to gain first-hand experience with the technology, organisation, and processes of the trust infrastructure – even before it is introduced into productive operation.

The experience and know-how gathered can be reused for implementation in the productive environment, thereby accelerating the overall rollout process.

The number of participants is unlimited, and no participation fees are charged.

How you can use swiyu in your company or organisation in the future

swiyu offers organisations a wide range of integration options for existing processes and workflows – from age verification at a supermarket checkout to complex, custom applications for issuing and verifying digital credentials of all kinds.

Age verification in online retail

Use the e-ID to reliably verify the age of your customers when selling age‑restricted products in your online shop.

Integrating the e-ID into your process offers the following benefits:
• Increased efficiency: age verification is automated, eliminating the need for manual checks.
• Legal certainty: the e‑ID issued by Switzerland meets the legal requirements.
• Data minimisation: only whether the user is old enough is checked.

Test applications from the Public Beta

• Neovo Brewing Company

  Test the age verification process for purchasing age‑restricted products in a fictional online shop.

  Links:

  • Test application
  • Issuer / Verifier

• Unchained Commerce

  Test the age verification process for purchasing age‑restricted products in a fictional online shop.

  Links:

  • Test application
  • Issuer / Verifier

Digital certificates and credentials

Issue digital diplomas and certificates as proof of qualifications or verify them, for example as part of application processes.

The use of digital diplomas and certificates offers the following advantages:
• Increase efficiency: the authenticity of qualifications is verified automatically, without manual checks.
• Accelerate processes: recruitment and application procedures are shortened through immediate verification.
• Forgery protection: digitally issued credentials are tamper‑proof.

Test applications from the Public Beta

• Digital Maturity Certificate

  Pilot project for the use of the Beta ID and other digital credentials in the student enrolment process.

  Links:

  • Test application
  • Issuer / Verifier

Digital employee IDs

Issue digital employee ID cards and control access to IT systems as well as access to premises.

Using digital employee ID cards offers the following advantages:
• Increase efficiency: access controls are automated, without manual checks.
• Reduce costs: no issuance, management, or replacement of physical ID cards is required.
• Data minimisation: only the necessary employee data is used, with no central storage.
• Reduce risks: credentials are tamper‑proof, thereby almost completely eliminating fraud and operational risks.

Test applications from the Public Beta

• Digital ID for SBB Employees

  Digital test ID for secure access to IT systems and, in the future, additional application scenarios for SBB employees.

  Links:

  • Issue ID
  • Verify ID
  • Issuer / Verifier

• Fictional Membership ID

  Example of the complete process—from issuing to verifying a digital membership ID using the trust infrastructure.

  Links:

  • Test application
  • Issuer / Verifier

Further practical examples from the swiyu Public Beta

Within the swiyu Public Beta, new fields of action are identified, application scenarios are developed, solutions are created, and published on GitHub. Here you can subsequently find information about these test applications.

• Authorities & administration

  Beta-ID

  Issue a Beta-ID, verify it and revoke it if necessary.

  Links:

  • Test application
  • Issuer / Verifier

  ---

  AGOV-Integration

  Log in to the fictitious Alphaoffice authority using the Beta-ID via AGOV.

  Links:

  • Test application
  • Issuer / Verifier

• e-Democracy

  e-Collecting

  Support fictitious referendums and popular initiatives with the Beta-ID. The confirmation is issued as a credential into the swiyu Wallet.

  Links:

  • Test application
  • Issuer / Verifier

  ---

  Blockchain-based e-Collecting

  After identification with the Beta-ID, the ‘signature’ is stored as a smart contract on a blockchain.

  Links:

  • Test application
  • Issuer / Verifier

The e-ID programme assumes no responsibility for these applications.

How to get started

Test the Public Beta now to quickly build your first proof‑of‑concept (showcase) for your organisation or public authority. Gain hands‑on experience with the trust infrastructure and create momentum for the digitalisation of your own business cases – from simple identity or age verification using the swiyu Check App to issuing your own digital certificates, tickets, or employee IDs.

Follow the steps below to build your individual test solution:

Step-by-step to your own showcase

• 1. Define your use case & choose your solution variant

  Consider which specific problem you want to solve: do you want to issue digital credentials (Issuer) or verify them (Verifier)? Decide whether to use the federal government’s open‑source reference solutions (swiyu Generic Issuer / Generic Verifier), rely on DVS4U (a tailored software‑as‑a‑service solution for authorities), or develop your own solution for your organisation or as a service for your customers.
  Further information can be found in the documentation and guides (How to use Beta-ID for my business, Onboarding the swiyu Base & Trust Registry, Getting started with the swiyu Generic Issuer, Getting started with the swiyu Generic Verifier, Designing the visualization for Issuer, Verifier and Credential).

• 2. Register your organisation in the swiyu trust infrastructure

  Start the onboarding process by registering your organisation via the swiyu Service Portal. This requests a free entry in the Public Beta base and trust registry, making you visible to other participants as a trusted Issuer or Verifier.

• 3. Generate DID(s) and manage cryptographic key material

  Use the provided DID Toolbox to generate your cryptographic key material. This creates your own “Decentralized Identifier” (DID), which is stored in the base registry and forms the foundation for secure and tamper‑proof communication within the trust infrastructure.

• 4. Build your individual solution (setup)

  Install and configure the swiyu Generic Issuer or swiyu Generic Verifier in your IT environment. With these generic components, you can easily implement and test issuance and verification processes in your own systems without having to develop these complex components yourself.

• 5. Test your proof‑of‑concept (showcase)

  Actively test the trust infrastructure: issue your first test credentials, revoke them, or verify a Beta ID issued by the federal government until the official e‑ID becomes available. For end‑to‑end tests, you can use the swiyu Wallet App (holder perspective) and the swiyu Check App (for verifiers).

• 6. Engage, collaborate, and provide feedback!

  Become part of the swiyu community today! Get in touch with us and exchange ideas with other projects and organisations. On GitHub you will find detailed guides, technical documentation, and direct support. Share your showcases and test applications with us and send us your feedback ([e-mail]) – helping us further improve the system for the productive rollout.

Further information and technical documentation

Organisations and individuals who wish to verify e‑IDs as well as issue and verify other digital credentials can do so as part of the Public Beta.

It is particularly possible to simulate the verification of an e‑ID using the Beta ID. The Beta ID has the technical characteristics of the future e‑ID but has no legal validity.

With the swiyu Generic Issuer and the swiyu Generic Verifier, issuance and verification processes can be easily implemented in your own systems. These software components are available free of charge as open‑source software.

Technical documentation and cookbooks

Currently, only a test environment (Preview) of the swiyu trust infrastructure is available. This environment allows credentials to be issued and verified. All credentials issued in the test environment are marked as “Demo”.

Entry in the Public Beta base and trust register

If you have questions or encounter issues, we recommend consulting our help topics. You can also open a support ticket; we will contact you as soon as possible.

Go to help

Data protection in the Public Beta

Anyone using the Public Beta is responsible for protecting any data they may process. It is recommended to use test data only.

Terms of use and data protection policies of the individual products

Security of the Public Beta

The availability of the Public Beta is ensured on a best‑effort basis. A bug bounty programme (reward for ethical hackers) was launched during 2025 to test the systems, identify potential vulnerabilities, and address them.