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 with Google: the phone camera scans the QR code, the user picks a Google account, taps Yes on the confirmation page, and sees "Sign-in confirmed".

The user scans the QR code with their phone camera, picks a Google account and taps Yes on the confirmation page.

​
Signing in on a phone

Signing in on a phone with Google: the user taps "Sign in with Google", picks an account, allows access on the first sign-in, taps Yes, and sees "Sign-in confirmed".

The user taps "Sign in with Google", picks an account and taps Yes on the confirmation page. Google asks for consent only on the first sign-in.

​
Claims your app can get

Claims your app can get from signing in with Google: sub, amr, channel_type, channel_user_id, name, email, email_verified, given_name, family_name, locale, picture.