Version
READ

list_payments

Page the payment ledger the dashboard's All Transactions page shows, newest first, across every project the token may see or one project, with the page's filters.

Read the ledger a creator reads on All Transactions: every payment a member made or attempted, newest first, across every project the token may see, or one project via project_id. Each row carries the amount in the currency it was paid in (never converted), the gateway with its mode and the references it gave, the fee Subscriby calculated, why it was billed, the member and the plan, and the gateway's own words when it failed. A refund is a row of its own with status refunded; nothing here issues one, because refunds are recorded from the gateways and never raised from Subscriby.

Narrow with status (successful, failed, pending, refunded), plan_id, method_id, connector (the key of the project's live installation), from/to (ISO 8601) and search (the gateway references, the subscription's payment id, or a member, plan or project name). Page with limit (1..100, default 25) and page.

Requires ability

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

Runs the same action as

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

Read-only

It reads and never changes anything.

Arguments

project_idstringoptional

Optional project UUID to keep to one project's payments.

statusstringoptional

Optional status: successful, failed, pending or refunded.

plan_idstringoptional

Optional plan UUID.

method_idstringoptional

Optional payment method UUID.

connectorstringoptional

Optional connector key; keeps to projects whose live installation is that connector.

fromstringoptional

Optional ISO 8601 moment; payments that occurred at or after it.

tostringoptional

Optional ISO 8601 moment; payments that occurred at or before it.

searchstringoptional

Optional text matched against the gateway references, the subscription's payment id, or a member, plan or project name.

limitintegeroptional

Maximum payments to return per page (1..100).

min1max100
pageintegeroptional

1-indexed page number.

min1

What it returns

{  "data": [    {      "id": "8b0c4a15-e792-4360-95d8-1f47c0b3e926",      "subscription_id": "5b7e2d40-1a86-4c39-97f2-e83d0b16c5a4",      "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",      "plan_id": "2c1e7a9d-4b3f-4e8a-9c21-7d5e0b6a8f31",      "plan_name": "Monthly Pass",      "subscriber_id": "9a3b2c1d-6e5f-4a7b-8c9d-0e1f2a3b4c5d",      "subscriber_name": "Ada Lovelace",      "method_id": "a15d70c8-3e46-4b92-b70f-58c9d2140e63",      "provider": "stripe",      "provider_label": "Stripe",      "mode": "live",      "status": "successful",      "status_label": "Successful",      "amount": "29.0000",      "currency": "USD",      "calculated_fee": "0.8700",      "billing_reason": "subscription_cycle",      "external_payment_id": "pi_3QX1Y2Z3A4B5C6D7",      "external_event_id": "evt_1QX1Y2Z3A4B5C6D7",      "failure_reason": null,      "occurred_at": "2026-11-15T10:05:00+00:00",      "created_at": "2026-11-15T10:05:04+00:00"    }  ],  "meta": {    "page": 1,    "limit": 25,    "total": 1,    "has_more": false  }}

The raw gateway payload is never part of a row, on this tool or over REST.

How it fails

TOKEN_MISSING_ABILITY

token lacks payment:view-any.

RESOURCE_NOT_FOUND

project_id names a project the token cannot see: unknown, another team's, or outside the token's scope:project: allow-list.

VALIDATION_FAILED

status is not one of the four statuses, or from/to is not a moment; the error context lists what was expected.

How is this guide?

Last updated on