activate_payment_method
Offer a configured payment method to buyers again and re-queue its plan sync. Refuses a Stripe method whose Connect onboarding never finished.
The creator's on-switch for a gateway. Activating offers the method at checkout again and re-queues
the plan sync for its gateway, so its catalogue is current by the time the first buyer arrives.
Idempotent: a method that is already on is a no-op and emits nothing. When the switch flips,
project.payment_method.updated emits once with
changes.active.
Stripe needs its Connect handshake first
A Stripe method whose Connect onboarding never finished is refused with
VALIDATION_FAILED. Switching it on early would offer buyers a gateway that
fails at checkout; onboarding can only be completed from the dashboard, the
one place the Connect handshake can run.
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.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time.
Arguments
project_id*stringUUID of the project the method belongs to.
payment_method_id*stringUUID of the payment method to switch on.
What it returns
{ "data": { "id": "a15d70c8-3e46-4b92-b70f-58c9d2140e63", "provider": "paypal", "mode": "live", "active": true, "created_at": "2026-05-18T10:05:00+00:00" }}How it fails
VALIDATION_FAILEDa Stripe method whose Connect onboarding is incomplete.
RESOURCE_NOT_FOUNDunknown project_id or payment_method_id, a method of another project, or a project outside the token's scope.
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project-payment-method:update.
How is this guide?
Last updated on