> 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-a-paycode-and-how-can-i-use-it.md).

# Paycode kye ki era ngikozesa ntya?

Paycode ya Blink yeesigamiziddwa ku nkola ya LNURL. Kisobozesa abakozesa okukola koodi ya QR etali ya kukyukakyuka esobola okukozesebwa okufuna ssente za Lightning. Paycode QR yo ey’enjawulo esobola okulagibwa ku lutimbe oba okukubibwa, ekigifuula engeri ey’enjawulo era ennyangu ey’okukkiriza okusasula mu mbeera ez’enjawulo.

Blink Paycode yo ekwatagana n'ebikozesebwa byonna ebya Lightning, kyokka walleti za Lightning zokka ezirina obuwagizi bwa LNURL bye bisobola okugisasula butereevu.

Abakozesa Walleti za Lightning ezitawagira LNURL balina okusika Paycode ne camera enzaaliranwa y’essimu yaabwe ne bagoberera link. Bajja kulagirwa ku Point of Sale yo ey’enjawulo (PoS oba Cash Register) gye basobola okukola yinivoyisi ya Lightning okukusasula.

Abasasula basobola okuteekawo ssente ze baagala okusasula ku Paycode yo mu waleti yaabwe eya Lightning, wamu n’okwongerako okunnyonnyola ku nsasula.

Okufuna Paycode ey'enjawulo:

1. Nyiga ku menu waggulu ku ddyo ku ssimu yo eriko Blink
2. Genda ku "Engeri y'okusasulwa".
3. Enyunga ku Paycode yo eragiddwa wano


---

# 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-a-paycode-and-how-can-i-use-it.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.