VeriGate issues your organisation's digital credentials for the federal swiyu Wallet, and verifies them. No IT project needed, in your own branding, operated in Switzerland.
Name and address stay in the wallet.
For companies, municipalities, schools and associations without their own IT project. In the wallet, each credential shows its name, the issuer and your logo, in your colour.
Revoked when someone leaves, instead of chasing plastic cards.
SMEsIndustryAdministrationCertificate of residence, recycling centre pass or resident parking permit, into the wallet by link or QR code. Parking permit process Recycling centre process
MunicipalitiesCitiesShown on site or to a client, forgery-proof and verifiable instantly.
ConstructionVocational trainingSchoolsAccess and permits, time-limited and revoked at once if necessary.
Public authoritiesHealthcareIndustryTime-limited, also for temporary staff, and checked at a staffed reception.
IndustryLogisticsInstead of a plastic card, and revoked in the console when someone leaves.
AssociationsSports clubsThe organisations in these examples are invented.
Your staff work in the VeriGate console. Holders only need the free swiyu Wallet.
Set the colour, logo and details, in four languages. The preview shows the credential as it appears in the swiyu Wallet.
Enter the details, supply them from your system or take them from a check. VeriGate creates a QR code or link, and the person adds the credential to their wallet.
When it is presented, the verifier sees only the details it needs. If a credential no longer applies, you revoke it at once.
VeriGate requests a credential from the wallet and checks it: genuine, from the right organisation, not revoked, still valid. This applies to your own credentials and, once it is available, to the e-ID. What happens next is up to you.
Once it is available, the e-ID will supply the details for a new credential directly: name and date of birth from the verified e-ID, not typed in at a counter. No more typing errors or forged copies.
This is only the start: credentials can build on each other, and more processes will follow. More in the article “Verify first, then issue”
VeriGate runs entirely in a data centre in Switzerland, with a Swiss provider. What you issue, verify and revoke is processed and stored only there.
A digital credential carries a forgery-proof signature. Whoever checks it sees only the details needed for that purpose.
For the swiyu Wallet, your organisation is entered in the federal base registry and trust registry. The Federal Office of Justice checks its identity for this, and the wallet shows your organisation with a green tick. The signature proves that the credential comes from you.
At the recycling centre entrance, staff see that someone lives in the municipality, but not their name or address. The holder sees in the wallet what is requested, and shares it.
Someone leaves, moves or loses a phone: one click in the console, and the credential is no longer valid at the next check.
Your staff sign in with a second factor or directly with an access credential in the swiyu Wallet. Roles separate administration from casework.
The log records who issued, verified or revoked what and when, but never the content of a credential.
The easiest place to start is the console. As numbers grow, your existing system takes over the issuing.
Design, issue, verify and revoke credentials. In English, German, French and Italian.
Your HR, CRM or specialist system issues credentials itself, for example when someone joins or a permit is granted.
POST …/credential-types/parking-permit/offers
{ "claims": { "zone": "B",
"number_plate": "BE 482 117",
"valid_until": "2027-12-31" } }How the integration works →Anyone working in your console signs in with their own access credential from the swiyu Wallet. No password to forget or pass on.
You decide which credential comes first. We help you with the rest.
We clarify what you check today and which credential brings the greatest benefit.
Your organisation is entered in the federal base registry and trust registry. This requires a registered office in Switzerland and a UID number. For the test phase, the free test registries are enough.
Set up checks, design, details and access. Until production starts, everything runs in swiyu Sandbox, and a test credential goes to the swiyu Sandbox Wallet on your phone, the federal test app.
Your staff issue credentials. We operate the platform in Switzerland and keep it up to date.
How a new digital credential takes over verified details, the process with the e-ID, chains of credentials, and what already works today.
Read article →Colour, logo, texts in four languages, details and groups: what the swiyu Wallet shows, and what makes a good design.
Read article →Integration through the REST interface: access, process, error cases and revocation, with examples you can follow.
Read article →Which certificates are worth doing first, what the residents' registration office needs to consider, and how to take pressure off the counter.
Why the recycling centre does not need your name, and why no check happens without your consent.
What the FADP and the CLOUD Act mean for credentials, and which questions to ask any provider.
For organisations that want to issue or verify credentials without setting up their own IT project: companies, municipalities, schools and associations. For the swiyu Wallet, the federal government requires a registered office in Switzerland and a UID number.
The federal trust infrastructure is expected to become operational in the first half of 2027. Until then, we set up and test your credentials in swiyu Sandbox. The federal government postponed the e-ID in June 2026, and there is no new date yet.
Your own credentials do not need the e-ID. Your staff enter the details or supply them from your system, or VeriGate takes them from another verified credential.
If you only want to verify the e-ID and connect nothing to your systems, often yes: the federal government plans the free swiyu Check app for that. VeriGate is worthwhile if you issue or verify your own credentials, need roles and a log, or want a check to lead straight to a new credential.
No. VeriGate is operated for you. Your staff work in the browser. Connecting your systems is possible, but not necessary to start.
In a data centre in Switzerland, with a Swiss provider: database, keys, logs and email sending. No data is transferred abroad, and no US cloud services are involved.
The free federal swiyu Wallet on their phone. A QR code or link is enough to collect a credential. Until production starts, testing uses the swiyu Sandbox Wallet, the federal test app.
No. For every check, the swiyu Wallet shows who is asking, whether that organisation is registered with the federal government, and which details it requests. The details are transmitted only once you share them.
You revoke the credential in the console and issue a new one. The old one is no longer valid at the next check.
What is needed for issuing and revoking. The log records which details were issued or verified, never their values.
Yes. Each credential has its own design and details. Start with one and add more once the first is running.
It depends on the number of credentials and checks. After the first call, you receive a quote from us. In addition, under the current ordinance, there are one-off federal fees: CHF 150 per identifier in the base registry and CHF 350 for the trust registry. Public authorities and public educational institutions can request an exemption from the Federal Office of Justice.
In a call, we show you what it would look like and what it takes to start. No obligation.