> 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/lightning-address/how-can-i-create-lightning-address-with-blink.md).

# How can I create Lightning Address with Blink?

Your Lightning Address in Blink is generated using the username you created for your Blink account. If you haven’t chosen a username yet, you can follow these instructions to do so:

* Click on settings
* Click on “receive payments using your Lightning Address address or the merchants feature
* Write your username

Your Lightning Address will look like this: <username@blink.sv>, where \[username] is your personal Blink username that you set. You can share your Lightning Address to receive Lightning payments from other compatible wallets.

By following these steps and setting a Blink username, you will also have unlocked the Point of Sale (PoS or Cash Register) and Paycode features. The PoS allows you to generate invoices for Lightning payments in a quick and easy way. Your unique Paycode is a static QR code that always stays the same and that you can receive Lightning payments to. You can print it out or share it on social media to receive variable amounts of Lightning payments e.g. tips, donations or other payments.


---

# 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/lightning-address/how-can-i-create-lightning-address-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.