Stripe billing_portal webhook events
Stripe sends 3 billing_portal events: billing_portal.configuration.created, billing_portal.configuration.updated and billing_portal.session.created.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
billing_portal.configuration.created
documented official schema
billing_portal.configuration.created Customer portal configuration created
Identified by type field in the body
Resource billing_portal
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"active": true,
"application": null,
"business_profile": { … },
"created": 1234567890,
"default_return_url": null,
"features": { … },
"id": "bpc_1Pgc70B7WZ01zgkWSnFO04Vt",
"is_default": true,
"livemode": true,
"login_page": { … }
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "billing_portal.configuration.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | bpc_1Pgc70B7WZ01zgkWSnFO04Vt |
data.object.created | integer | 1234567890 |
Full schema: 66 fields.
From Stripe docs
-
Content type
application/json
billing_portal.configuration.updated
documented official schema
billing_portal.configuration.updated Customer portal configuration changes
Identified by type field in the body
Resource billing_portal
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"active": true,
"application": null,
"business_profile": { … },
"created": 1234567890,
"default_return_url": null,
"features": { … },
"id": "bpc_1Pgc70B7WZ01zgkWSnFO04Vt",
"is_default": true,
"livemode": true,
"login_page": { … }
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "billing_portal.configuration.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | bpc_1Pgc70B7WZ01zgkWSnFO04Vt |
data.object.created | integer | 1234567890 |
Full schema: 66 fields.
From Stripe docs
-
Content type
application/json
billing_portal.session.created
documented official schema
billing_portal.session.created Customer portal session starts
Identified by type field in the body
Resource billing_portal
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"configuration": "bpc_1Pgc7HB7WZ01zgkWxH2EPWRX",
"created": 1234567890,
"customer": "cus_QXg1o8vcGmoR32",
"flow": { … },
"id": "bps_1Pgc7HB7WZ01zgkWNs8s9Auh",
"livemode": true,
"locale": null,
"object": "billing_portal.session",
"on_behalf_of": null,
"return_url": "https://example.com/account",
"url": "https://sangeekp-15t6ai--customer_portal-mydev.dev.stripe.me/session/{SESSION_SECRET}"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "billing_portal.session.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | bps_1Pgc7HB7WZ01zgkWNs8s9Auh |
data.object.customer | string | cus_QXg1o8vcGmoR32 |
data.object.created | integer | 1234567890 |
Full schema: 49 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.