delete_payment_method
Remove a payment method from a project. Destructive — buyers lose that way to pay at once; the row is soft-deleted so history survives.
Take a gateway off a project. The row is soft-deleted rather than destroyed: subscriptions sold through it keep their gateway for refunds and history, and configuring the same provider in the same mode again later revives the row instead of creating a duplicate. What changes immediately is the checkout — buyers lose that way to pay.
Emits project.payment_method.deleted with a
credential-free snapshot. Idempotent: an already-deleted id surfaces as RESOURCE_NOT_FOUND,
exactly as an unknown or out-of-scope id does.
Destructive — confirm with a human first
Confirm the exact payment_method_id with the creator before calling. If the
intent is "stop offering it for now",
deactivate_payment_method does that
reversibly.
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 remove.
What it returns
{ "data": { "payment_method_id": "a15d70c8-3e46-4b92-b70f-58c9d2140e63", "deleted": true }}How it fails
VALIDATION_FAILEDthe removal was refused for the method's current state.
RESOURCE_NOT_FOUNDunknown or already-deleted 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:delete.
How is this guide?
Last updated on