> 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-payment-methods/lightning-address/how-can-i-use-blinks-cash-register-feature.md).

# How can I use Blink's Point of Sale feature?

There are two ways to use the Blink Point of Sale:

**Option 1:**

1. Click on the menu in the top right of your Blink home screen
2. Click on "Ways to get paid"
3. Here you will find your v link
4. You can share this link with your employees, clients, or add it directly to your social media, website, or blog to receive payments.

**Option 2:**

1. Go to [pay.blink.sv](https://pay.blink.sv/)
2. Enter your Blink username or Log in with Blink
3. Start receiving payments using your unique Blink Point of Sale

By using the Point of Sale, you can easily receive payments directly to both accounts (BTC / USD) without relying on a single device. It's an ideal solution for small business owners who need a functioning POS system without the added costs of traditional payment processors.


---

# 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-payment-methods/lightning-address/how-can-i-use-blinks-cash-register-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.