> 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/luganda/blink-payment-methods/lightning-address/what-is-the-cash-register-in-blink.md).

# Point of Sale (PoS oba Cash Register) mu Blink kye ki?

Point of Sale mu Blink ngeri nnyangu ey’okufuna ssente za bitcoin. Kya mugaso nnyo naddala abasuubuzi okufuna ssente butereevu mu waleti zaabwe, nga tebeesigamye ku kyuma kimu, ekigifuula engeri ennyangu era etali ya ssente nnyingi ey’okubeera ne POS ekola mu tterekero zaabwe.

Okukozesa PoS, nyiga ku menu waggulu ku ddyo ku ssimu yo eya Blink ogende ku "Engeri z'ofunamu ssente". Wano ojja kusanga ekikwata ku PoS yo, okugeza pay.blink.sv/username.

* Osobola okuggulawo enkolagana ya PoS mu browser yonna n’okola yinivoyisi za Lightning mu ngeri ey’amangu era ennyangu.
* Osobola okugabana enkolagana ya PoS ne bakasitoma bo: kasitoma bw’aggulawo enkolagana, bajja kulagirwa ku PoS gye basobola okuyingiza ssente z’ayagala okusasula n’okumaliriza okutunda.
* Osobola okugabana enkolagana ya PoS n’abakozi bo oba abakozi bo n’obaleka ne bafuna ssente ku lulwo. Kuuma mu mutima, nti ssente zonna ezisindikibwa ku invoice ezikoleddwa mu PoS yo ey’enjawulo zigenda butereevu mu akawunti yo eya Blink. PoS ya kufuna ssente zokka, so si kusindika. Ssente eziri ku akawunti yo eya Blink zisobola okweyongera, tezikendeera, ng’ozigabana n’omukozi oba kasitoma.

Ekintu kya PoS era kiwa engeri ennyangu ey’okulondoola by’otunze n’okukola lipoota okukuyamba okulondoola emirimu gyo mu bizinensi.


---

# 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/luganda/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.