> 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/espanol/using-blink/how-do-i-receive-a-transaction-with-blink.md).

# ¿Cómo recibo una transacción con Blink?

Blink fue creado para facilitar el envío y recepción de transacciones de Bitcoin utilizando on-chain, LNURL y Lightning.

Puede proporcionar la siguiente información para recibir una transacción:

* Tu dirección en la cadena (comienza con `bc1...`). Las transacciones entrantes en la cadena (depósito) requieren 2 confirmaciones para estar disponibles para gastar.
* Crear una factura de Lightning (formato BOLT11, comenzando con `lnbc1...`)
* Caja registradora aplicación web
* Utilice la Dirección Lightning, que utiliza una forma de dirección de correo electrónico (por ejemplo, <yourusername@blink.sv>)
* Usando tu Blink Paycode (también conocido como LNURL)

También puedes recibir pagos a tu nombre de usuario de Blink de otros usuarios de Blink. Ten en cuenta que esta función solo está disponible para pagos de Blink a Blink y NO funcionará con otras aplicaciones como Chivo o Strike.


---

# 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/espanol/using-blink/how-do-i-receive-a-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.