order.refundedOrder refunded
A refund was issued — partial or full. Payload includes the deduction amount.
When this fires
A refund (partial or full) was issued against an order — payload includes the deduction amount and a running total.
Sample payload
This is the exact envelope shape we POST to your endpoint — outer wrapper plus the per-event data payload. Field values are randomised on each render so you see the general shape, not a fixed example.
json
{
"id": "657f8365-6e5d-4e53-acfa-e7fd5c2761ba",
"event": "order.refunded",
"created": "2026-06-12T15:00:35.341Z",
"data": {
"id": "cn58asug8d9k0000000000000",
"number": "TY-1ZXXP1B",
"refundId": "cfog38hwblvq0000000000000",
"amountKobo": 791113,
"totalRefundedKobo": 8583791,
"orderTotalKobo": 8794648,
"refundStatus": "partial",
"reason": "wrong_item",
"reasonNote": null,
"isManual": false
}
}Use cases
- Update your books with the refund amount and reason.
- If the refund is full, restock the items in your inventory ERP.
- Tag the customer record for a follow-up call in your CRM.
Subscribe in the dashboard
To start receiving this event, add it to a webhook's subscription list in Developers → Webhooks. Wildcard subscriptions ( order.*) work too — see the webhooks guide for the matching rules.