Outcome of a refund

Receive webhooks with the outcome of referenced or unreferenced refunds.

Refunds are usually not processed synchronously. When you send a request for a referenced or unreferenced refund, the Terminal API response only confirms we received the request. Unreferenced refunds, however, can be processed synchronously. This depends on the card scheme and the country/region where the card is used. If processed synchronously, you receive an additional field in the Terminal API response: acquirerResponseCode.

We inform you about the refund asynchronously, through a webhook.

For a referenced refund, we return a CANCEL_OR_REFUND webhook.
For an unreferenced refund, we return a REFUND_WITH_DATA webhook.

To receive updates about your refunds, you must set up webhooks.

When a refund is processed, the amount is deducted from your in-process funds, and appears in your shopper's account within a few days.

CANCEL_OR_REFUND webhook

Before we send your referenced refund request to be processed, we perform various validations. If these validations succeed, usually the refund itself also succeeds. You receive the outcome of the validations asynchronously, in a CANCEL_OR_REFUND webhook that includes:

eventCode: CANCEL_OR_REFUND.
originalReference: the PSP reference of the original payment.
pspReference: the pspReference from the reversal response.
success: indicates the outcome of the refund validations. Possible values:
- true: Adyen's validations were successful and we sent the refund request to the card scheme. This usually means that the refund will be processed successfully. However, in rare cases the refund can be rejected by the card scheme, or reversed. For information about these exceptions, see REFUND_FAILED webhook, and REFUNDED_REVERSED webhook.
- false: the refund validations failed. The webhook includes a reason field with a short description of the problem. Review the reason, fix the issue if possible, and resubmit the refund request.

{
   "live":"false",
   "notificationItems":[
      {
         "NotificationRequestItem":{
            "additionalData":{
               "modification.action": "refund"
            },
            "amount":{
               "currency": "EUR",
               "value": 1025
            },
            "eventCode":"CANCEL_OR_REFUND",
            "eventDate":"2022-02-03T15:14:15.004Z",
            "merchantAccountCode":"YOUR_MERCHANT_ACCOUNT",
            "originalReference":"VK9DRSLLRCQ2WN82",
            "paymentMethod":"mc",
            "pspReference":"TF995R5G6L2GWR82",
            "reason":"",
            "success":"true"
         }
      }
   ]
}

For more information about the included fields, see the CANCEL_OR_REFUND webhook reference.

REFUND_WITH_DATA webhook

Before we send your unreferenced refund request to be processed, we perform various validations. If these validations succeed, usually the refund itself also succeeds. You receive the outcome of the validations asynchronously, in a REFUND_WITH_DATA webhook that includes:

eventCode: REFUND_WITH_DATA.
additionalData: the information in this objects depends on the additional settings that you enabled.
pspReference: the PSP reference of the original payment request.
success: indicates the outcome of the refund validations. Possible values:
- true: Adyen's validations were successful and we sent the refund request to the card scheme. This usually means that the refund will be processed successfully. However, in rare cases the refund can be rejected by the card scheme, or reversed. For information about these exceptions, see REFUND_FAILED webhook, and REFUNDED_REVERSED webhook.
- false: the refund validations failed. The webhook includes a reason field with a short description of the problem. Review the reason, fix the issue if possible, and resubmit the refund request.

{
   "live":"false",
   "notificationItems":[
      {
         "NotificationRequestItem":{
            "additionalData":{
                "fundingSource":"CREDIT"
            },
            "amount":{
               "currency":"EUR",
               "value":1500
            },
            "eventCode":"REFUND_WITH_DATA",
            "eventDate":"2018-07-16T17:46:51+02:00",
            "merchantAccountCode":"YOUR_MERCHANT_ACCOUNT",
            "merchantReference": "YOUR_MODIFICATION_REFERENCE",
            "paymentMethod":"mc",
            "pspReference":"NC6HT9CRT65ZGN82",
            "reason":"",
            "success":"true"
         }
      }
   ]
}

For more information about the included fields, see the REFUND_WITH_DATA webhook reference.

Reasons for failed refund validation

When our validations of a refund fail, you receive a webhook for the refund with success: false and the reason of the failure. The next table shows the most common reasons.

`reason`	Description
`Requested refund amount too high`	No chargeback or refund has been processed, and the requested refund amount is more than the balance on the payment.
`Already partially refunded, new requested refund amount too high`	Partial refund(s) has(/have) been processed, and the requested refund amount is more than the balance on the payment.
`Already partially disputed, new requested refund amount too high`	Partial chargeback(s) has(/have) been processed, and the requested refund amount is more than the balance on the payment.
`Already fully refunded, no balance available for new requested refund`	Full refund has been processed, and the remaining balance on the payment is 0.
`Partially refunded and partially disputed, no balance available for new requested refund`	Partial refund(s) and chargeback(s) have been processed, and the requested refund amount is more than the balance on the payment. Partial refund(s) and chargeback(s) have been processed, and the balance on the payment is a negative amount.
`Already fully disputed, no balance available for new requested refund`	Full chargeback has been processed, and the balance on the payment is 0. A full chargeback and partial refund(s) have been processed, and the balance on the payment is a negative amount.
`Insufficient in-process funds on account`	There is not enough balance on your merchant account to process the refund.
`Transaction hasn't been captured, refund not possible`	The refund was requested before the transaction was captured. You need to cancel the transaction instead or wait until the transaction is settled.
`The maximum period for this operation has expired`	The refund was requested past the expiration date permitted by the payment method to process the request.
`Amount too low to be accepted by Card Network`	The refund amount was too low. The amount must be greater than 0.01 in any currency.
`Modification in different currency than authorisation`	The refund was requested in a currency different from the currency in which the authorization was made.

The balance on the payment is the amount that remains from the original payment. For example, if a transaction has a total of EUR 10 and no refund or chargeback is processed, then the balance on the payment is EUR 10. After a refund or chargeback of EUR 3 is processed, the remaining balance on the payment is EUR 7.

Outcome of a refund

CANCEL_OR_REFUND webhook

REFUND_WITH_DATA webhook

Reasons for failed refund validation

See also