Stripe refund webhook events
Stripe sends 3 refund events: refund.created, refund.failed and refund.updated.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
refund.created
documented official schema
refund.created Refund created
Identified by type field in the body
Resource refund
stripe-refund-created.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 100,
"balance_transaction": null,
"charge": "ch_1PgafuB7WZ01zgkWXYmPNZs8",
"created": 1234567890,
"currency": "usd",
"destination_details": { … },
"id": "re_1Pgc72B7WZ01zgkWqPvrRrPE",
"metadata": { … },
"object": "refund",
"payment_intent": null,
"reason": null,
"status": "succeeded"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "refund.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | re_1Pgc72B7WZ01zgkWqPvrRrPE |
data.object.status | string | succeeded |
data.object.amount | integer | 100 |
data.object.created | integer | 1234567890 |
Full schema: 33 fields.
From Stripe docs
-
Content type
application/json
refund.failed
documented official schema
refund.failed Refund fails
Identified by type field in the body
Resource refund
stripe-refund-failed.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 100,
"balance_transaction": null,
"charge": "ch_1PgafuB7WZ01zgkWXYmPNZs8",
"created": 1234567890,
"currency": "usd",
"destination_details": { … },
"id": "re_1Pgc72B7WZ01zgkWqPvrRrPE",
"metadata": { … },
"object": "refund",
"payment_intent": null,
"reason": null,
"status": "succeeded"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "refund.failed"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | re_1Pgc72B7WZ01zgkWqPvrRrPE |
data.object.status | string | succeeded |
data.object.amount | integer | 100 |
data.object.created | integer | 1234567890 |
Full schema: 33 fields.
From Stripe docs
-
Content type
application/json
refund.updated
documented official schema
refund.updated Refund changes
Identified by type field in the body
Resource refund
stripe-refund-updated.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 100,
"balance_transaction": null,
"charge": "ch_1PgafuB7WZ01zgkWXYmPNZs8",
"created": 1234567890,
"currency": "usd",
"destination_details": { … },
"id": "re_1Pgc72B7WZ01zgkWqPvrRrPE",
"metadata": { … },
"object": "refund",
"payment_intent": null,
"reason": null,
"status": "succeeded"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "refund.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | re_1Pgc72B7WZ01zgkWqPvrRrPE |
data.object.status | string | succeeded |
data.object.amount | integer | 100 |
data.object.created | integer | 1234567890 |
Full schema: 33 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.