> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://ixopay.ferndocs.com/user-manual/manual/transactions/transaction-details/cancel-resolve/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://ixopay.ferndocs.com/_mcp/server.

# Cancel/Resolve

## Cancel Transaction

Depending on the given Permissions and prerequisites, Users can cancel transactions manually (e.g. in case a Transaction gets stuck). This can be done by using the **Cancel** Action Buttons in the Transaction Details.

To cancel a Transaction, the Transaction has to fulfill the following condition:

* The **Transaction status** has to be Open (except Pending\_Postback)

Once confirmed the Transaction will be cancelled and shown as such in the Transaction Status.

![Cancel](https://documentation.ixopay.com/manual/assets/ideal-img/cancel.bc97e4d.1280.png)Cancel![Cancel confirmation](https://documentation.ixopay.com/manual/assets/ideal-img/concel-confirmation.7d04470.1000.png)Cancel confirmation![Cancel success](https://documentation.ixopay.com/manual/assets/ideal-img/cancel-success.793ea1e.1280.png)Cancel success

## Resolve conflicted Transaction

Depending on the given Permissions, Users can resolve conflicted transactions manually. Conflicts are raised by the system automatically in case of internal mismatch (e.g. Reconciliation or Settlement data does not match transaction data). This can be done by using the **Resolve** Action Buttons in the Transaction Details, once you clarified the conflict with your PSP / Acquirer.

![Conflict](https://documentation.ixopay.com/manual/assets/ideal-img/conflict.cc0f844.1280.png)Conflict![Conflict confirmation](https://documentation.ixopay.com/manual/assets/ideal-img/conflict-confirmation.ad7794c.826.png)Conflict confirmation

> **Tip**
>
> Keep in mind that no further action is initiated by system through resolving conflicts except marking conflicted Transactions as solved.