Gallery - Veriqa Docs

The screenshots were taken from demo applications and samples running on the Veriqa core, version 0.7.0. Each channel also has its own page: Telegram, WhatsApp, Messenger, Instagram, Google, Email.

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.

Telegram

Signing in on a computer

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". — The user scans the QR code with their phone camera and confirms in the Telegram chat.

Signing in on a phone

Signing in on a phone: the user taps "Sign in with Telegram", confirms in the Telegram chat, and the chat replies "Sign-in confirmed". — The user taps "Sign in with Telegram" and confirms in the Telegram chat.

Step-up: confirming an action

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. — 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.

Collecting extra details at sign-in: after confirming in Telegram, the user shares a phone number, fills in the missing fields of a short form, confirms the email with one ready-made message, and the app receives the verified claims. — At sign-in, your app gets what the messaging app doesn't provide: a phone number, answers to a short form and a confirmed email address.

The last frame of the animation shows test values from a real ID token.

Claims your app can get

Claims your app can get from signing in with Telegram: sub, amr, channel_type, channel_user_id, name, given_name, family_name, preferred_username, locale, picture, phone_number, phone_number_verified true, and email with email_verified after an email confirmation.

WhatsApp

Signing in on a computer

Signing in on a computer with WhatsApp: the phone camera scans the QR code, WhatsApp opens a ready-made message, the user sends it, taps Confirm, and the chat replies "Sign-in confirmed". — The user scans the QR code with their phone camera, sends the ready-made message in WhatsApp and taps Confirm.

Signing in on a phone

Signing in on a phone with WhatsApp: the user taps "Sign in with WhatsApp", sends the ready-made message, taps Confirm, and the chat replies "Sign-in confirmed". — The user taps "Sign in with WhatsApp", sends the ready-made message and taps Confirm.

Step-up: confirming an action

Confirming a purchase with WhatsApp: the app shows a QR code, the phone camera scans it, the user sends a ready-made message, taps Confirm, and the chat replies "Purchase confirmed". — The app shows a QR code, and the user scans it with their phone camera, sends the ready-made message in WhatsApp and taps Confirm.

Claims your app can get

Claims your app can get from signing in with WhatsApp: sub, amr, channel_type, channel_user_id, name, given_name, preferred_username, phone_number, phone_number_verified true, and email with email_verified after an email confirmation.

Messenger

Signing in on a computer

Signing in on a computer with Messenger: the sign-in window shows a QR code, the phone camera scans it, the user taps Confirm in the Messenger chat, and the chat replies "Sign-in confirmed". — The user scans the QR code with their phone camera and confirms in the Messenger chat.

Signing in on a phone

Signing in on a phone: the user taps "Sign in with Messenger", confirms in the Messenger chat, and the chat replies "Sign-in confirmed". — The user taps "Sign in with Messenger" and confirms in the Messenger chat.

Step-up: confirming an action

Confirming a purchase: the app shows a QR code for a $99 plan, the phone camera scans it, the user confirms in Messenger, and the chat replies "Purchase confirmed". — The app shows a QR code, and the user scans it with their phone camera and confirms the purchase in Messenger.

Claims your app can get

Claims your app can get from signing in with Messenger: sub, amr, channel_type, channel_user_id, name, given_name, family_name, locale, picture, phone_number, phone_number_verified false, and email with email_verified after an email confirmation.

Instagram

Signing in on a computer

Signing in on a computer with Instagram: the sign-in window shows a QR code, the phone camera scans it, the user taps Confirm in the Instagram chat, and the chat replies "Sign-in confirmed". — The user scans the QR code with their phone camera and confirms in the Instagram chat.

Signing in on a phone

Signing in on a phone: the user taps "Sign in with Instagram", confirms in the Instagram chat, and the chat replies "Sign-in confirmed". — The user taps "Sign in with Instagram" and confirms in the Instagram chat.

Step-up: confirming an action

Confirming an action: the app shows a QR code for deleting a project, the phone camera scans it, the user confirms in Instagram, and the chat replies "Confirmed". — The app shows a QR code, and the user scans it with their phone camera and confirms the deletion in Instagram.

Claims your app can get

Claims your app can get from signing in with Instagram: sub, amr, channel_type, channel_user_id, name, preferred_username, picture, phone_number, phone_number_verified false, and email with email_verified after an email confirmation.

Google

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.

Email

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.