Issuer included comments

webhookISSUER_COMMENTS

API Version

The issuer included free-text comments with relevant information about the dispute process, such as why the issuer decided to initiate or continue the dispute. You can receive issuer comments for chargebacks and pre-arbitration cases.

Request Parameters

Required

Optional

Informs about the origin of the notification. The value is true when originating from the live environment, false for the test environment.

A container object for the details included in the notification.

This object is a generic container that can hold extra fields.

Acquirer Reference Number of the dispute.

Indicates if the dispute was automatically defended.

The merchant reference of the capture.

The PSP reference of the capture.

The reason code for the chargeback.

The card scheme for the chargeback.

Indicates if you can defend the dispute.

When the defense period ends. Format: ISO 8601 format with time zone offset: YYYY-MM-DDThh:mm:ss+TZD, for example, 2020-12-18T10:15:30+01:00.

More information about the stage the dispute is in. This parameter is not returned for disputed payments processed in Brazil.

Chargeback gross currency.

Chargeback gross value.

The reason code for the Notification of Fraud (NOF).

The card scheme for the Notification of Fraud (NOF).

The Adyen sub-variant of the payment method used for the payment request.

The reason code for the Request for Information (RFI).

The card scheme for the Request for Information (RFI).

The ID that uniquely identifies the shopper. This is the same as the shopperReference used in the initial payment.

The payment amount. For HTTP POST notifications, currency and value are returned as URL parameters.

The type of event the notification item is for.

The time when the event was generated. Format: ISO 8601; yyyy-MM-DDThh:mm:ssTZD

The merchant account identifier used in the transaction the notification item is for.

Your reference to uniquely identify the payment.

For modifications, this field corresponds to the payment request assigned to the original payment.

The payment method used in the transaction.

Adyen's 16-character unique reference associated with the transaction or request. This value is globally unique. Use it when communicating with us about this request.

If success = false, then this includes a short message with an explanation for the refusal.

Informs about the outcome of the event (eventCode) the notification is for. If true: the event was executed successfully. If false: the event was not executed successfully.

Response parameters

When you receive a webhook, you must respond with an HTTP status code.

HTTP Responses

200 - No Content
Webhook events are accepted on the basis of the HTTP status code.

Issuer included comments

HTTP Responses

200 - No Content