The chargeback was successfully defended towards the issuing bank. This stage is not final. If the issuing bank presents a second chargeback, you can still lose the chargeback case.
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.
A generic container for extra fields.
Additional cost used in BIN or card verification.
The number of installments that the payment amount should be charged with.
Only relevant for card payments in countries that support installments.
A set of key-value pairs provided in the request, prefixed with 'metadata.'. For example, 'metadata.myField: myValue'
If the payment is referred, this field is set to true.
This field is unavailable if the payment is referred and is usually not returned with ecommerce transactions.
Raw refusal reason received from the acquirer, where available.
A Boolean value indicating whether 3DS authentication was completed on this payment.
The raw 3DS authentication result from the card issuer.
A Boolean value indicating whether 3DS was offered for this payment.
The raw enrollment result from the 3DS directory services of the card schemes.
The payment amount. For HTTP POST notifications, currency and value are returned as URL parameters.
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.
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.
false, then this includes a short message with an explanation for the refusal.
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.