Version

Payments API

A payment is one row of the ledger behind the dashboard's All Transactions page: a member's successful, failed, pending or refunded charge for a subscription, with the amount as the gateway took it, the gateway and the references it gave, the fee Subscriby calculated, why it was billed and, when it failed, the gateway's own words.

A payment is one row of the ledger behind the dashboard's All Transactions page: a member's successful, failed, pending or refunded charge for a subscription, with the amount as the gateway took it, the gateway and the references it gave, the fee Subscriby calculated, why it was billed and, when it failed, the gateway's own words. The rows are written as the gateways report them (a charge, a renewal, a failed card, a refund), so there is no POST here and no refund endpoint: Subscriby issues no refunds of its own, a refund arrives from the gateway as a row with status refunded, and payment.refunded announces it.

These endpoints read the ledger as the page reads it, across every project the token reaches, with the page's own filters, and one payment with everything its flyout shows. The reporting view of the same rows, one project over one period with keyset pagination, is GET /v1/analytics/transactions.

Endpoints

How is this guide?

Last updated on

Version

On this page

Subscriby is a product
designed by you — for you.
No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request

For AI agents: llms.txt · llms-full.txt