partner.reward_reversed
A full refund, a dispute or a rejected review reversed a commission, or clawed back one already settled.
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.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
Header Parameters
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
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.
How is this guide?
Last updated on