Adyen management webhook events
Adyen sends 9 management events, including merchant.created, merchant.updated and paymentMethod.created. 6 have sample payloads.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
merchant.created
documented from Adyen docs (example)
merchant.created Merchant account is created
Identified by eventCode in Payments, type in body on Platforms
Resource management
{
"type": "merchant.created",
"environment": "test",
"createdAt": "2022-08-12T10:50:01+02:00",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | merchant.created |
Full schema: 11 fields.
From Adyen docs
-
Content type
application/json
merchant.updated
documented from Adyen docs (example)
merchant.updated Merchant verification status or capabilities change
Identified by eventCode in Payments, type in body on Platforms
Resource management
{
"type": "merchant.updated",
"environment": "test",
"createdAt": "2022-09-20T13:41:12+02:00",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | merchant.updated |
Full schema: 27 fields.
From Adyen docs
-
Content type
application/json
paymentMethod.created
documented from Adyen docs (example)
paymentMethod.created Request to add a payment method completes
Identified by eventCode in Payments, type in body on Platforms
Resource management
{
"createdAt": "2022-01-24T14:59:11+01:00",
"data": { … },
"environment": "test",
"type": "paymentMethod.created"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | paymentMethod.created |
Full schema: 9 fields.
From Adyen docs
-
Content type
application/json
paymentMethodRequest.scheduledForRemoval
documented No payload yet
paymentMethodRequest.scheduledForRemoval Pending payment method request is scheduled for removal
Identified by eventCode in Payments, type in body on Platforms
Resource management
No payload yet.
paymentMethodRequest.removed
documented No payload yet
paymentMethodRequest.removed Pending payment method request is removed
Identified by eventCode in Payments, type in body on Platforms
Resource management
No payload yet.
terminalSettings.modified
documented from Adyen docs (example)
terminalSettings.modified Terminal settings update completes
Identified by eventCode in Payments, type in body on Platforms
Resource management
{
"type": "terminalSettings.modified",
"environment": "Live",
"createdAt": "2024-04-23T22:42:51+02:00",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | terminalSettings.modified |
Full schema: 10 fields.
terminalBoarding.triggered
documented from Adyen docs (example)
terminalBoarding.triggered Payment terminal boarding completes
Identified by eventCode in Payments, type in body on Platforms
Resource management
{
"type": "terminalBoarding.triggered",
"environment": "live",
"createdAt": "2024-04-23T22:42:51+02:00",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | terminalBoarding.triggered |
Full schema: 8 fields.
terminalAssignment.completed
documented No payload yet
terminalAssignment.completed Scheduled payment terminal assignment completes
Identified by eventCode in Payments, type in body on Platforms
Resource management
No payload yet.
forwardApi.notification
documented from Adyen docs (example)
forwardApi.notification Adyen forwards a payment request to a third party
Identified by eventCode in Payments, type in body on Platforms
Resource management
{
"type": "forwardApi.notification",
"version": "1",
"createdAt": "2023-02-27T16:14:06+01:00",
"environment": "test",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | forwardApi.notification |
Full schema: 18 fields.
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.