> ## 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. # Gallery > This section shows real screens for the main scenarios, step by step. The screenshots were taken from demo applications and samples running on the Veriqa core, version 0.7.0. Each channel also has its own page: [Telegram](https://veriqa.app/docs/samples/screenshots/telegram.md), [WhatsApp](https://veriqa.app/docs/samples/screenshots/whatsapp.md), [Messenger](https://veriqa.app/docs/samples/screenshots/messenger.md), [Instagram](https://veriqa.app/docs/samples/screenshots/instagram.md), [Google](https://veriqa.app/docs/samples/screenshots/google.md), [Email](https://veriqa.app/docs/samples/screenshots/email.md). ## General scheme A sign-in starts in your app: it sends the browser to the sign-in page with a standard OpenID Connect redirect. The user confirms in a channel, and the browser returns to your app with a code that your app exchanges for tokens. ![Signing in through Veriqa: your app sends the browser to the sign-in page by an OpenID Connect redirect, the person confirms in a channel, and Veriqa redirects back so your app can exchange the code for tokens.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-flow-sign-in.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=ded6eede4a7e26ade7410dd12eb871de) An action confirmation starts on your server: it creates a transaction through the Veriqa API. The user confirms in a channel, and your server reads the answer and performs the action. The browser is not redirected. ![Confirming an action through Veriqa: your server creates the transaction, the person scans the QR code your app shows and confirms in a channel, and your server reads the answer and performs the action.](https://mintcdn.com/veriqa/XLg27VdhWjZL50TY/images/examples/en-flow-confirm.webp?fit=max\&auto=format\&n=XLg27VdhWjZL50TY\&q=85\&s=03bda77eac10a8b5d7423cfc53fc142b) See [Basic scenarios](https://veriqa.app/docs/basic-scenarios.md). ## Telegram ### Signing in on a computer ![Signing in on a computer with Telegram: the sign-in window shows a QR code, the phone camera scans it, the user taps Confirm in the Telegram chat, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-cross-device.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=83822cdb7c6dea4c6378491adb285665) The user scans the QR code with their phone camera and confirms in the Telegram chat. ### Signing in on a phone ![Signing in on a phone: the user taps "Sign in with Telegram", confirms in the Telegram chat, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-phone.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=c4f0468d1de8643cfb50643c8cb0b2e1) The user taps "Sign in with Telegram" and confirms in the Telegram chat. ### Step-up: confirming an action ![Confirming an action: the app shows a QR code for deleting a project, the phone camera scans it, the user gets the request in Telegram, and the decision goes back to the app.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-confirm.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=ab6865aea1dbbd877c9ab587cce1b6ef) The app shows a QR code, and the user scans it with their phone camera and declines the request in Telegram. The app receives the answer. ### Collecting extra details at sign-in ![Collecting extra details at sign-in: after confirming in Telegram, the user shares a phone number, fills in the missing fields of a short form, confirms the email with one ready-made message, and the app receives the verified claims.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-progressive.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=73b3a64321c0161e6c60de18bbece412) At sign-in, your app gets what the messaging app doesn't provide: a phone number, answers to a short form and a confirmed email address. The last frame of the animation shows test values from a real ID token. ### Claims your app can get ![Claims your app can get from signing in with Telegram: sub, amr, channel\_type, channel\_user\_id, name, given\_name, family\_name, preferred\_username, locale, picture, phone\_number, phone\_number\_verified true, and email with email\_verified after an email confirmation.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-claims.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=1990d6f4ae645a60d5bb69712bdc80d8) ## WhatsApp ### Signing in on a computer ![Signing in on a computer with WhatsApp: the phone camera scans the QR code, WhatsApp opens a ready-made message, the user sends it, taps Confirm, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-whatsapp-cross-device.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=75312dbb5618ea5372f71f35112fc9d9) The user scans the QR code with their phone camera, sends the ready-made message in WhatsApp and taps Confirm. ### Signing in on a phone ![Signing in on a phone with WhatsApp: the user taps "Sign in with WhatsApp", sends the ready-made message, taps Confirm, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-whatsapp-phone.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=211e4dab439cbe9f45d80ed1faf29978) The user taps "Sign in with WhatsApp", sends the ready-made message and taps Confirm. ### Step-up: confirming an action ![Confirming a purchase with WhatsApp: the app shows a QR code, the phone camera scans it, the user sends a ready-made message, taps Confirm, and the chat replies "Purchase confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-whatsapp-confirm.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=73bda60a3615f737df3c577a80e9471c) The app shows a QR code, and the user scans it with their phone camera, sends the ready-made message in WhatsApp and taps Confirm. ### Claims your app can get ![Claims your app can get from signing in with WhatsApp: sub, amr, channel\_type, channel\_user\_id, name, given\_name, preferred\_username, phone\_number, phone\_number\_verified true, and email with email\_verified after an email confirmation.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-whatsapp-claims.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=9c935e22df243a92b3e6df97b378ef48) ## Messenger ### Signing in on a computer ![Signing in on a computer with Messenger: the sign-in window shows a QR code, the phone camera scans it, the user taps Confirm in the Messenger chat, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-messenger-cross-device.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=7c41db65ada72bf6e412229518ea3e7a) The user scans the QR code with their phone camera and confirms in the Messenger chat. ### Signing in on a phone ![Signing in on a phone: the user taps "Sign in with Messenger", confirms in the Messenger chat, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-messenger-phone.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=dffd895ea37c79da02351efbb8227e14) The user taps "Sign in with Messenger" and confirms in the Messenger chat. ### Step-up: confirming an action ![Confirming a purchase: the app shows a QR code for a \$99 plan, the phone camera scans it, the user confirms in Messenger, and the chat replies "Purchase confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-messenger-confirm.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=19901b2ea8f8eb45939ca8f9ded6544d) The app shows a QR code, and the user scans it with their phone camera and confirms the purchase in Messenger. ### Claims your app can get ![Claims your app can get from signing in with Messenger: sub, amr, channel\_type, channel\_user\_id, name, given\_name, family\_name, locale, picture, phone\_number, phone\_number\_verified false, and email with email\_verified after an email confirmation.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-messenger-claims.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=663f7e823c2d56ab66962b7bf6a239b7) ## Instagram ### Signing in on a computer ![Signing in on a computer with Instagram: the sign-in window shows a QR code, the phone camera scans it, the user taps Confirm in the Instagram chat, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-instagram-cross-device.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=e15b279ed80cac482d460d39ddc90f1b) The user scans the QR code with their phone camera and confirms in the Instagram chat. ### Signing in on a phone ![Signing in on a phone: the user taps "Sign in with Instagram", confirms in the Instagram chat, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-instagram-phone.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=4ef51a2115edd35a9496ec069dcb2f1f) The user taps "Sign in with Instagram" and confirms in the Instagram chat. ### Step-up: confirming an action ![Confirming an action: the app shows a QR code for deleting a project, the phone camera scans it, the user confirms in Instagram, and the chat replies "Confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-instagram-confirm.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=a0e0dd7d112b50b201e5852ce486cdeb) The app shows a QR code, and the user scans it with their phone camera and confirms the deletion in Instagram. ### Claims your app can get ![Claims your app can get from signing in with Instagram: sub, amr, channel\_type, channel\_user\_id, name, preferred\_username, picture, phone\_number, phone\_number\_verified false, and email with email\_verified after an email confirmation.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-instagram-claims.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=7dcbe9d130ed06fd1b89c6702f1ca82f) ## Google ### Signing in on a 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) The user scans the QR code with their phone camera, picks a Google account and taps Yes on the confirmation page. ### Signing in on a phone ![Signing in on a phone with Google: the user taps "Sign in with Google", picks an account, allows access on the first sign-in, taps Yes, and sees "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-google-phone.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=7486885492d64617e628658b0baebcdf) The user taps "Sign in with Google", picks an account and taps Yes on the confirmation page. Google asks for consent only on the first sign-in. ### Claims your app can get ![Claims your app can get from signing in with Google: sub, amr, channel\_type, channel\_user\_id, name, email, email\_verified, given\_name, family\_name, locale, picture.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-google-claims.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=96564442bb5972250106cab4600dcca8) ## Email ### Signing in on a computer ![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) The user scans the QR code with their phone camera, sends the ready-made email and confirms the sign-in on the computer. ### Signing in on a phone ![Signing in on a phone by email: the user taps the email button and sends a ready-made email, the page verifies the sender, and the user confirms the sign-in.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-email-phone.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=454374ad99e15d2e71f36a3187836041) The user taps "Send confirmation email", sends the ready-made email and taps Yes on the confirmation page. ### Claims your app can get ![Claims your app can get from signing in with Email: sub, amr, channel\_type, channel\_user\_id, name, email, email\_verified, preferred\_username, veriqa\_channel, veriqa\_email\_mode.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-email-claims.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=c30cefea728b445078e7e15514cdc24d) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.