Stripe topup webhook events
Stripe sends 5 topup events, including topup.canceled, topup.created and topup.failed.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
topup.canceled
documented official schema
topup.canceled Top-up canceled
Identified by type field in the body
Resource topup
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 1000,
"balance_transaction": null,
"created": 1234567890,
"currency": "usd",
"description": "Top-up description",
"expected_availability_date": 123456789,
"failure_code": null,
"failure_message": null,
"id": "tu_1Pgc7BB7WZ01zgkWwH7rkBgR",
"livemode": false,
"metadata": { … },
"status": "pending"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "topup.canceled"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | tu_1Pgc7BB7WZ01zgkWwH7rkBgR |
data.object.status | string | pending |
data.object.amount | integer | 1000 |
data.object.created | integer | 1234567890 |
Full schema: 72 fields.
From Stripe docs
-
Content type
application/json
topup.created
documented official schema
topup.created Top-up created
Identified by type field in the body
Resource topup
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 1000,
"balance_transaction": null,
"created": 1234567890,
"currency": "usd",
"description": "Top-up description",
"expected_availability_date": 123456789,
"failure_code": null,
"failure_message": null,
"id": "tu_1Pgc7BB7WZ01zgkWwH7rkBgR",
"livemode": false,
"metadata": { … },
"status": "pending"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "topup.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | tu_1Pgc7BB7WZ01zgkWwH7rkBgR |
data.object.status | string | pending |
data.object.amount | integer | 1000 |
data.object.created | integer | 1234567890 |
Full schema: 72 fields.
From Stripe docs
-
Content type
application/json
topup.failed
documented official schema
topup.failed Top-up fails
Identified by type field in the body
Resource topup
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 1000,
"balance_transaction": null,
"created": 1234567890,
"currency": "usd",
"description": "Top-up description",
"expected_availability_date": 123456789,
"failure_code": null,
"failure_message": null,
"id": "tu_1Pgc7BB7WZ01zgkWwH7rkBgR",
"livemode": false,
"metadata": { … },
"status": "pending"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "topup.failed"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | tu_1Pgc7BB7WZ01zgkWwH7rkBgR |
data.object.status | string | pending |
data.object.amount | integer | 1000 |
data.object.created | integer | 1234567890 |
Full schema: 72 fields.
From Stripe docs
-
Content type
application/json
topup.reversed
documented official schema
topup.reversed Top-up reversed
Identified by type field in the body
Resource topup
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 1000,
"balance_transaction": null,
"created": 1234567890,
"currency": "usd",
"description": "Top-up description",
"expected_availability_date": 123456789,
"failure_code": null,
"failure_message": null,
"id": "tu_1Pgc7BB7WZ01zgkWwH7rkBgR",
"livemode": false,
"metadata": { … },
"status": "pending"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "topup.reversed"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | tu_1Pgc7BB7WZ01zgkWwH7rkBgR |
data.object.status | string | pending |
data.object.amount | integer | 1000 |
data.object.created | integer | 1234567890 |
Full schema: 72 fields.
From Stripe docs
-
Content type
application/json
topup.succeeded
documented official schema
topup.succeeded Top-up succeeds
Identified by type field in the body
Resource topup
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 1000,
"balance_transaction": null,
"created": 1234567890,
"currency": "usd",
"description": "Top-up description",
"expected_availability_date": 123456789,
"failure_code": null,
"failure_message": null,
"id": "tu_1Pgc7BB7WZ01zgkWwH7rkBgR",
"livemode": false,
"metadata": { … },
"status": "pending"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "topup.succeeded"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | tu_1Pgc7BB7WZ01zgkWwH7rkBgR |
data.object.status | string | pending |
data.object.amount | integer | 1000 |
data.object.created | integer | 1234567890 |
Full schema: 72 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.