> 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/intraledger/what-information-is-needed-to-send-or-receive-bitcoin-between-blink-wallets.md).

# What information is needed to send or receive Bitcoin between Blink wallets?

To send Bitcoin to another Blink user, you only need to know their Blink username. Simply enter their Blink username as the recipient, and the funds will be sent directly to their wallet. It's a convenient and hassle-free way to make payments within the Blink ecosystem.

To receive Bitcoin from another Blink user, you need to provide them with your Blink username. Share your Blink username with the sender, and they can easily send funds to your wallet using your username. Once a transaction is completed with a Blink user, their username will be automatically saved in your contacts list, making future transactions even easier.

With Blink's user-friendly interface, sending and receiving Bitcoin between Blink wallets is seamless and straightforward. No complicated wallet addresses or QR codes are required, simplifying the process and enhancing the user experience.


---

# 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/intraledger/what-information-is-needed-to-send-or-receive-bitcoin-between-blink-wallets.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.
