A lightweight authentication API that adds secure login to your website or application without user accounts or a password database.
QR issuance is protected by e-mail verification, while passwords and e-mail addresses are not permanently stored by QR Login.
Give Access. Not Accounts.
Before a QR access key is issued, QR Login verifies the user's e-mail address with a one-time verification code. The QR is generated only after the correct code is entered.
Enter your e-mail address, Private Phrase and password.
A six-digit verification code is sent to the e-mail address.
Enter the verification code to confirm the e-mail address.
The cryptographically protected DSQR access key is generated.
Your service sends the QR access key and password to the API. The API verifies them and returns an authentication result. Your service then decides what the user can access.
Existing website, portal, app, or service.
User presents the QR access key and password.
Cryptographically verifies the login credentials.
Your service grants or denies access.
Watch how easy it is to use QR Login.
The API is not tied to one cloud service. It can be connected to many kinds of existing web services and applications.
Add lightweight login to private pages without building a conventional account system.
Protect training videos, manuals, reports, or downloadable documents.
Give authorized staff access to selected internal pages or resources.
Provide project-specific or customer-only information without creating permanent accounts.
Control access to event materials, VIP pages, or participant-only information.
Provide controlled access to course material, assignments, tests, or class resources.
Users do not need to create and maintain another service account.
QR Login does not store user passwords on the server.
The e-mail address is used only during QR issuance verification and is not maintained as a user account record.
A one-time e-mail verification code must be confirmed before the DSQR access key is generated.
DSQR access keys use cryptographic verification to detect invalid or modified authentication data.
Add authentication to an existing service while keeping your application in control.
QR Login combines e-mail verification for QR issuance with cryptographically protected DSQR access keys and password-based login verification. Modification of the QR authentication data invalidates authentication.
DSQR uses an ECDSA-based digital signature mechanism for self-authentication. The signature and verification algorithms are extended so that the user's password is mathematically incorporated into the authentication process, rather than being stored directly inside the QR code.
Because the security parameters used in DSQR generation change each time a new DSQR is issued, the resulting digital signature also changes, even when the same password is used. The password therefore does not appear as fixed or recoverable data in the DSQR.
This design makes recovery of the original password from the DSQR code or its digital signature computationally infeasible, while allowing the DSQR itself to provide cryptographic authenticity verification.
Create a DSQR access key with e-mail verification, try the login flow, and imagine it connected to your own web service.