> For the complete documentation index, see [llms.txt](https://faq.blink.sv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.blink.sv/blink-merchant-map/what-is-blinks-map-feature.md).

# What is Blink's map feature?

The Map feature in Blink allows users to easily locate businesses that accept Bitcoin payments. By accessing the Map feature, users can view all registered businesses and their locations.

Additionally, the Map feature allows users to make payments directly to a merchant by clicking the “Pay to this business” button that appears when a business pin is clicked. This streamlines the payment process and makes it more convenient for both customers and merchants.

If you are a business that accepts Bitcoin payments and would like to be listed on the Map feature, simply contact us at <support@blink.sv> for instructions on how to register your business.

When you open the map the first time or click the location icon you can allow Blink to access your device's location which make the merchant map default to your current location.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://faq.blink.sv/blink-merchant-map/what-is-blinks-map-feature.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.