> 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/cardholders-name-and-billing-address.md).

# Cardholder's Name and Billing Address

At Azul Cards, **your privacy always comes first**. Every part of our system is designed to give you freedom and control without unnecessary data collection.

You can use **any cardholder name or billing address** you choose. For smoother transactions, we recommend entering details that **match the merchant’s country** when making payments — this helps ensure compatibility with certain payment gateways.

Your **Azul Card is built for global use** and doesn’t require any specific personal information to function. No name verification, no address validation — just simple, private payments that work anywhere in the world. Whether you’re shopping online, subscribing to a service, or booking travel, your identity and data always stay protected.


---

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

```
GET https://docs.azul.cards/how-to-use/cardholders-name-and-billing-address.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.