Search docs

Are you looking for test card numbers?

Would you like to contact support?

Start searching Adyen's documentation...

  Documentation

Event codes

Learn about event codes and what they mean. 


Each notification contains an eventCode, which indicates which event has occurred. These are described below.

Most event codes will be enabled when you've set up Standard notifications, but some need to be set up by our Support team. 

We may introduce new event types from time to time. When setting up notifications, we recommend that your server does not expect a predefined set of values.

Event code Description
AUTHORISATION

The result of an authorised transaction is returned with this event code.

This does not mean the authorisation was successful. For more information, see success in the Notifications API.

Modification events

AUTHORISATION_ADJUSTMENT The result of an Adjust Authorisation modification is returned with this event code.
CANCELLATION The result of a Cancel modification is returned with this event code.
CANCEL_OR_REFUND

The result of a Cancel or refund modification is returned with this event code.

CAPTURE

The result of a capture modification is returned with this event code.

This notification is only sent for manual captures by default. For more information, refer to Automatic capture.

CAPTURE_FAILED*

The capture has failed due to a technical issue. We will fix the issue if possible, and resubmit the capture request. For more information, refer to Failed capture.

PAIDOUT_REVERSED* Returned when the issuer was unable to pay out the funds to the account holder, and the funds were returned to Adyen.
POSTPONED_REFUND

Notifies you that the refund for the payment will be performed after the payment is captured.

This notification is not enabled when you set up Standard notifications. Contact the Support Team to enable it.

REFUND The result of a Refund modification is returned with this event code.
REFUND_FAILED*

The refund has failed due to a technical issue. You should retry the refund.

If you receive more than two failures on the same refund, contact the Support Team.

REFUNDED_REVERSED*

When we receive back the funds from the bank we book the transaction to Refunded Reversed. This can happen if the card is closed.

VOID_PENDING_REFUND

Applicable to POS only. The voidPendingRefund service attempts to cancel a POS refund request. The final outcome will be reported through notifications.

The success field holds the outcome of the request. If true, the refund has been cancelled, and no funds are transferred to the shopper. If false, the refund was processed (not cancelled) and the funds have been transferred to the shopper. For more information, refer to Cancel a POS refund request.

Recurring events

RECURRING_CONTRACT

Confirmation that a recurring contract was created.

This notification is not enabled when you set up Standard notifications. Contact the Support Team   to enable it.

Dispute events

CHARGEBACK* Sent when the funds are deducted from your account.
SECOND_CHARGEBACK

Sent when the disputed amount is deducted from your account after the issuing bank declines the material submitted during defense of the original chargeback.

The SecondChargeback journal type is available from November 5. For more information, see our FAQ.

CHARGEBACK_REVERSED*

Triggered when the funds are returned to your account.

NOTIFICATION_OF_CHARGEBACK*

The dispute process has opened. You should investigate the dispute and upload defense documents. For more information, see Supply dispute defense documents.

NOTIFICATION_OF_FRAUD*

The alert passed on by issuers to schemes and subsequently to processors. Visa calls them TC40 and Mastercard calls them System to Avoid Fraud Effectively (SAFE). These are informational notifications offered at no charge by Adyen, providing merchants the opportunity to take actions, such as blocking a shopper or issuing a refund before a chargeback is incurred.

PREARBITRATION_WON

Sent when merchant initiated Pre-Arbitration has been accepted by the cardholder's bank.

PREARBITRATION_LOST

Sent when merchant initiated Pre-Arbitration has been declined by the cardholder's bank.

REQUEST_FOR_INFORMATION* Sent when a shopper opens an RFI (Request for Information) case with the bank. You should upload defense documents to help the information to the shopper understand the charge. For more information, see Supply dispute defense documents.

Manual review events

MANUAL_REVIEW_ACCEPT*

Confirmation that the manual review was accepted.

This notification is not enabled when you set up Standard notifications. Contact the Support Team   to enable it.

MANUAL_REVIEW_REJECT*

Confirmation that the manual review was rejected.

This notification is not enabled when you set up Standard notifications. Contact the Support Team   to enable it.

Payout events

PAYOUT_EXPIRE* The payout has expired.
PAYOUT_DECLINE* The payout was declined.
PAYOUT_THIRDPARTY

The third-party payout has been processed.

REFUND_WITH_DATA

The refund with data has been processed.

Other

HANDLED_EXTERNALLY* The payment has been handled outside the Adyen payments platform.
OFFER_CLOSED*

The offer has closed.

This notification is not enabled when you set up Standard notifications. Contact the Support Team   to enable it.

ORDER_OPENED*

The order has been created.

ORDER_CLOSED*

Sent when a partial payments transaction for an order is complete.

This event code does not mean that the order was successful. When success=true, the order closed because the full amount was paid. When success=false, it closed because the shopper did not pay the full amount within the sessionValidity .

PENDING* The transaction is pending.
PROCESS_RETRY* An idempotent request has been processed.
REPORT_AVAILABLE*

A report has been generated by Adyen. Use the included URL to retrieve this report.

You won't receive a notification when a payment is settled. 

success always = true for this notification.