Verify first, then issue
A credential is only as reliable as the details it is made from. That is why, with VeriGate, much starts with a check: the new credential takes over what a verified credential confirms.
The problem with typed-in details
Today, an ID card or confirmation is usually made like this: someone presents a copy, a member of staff types in the name and date of birth, and in the end the document says what was entered. The result does not show whether the copy was genuine or whether it was typed correctly.
With the e-ID, it works differently. The person presents their e-ID from the swiyu Wallet, VeriGate verifies it, and the confirmed details flow straight into the new credential. The federal government postponed the e-ID in June 2026; until it is available, the same process works with any other credential from the wallet.
How a process runs
- A member of staff starts a process in the console, for example “Verify e-ID, issue staff ID”.
- The person scans the first QR code and presents their e-ID. The app shows which details are requested, and the person shares them.
- VeriGate checks: genuine, issued by the federal government, not revoked, still valid.
- If the check is valid, VeriGate immediately creates the offer for the new credential. The console shows the second QR code.
- The person adds the staff ID to their wallet. The process is complete.
| Detail on the staff ID | Where it comes from |
|---|---|
| First name | from the e-ID |
| Last name | from the e-ID |
| Date of birth | from the e-ID |
| Department | fixed value, for example “Workshop” |
| Valid until | fixed value, for example 31.12.2027 |
Credentials that build on each other
Not only the e-ID can be verified, but any credential from the swiyu Wallet, including one you issued yourself. This creates chains:
For municipalities, it works the same way: the e-ID confirms the person, the register of residents confirms the residence, and the recycling centre pass is made from these. At the entrance, the person shows it and shares only that they live in the municipality. See the use case
What works today, and what comes next
- Verify onlyRequest a credential and see the result, without issuing anything.Available
- Verify, then issueA credential is verified, and a new one takes over its details.Available
- Verify several credentials togetherFor example the e-ID and a professional licence, before a permit is issued.In planning
- Renew after verifying the old credentialWhoever presents their current credential receives the new one, with no new details.Planned
- Revoke and reissue in one stepWhen someone moves or changes role: the old credential ends, the new one begins.Planned
- Started by your system or by the personWith no member of staff at the console, for example at a self-service terminal.Planned
Where to start
With the simplest process, the one that saves the most typing or copying today. Usually that is “Verify e-ID, then issue” for a single credential. Until the e-ID is available, the easiest start is a credential you issue and verify yourself. Chains can follow once the first credential is in use.