> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Pay

> What is specific to Google Pay on top of the shared wallet flow, registering your domains, and how to test it in sandbox.

Google Pay runs in the browsers Google supports, and the customer pays with a card in their Google account.
Elements loads Google's `pay.js` from `pay.google.com` on demand and asks whether the browser can pay on one of
the supported networks, not whether the customer has a card saved.

When Payra cannot take the token, the sheet stays open with a message and the customer can try again in it. So
`error` can be followed by `confirmed`, or by `cancel` if they close the sheet.

## Register your domains

On live, Google opens Google Pay only on a page whose domain is registered with Google. On any other domain,
Google shows an error when the customer taps the button, and the customer cannot pay there.

To register, send your Payra contact the hostnames that will show the button, the same list as for
[Apple Pay](https://docs.payra.com/apple-pay.md#register-your-domains): each one in full, such as `checkout.example.com` and
`www.example.com`. Google reviews each domain before Google Pay works on it, so send them ahead of launch. Unlike
Apple Pay, there is no file to host.

Sandbox needs no registration.

## Test Google Pay

In sandbox Google Pay runs in Google's test environment. Any Google account with a card in Google Pay can pay:
the sheet shows the customer's cards, Google hands over a test token, and the sandbox processor approves it.


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