Skip to main content
A feedback form collects whatever was typed into it: a mistyped address, a disposable mailbox, a made-up number. CAPTCHA filters out some bots, but it does nothing for the quality of the contact. Veriqa handles it differently: the visitor verifies themselves in a messaging app within seconds, and the site receives a verified contact and a live channel — one you can actually write to later, not just store.

​
Two ways, and they are different solutions

Submission without sign-in

The user confirms the submission, but no session is created and no account is provisioned. Needs a small server-side handler next to the form.

Sign-in with channel linking

The user signs in and you gain the channel along the way — if you have accounts and a member area.
No OIDC plugin for any CMS does the first one. Plugins cover signing in to an account, while Contact Form 7, WPForms and Bitrix web forms are not tied to an account at all. “A member area” and “a confirmed submission” are two different solutions, not two settings of one.

​
What the site gets

  • proof of confirmation — who exactly (sub) confirmed the submission and in which channel (channel_type);
  • a live channel to reply through: a message in the messaging app someone just confirmed in beats an address typed by hand;
  • a bot filter that, unlike a CAPTCHA, gives the user nothing to solve: Telegram and some other channels report that the sender is a bot, Veriqa returns that flag in the claims, and such submissions can be cut off before a record is created.
This is a filter, not anti-fraud. It removes the stream of junk submissions; it does not replace a fraud-prevention system.

​
What it takes

The server-side handler is minimal: about 250 lines of PHP with no external dependencies. Step by step on Confirmed form submission.