Stripe issuing_authorization webhook events
Stripe sends 3 issuing_authorization events: issuing_authorization.created, issuing_authorization.request and issuing_authorization.updated.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
issuing_authorization.created
documented official schema
issuing_authorization.created Issuing authorization created
Identified by type field in the body
Resource issuing_authorization
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 0,
"amount_details": { … },
"approved": true,
"authorization_method": "keyed_in",
"balance_transactions": [ … ],
"card": { … },
"cardholder": null,
"created": 1234567890,
"currency": "usd",
"fleet": { … },
"id": "iauth_1Pgc77B7WZ01zgkWn0SmtHBY",
"status": "pending"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "issuing_authorization.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | iauth_1Pgc77B7WZ01zgkWn0SmtHBY |
data.object.status | string | pending |
data.object.amount | integer | 0 |
data.object.created | integer | 1234567890 |
Full schema: 215 fields.
From Stripe docs
-
Content type
application/json
issuing_authorization.request
documented official schema
issuing_authorization.request Synchronous request for you to approve or decline an authorization
Identified by type field in the body
Resource issuing_authorization
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 0,
"amount_details": { … },
"approved": true,
"authorization_method": "keyed_in",
"balance_transactions": [ … ],
"card": { … },
"cardholder": null,
"created": 1234567890,
"currency": "usd",
"fleet": { … },
"id": "iauth_1Pgc77B7WZ01zgkWn0SmtHBY",
"status": "pending"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "issuing_authorization.request"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | iauth_1Pgc77B7WZ01zgkWn0SmtHBY |
data.object.status | string | pending |
data.object.amount | integer | 0 |
data.object.created | integer | 1234567890 |
Full schema: 215 fields.
From Stripe docs
-
Content type
application/json
issuing_authorization.updated
documented official schema
issuing_authorization.updated Issuing authorization changes
Identified by type field in the body
Resource issuing_authorization
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 0,
"amount_details": { … },
"approved": true,
"authorization_method": "keyed_in",
"balance_transactions": [ … ],
"card": { … },
"cardholder": null,
"created": 1234567890,
"currency": "usd",
"fleet": { … },
"id": "iauth_1Pgc77B7WZ01zgkWn0SmtHBY",
"status": "pending"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "issuing_authorization.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | iauth_1Pgc77B7WZ01zgkWn0SmtHBY |
data.object.status | string | pending |
data.object.amount | integer | 0 |
data.object.created | integer | 1234567890 |
Full schema: 215 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.