> 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/on-chain/how-can-i-receive-an-on-chain-transaction-with-blink.md).

# Nsobola ntya okufuna okutunda ku lujegere ne Blink?

Okufuna enkolagana ku lujegere ng’okozesa Blink, goberera emitendera gino:

1. Gulawo app ya Blink onyige ku `Funa`
2. Wansi wa QR code nyiga ku `Onchain`
3. Osobola okukoppa endagiriro eyo, n’ogigabana oba okulaga oyo akuweerezza koodi ya QR. Weetegereze nti okwewala okuddamu okukozesa endagiriro wajja kubaawo endagiriro empya eragiddwa ng’ofunye enkolagana ku ndagiriro gye wagabana emabegako. Endagiriro enkadde ejja kusigala nga ntuufu okufuna emirimu ku akawunti yo ne bwe wabaawo endagiriro empya eragiddwa.
4. Enkolagana bwemala okusindikibwa, enkolagana erina okulabika mu bbanga ttono nga `Tekinagwa` mu waleti yo. Nywa ku nkolagana olabe nti \`Transaction Hash\`. Nga okozesa Transaction Hash (era emanyiddwa nga TXID) osobola okulaba ebikwata ku nkolagana mu block explorer nga [mempool.space](https://mempool.space) n’olaba ddi lwe kikakasibwa mu block.


---

# 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/on-chain/how-can-i-receive-an-on-chain-transaction-with-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.