Stripe issuing_transaction webhook events
Stripe sends 3 issuing_transaction events: issuing_transaction.created, issuing_transaction.purchase_details_receipt_updated and issuing_transaction.updated.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
issuing_transaction.created
documented official schema
issuing_transaction.created Issuing transaction created
Identified by type field in the body
Resource issuing_transaction
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": -100,
"amount_details": { … },
"authorization": "iauth_1Pgc78B7WZ01zgkW9IPKCfII",
"balance_transaction": null,
"card": "ic_1Pgag5B7WZ01zgkWephORn8N",
"cardholder": "ich_1Pgag4B7WZ01zgkWdPVfBngi",
"created": 1234567890,
"currency": "usd",
"dispute": null,
"id": "ipi_1Pgc78B7WZ01zgkWm0QxtFzQ",
"livemode": false,
"type": "capture"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "issuing_transaction.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | ipi_1Pgc78B7WZ01zgkWm0QxtFzQ |
data.object.type | string | capture |
data.object.amount | integer | -100 |
data.object.created | integer | 1234567890 |
Full schema: 48 fields.
From Stripe docs
-
Content type
application/json
issuing_transaction.purchase_details_receipt_updated
documented official schema
issuing_transaction.purchase_details_receipt_updated Issuing transaction gets receipt data
Identified by type field in the body
Resource issuing_transaction
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": -100,
"amount_details": { … },
"authorization": "iauth_1Pgc78B7WZ01zgkW9IPKCfII",
"balance_transaction": null,
"card": "ic_1Pgag5B7WZ01zgkWephORn8N",
"cardholder": "ich_1Pgag4B7WZ01zgkWdPVfBngi",
"created": 1234567890,
"currency": "usd",
"dispute": null,
"id": "ipi_1Pgc78B7WZ01zgkWm0QxtFzQ",
"livemode": false,
"type": "capture"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "issuing_transaction.purchase_details_receipt_updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | ipi_1Pgc78B7WZ01zgkWm0QxtFzQ |
data.object.type | string | capture |
data.object.amount | integer | -100 |
data.object.created | integer | 1234567890 |
Full schema: 48 fields.
From Stripe docs
-
Content type
application/json
issuing_transaction.updated
documented official schema
issuing_transaction.updated Issuing transaction changes
Identified by type field in the body
Resource issuing_transaction
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": -100,
"amount_details": { … },
"authorization": "iauth_1Pgc78B7WZ01zgkW9IPKCfII",
"balance_transaction": null,
"card": "ic_1Pgag5B7WZ01zgkWephORn8N",
"cardholder": "ich_1Pgag4B7WZ01zgkWdPVfBngi",
"created": 1234567890,
"currency": "usd",
"dispute": null,
"id": "ipi_1Pgc78B7WZ01zgkWm0QxtFzQ",
"livemode": false,
"type": "capture"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "issuing_transaction.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | ipi_1Pgc78B7WZ01zgkWm0QxtFzQ |
data.object.type | string | capture |
data.object.amount | integer | -100 |
data.object.created | integer | 1234567890 |
Full schema: 48 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.