---
title: "A full refund, a dispute or a rejected review reversed a commission, or clawed back one already settled."
method: POST
path: "partner.reward_reversed"
tags: ["partner.* events"]
---

# A full refund, a dispute or a rejected review reversed a commission, or clawed back one already settled.

`POST partner.reward_reversed` (webhook)

### When this fires

The platform charge that earned a commission was refunded in full (`reason: refund`) or disputed (`reason: dispute`), or Subscriby rejected a referral it had held for review (`reason: rejected`). A row never settled is reversed in place; a row already credited or paid is answered with a clawback, a second row carrying the negative amount, so the partner's balance drops and the next credit or payout nets it off. One event per commission touched.

> **A partial refund changes nothing.** Subscriby kept most of the money, and the rule a partner can be told is the simple one: only a full refund or a dispute takes a commission back.

### Caveats

- **A redelivered refund writes no second clawback.** The second delivery finds the rows reversed and the clawback written, and touches nothing.
- **A dispute reverses on the day it opens**, because the money is withheld from then; a dispute later won is not revisited.
- **A rejected review reverses every commission the referral earned**, and the referral earns nothing further.

### Related events

- `partner.reward_credited`: where a clawback is netted off on the credit rail.
- `partner.payout_recorded`: where a clawback is netted off in cash.

## 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` 'partner.reward_reversed', required: The event name, always `partner.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 reversal touched.
    - `referral_id` string, uuid, required: The referral it was earned on.
    - `amount` string, decimal, required: The commission's own amount, positive, four decimal places.
    - `currency` string, required: `USD`.
    - `reason` 'refund' | 'dispute' | 'rejected', required: Why.
    - `clawback_reward_id` string, uuid, nullable, required: The negative row written against a commission already credited or paid. `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)