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

# How can I receive an on-chain transaction with Blink?

To receive an on-chain transaction using Blink, follow these steps:

1. Open the Blink app and click on `Receive`
2. Under the QR code click on `Onchain`
3. You can copy the address, share it, or show the QR code to the sender. Note that to avoid address reuse there will be a new address displayed when you have received a transaction on the address shared previously. The old address will remain valid to receive transactions on your account even when there is a new address shown.
4. Once the transaction has been sent, the transaction should shortly appear as `Pending` in your wallet. Click on the transaction to see it's \`Transaction Hash\`. Using the Transaction Hash (also known as TXID) you can see the details of the transaction in a block explorer like [mempool.space](https://mempool.space) and see when it is confirmed in a 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/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.