Adyen recurring webhook events
Adyen sends 4 recurring events, including recurring.token.alreadyExisting, recurring.token.created and recurring.token.disabled.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
recurring.token.alreadyExisting
documented from Adyen docs (example)
recurring.token.alreadyExisting New token matches one that already exists
Identified by eventCode in Payments, type in body on Platforms
Resource recurring
{
"createdAt": "2025-06-30T16:40:23+02:00",
"eventId": "QBQQ9DLNRHHKGK38",
"environment": "test",
"data": { … },
"type": "recurring.token.alreadyExisting"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | recurring.token.alreadyExisting |
Full schema: 10 fields.
From Adyen docs
-
Content type
application/json
recurring.token.created
documented from Adyen docs (example)
recurring.token.created Stored payment token is created
Identified by eventCode in Payments, type in body on Platforms
Resource recurring
{
"createdAt": "2025-06-30T16:40:23+02:00",
"eventId": "QBQQ9DLNRHHKGK38",
"environment": "test",
"data": { … },
"type": "recurring.token.created"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | recurring.token.created |
Full schema: 10 fields.
From Adyen docs
-
Content type
application/json
recurring.token.disabled
documented from Adyen docs (example)
recurring.token.disabled Stored payment token is disabled
Identified by eventCode in Payments, type in body on Platforms
Resource recurring
{
"createdAt": "2025-06-30T16:40:23+02:00",
"eventId": "QBQQ9DLNRHHKGK38",
"environment": "test",
"data": { … },
"type": "recurring.token.disabled"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | recurring.token.disabled |
Full schema: 9 fields.
From Adyen docs
-
Content type
application/json
recurring.token.updated
documented from Adyen docs (example)
recurring.token.updated Stored payment token is updated
Identified by eventCode in Payments, type in body on Platforms
Resource recurring
{
"createdAt": "2025-06-30T16:40:23+02:00",
"eventId": "QBQQ9DLNRHHKGK38",
"environment": "test",
"data": { … },
"type": "recurring.token.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
type | string | recurring.token.updated |
Full schema: 10 fields.
From Adyen docs
-
Content type
application/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.