Transaction Fees API
Transaction Fees are what Subscriby charges a creator on the money their members pay: a percentage of each payment at the plan's rate, a code redeemed past the plan's free allotment, the metered fees a platform trial waived, emails sent to members during a recovery, and the cost of collecting an invoice's fee lines.
Transaction Fees are what Subscriby charges a creator on the money their members pay: a percentage of each payment at the plan's rate, a code redeemed past the plan's free allotment, the metered fees a platform trial waived, emails sent to members during a recovery, and the cost of collecting an invoice's fee lines. Every one of them is a line of the creator's Transaction Fees ledger, written the moment the fee is decided and never re-priced. The dashboard shows the same ledger under Plans & Billing → Transaction Fees, with a month picker and a CSV export.
These routes are about the caller's own fees, so they live under /v1/me and need no project or team in the path; both need account:read. Nothing here writes: a line is written by the sale, the meter event or the invoice that decided the fee.
Two channels, one ledger. A fee is collected one of two ways and the ledger says which on every line.
connect_at_source: Stripe Connect deducted it from the member's payment as it passed through, so it never appears on a Subscriby invoice.metered: it was reported to the usage meter and billed on the creator's own Subscriby invoice; once that invoice is paid, the line carries itsinvoice_idandinvoiced_at, so every unit of a Transaction Fees invoice line can be followed back to the sale it was earned on.
Endpoints
/v1/me/transaction-feesList your transaction feesGET/v1/me/transaction-fees/summaryGet a month's fee summaryRelated
How is this guide?
Last updated on