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

Top-up canceled

Identified by type field in the body Resource topup

stripe-topup-canceled.json
{
  "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

Send example to Inspect → View as JSON

topup.created

documented official schema

Top-up created

Identified by type field in the body Resource topup

stripe-topup-created.json
{
  "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

Send example to Inspect → View as JSON

topup.failed

documented official schema

Top-up fails

Identified by type field in the body Resource topup

stripe-topup-failed.json
{
  "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

Send example to Inspect → View as JSON

topup.reversed

documented official schema

Top-up reversed

Identified by type field in the body Resource topup

stripe-topup-reversed.json
{
  "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

Send example to Inspect → View as JSON

topup.succeeded

documented official schema

Top-up succeeds

Identified by type field in the body Resource topup

stripe-topup-succeeded.json
{
  "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

Send example to Inspect → View as 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.

Not affiliated with Stripe. Facts are compiled from public sources and linked inline.