Stripe person webhook events
Stripe sends 3 person events: person.created, person.deleted and person.updated.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
person.created
documented official schema
person.created Person added to an account
Identified by type field in the body
Resource person
stripe-person-created.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"account": "acct_1PgafTB7WZ01zgkW",
"additional_tos_acceptances": { … },
"created": 1234567890,
"dob": { … },
"first_name": null,
"future_requirements": { … },
"id": "person_1Pgc6oB7WZ01zgkWnmLL70wS",
"id_number_provided": false,
"last_name": null,
"metadata": { … },
"object": "person"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "person.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | person_1Pgc6oB7WZ01zgkWnmLL70wS |
data.object.account | string | acct_1PgafTB7WZ01zgkW |
data.object.created | integer | 1234567890 |
Full schema: 67 fields.
From Stripe docs
-
Content type
application/json
person.deleted
documented official schema
person.deleted Person removed from an account
Identified by type field in the body
Resource person
stripe-person-deleted.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"account": "acct_1PgafTB7WZ01zgkW",
"additional_tos_acceptances": { … },
"created": 1234567890,
"dob": { … },
"first_name": null,
"future_requirements": { … },
"id": "person_1Pgc6oB7WZ01zgkWnmLL70wS",
"id_number_provided": false,
"last_name": null,
"metadata": { … },
"object": "person"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "person.deleted"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | person_1Pgc6oB7WZ01zgkWnmLL70wS |
data.object.account | string | acct_1PgafTB7WZ01zgkW |
data.object.created | integer | 1234567890 |
Full schema: 67 fields.
From Stripe docs
-
Content type
application/json
person.updated
documented official schema
person.updated Person on an account changes
Identified by type field in the body
Resource person
stripe-person-updated.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"account": "acct_1PgafTB7WZ01zgkW",
"additional_tos_acceptances": { … },
"created": 1234567890,
"dob": { … },
"first_name": null,
"future_requirements": { … },
"id": "person_1Pgc6oB7WZ01zgkWnmLL70wS",
"id_number_provided": false,
"last_name": null,
"metadata": { … },
"object": "person"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "person.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | person_1Pgc6oB7WZ01zgkWnmLL70wS |
data.object.account | string | acct_1PgafTB7WZ01zgkW |
data.object.created | integer | 1234567890 |
Full schema: 67 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.