Sign in
Events/Orders
order.refunded

Order 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": "5e61bdf1-804b-447c-9b8e-6dc6060979af",
  "event": "order.refunded",
  "created": "2026-10-28T01:10:52.683Z",
  "data": {
    "id": "cdbsi933z4r80000000000000",
    "number": "TY-F4HE3VL",
    "refundId": "cfsd7wndl42w0000000000000",
    "amountKobo": 1630894,
    "totalRefundedKobo": 916051,
    "orderTotalKobo": 1722946,
    "refundStatus": "full",
    "reason": "damaged",
    "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.