# gateway.transaction_authorization.already_captured

> 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 payment has already been captured. This happens when a duplicate capture attempt is made, the payment workflow logic caused a retry on a completed transaction, or delayed acknowledgments resulted in repeated capture attempts.

## Recommended Customer Message

This payment has already been completed. Please review your transaction details or contact our support team if you need assistance.

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

-   **Duplicate capture attempt:** The system attempted to capture funds for a transaction that has already been successfully captured.
-   **Incorrect transaction workflow:** Your system retried a capture on a completed transaction due to an error or misconfiguration.
-   **Delayed response handling:** A delayed acknowledgment from the payment gateway caused a repeated capture attempt.
-   **Manual capture already processed:** The transaction was previously captured manually, but the system initiated another capture automatically.

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

-   Verify the transaction records to confirm that the payment has already been successfully captured.
-   Inform the customer that the payment was processed successfully and no further action is required.
-   Prevent duplicate capture attempts by reviewing and correcting the payment workflow logic.
-   Contact your payment gateway support if system-level retries or delayed acknowledgments are causing repeated captures.
-   Implement safeguards to ensure transactions marked as captured are not processed again.