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

# Google

> Step-by-step screens for the Google channel: signing in on a computer and on a phone, and the claims your app can get.

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

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


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