> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/es/faq/c160/c165/q544.md).

# ¿Por qué no puedo pagar la suscripción en el portal web?

Si no puedes pagar una suscripción:&#x20;

* Comprueba que tu método de pago esté actualizado
* Comprueba que estás usando el nombre y la dirección correctos para los datos de la tarjeta

El portal web no te permitirá crear un nuevo pago hasta que se hayan resuelto los pagos anteriores fallidos. Si has recibido un error después de intentar realizar un pago:

* Haz clic en la opción "cancelar" en el banner de error de la página de suscripción

Este artículo muestra los pasos para [volver a suscribirse en el portal web](https://docs.reportandrun.com/manual/cloud/account-management/resubscribe).

## Relacionado

* [FAQ: ¿Qué métodos de pago puedo usar para suscribirme a la app?](https://docs.reportandrun.com/manual/es/faq/c142/c148/q424.md)
* [FAQ: ¿Por qué se me pide que me suscriba a la versión premium aunque mi suscripción esté activa?](https://docs.reportandrun.com/manual/es/faq/c160/c165/q546.md)
* [Preguntas frecuentes: ¿Por qué mi suscripción aparece inactiva o no es reconocida por la app después de haber pagado?](https://docs.reportandrun.com/manual/es/faq/c160/c165/q543.md)
* [Preguntas frecuentes: ¿Cómo contacto con el soporte?](https://docs.reportandrun.com/manual/es/faq/c169/q575.md)


---

# 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://docs.reportandrun.com/manual/es/faq/c160/c165/q544.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.
