Skip to main content

Built-in channels

The channels that ship with Veriqa: messaging apps, email and sign-in with a provider account.

Every channel issues the base claims: channel_type channel_user_id name

A channel card lists what the channel adds on top of them.

— the phone number: it comes only when the application asks for it, and each channel returns it in its own way. More about the phone number

Built-in channels

Available

They ship with Veriqa. The Docker image and the OS service already include all of them — you only enable the ones you need in configuration. When Veriqa is embedded in a .NET application, each channel is a package of its own: install only the ones you need. Eight channels — Telegram, WhatsApp, MAX, Instagram Direct, Messenger, WeChat, Viber and email.

Email

Claims on top of the base
  • email
  • email_verified
  • preferred_username
  • veriqa_channel
  • veriqa_email_mode
Confirmation in the channel
No — optionally in the browser
Secret message
Yes, or a classic magic link

Sign-in with a provider account

Available

Sign-in with a Google, Apple, Huawei, Yandex or VK ID account — or with any other of the 80+ providers the OpenIddict client supports. The screen shows a QR code, the user signs in to their account on their own phone and confirms on a page there, and the sign-in completes on the screen. It helps wherever a password cannot be typed or is risky to type — on a TV, on a shared computer — and a user who has none of the messaging apps can sign in too. Even on your own computer a social sign-in through a QR code is safer: the password of your account is never typed there, so malware has nothing to intercept. And since nobody types a password each time, sessions can be kept shorter, which lowers the risk too.

The full list of providers is on this page.

Terms

A channel card says whether a secret message is needed, whether there is confirmation in the channel and how the phone number comes. Here is what that means.

Secret message

The message with the sign-in code that the user sends to the channel themselves after tapping the link or scanning the QR code. Veriqa fills it in, the messaging app shows it ready, and the user only taps Send. Not every channel needs one.

Telegram, MAX
Not needed — the messaging app opens the bot and hands it the code by itself.
WhatsApp
Needed, for stronger security — the ready message goes out with one tap.
Email
The same with a pre-filled message — the one-tap email.

Confirmation in the channel

The bot asks right in the chat whether to let the sign-in through — into which app and from which device — with Confirm and Decline buttons. It can be switched to automatic mode, and then the sign-in goes through without an extra request.

MAX, Telegram
The question comes as soon as the user opens the link.
WhatsApp
The question comes in reply to the secret message.
Email
No question in the channel — optionally it is asked on a page in the browser.

Phone number

Veriqa takes the number only from the channel — the messaging app hands it over, the user never types it. It comes when the application asks for the phone scope, and each channel returns it in its own way; phone_number_verified says whether the channel proves the number is the user's.

WhatsApp
The simplest: the number comes with every message, nothing is asked.
Telegram, MAX
The bot asks after the sign-in is confirmed: the user shares their own contact with one button. MAX — in webhook mode only.
Other channels
A button or the profile without proof of ownership, only your own integration with the platform, or no number at all.

Secret message — examples

WhatsApp: the secret message filled in by Veriqa, ready to send
WhatsApp
Email: the sign-in message filled in by Veriqa, ready to send
Email

Confirmation in the channel — examples

Telegram: the bot asks to confirm the sign-in, with Confirm and Decline buttons
Telegram
WhatsApp: the user has sent the secret message, and the bot asks to confirm the sign-in
WhatsApp