# gateway.transaction_authorization.auth_already_reversed

> For the complete machine-readable documentation index, see [llms.txt](https://apidocs.chargebee.com/llms.txt).


**gateway**

The transaction could not be processed because the authorization has already been reversed. This happens when a reversal has been previously processed, duplicate reversal requests are submitted, the session has expired, or the gateway automatically processed the reversal.

## Recommended Customer Message

This authorization has already been reversed. If you think this is incorrect or need further assistance, please contact your payment provider's support team.

## Root Cause[](#root-cause)

-   **Authorization reversal already processed:** The transaction's authorization was previously reversed, and no further action can be taken on it.
-   **Duplicate reversal request:** A reversal request was submitted multiple times for the same authorization.
-   **Session timeout or mismatch:** The transaction session expired, or the authorization reference is no longer valid.
-   **Gateway automatic reversal:** The payment gateway processed the reversal automatically due to policy or timeout settings.

## Troubleshooting and Solutions[](#troubleshooting-and-solutions)

-   Inform the customer that the authorization has already been reversed and no funds were captured.
-   If the customer still sees a hold on their account, advise them to contact their bank for clarification on pending holds.
-   Avoid attempting further reversal or capture actions on the same authorization reference.
-   If this message appears in error, contact the payment gateway support team to verify the authorization's status.
-   Ensure that transaction workflows prevent multiple reversal requests for the same authorization.