← All webhook events

Subscribe to service_order.refunded

A service order payment is refunded through the original payment gateway.

When does service_order.refunded fire?

Admin issues refund via the order detail page; gateway confirms.

What developers build with it

• → Accounting reversal
• → Provider clawback if already paid
• → Audit trail

Sample payload

The full envelope (with HMAC-SHA256 signature, delivery UUID and headers) is documented on the webhooks hub page. Below is the per-event data block for service_order.refunded:

{
    "order_id": 1421,
    "order_number": "SO/2026-27/00091",
    "ngo_id": 7,
    "status": "refunded",
    "assigned_provider_id": null
}

Subscribe to this event

From your NGO dashboard, head to System · Webhooks · Add new. Paste your HTTPS endpoint, copy the signing secret, tick service_order.refunded in the events list, save. The first matching event fires within seconds. Verify the X-Donateazy-Signature header on every request.

// PHP example - drop into your webhook receiver
$raw = file_get_contents('php://input');
$expected = hash_hmac('sha256', $raw, $WEBHOOK_SECRET);
if (! hash_equals($expected, $_SERVER['HTTP_X_DONATEAZY_SIGNATURE'] ?? '')) {
    http_response_code(401); exit;
}

$payload = json_decode($raw, true);
if ($payload['event'] !== 'service_order.refunded') {
    http_response_code(202); exit; // not for this handler
}

// $payload['data'] is the block documented above.
handleServiceOrderRefunded($payload['data'], $payload['id']);
http_response_code(200);

Often paired with

All 20 webhook events