The result of the authorisation request.
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.
Additional cost used in BIN or card verification.
The number of installments that the payment amount should be charged with.
Example: 5
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'
The eligibility for PayPal Seller Protection for this payment.
Example: Ineligible
The token for stored payment details to make recurring payments.
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.
Example: true
Raw refusal reason received from the acquirer, where available.
Example: AUTHORISED
Its value corresponds to the pspReference value of the transaction.
This field can take one of the following values:
OneOff: (OOFF) Direct debit instruction to initiate exactly one direct debit transaction.
First: (FRST) Initial/first collection in a series of direct debit instructions.
Recurring: (RCUR) Direct debit instruction to carry out regular direct debit transactions initiated by the creditor.
Final: (FNAL) Last/final collection in a series of direct debit instructions.
Example: OOFF
A Boolean value indicating whether 3DS authentication was completed on this payment.
Example: true
The raw 3DS authentication result from the card issuer.
Example: N
A Boolean value indicating whether 3DS was offered for this payment.
Example: true
The raw enrollment result from the 3DS directory services of the card schemes.
Example: Y
The payment amount. For HTTP POST notifications, currency and value are returned as URL parameters.
The amount of the transaction, in minor units.
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.
The operations indicate the supported follow-up actions concerning the payment.
This is an experimental field. Do not base your code on this field. Not all specific cases are covered yet. It's possible that the field is empty or contains generic information.
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
= true
and paymentMethod
= visa
, mc
, or amex
then this field contains the following details:
Authorisation code, last 4 digits of the card, card expiry date.
In case of failure, this contains information about the authorisation failure
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.