> ## Documentation Index
> Fetch the complete documentation index at: https://veriqa.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Messaging apps, email and account services

> The channels your users sign in and confirm actions through: messaging apps, email, account services such as Google and Apple, the adapters of the repository and a channel of your own over HTTP.

**Single sign-in.** Veriqa gives you one integration and your users one place to sign in or confirm
an action. A detailed comparison of Veriqa with other sign-in methods is on the page
[Sign-in methods compared](https://veriqa.app/docs/concepts/sign-in-comparison.md).

## Messaging apps

Veriqa ships with popular messaging apps — **Telegram, WhatsApp, Instagram Direct, Messenger, WeChat
and Viber**: your users sign in and confirm actions through them. More on the page
[Supported messaging apps](https://veriqa.app/docs/guides/supported-channels.md#built-in-messaging-apps).

Veriqa was built for single sign-in through popular messaging apps, but its architecture is not
limited to them.

> [!NOTE]
>
> Veriqa's architecture is built on one general notion — the channel. A channel is where the user
> confirms a sign-in, and also the source that vouches for who confirmed it. What stands behind a
> channel does not matter to Veriqa — only what the channel vouches for. So a channel can be any
> service, as long as the data about the user that it passes on meets three conditions:
>
> * the service vouches for it, and the user does not type it;
> * it is tied to a stable identifier;
> * it reaches Veriqa along a path whose authenticity can be checked.
>
> A channel can be [email](https://veriqa.app/docs/guides/email.md) or an account service such as
> [Google or Apple](https://veriqa.app/docs/guides/account-services.md).

## Email

With Veriqa your website gets not only the classic sign-in by email but also the **one-tap email**:
the user scans a QR code, the phone opens an email already filled in with a secret token, and all
that is left is to tap Send.

It is simpler than a code or a magic link: **fewer steps, nothing to type and nothing to wait for**.
And it is safer: the email proves that the user controls the mailbox, and it carries no link for a
mail gateway to use up.

![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.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-email-cross-device.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=f09bc7035c1c42fdb2ab4b59e4679914)

A QR code, a ready-made email, then the page verifies the sender.

[How sign-in by email works](https://veriqa.app/docs/guides/email.md)

## Account services

Users can sign in with Google, Apple, Huawei and other account services —
[80+ providers in all](https://documentation.openiddict.com/integrations/web-providers). The flow is
the same everywhere: the user scans a QR code and confirms on their own phone, or taps a single
button when signing in on the same device.

**Why it is safer than the usual sign-in button.** With a QR code, the account password is never
typed on the computer, so malware has nothing to intercept. And since nobody types a password each
time, sessions can be kept shorter, which lowers the risk too.

**Why it is more convenient.** There is no password to remember: on the phone the user is usually
signed in to their account already. It helps wherever a password cannot be typed or is risky to
type — on a TV, on a shared computer, on a work 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".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-google-cross-device.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=52f0152b194a72506f88d8f49a704db7)

A QR code, the phone camera, a Google account, one tap on the confirmation page.

[Sign-in with account services](https://veriqa.app/docs/guides/account-services.md)

## Devices in scenarios

A device is not a channel: a channel answers "who confirmed", while a device answers "where". You can
still use devices in scenarios. For example, your server can put a confirmation QR code on a sheet
from the office printer, on a meeting room screen or on a desk phone with a display. The person scans
the code and confirms in a regular channel, and your application learns that they are at that place.

The [Place and identity](https://veriqa.app/docs/scenarios/place-and-identity.md) scenario works this way.

## Other channels

The repository holds more than ten further messaging app adapters, among them VK, LINE, Slack,
Microsoft Teams, Discord, Zalo, KakaoTalk and Threema. Each connects either as a .NET assembly in
your project or as an external service over HTTP — the same way as a channel of your own.

[Other messaging apps](https://veriqa.app/docs/guides/supported-channels.md#other-messaging-apps)

## Your own channel in any language

A channel Veriqa does not ship connects as an external service written in any language. Veriqa talks
to it over HTTP, the platform's keys stay with your service, and nothing has to be compiled — the
service is plugged in by configuration. This is how a corporate messaging app, a bot of your own, a
regional platform or a bot you already run is brought in.

[A channel in any language](https://veriqa.app/docs/guides/http-channel-adapter.md) ·
[I already have a bot](https://veriqa.app/docs/guides/existing-bot.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.