Veriqa.Core.BaseChannels
0.7.3
Prefix Reserved
dotnet add package Veriqa.Core.BaseChannels --version 0.7.3
NuGet\Install-Package Veriqa.Core.BaseChannels -Version 0.7.3
<PackageReference Include="Veriqa.Core.BaseChannels" Version="0.7.3" />
<PackageVersion Include="Veriqa.Core.BaseChannels" Version="0.7.3" />
<PackageReference Include="Veriqa.Core.BaseChannels" />
paket add Veriqa.Core.BaseChannels --version 0.7.3
#r "nuget: Veriqa.Core.BaseChannels, 0.7.3"
#:package Veriqa.Core.BaseChannels@0.7.3
#addin nuget:?package=Veriqa.Core.BaseChannels&version=0.7.3
#tool nuget:?package=Veriqa.Core.BaseChannels&version=0.7.3
Veriqa.Core.BaseChannels
Telegram, WhatsApp and Email login and authentication by QR code in one package.
- One
dotnet add packageinstead of four. - Your users scan a QR code on the sign-in page (on a phone, they tap a button) and confirm the sign-in with no password and no SMS code.
- Your users can also sign in with a QR code or a button through a Google or Apple account and 80+
other services, with the
Veriqa.Core.ChannelAdapter.WebProviderspackage. - Your users can sign in this way on a computer, a TV, a kiosk or any other device that can show a QR code.

Gallery · Live demo · Source code · Open source under MPL-2.0
Part of Veriqa, an open-source project for passwordless authentication through popular messaging apps and email, over standard OpenID Connect. Documentation: Supported messaging apps.
Use cases
- Passwordless sign-in and sign-up. Your users scan a QR code or tap a button instead of typing a password, and a new user signs up with the same action. Passwordless sign-in
- Second factor and action confirmation. Your product asks the user to confirm a sensitive action with one tap in their messaging app, with no code to type. Second factor and step-up
- AI agents. A risky agent step runs only after a person approves it in their own messaging app. Approving AI agent actions
- Replacing SMS codes. Your users confirm the sign-in with a button in their messaging app, and you pay no SMS charges. Replacing SMS codes
- A direct channel to the user. The same sign-in gives your product a channel for notifications. Sign-in and channel linking
- Leads and feedback without CAPTCHA. Your site gets a confirmed contact instead of an address typed into a field. Leads and feedback without CAPTCHA
- Surfaces with no keyboard. A smart TV, a set-top box or a kiosk shows a QR code, and the user types nothing. Sign-in surfaces
About this package
A metapackage of the base Veriqa channel set: it carries no library of its own, only the dependencies that make up the usual starting set — the channel contour plus the Telegram, WhatsApp and Email channels. No API of its own appears at the consumer.
MAX, Instagram, Messenger, WeChat and Viber are not part of it: each is installed separately with
its own dotnet add package. A deployment that wants a single channel takes that channel's package
instead of this one; installing both the metapackage and a separate channel is fine — NuGet resolves
it to one copy.
Install
dotnet add package Veriqa.Core.BaseChannels
Wiring
The channels arrive as their own packages, so the registration is theirs:
authServer.AddChannelAdapters(adapters =>
{
adapters.AddTelegram();
adapters.AddWhatsApp();
adapters.AddEmail();
});
License
Mozilla Public License 2.0 — see the LICENSE file in the repository root; the package carries
the MPL-2.0 license expression in its metadata.
Veriqa™ — © Dmitrii Erusov. Sources and mirrors: https://veriqa.app · devs@veriqa.app
Learn more about Target Frameworks and .NET Standard.
-
net10.0
- Veriqa.Core.ChannelAdapter (= 0.7.3)
- Veriqa.Core.ChannelAdapter.Email (= 0.7.3)
- Veriqa.Core.ChannelAdapter.Telegram (= 0.7.3)
- Veriqa.Core.ChannelAdapter.WhatsApp (= 0.7.3)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.