Asynchronous Refund

WARNING: This page is a document under construction, subject to change without notice, and still uncoupled from our full documentation. If you wish to access all our documentation, check here.

The asynchronous refund functionality changes how cancellations are handled. As a result, cancellations are no longer processed immediately. Instead, they enter an asynchronous processing queue waiting to be cancelled. This approach allows you to improve processing efficiency, especially in cases of high transaction volume.

Note: This functionality is only available for BIN.

In this modality, the initial refund response will be pending (PEN) and when processed it will have a confirmed (CON) or denied (NEG) status. In case of process failure, error status (ERR) would be returned.

Note: The asynchronous refund process is currently not supported for pre-authorizations.

Necessary configurations in Carat

The store will only be able to perform asynchronous cancellation if it has permission for this operation in the Carat back office. To do this, it is necessary to communicate to the Carat registration team about this specific demand.

Flow related to cancellation processes

This flow below exemplifies the flow, starting from payment and going until cancellation. Including webhook endpoints and transaction status checker.

Status API Omnipay vs Tratamento & Retorno

Authorizer resp code	Authorizer resp msg	Transaction Status
0	OK	CON
0	OK	PEN
03	Invalid Merchant ID	NEG
05	Invalid	NEG
05	Error	PEN
13	Invalid Amount	NEG
79	Invalid Transaction Date	NEG
79	Mandatory fields missing	NEG
93	Original Transaction not Found	NEG
98	Invalid Merchant ID	NEG
108	Invalid Merchant Contract Status	NEG
110	Invalid Transaction Type	NEG
112	Original transaction has a chargeback	NEG
113	Insufficient Funds	NEG
400	System Error	ERR
401	System Error	NEG