Stripe credit_note webhook events
Stripe sends 3 credit_note events: credit_note.created, credit_note.updated and credit_note.voided.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
credit_note.created
documented official schema
credit_note.created Credit note created
Identified by type field in the body
Resource credit_note
stripe-credit-note-created.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 1690,
"amount_shipping": 0,
"created": 1234567890,
"currency": "usd",
"customer": "cus_QXg1o8vcGmoR32",
"customer_balance_transaction": null,
"discount_amount": 0,
"discount_amounts": [ … ],
"effective_at": 1234567890,
"id": "cn_1Pgc75B7WZ01zgkWJMPt5riP",
"invoice": "in_1Pgc75B7WZ01zgkWYv4iMwt7",
"status": "issued",
"type": "pre_payment"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "credit_note.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | cn_1Pgc75B7WZ01zgkWJMPt5riP |
data.object.status | string | issued |
data.object.type | string | pre_payment |
data.object.amount | integer | 1690 |
data.object.customer | string | cus_QXg1o8vcGmoR32 |
Full schema: 105 fields.
From Stripe docs
-
Content type
application/json
credit_note.updated
documented official schema
credit_note.updated Credit note changes
Identified by type field in the body
Resource credit_note
stripe-credit-note-updated.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 1690,
"amount_shipping": 0,
"created": 1234567890,
"currency": "usd",
"customer": "cus_QXg1o8vcGmoR32",
"customer_balance_transaction": null,
"discount_amount": 0,
"discount_amounts": [ … ],
"effective_at": 1234567890,
"id": "cn_1Pgc75B7WZ01zgkWJMPt5riP",
"invoice": "in_1Pgc75B7WZ01zgkWYv4iMwt7",
"status": "issued",
"type": "pre_payment"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "credit_note.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | cn_1Pgc75B7WZ01zgkWJMPt5riP |
data.object.status | string | issued |
data.object.type | string | pre_payment |
data.object.amount | integer | 1690 |
data.object.customer | string | cus_QXg1o8vcGmoR32 |
Full schema: 105 fields.
From Stripe docs
-
Content type
application/json
credit_note.voided
documented official schema
credit_note.voided Credit note voided
Identified by type field in the body
Resource credit_note
stripe-credit-note-voided.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"amount": 1690,
"amount_shipping": 0,
"created": 1234567890,
"currency": "usd",
"customer": "cus_QXg1o8vcGmoR32",
"customer_balance_transaction": null,
"discount_amount": 0,
"discount_amounts": [ … ],
"effective_at": 1234567890,
"id": "cn_1Pgc75B7WZ01zgkWJMPt5riP",
"invoice": "in_1Pgc75B7WZ01zgkWYv4iMwt7",
"status": "issued",
"type": "pre_payment"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "credit_note.voided"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | cn_1Pgc75B7WZ01zgkWJMPt5riP |
data.object.status | string | issued |
data.object.type | string | pre_payment |
data.object.amount | integer | 1690 |
data.object.customer | string | cus_QXg1o8vcGmoR32 |
Full schema: 105 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.