This page lists the common eventCode values you receive in Standard webhooks and what each one tells you.
How to read an event
Every notification carries an eventCode that identifies what happened. Two fields are central to interpreting it:
successtells you the outcome of the event,trueorfalse. For some event codes the field is alwaystrue, because the event itself is the outcome.originalReferencelinks a follow-up event back to the original payment. It contains thepspReferenceof the original payment, so you can match a capture, refund, or cancellation to the authorization it belongs to.
Set up your server to accept event types beyond those listed here, because Adyen adds new ones over time.
Payment lifecycle events
eventCode | What it means |
| The outcome of a payment request. |
| The outcome of a request to capture an authorized payment. Not sent for automatic captures by default. |
| The capture failed due to rejection by the card scheme. |
| The outcome of a request to cancel a payment. |
| The outcome of a request to refund a payment. |
| The refund failed due to rejection by the card scheme. |
| The outcome of a request to cancel or refund a payment, depending on whether it had been captured. |
For capture and refund events, originalReference contains the pspReference of the original payment. For how authorization and capture relate, see Payment Lifecycle States.
Dispute events
eventCode | What it means |
| The dispute process has opened. You should investigate and supply defense documents. |
| A payment was charged back and the funds were deducted from your account. |
| A chargeback was defended toward the issuing bank. This stage is not final. |
| The issuing bank declined your defense material. The disputed amount is deducted from your account. |
| An informational fraud alert from the issuer, giving you the chance to act before a chargeback. |
Many more exist
The Standard webhook includes additional default event types, such as AUTHORISATION_ADJUSTMENT, EXPIRE, ORDER_OPENED, and ORDER_CLOSED, as well as payout and non-default event types you can enable. Handle the events relevant to your integration and ignore the rest, while keeping your server tolerant of unknown event codes.
For how to act on these events safely, see Handling Webhooks.