Skip to main content

​
General scheme

A sign-in starts in your app: it sends the browser to the sign-in page with a standard OpenID Connect redirect. The user confirms in a channel, and the browser returns to your app with a code that your app exchanges for tokens.
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.
An action confirmation starts on your server: it creates a transaction through the Veriqa API. The user confirms in a channel, and your server reads the answer and performs the action. The browser is not redirected.
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.
See Basic scenarios.

​
Signing in on a computer

Signing in on a computer by email: QR code, phone camera, the user sends a ready-made email, the page verifies the sender, and the user confirms the sign-in on the computer.

The user scans the QR code with their phone camera, sends the ready-made email and confirms the sign-in on the computer.

​
Signing in on a phone

Signing in on a phone by email: the user taps the email button and sends a ready-made email, the page verifies the sender, and the user confirms the sign-in.

The user taps "Send confirmation email", sends the ready-made email and taps Yes on the confirmation page.

​
Claims your app can get

Claims your app can get from signing in with Email: sub, amr, channel_type, channel_user_id, name, email, email_verified, preferred_username, veriqa_channel, veriqa_email_mode.