> 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/deutsch/blink-payment-methods/intraledger/are-there-any-fees-for-transaction-between-blink-users.md).

# Gibt es irgendwelche Gebühren für Transaktionen zwischen Blink-Nutzern?

Nein, es fallen keine Gebühren für Transaktionen zwischen Blink-Nutzern an. Wenn Sie Bitcoin innerhalb des Blink-Ökosystems senden oder empfangen, sei es durch On-Chain-Transaktionen, Lightning Network-Zahlungen oder LNURL-Transaktionen, gibt es keine zusätzlichen Gebühren, die von Blink erhoben werden. Sie können Geldbeträge frei zwischen Blink Wallets senden und empfangen, ohne dass Gebühren anfallen. Dies macht Blink zu einer attraktiven Option für Nutzer, die Bitcoin transferieren möchten, ohne sich über Transaktionsgebühren Gedanken machen zu müssen, und ermöglicht nahtlose und kostengünstige Peer-to-Peer-Transaktionen innerhalb der Blink-Community.


---

# 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/deutsch/blink-payment-methods/intraledger/are-there-any-fees-for-transaction-between-blink-users.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.