Skip to main content
Every Veriqa scenario is built from one of two mechanisms. The user experience is the same in both — a QR code on screen or a button on the phone, then one tap in a messaging app — but who starts the transaction and what comes back are different.

Sign-in and registration

Signing in through Veriqa: your app sends the browser to the sign-in page by an OpenID Connect redirect, the person confirms in a channel, and Veriqa redirects back so your app can exchange the code for tokens.
The ordinary OpenID Connect flow. Your application sends the user to /connect/authorize, the sign-in window shows a QR code (or a channel button on the phone), the user confirms in the messaging app, and your application exchanges the code for tokens at /connect/token.
  • Registration happens in the same step — there is no form and no password to create.
  • The result is an id_token with sub, auth_time and the claims you asked for; the session is yours to open.
  • Your application stays a plain OIDC client: no Veriqa package, no SDK, only configuration.
Signing in on a computer with Telegram: the sign-in window shows a QR code, the phone camera scans it, the user taps Confirm in the Telegram chat, and the chat replies "Sign-in confirmed".

A sign-in: a QR code, the phone camera, one tap in the messaging app.

Details: Passwordless sign-in and registration, How the auth flow works.

Server-to-server transaction

Confirming an action through Veriqa: your server creates the transaction, the person scans the QR code your app shows and confirms in a channel, and your server reads the answer and performs the action.
A confirmation your backend asks for, with no sign-in and no browser redirect. The backend gets a token with the Client Credentials grant, creates the transaction with POST /api/transaction/confirmation for a declared action type, shows the user the QR code or link from the response, and reads the outcome with GET /api/transaction/{id}/result.
  • The user sees wording declared on your host with typed slot values — “Delete ticket A-900?”, “Buy for 4.99 EUR?” — never free text from the caller.
  • expected_identities lets only a specific person confirm — for example the owner of the current session.
  • No session is created. A confirmed transaction can optionally be exchanged for the id_token of the person who confirmed.
Confirming an action: the app shows a QR code for deleting a project, the phone camera scans it, the user gets the request in Telegram, and the decision goes back to the app.

A server-to-server transaction: the app shows a QR code, and the user scans it with their phone camera and declines the request in Telegram. The app receives the answer.

Details: Server-to-server confirmation API.

How they differ

Rule of thumb. If the result should be “the user is signed in”, use sign-in. If the result should be “this action is confirmed” — and your server performs the action — use the server-to-server transaction.

Scenarios and their mechanism

Every use case is listed on All use cases.