Version
READ

get_payment

One payment by UUID, in the row list_payments pages — the amount as paid, the gateway and its references, the fee, the member, the plan and why it failed.

Read one payment the way the dashboard's transaction flyout shows it: the amount in the currency it was paid in, 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. The row is the one list_payments returns, so an agent that found a payment in the list reads the same fields back.

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

payment_id*string

UUID of the payment to fetch.

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": "failed",    "status_label": "Failed",    "amount": "29.0000",    "currency": "USD",    "calculated_fee": "0.0000",    "billing_reason": "subscription_cycle",    "external_payment_id": "pi_3QX1Y2Z3A4B5C6D8",    "external_event_id": "evt_1QX1Y2Z3A4B5C6D8",    "failure_reason": "card_declined",    "occurred_at": "2026-11-16T08:12:00+00:00",    "created_at": "2026-11-16T08:12:03+00:00"  }}

billing_reason is subscription_create, subscription_cycle, backfill, refund or access_code, or null when the gateway gave none. The raw gateway payload is never part of the row.

How it fails

RESOURCE_NOT_FOUND

unknown payment_id, a payment on another creator's project, or one outside the token's scope:project: allow-list; a malformed UUID answers the same.

TOKEN_MISSING_ABILITY

token lacks payment:view.

How is this guide?

Last updated on