---
title: "A full refund reversed a commission, or clawed back one the creator had already paid."
method: POST
path: "referral.reward_reversed"
tags: ["referral.* events"]
---

# A full refund reversed a commission, or clawed back one the creator had already paid.

`POST referral.reward_reversed` (webhook)

### When this fires

A payment that had earned a commission was fully refunded or charged back, which Subscriby learns from the same gateway event that emits `payment.refunded`. A row never paid out is reversed in place; a row already paid is answered with a clawback, a second row carrying the negative amount, so the affiliate's balance drops and the creator's next payout nets it off.

> **A partial refund changes nothing.** The creator kept most of the money, and the rule an affiliate can be told is the simple one: only a full refund takes a commission back. Days are never taken back.

### Caveats

- **A redelivered refund writes no second clawback.** The second delivery finds the rows reversed and the clawback written, and touches nothing.
- **A refund that names its payment touches that payment's commission only.** One that names none unwinds every live commission on the subscription, which is what a refund of "the last charge" means.

### Related events

- `payment.refunded`: the refund this followed.
- `referral.payout_recorded`: where a clawback is netted off.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'referral.reward_reversed', required: The event name, always `referral.reward_reversed` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `reward_id` string, uuid, required: The commission the refund touched.
    - `referral_id` string, uuid, required: The referral it was earned on.
    - `affiliate_id` string, uuid, required: The referrer.
    - `amount` string, decimal, nullable, required: The commission's own amount, positive, four decimal places.
    - `currency_id` string, uuid, nullable, required: Its currency.
    - `reason` string, required: Why. Only `refund` today.
    - `clawback_reward_id` string, uuid, nullable, required: The negative row written against a commission that was already paid out. `null` when the commission was reversed in place.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)