Documentation
MCP

Unavailable operations

Operations FloPay MCP deliberately does not serve, with the reason recorded for each in the reviewed API contract, including high-risk actions.

Unavailable operations

FloPay MCP never lists or runs these operations. Each exclusion and its reason come from the FloPay MCP contract version 1, revision 764b41d5c7205d6df7eeaeac832fafe882247f5526b1d4d6bc6f98e3eaca7784. An exclusion here does not change how the REST API behaves, and an operation that has not been reviewed for MCP is unavailable too, even though it is not listed.

OperationReason
PATCH /v1/settings/chargebacks/{id}Chargeback settings require the state-bound MCP confirmation contract.
POST /v1/settings/chargebacks/{id}/descriptorsChargeback settings require the state-bound MCP confirmation contract.
GET /v1/checkouts/sessions/{id}Checkout-session-token operations are outside the merchant MCP surface.
POST /v1/checkouts/sessions/{id}/3ds/completeCheckout-session-token operations are outside the merchant MCP surface.
PATCH /v1/checkouts/sessions/{id}/accountCheckout-session-token operations are outside the merchant MCP surface.
PATCH /v1/checkouts/sessions/{id}/claimCheckout-session-token operations are outside the merchant MCP surface.
POST /v1/checkouts/sessions/{id}/processCheckout-session-token operations are outside the merchant MCP surface.
GET /v1/checkouts/sessions/{id}/productsCheckout-session-token operations are outside the merchant MCP surface.
GET /v1/checkouts/sessions/{id}/statusCheckout-session-token operations are outside the merchant MCP surface.
POST /v1/checkouts/sessions/{id}/vault/captureCheckout-session-token operations are outside the merchant MCP surface.
POST /v1/api-tokensCredential operations require the state-bound MCP confirmation contract.
DELETE /v1/api-tokens/{id}Credential operations require the state-bound MCP confirmation contract.
DELETE /v1/collections/{uuid}Destructive catalog operations are reviewed and implemented separately.
DELETE /v1/coupons/{uuid}Destructive catalog operations are reviewed and implemented separately.
DELETE /v1/products/brands/{uuid}Destructive catalog operations are reviewed and implemented separately.
POST /v1/products/brands/{uuid}/lifecycle/deleteDestructive catalog operations are reviewed and implemented separately.
DELETE /v1/products/categories/{uuid}Destructive catalog operations are reviewed and implemented separately.
POST /v1/products/categories/{uuid}/lifecycle/deleteDestructive catalog operations are reviewed and implemented separately.
DELETE /v1/products/{productUuid}/media/{uuid}Destructive catalog operations are reviewed and implemented separately.
POST /v1/products/{productUuid}/media/{uuid}/lifecycle/deleteDestructive catalog operations are reviewed and implemented separately.
DELETE /v1/products/{productUuid}/prices/{uuid}Destructive catalog operations are reviewed and implemented separately.
POST /v1/products/{productUuid}/prices/{uuid}/lifecycle/deleteDestructive catalog operations are reviewed and implemented separately.
DELETE /v1/products/{productUuid}/variants/{uuid}Destructive catalog operations are reviewed and implemented separately.
POST /v1/products/{productUuid}/variants/{uuid}/lifecycle/deleteDestructive catalog operations are reviewed and implemented separately.
DELETE /v1/products/{uuid}Destructive catalog operations are reviewed and implemented separately.
DELETE /v1/settings/dunning-policyDunning-policy mutations require the state-bound MCP confirmation contract.
PATCH /v1/settings/dunning-policyDunning-policy mutations require the state-bound MCP confirmation contract.
GET /v1/exports/statusExport kill-switch status is a Dashboard preflight, not an MCP merchant operation.
DELETE /v1/brandingHigh- and critical-risk merchant operations are reviewed and implemented separately.
DELETE /v1/checkout-links/{uuid}High- and critical-risk merchant operations are reviewed and implemented separately.
PATCH /v1/checkout-links/{uuid}High- and critical-risk merchant operations are reviewed and implemented separately.
POST /v1/checkouts/sessionsHigh- and critical-risk merchant operations are reviewed and implemented separately.
POST /v1/paymentsHigh- and critical-risk merchant operations are reviewed and implemented separately.
POST /v1/settings/gatewaysHigh- and critical-risk merchant operations are reviewed and implemented separately.
PATCH /v1/settings/gateways/{id}High- and critical-risk merchant operations are reviewed and implemented separately.
POST /v1/settings/gateways/{id}/activateHigh- and critical-risk merchant operations are reviewed and implemented separately.
POST /v1/settings/gateways/{id}/deactivateHigh- and critical-risk merchant operations are reviewed and implemented separately.
POST /v1/webhooksHigh- and critical-risk merchant operations are reviewed and implemented separately.
DELETE /v1/webhooks/{id}High- and critical-risk merchant operations are reviewed and implemented separately.
PATCH /v1/webhooks/{id}High- and critical-risk merchant operations are reviewed and implemented separately.
POST /v1/mcp/token-exchangeMCP adapter infrastructure: the credential exchange is not a merchant tool.
PUT /v1/payments/{id}/cancelPayment mutations require the state-bound MCP confirmation contract.
PUT /v1/payments/{id}/capturePayment mutations require the state-bound MCP confirmation contract.
POST /v1/payments/{id}/refundPayment mutations require the state-bound MCP confirmation contract.
DELETE /v1/payment-methods/{id}Payment-method deletion requires the state-bound MCP confirmation contract.
PATCH /v1/settings/pre-dispute-alerts/{id}Pre-dispute settings require the state-bound MCP confirmation contract.
POST /v1/settings/pre-dispute-alerts/{id}/descriptorsPre-dispute settings require the state-bound MCP confirmation contract.
POST /v1/subscriptions/{id}/changeSubscription changes require the state-bound MCP confirmation contract.
PUT /v1/subscriptions/{id}/cancelSubscription control requires the state-bound MCP confirmation contract.
PUT /v1/subscriptions/{id}/extendSubscription control requires the state-bound MCP confirmation contract.
PUT /v1/subscriptions/{id}/pauseSubscription control requires the state-bound MCP confirmation contract.
PUT /v1/subscriptions/{id}/reactivateSubscription control requires the state-bound MCP confirmation contract.
PUT /v1/subscriptions/{id}/resumeSubscription control requires the state-bound MCP confirmation contract.
POST /v1/subscriptionsSubscription creation requires the state-bound MCP confirmation contract.
POST /v1/client-usersTeam and role changes require the state-bound MCP confirmation contract.
POST /v1/client-users/ownership/transferTeam and role changes require the state-bound MCP confirmation contract.
DELETE /v1/client-users/{id}Team and role changes require the state-bound MCP confirmation contract.
PATCH /v1/client-users/{id}Team and role changes require the state-bound MCP confirmation contract.
GET /v1/subscriptions/activeThis is a deprecated compatibility route: it stays operational for existing direct API and SDK callers but is excluded from MCP parity.
GET /v1/products/{productUuid}/mediaThis legacy collection returns a bare array for backward compatibility.
GET /v1/products/{productUuid}/variantsThis legacy collection returns a bare array for backward compatibility.
GET /v1/products/{productUuid}/pricesThis legacy collection returns a bare array; MCP clients use GET /v1/product-prices.
GET /v1/settings/chargebacksThis legacy collection returns a bare array; MCP clients use GET /v1/settings/pre-dispute-alerts.
GET /v1/settings/chargebacks/{id}/descriptorsThis legacy collection returns a bare array; MCP clients use GET /v1/settings/pre-dispute-alerts/{id}/descriptors.
POST /v1/auth/password-reset/confirmUnauthenticated identity recovery is outside the merchant MCP surface.
POST /v1/auth/password-reset/requestUnauthenticated identity recovery is outside the merchant MCP surface.
POST /v1/auth/password-reset/validateUnauthenticated identity recovery is outside the merchant MCP surface.
GET /v1/webhooks/{id}Webhook configuration requires the state-bound MCP confirmation contract.
POST /v1/webhooks/events/resendWebhook replay actions require the state-bound MCP confirmation contract.
PUT /v1/webhooks/events/{id}/resendWebhook replay actions require the state-bound MCP confirmation contract.

On this page