> 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-can-i-change-my-transaction-limits-on-my-blink-account.md).

# Actualización a una cuenta de nivel 2

Actualizar tu cuenta al nivel 2 vendrá con beneficios.

* límites de transacción aumentados
* acceso a [transferir a cuentas bancarias en países seleccionados](https://faq.blink.sv/using-blink/how-do-i-cash-out-my-blink-funds)
* posible recuperación a través del soporte si pierdes acceso a tu cuenta

Para completar el proceso, deberás proporcionar datos adicionales para ser verificados: tu nombre, un documento de identidad emitido por el gobierno y una selfie.

Siga estos pasos para actualizar tu cuenta:

1. Ve a la sección "Ajustes" de tu aplicación Blink.
2. Vaya a la configuración de "Cuenta"
3. Seleccione la opción "Actualizar tu cuenta"
4. Sigue las instrucciones que te guían a través del proceso de actualización.

Con cualquier pregunta o inquietud sobre el proceso de actualización de la cuenta, puede contactarnos por correo electrónico a <support@blink.sv>.

Estamos siempre listos para ayudarte y responder cualquier pregunta que puedas tener.


---

# 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-can-i-change-my-transaction-limits-on-my-blink-account.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.