Version
DESTRUCTIVE

sync_payment_method_plans

Queue a push of the project's plans into a payment gateway's catalogue. Answers sync_queued; the work runs in the background.

Some gateways keep their own catalogue — Stripe products and prices, PayPal, Razorpay and CoinPayments plans — and a subscription can only be sold through them once the plan exists there. Subscriby pushes the catalogue after every plan write and every method switch; this tool queues that push by hand, for the times a gateway was reconfigured or a sync failed and the creator wants it re-run now.

The answer is sync_queued, not a result: the work runs in the background and each plan reports through the plan-sync webhook events as it lands. Idempotent in the sense that it can be repeated safely — queuing twice pushes the same catalogue twice, which changes nothing.

Not every gateway has a catalogue

Telegram Stars, access codes and the redirect gateways (Paystack, CeyPay, Skrill) take the price at checkout and keep no plan objects, so a sync for them is refused with VALIDATION_FAILED rather than queued as a no-op.

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

DestructiveIdempotentOpen world

A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time. It reaches beyond Subscriby: a connector, a provider or a member.

Arguments

project_id*string

UUID of the project the method belongs to.

payment_method_id*string

UUID of the payment method whose gateway catalogue to refresh.

What it returns

{  "data": {    "payment_method_id": "a15d70c8-3e46-4b92-b70f-58c9d2140e63",    "status": "sync_queued"  }}

How it fails

VALIDATION_FAILED

the gateway keeps no catalogue (connector currencies, access codes, the redirect gateways).

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:update.

How is this guide?

Last updated on