Для AI-агентов: markdown этой страницы — /docs/mcp-payments.mdиндекс документации — /llms.txt
MCP: payments
Обновлено
Определения инструментов. Обновляйте tools/list после изменения прав. required_scopes: ALL.
configure_payment_credentials
Configure (upsert) ONE payment provider for the tenant. Provide `credentials` — discriminated by `provider` (e.g. yookassa {shop_id, api_key}; stripe {secret_key, webhook_secret, currency?}) — plus optional `enabled` (default true) and `default_currency`. Credentials are stored server-side and NEVER returned by a read. Idempotent upsert on the tenant. OWNER-ONLY money-config — runs ONLY as this dedicated typed tool, never via execute_admin_action.
Scopes (ALL): ["payments:config"]. Risk: "money".
disable_payment_provider
Switch OFF one payment provider by `provider` (keeps the stored credentials — re-enable by reconfiguring). Idempotent — disabling an already-off/absent provider returns disabled:true. OWNER-ONLY money-config (dedicated typed tool only).
Scopes (ALL): ["payments:config"]. Risk: "money".
enable_payment_provider
Switch ON one payment provider by `provider` WITHOUT sending credentials. This is how Telegram Stars (`stars`) is connected — it has no secrets, so it is not part of configure_payment_credentials. Also re-arms a credentialed provider that was switched off, reusing the secrets already on file. Idempotent — enabling an already-on provider returns enabled:true. The response `hasCredentials:false` means the provider still needs configure_payment_credentials before checkout works. OWNER-ONLY money-config (dedicated typed tool only).
Scopes (ALL): ["payments:config"]. Risk: "money".
get_payment_config
Read the tenant payment-provider config: each of the 9 providers (yookassa / stripe / robokassa / tinkoff / prodamus / paypal / paddle / cryptobot / stars) with `enabled`, `hasCredentials` (whether a secret is on file — the secret itself is NEVER returned) and `currency`, plus the tenant `defaultCurrency`. OWNER-ONLY. 0-cost read.
Scopes (ALL): ["payments:config"]. Risk: "read".
list_payment_rows
List payment records for the current tenant. Each record is addressed by its tenant-scoped `seqNum` and references customers and orders by their sequence numbers. This reads payments, not payment-provider configuration.
Scopes (ALL): ["payments"]. Risk: "read".
onboarding_check_payment_provider
Verify the current payment configuration and return specific remaining requirements. Optional: payment setup is not part of the mandatory onboarding path and never blocks onboarding_complete.
Scopes (ALL): ["payments:config"]. Risk: "write".
onboarding_confirm_payment_webhook
After the owner reviews the exact provider configuration, record their explicit webhook setup confirmation. This is owner attestation, not verification of a live callback. Optional: payment setup is not part of the mandatory onboarding path and never blocks onboarding_complete.
Scopes (ALL): ["payments:config"]. Risk: "money".
onboarding_connect_payment_provider
Save the selected payment provider configuration and verify readiness without charging the owner. The first accepted payment of at least 10 RUB secures the trial advance. Optional: payment setup is not part of the mandatory onboarding path and never blocks onboarding_complete.
Scopes (ALL): ["payments:config"]. Risk: "money".