Void

A void is used to cancel a successful authorisation to reverse its effects. The most common use cases for a void is when a cardholder changes their mind about a purchase shortly after a successful authorisation but before the transaction is captured by the merchant and the other case is a void initiated directly by the merchant if it notices the order cannot be fulfilled due to a reason, such as the underlying system returning an error during the order creation. The void removes the hold on the cardholder's balance and any transaction record the cardholder might see in their records is also dropped.

Initiating a Void

Void is initiated by just calling the void endpoint with the identifier of the transaction you are trying to void and a new unique identifier for the void operation. There are no additional properties to set for this operation since Cards Connect voids all of the remaining, uncaptured authorisation amount.

A void can be used as long as there's an unused authorisation amount on the transaction. So, you may use this operation to fully void a successful authorisation before capturing it or void the unused portion of the authorisation after a partial capture. On the other hand, if you want to return the funds back to a customer for the captured portion, you need to use the Refund operation.

Void Response

Void is handled in a way that is similar to a capture and depending on the merchant settings, it has two modes:

Synchronous Mode:

If the merchant is configured to process voids in synchronous mode, as soon as the void API request is validated and accepted by Cards Connect, you receive a response with "Succeeded" outcome. Cards Connect then sends your void request to the schemes and informs you about the actual result of the void using the webhook notifications. Voids are also processes as advice messages down the line, unless there's a technical problem, the operation results remains as "Succeeded. In the unlikely case of a problem the webhook notification returns the current state of the void request as explained under the operational outcomes page.

Asynchronous Mode:

In certain cases a merchant might be configured to handle void operation as an asynchronous operation. In this mode, when Cards Connect receives a request to void an authorisation, it returns a response with "Accepted" as the outcome as soon as the API request is validated. This outcome eventually gets updated with the response we receive from the issuer. Then, once we receive the response from the scheme, we update you with a webhook notification.

Retrieving the Details of a Void

Cards Connect allows you to fetch the void details by providing the transactionId as well as the voidId. Depending on the internal state of the void operation in Cards Connect, you may receive "Accepted" as the outcome while the response code and description fields are null or you may receive the actual outcome provided by the issuer such as "Succeeded", with the corresponding response code and description. A sample response to retrieve the details of a void is illustrated below.

GET /transactions/60ba1b61-35a5-4a9d-86cf-38531256a631/voids/d822c33b-269c-41d4-907f-9ecc77e7d4a0

{
    "voids": [
        {
            "id": "d822c33b-269c-41d4-907f-9ecc77e7d4a0",
            "amount": 4120,
            "outcome": "Succeeded",
            "responseCode": "00",
            "responseDescription": "Approved or completed",
            "createdAt": "2025-08-21T04:06:17Z"
        }
    ],
    "transactionId": "60ba1b61-35a5-4a9d-86cf-38531256a631",
    "reconciliationId": "e8dd3707-0d8f-4dde-8691-dec639ba6f5e",
    "permittedActionHints": []
}