> 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/credit-not-processed.md).

# Credit not processed

This article explains how to prevent "credit not processed" disputes by implementing the right preventive measures.

"Credit not processed" disputes occur when a customer requests a refund for a purchase but does not receive it.

### Typical causes

* The refund was promised but forgotten internally or delayed.
* A technical error occurred while processing the refund.
* Communication regarding the processing time for refunds was unclear or missing entirely.
* The customer did not receive a refund confirmation and therefore assumes no action was taken.

### Recommendations

* Display cancellation and return policies prominently throughout the checkout process.
* Establish a fixed processing timeframe for refunds (e.g., within 5 business days) and communicate it proactively.
* Respond promptly to refund requests and acknowledge receipt of the inquiry, ideally via automated email.
* Monitor the status of your refunds in your Payrexx merchant administration panel to avoid overlooking open cases.

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/zLYNwDQY0VRgT7uKvQma" %}
[Credit not processed](/merchant/english/payment/disputes/processing-and-submitting-evidence/credit-not-processed.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/credit-not-processed.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.