Stripe terminal webhook events
Stripe sends 3 terminal events: terminal.reader.action_failed, terminal.reader.action_succeeded and terminal.reader.action_updated.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
terminal.reader.action_failed
documented official schema
terminal.reader.action_failed Action sent to a Terminal reader fails
Identified by type field in the body
Resource terminal
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"action": { … },
"device_sw_version": null,
"device_type": "bbpos_wisepos_e",
"id": "tmr_iGOgDOlmFAot3zIp2JzEqXYs",
"ip_address": "192.168.2.2",
"label": "Blue Rabbit",
"livemode": false,
"location": null,
"metadata": { … },
"status": "online"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "terminal.reader.action_failed"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | tmr_iGOgDOlmFAot3zIp2JzEqXYs |
data.object.status | string | online |
Full schema: 31 fields.
From Stripe docs
-
Content type
application/json
terminal.reader.action_succeeded
documented official schema
terminal.reader.action_succeeded Action sent to a Terminal reader succeeds
Identified by type field in the body
Resource terminal
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"action": { … },
"device_sw_version": null,
"device_type": "bbpos_wisepos_e",
"id": "tmr_iGOgDOlmFAot3zIp2JzEqXYs",
"ip_address": "192.168.2.2",
"label": "Blue Rabbit",
"livemode": false,
"location": null,
"metadata": { … },
"status": "online"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "terminal.reader.action_succeeded"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | tmr_iGOgDOlmFAot3zIp2JzEqXYs |
data.object.status | string | online |
Full schema: 31 fields.
From Stripe docs
-
Content type
application/json
terminal.reader.action_updated
documented official schema
terminal.reader.action_updated Action sent to a Terminal reader changes
Identified by type field in the body
Resource terminal
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"action": { … },
"device_sw_version": null,
"device_type": "bbpos_wisepos_e",
"id": "tmr_iGOgDOlmFAot3zIp2JzEqXYs",
"ip_address": "192.168.2.2",
"label": "Blue Rabbit",
"livemode": false,
"location": null,
"metadata": { … },
"status": "online"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "terminal.reader.action_updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | tmr_iGOgDOlmFAot3zIp2JzEqXYs |
data.object.status | string | online |
Full schema: 31 fields.
From Stripe docs
-
Content type
application/json
Route Stripe events by type.
Event Gateway receives every Stripe delivery and filters and routes it by event type, so each service gets only the events it handles.