> For the complete documentation index, see [llms.txt](https://docs.allforclimate.earth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allforclimate.earth/all-for-climate/es/donations/cambiar-las-contribuciones-recurrentes.md).

# Cambiar las contribuciones recurrentes

Los donantes pueden gestionar sus contribuciones recurrentes por sí mismos en cualquier momento\
\
Pueden:

* **Cambiar el importe de la contribución** — aumentar o disminuir su donación.
* **Cambiar el método de pago** — por ejemplo, cambiar de PayPal a otro método de pago.
* **Cambiar o eliminar su propina de la plataforma** — ajustar la propina opcional que dan a Open Collective.
* **Cancelar su contribución recurrente** — detener los pagos futuros.

#### ¿Cómo pueden los donantes hacer cambios?

1. Iniciar sesión en su cuenta de Open Collective e ir a **Panel → Contribuciones**.
2. Seleccionar la contribución recurrente que desean cambiar y editar la configuración disponible o cancelarla.

{% hint style="info" %}
**Tenga en cuenta:** Algunos métodos de pago, como SEPA y ACH, no admiten cambios en las contribuciones recurrentes existentes. En estos casos, los donantes deben cancelar su contribución existente y crear una nueva con la configuración deseada.
{% endhint %}


---

# 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.allforclimate.earth/all-for-climate/es/donations/cambiar-las-contribuciones-recurrentes.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.
