> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/merchant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payrexx.com/merchant/english/payment/disputes/prevention/subscription-canceled.md).

# Subscription canceled

In this article, you will learn how to prevent "Subscription canceled" disputes using appropriate preventive measures.

Disputes categorized as "Subscription canceled" occur when shoppers believe a [subscription](/merchant/english/account/payments/subscriptions.md) was unjustly renewed.

Firstly, reduce the incidence of unintended subscription renewals through transparent communication. Secondly, try to resolve the issue before a dispute is initiated.

### Recommendations

* Display clear and understandable cancellation policies on your website.
* Obtain customer consent in the ordering process with a checkbox.
* Send reminders about the upcoming cancellation deadline.
* Implement an in-app cancellation button or a similar easy-to-access cancellation option.
* Implement a flexible refund process.
* Show leniency in dealing with customers when necessary.

If you nevertheless receive a dispute of this type, the following article provides helpful tips to help you resolve the dispute in your favor:

{% content-ref url="/pages/j6BrUVksE4atVb14ehh2" %}
[Subscription canceled](/merchant/english/payment/disputes/processing-and-submitting-evidence/subscription-canceled.md)
{% endcontent-ref %}


---

# 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.payrexx.com/merchant/english/payment/disputes/prevention/subscription-canceled.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.