> 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/what-is-the-cash-register-in-blink.md).

# What is the Point of Sale (PoS or Cash Register) in Blink

The Point of Sale in Blink is a convenient way to receive bitcoin payments. It's especially useful for merchants to receive payments directly into their wallets, without relying on a single device, making it an easy and cost-effective way to have a functioning POS in their stores.

To use the PoS, click the menu in the top right of your Blink home screen and go to "Ways to get paid". Here you will find the link to your PoS, e.g. pay.blink.sv/username.

* You can open the PoS link in any browser and create Lightning invoices in a quick and easy way.
* You can share the PoS link with your customers: when a customer opens the link, they will be directed to PoS where they can enter the amount they wish to pay and complete the transaction.
* You can share the PoS link with your employees or staff and let them receive payments on your behalf. Keep in mind, that any amount sent to invoices generated in your unique PoS goes directly into your Blink account. The PoS is only for receiving payments, not sending. Sharing your PoS link with an employee or customer allows them to receive payments on your behalf — it does not give them the ability to send or withdraw funds from your account.

The PoS feature also provides a simple way to keep track of your sales and generate reports to help you keep track of your business transactions.


---

# 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/what-is-the-cash-register-in-blink.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.
