Version
READ

get_payment_method

One configured payment method of a project by UUID — provider, mode and switch only, never a credential.

Read one payment gateway back before switching it, syncing it or removing it. The row is the one list_payment_methods returns: id, provider, connector, mode, active and created_at, and nothing else. provider is a gateway slug or a connector:provider key for a currency a connector brings (telegram:stars), and connector names that connector or is null.

Deliberately thin

Provider secrets, webhook signing secrets and Stripe Connect account ids live in an encrypted column and are never surfaced through MCP or REST, whatever ability the token carries. The dashboard is the only place a creator sees them.

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

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_id*string

UUID of the project the method belongs to.

payment_method_id*string

UUID of the payment method to fetch.

What it returns

{  "data": {    "id": "a15d70c8-3e46-4b92-b70f-58c9d2140e63",    "provider": "stripe",    "connector": null,    "mode": "live",    "active": true,    "created_at": "2026-05-18T10:05:00+00:00"  }}

mode is test or live and decides which set of credentials the gateway uses; the same provider can be configured once in each.

How it fails

RESOURCE_NOT_FOUND

unknown project_id or payment_method_id, a method of another project, or a project outside the token's scope.

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks project-payment-method:view.

How is this guide?

Last updated on