Use cases
One protocol for every door — digital or physical.
Digi-ID works anywhere you can show a QR code and receive an HTTPS callback. Here's how teams use it, and how to build each one.
Website & SaaS login
Eliminate passwords, reset flows, and SMS 2FA costs.
- Problem
- Password databases leak, users reuse passwords everywhere, and every reset or SMS code costs support time and money.
- With Digi-ID
- Show a Digi-ID QR code on the login page. The user scans, approves, and the callback signs the browser session in. You store one public address per user.
Benefits
- Nothing secret to steal from your database
- No password resets or SMS fees
- Faster sign-in on desktop and mobile
- Works next to existing passwords during migration
Flow
- 1 Login page requests a challenge
- 2 User scans the QR code
- 3 Wallet posts the signed URI
- 4 Server verifies and upgrades the session
Try it: Add Digi-ID login to a web app
Works with: digiid-js, digiid-php
Checkout without accounts
Returning customers, zero sign-up forms.
- Problem
- Forced account creation is a top reason for abandoned carts, yet guest checkout loses the returning-customer relationship.
- With Digi-ID
- Offer “Continue with Digi-ID” at checkout. The address becomes the customer ID; ask only for the shipping details you actually need.
Benefits
- One-scan return visits
- No password to forget between orders
- Collect only the data you need
- Order history without a password database
Flow
- 1 Checkout shows the Digi-ID option
- 2 Customer scans and approves
- 3 Store links the order to the address
- 4 Next visit: scan once to see orders
Gaming accounts
Bind player assets and profiles directly to wallet signatures.
- Problem
- Ranks, items and years of progress are lost to phishing, credential stuffing and forgotten passwords.
- With Digi-ID
- Use Digi-ID as the primary login or as a strong second factor for trades and account changes. Keys never leave the player's phone.
Benefits
- Phishing-resistant: signatures are bound to your domain
- No password to reuse or leak
- Confirm high-value actions with a scan
- Works for launchers, web portals and consoles with QR display
Flow
- 1 Launcher shows a QR code
- 2 Player scans with their wallet
- 3 Game server verifies the signature
- 4 Session token issued to the launcher
Doors, lockers & IoT
Replace swipe cards with a scan.
- Problem
- Access cards get lost, cloned and shared; changing who can enter means reissuing hardware.
- With Digi-ID
- Put a small screen at each door showing a fresh, short-lived Digi-ID challenge. One callback serves every door; the server knows which door issued each nonce, checks the address against that door's allow-list and triggers the lock.
Benefits
- No cards to issue or revoke
- Per-door audit trail by address
- Revoke access instantly in software
- Short challenge lifetime defeats photographed codes
Flow
- 1 Door screen shows a per-door QR code
- 2 Visitor scans and approves
- 3 Access server checks the allow-list
- 4 Lock opens and the event is logged
Identity & age checks
Cryptographically prove returning status without re-entering personal data.
- Problem
- Users upload the same ID documents to service after service, creating copies of sensitive data everywhere.
- With Digi-ID
- After a one-time verification, a trusted verifier links the result to the user's Digi-ID address for your service. Later visits just prove control of that address.
Benefits
- Stop re-collecting documents
- Store a verification flag, not a passport scan
- Hard to forge or share
- Pseudonymous by default
Flow
- 1 User completes a one-time ID check
- 2 Verifier records the address as verified
- 3 Later, user signs in with Digi-ID
- 4 Service trusts the stored verification
Internal tools & admin panels
Strong sign-in without an identity-provider bill.
- Problem
- Small teams run dashboards, CMS back-ends and staging servers with shared or weak passwords.
- With Digi-ID
- Allow-list staff addresses and require a Digi-ID scan to reach admin routes. Remove an address to revoke access immediately.
Benefits
- No shared admin passwords
- Instant revocation
- Free and self-hosted
- Easy to add in front of existing tools
Flow
- 1 Admin route requests Digi-ID
- 2 Staff member scans and approves
- 3 Server checks the staff allow-list
- 4 Short-lived admin session issued
Try it: Add Digi-ID login to a web app
Works with: digiid-js, digiid-php
Forums & communities
Pseudonymous, spam-resistant membership.
- Problem
- Communities fight spam sign-ups and account takeovers while members want privacy.
- With Digi-ID
- Let members link a Digi-ID to their forum account and sign in by scanning. Each forum sees a different address, so members can't be tracked across sites.
Benefits
- No email or phone required to sign in
- Per-site addresses protect privacy
- Account takeover via leaked passwords is gone
- Plugins exist for phpBB and WordPress
Flow
- 1 Member links Digi-ID in their profile
- 2 Login page shows a QR code
- 3 Member scans and approves
- 4 Forum signs the member in
Events & check-in
Dynamic ticket authentication that prevents screenshot fraud.
- Problem
- PDF and screenshot tickets are easy to duplicate and resell; check-in lines are slow.
- With Digi-ID
- Bind each ticket to the buyer's Digi-ID address. At the gate a screen shows a challenge; the attendee scans and the ticket is checked against the signed address.
Benefits
- Tickets tied to a key, not an image
- Fast gate check-in
- Transfer by re-binding to a new address
- No attendee personal data needed at the gate
Flow
- 1 Buyer links a ticket to their address
- 2 Gate screen shows a challenge
- 3 Attendee scans and approves
- 4 Server marks the ticket as used
Open source · Community built
Build the passwordless web with us.
Digi-ID has no company, no tokens to sell and no admin keys. Libraries, plugins and this site are maintained by volunteers. Ship an integration, improve a library or put your app on the map.