> ## 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.

# 0.6.2 — hop mode, the HTTP channel and claim completion (upcoming)

> What Veriqa 0.6.2 brings: hop mode for the QR code, a channel in any language over HTTP, Twilio for WhatsApp, claim completion and the phone number from the channels.

<Note>
  This version is being prepared for release: nothing described here is in the published packages
  and image yet. The latest release is [0.6.1](/docs/releases/0.6#061).
</Note>

## Hop mode

The QR code carries a short one-time link to your Veriqa server instead of the channel link. That
gives a light QR code, a scan signal on the computer, a launch page on the phone, one QR code for
every channel and the context of the scanning device. It is off by default; we recommend turning it
on — see [Hop mode](/docs/concepts/hop-mode).

## A channel in any language over HTTP

A new package, `Veriqa.Core.ChannelAdapter.Http`: your own channel is a separate service in any
language, connected by configuration, with no rebuild of the host. A schema describes the wire
contract, and a conformance suite checks your service before you connect it — see
[An HTTP channel adapter in any language](/docs/guides/custom-channel-adapter#an-http-channel-adapter-in-any-language).

## WhatsApp through Twilio

Twilio is a built-in WhatsApp delivery provider next to the Meta WhatsApp Business Platform; one key
selects it — see [Delivery through Twilio](/docs/guides/channels#delivery-through-twilio).

## Claim completion and the phone number

* **The phone number from the channel itself:** the user shares it with a button in the chat — see
  [Phone number](/docs/guides/phone-number).
* **Missing claims completed inside the sign-in** — a form on the sign-in page or on the confirming
  device, and ways to verify an email address — see
  [Progressive claim enrichment](/docs/concepts/claim-enrichment).
* **A collected claims store** on EF Core, with deletion by `sub` — see
  [Collected claims store](/docs/guides/storage#collected-claims-store).

## Security

* A confirmation is bound to the channel subject and to the browser the answer came from.
* The interstitial cookie is bound to the authorize request, GeoIP reads only a trusted IP, and the
  per-user rate limiter evicts old partitions.
* The response to creating a server-to-server confirmation returns the channel's `display_name`.

## What to check when you upgrade

* **The `sub` of WhatsApp users changes.** It was `whatsapp:+number` and is now `whatsapp:{BSUID}`,
  the ID Meta assigns per business portfolio; the number moves to `preferred_username`. There is no
  migration: existing WhatsApp users get a new `sub` in your application.
* **`ShowQrCode` defaults to `DesktopOnly`** instead of `Always`: a phone shows channel buttons
  instead of a QR code. To keep the old look, set `"ShowQrCode": "Always"`.
* **New EF Core migrations** for the transaction store and the audit trail — apply them when you
  upgrade; see [Storage](/docs/guides/storage).


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