---
title: "Subscriby recorded a cash payout to the partner."
method: POST
path: "partner.payout_recorded"
tags: ["partner.* events"]
---

# Subscriby recorded a cash payout to the partner.

`POST partner.payout_recorded` (webhook)

### When this fires

Subscriby paid a partner who chose a cash rail and recorded it: payouts run monthly for balances of $50 or more, by PayPal, Wise, Remitly or USDT, to the details the partner saved, less the rail's own transfer fee. The amount is checked against what the partner is owed, then the oldest payable rows are marked paid while the amount lasts; `rewards_paid` says how many it covered, clawbacks included.

### Caveats

- **The payout details never travel.** Where the money went, a PayPal email, a wallet address or the bank account a Wise or Remitly transfer was made to, is stored encrypted on the partner's account and appears in no event.
- **A payout above the balance is refused** and emits nothing, as is one to a partner who chose Subscriby Credit.

### Related events

- `partner.reward_approved`: what becomes payable.
- `partner.reward_reversed`: what gets 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` 'partner.payout_recorded', required: The event name, always `partner.payout_recorded` 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.
    - `payout_id` string, uuid, required: The payout row.
    - `amount` string, decimal, required: What was paid, four decimal places.
    - `currency` string, required: `USD`.
    - `method` 'paypal' | 'wise' | 'remitly' | 'crypto', required: The rail the money went by. A partner on Subscriby Credit is settled by `partner.reward_credited` and never sees this event.
    - `reference` string, nullable, required: Subscriby's reference for the transfer. `null` when none was recorded.
    - `rewards_paid` integer, required: How many ledger rows the payout covered, clawbacks included; a remainder smaller than the next row stays on the balance.

## 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)