Veriqa

What this solution does

The module provides site login and registration via confirmation in messengers. A user clicks the 'Login via messenger' button, scans a QR code with a phone camera, or follows a link, then confirms the action with a single tap in the chat with a bot. Passwords, SMS codes, and CAPTCHAs are not required. An account is created automatically upon the first login.

Authentication is provided by the Veriqa server, an open login server operating on the OpenID Connect standard. The server is deployed by the client or on a hosting service. The module integrates it with the standard 'Social Services' component: account creation and linking are handled by the platform without modifying the Bitrix core.

Capabilities

Login and registration via MAX, Telegram, WhatsApp, and other channels enabled on the Veriqa server.

'Login via messenger' and 'Register via messenger' buttons in the standard login form, displayed in the site language.

The 'Veriqa Buttons' component adds a button to the registration page, inserted into the registration form template in a single line.

Ability to link a messenger to an existing account via the user profile; the linked messenger is displayed in the list of connected profiles.

The Veriqa module supports user email selection: a placeholder address is used if the messenger does not transmit email data, or the user enters an address during login with email code verification if this feature is enabled on the Veriqa server. When the site requires email registration confirmation, email uniqueness, or phone-based registration, the module accepts only verified addresses.

The login window displays in the site language. The store name and window design are configured in the Veriqa server settings.

Button styling is controlled by the site template: Veriqa's default styling is disabled via a setting, allowing the site template to style the buttons.

Security is ensured by verifying token signatures using server keys and performing login via an authorization code with PKCE.

For multi-site installations, settings are configured per site using the standard Social Services mechanism.

During complete removal, the module deletes its files and settings while preserving user account bindings.

System requirements:

1C-Bitrix: Site Management with the Social Services module installed.

PHP 8.1 or newer.

A Veriqa server accessible from the site and a client registered on it. The server is deployed as a Docker image or a service for Linux and Windows.

To enter an email address during login, the Veriqa server version 0.6.6 or newer is required. Login using a placeholder address also works on earlier versions.

A bot or business account connected to the Veriqa server is required for each messenger through which login is performed (MAX, Telegram, WhatsApp Business, etc.). The conditions for connecting bots are set by the messengers themselves. For example, a MAX bot can only be created by an organization or an individual entrepreneur registered in the Russian Federation with a verified profile in the MAX business cabinet.

Personal data. The module receives visitor data only from the Veriqa server, the address of which is specified in the settings, and does not transmit it anywhere else. The data operator on the Veriqa server is its owner, which is the website owner.

Frequently Asked Questions

Is a paid service required? No, the Veriqa server itself is free: it is deployed on your side, and Veriqa does not charge for login, unlike SMS messages sent for each interaction. Messengers may charge for specific types of messages according to their own rules, for example, WhatsApp Business on the Meta platform; conditions should be clarified with the messenger provider.

What data does the website receive? The website receives the user identifier in Veriqa, the name from the messenger, and the login channel. An email address is received only if it is provided by the channel or entered by the user during login.

When the module is removed, user accounts and their associated links remain in the system. After the module is reinstalled, users can log in to their original accounts.

General iT can take care of implementing “Veriqa”, including installation, configuration and result verification.