Adyen classic_platforms webhook events

These 18 notifications belong to classic Adyen for Platforms, and they carry the event in eventType. New integrations use the balancePlatform webhooks instead. 16 have sample payloads.

Every event here can also reach agents as an MCP event through Hookdeck: MCP events →

ACCOUNT_HOLDER_CREATED

documented from Adyen docs (example)

Classic platforms: account holder is created

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-holder-created.json
{
  "error": { … },
  "eventDate": "2019-01-02T01:00:00+01:00",
  "eventType": "ACCOUNT_HOLDER_CREATED",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

ACCOUNT_HOLDER_UPDATED

documented from Adyen docs (example)

Classic platforms: account holder is updated

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-holder-updated.json
{
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "ACCOUNT_HOLDER_UPDATED",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

ACCOUNT_HOLDER_VERIFICATION

documented from Adyen docs (example)

Classic platforms: verification results are available

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-holder-verification.json
{
  "error": { … },
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "ACCOUNT_HOLDER_VERIFICATION",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

ACCOUNT_HOLDER_STATUS_CHANGE

documented from Adyen docs (example)

Classic platforms: account holder status changes

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-holder-status-change.json
{
  "error": { … },
  "eventDate": "2019-01-02T01:00:00+01:00",
  "eventType": "ACCOUNT_HOLDER_STATUS_CHANGE",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

ACCOUNT_HOLDER_STORE_STATUS_CHANGE

documented from Adyen docs (example)

Classic platforms: store status changes

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-holder-store-status-change.json
{
  "eventType": "ACCOUNT_HOLDER_STORE_STATUS_CHANGE",
  "eventDate": "2018-04-23T13:13:44+02:00",
  "executingUserKey": "ws",
  "live": true,
  "pspReference": "1313642467023511",
  "content": { … }
}

Send example to Inspect → View as JSON

ACCOUNT_HOLDER_UPCOMING_DEADLINE

documented from Adyen docs (example)

Classic platforms: account holder deadline is coming up

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-holder-upcoming-deadline.json
{
  "eventDate": "2019-09-25T09:52:28+02:00",
  "eventType": "ACCOUNT_HOLDER_UPCOMING_DEADLINE",
  "live": false,
  "pspReference": "9315693979482563",
  "content": { … }
}

Send example to Inspect → View as JSON

ACCOUNT_CREATED

documented from Adyen docs (example)

Classic platforms: account is created

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-created.json
{
  "error": { … },
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "ACCOUNT_CREATED",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

ACCOUNT_UPDATED

documented from Adyen docs (example)

Classic platforms: account is updated

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-updated.json
{
  "error": { … },
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "ACCOUNT_UPDATED",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

ACCOUNT_CLOSED

documented from Adyen docs (example)

Classic platforms: account is closed

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-closed.json
{
  "error": { … },
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "ACCOUNT_CLOSED",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

ACCOUNT_HOLDER_PAYOUT

documented from Adyen docs (example)

Classic platforms: payout to an account holder is scheduled

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-account-holder-payout.json
{
  "error": { … },
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "ACCOUNT_HOLDER_PAYOUT",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

TRANSFER_FUNDS

documented from Adyen docs (example)

Classic platforms: funds transfer between accounts

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-transfer-funds.json
{
  "error": { … },
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "TRANSFER_FUNDS",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

BENEFICIARY_SETUP

documented from Adyen docs (example)

Classic platforms: benefactor and beneficiary relationship is created

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-beneficiary-setup.json
{
  "error": { … },
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "BENEFICIARY_SETUP",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

SCHEDULED_REFUNDS

documented from Adyen docs (example)

Classic platforms: refunds of unpaid transfers are scheduled

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-scheduled-refunds.json
{
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "SCHEDULED_REFUNDS",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

COMPENSATE_NEGATIVE_BALANCE

documented from Adyen docs (example)

Classic platforms: liable account covers an overdrawn account

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-compensate-negative-balance.json
{
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "COMPENSATE_NEGATIVE_BALANCE",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

REFUND_FUNDS_TRANSFER

documented No payload yet

Classic platforms: funds transfer between accounts is refunded

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

No payload yet.

Help fill this in → View as JSON

ACCOUNT_FUNDS_BELOW_THRESHOLD

documented No payload yet

Classic platforms: liable account funds fall below your threshold

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

No payload yet.

Help fill this in → View as JSON

DIRECT_DEBIT_INITIATED

documented from Adyen docs (example)

Classic platforms: automated direct debit starts

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-direct-debit-initiated.json
{
  "eventDate": "2021-02-01T14:19:14-08:00",
  "eventType": "DIRECT_DEBIT_INITIATED",
  "live": "false",
  "executingUserKey": "executing-user-key",
  "pspReference": "8315659584588245",
  "content": { … }
}

Send example to Inspect → View as JSON

PAYMENT_FAILURE

documented from Adyen docs (example)

Classic platforms: split payment booking fails

Identified by eventCode in Payments, type in body on Platforms Resource classic_platforms

adyen-payment-failure.json
{
  "eventDate": "2019-01-01T01:00:00+01:00",
  "eventType": "PAYMENT_FAILURE",
  "executingUserKey": "executing-user-key",
  "live": false,
  "pspReference": "TSTPSPR0001",
  "content": { … }
}

Send example to Inspect → View as JSON

Route Adyen events by type.

Event Gateway receives every Adyen delivery and filters and routes it by event type, so each service gets only the events it handles.

Not affiliated with Adyen. Facts are compiled from public sources and linked inline.