> 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/transaction-fees/what-are-the-fees-for-receiving-bitcoin-in-my-blink-wallet.md).

# What are the fees for receiving Bitcoin in my Blink wallet?

When you receive a **Lightning transaction** in your Bitcoin wallet in Blink, there is no fee charged to you by Blink. However, the sender will pay a Lightning routing fee to cover the cost of routing the payment through the Lightning Network. This routing fee is not retained by Blink.

When you receive an **on-chain transaction** in your Bitcoin wallet in Blink, a tiered fixed fee applies (the amount depends on the transaction size — see the Blink App for current tiers). Note that on-chain deposits must exceed a minimum amount (the dust threshold plus the deposit fee) to be processed. Consider using Lightning to receive small payments where there is no minimum amount. The sender also pays a miner fee, which is not retained by Blink.

When you receive a payment to your Dollar Balance, a spread applies for the transfer. See the Blink App for current rates.


---

# 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/transaction-fees/what-are-the-fees-for-receiving-bitcoin-in-my-blink-wallet.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.