> For the complete documentation index, see [llms.txt](https://docs.azul.cards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.azul.cards/how-to-use/how-to-add-card-to-google-pay.md).

# How to add card to Google Pay?

1. **Open Google Wallet** on your Android device and tap **"Add to Wallet"**
2. Select **"Payment card"** from the options
3. Tap **"Enter details manually"**
4. Fill in your card information:
   * **Card number** (from your Azul Card details)
   * **Expiration date** (month/year)
   * **CVV code** (3 digits)
5. Enter any valid address that matches your Google account's country
6. Accept the Terms of Service
7. Choose verification method and tap **"Continue"**
8. Enter the verification code sent to your phone or email
9. Your Azul Card is now active in Google Pay! ✅

**Important notes:**

* Google Pay availability depends on your country/region settings
* Card works instantly once successfully added
* Use any name and address - no verification required
* Supports online and in-store payments worldwide

*Ready to pay anywhere Google Pay is accepted!* 📱


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.azul.cards/how-to-use/how-to-add-card-to-google-pay.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.