Refunds and chargebacks

Who deals with disputes, what a reversal does to access and earnings, and the webhook events your app gets.

Who handles them

Refunds are issued by our team, and chargebacks come to us, so your app doesn't deal with them. Your app can't issue refunds through the API.

What a reversal does

The buyer loses access to what they bought.
The sale leaves the creator's earnings, and any commission on it goes too.
If those earnings were already paid out, they're recovered from later earnings. See How payouts work.

Events your app gets

Event	When	Includes
`drop.refunded`	A paid drop is refunded or charged back	The order, `refundedAt`, and `reason` of `refund` or `chargeback`
`tip.refunded`	A paid tip is refunded or charged back	The tip, `refundedAt`, and `reason`
`subscription.ended`	A subscription's access ends	`reason`, which can be `refunded`

Counting money correctly

POST /drops/check-status still reports a refunded sale as paid, so use it for delivery only. GET /earnings leaves out refunds and chargebacks, so use that for money.

Reducing disputes

Show buyers what they're getting before they pay, and tell them what name will appear on their statement. How buyers pay covers what the statement shows.

Our refund policy sets out when buyers get money back.