CloudPayments (BYOK)

CloudPayments (BYOK) — connector documentation

• MCP endpoint: https://byok-cloudpayments.connectorbay.com/mcp
• REST API: POST https://byok-cloudpayments.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-cloudpayments.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own CloudPayments Public ID of the site (login), sent in the X-Upstream-Key header and the API secret of the site (password) in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-cloudpayments.connectorbay.com/health · Tool schemas: https://byok-cloudpayments.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-cloudpayments · agent@connectorbay.com

What CloudPayments (BYOK) is for

CloudPayments (BYOK) lets an AI assistant read your own CloudPayments data through the CloudPayments API with a key you supply (Public ID of the site (login)). Read-only: 6 tools (test_connection, get_transaction, find_payment_by_invoice, list_transactions_by_day, get_subscription, find_subscriptions). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.cloudpayments.ru. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by CloudPayments. CloudPayments and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Do my CloudPayments credentials work?"
• "What is the status of CloudPayments transaction 504?"
• "Was CloudPayments order 1234567 paid?"
• "Which CloudPayments transactions happened on 2026-10-01?"
• "What is the state of CloudPayments subscription sc_8cf8a9338fb8ebf7202b08d09c938?"
• "Which CloudPayments subscriptions does account user_x have?"

What it does

• test_connection: Check that the Public ID and API secret work; returns a success flag and a request id.
• get_transaction: Get one transaction by its number: amount, currency, order id, status and reason, payout amount, dates, card brand and issuing country. Card numbers, names and IP addresses are not returned by this tool.
• find_payment_by_invoice: Find the payment for an order or invoice number and return its status; if several attempts exist, all payments for the order are searched.
• list_transactions_by_day: List all transactions registered on one day, with amount, order id, status and reason, payout amount and dates (card numbers are not returned by this tool).
• get_subscription: Get one recurring-payment subscription by id: amount, interval, status, number of successful and failed charges and next charge date.
• find_subscriptions: List the subscriptions of one payer account id (the AccountId the shop used, often a user id or email) with amount, interval and status.

BYOK key

You bring your own CloudPayments Public ID of the site (login) (https://merchant.cloudpayments.ru/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.cloudpayments.ru over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developers.cloudpayments.ru/en/ (the API this connector calls, with a BYOK key)

Live from the CloudPayments API (api.cloudpayments.ru) with a BYOK key; documentation: https://developers.cloudpayments.ru/en/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by CloudPayments. CloudPayments and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your CloudPayments account.

Built for: Worldwide. Languages: English.

CloudPayments (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What CloudPayments (BYOK) is. CloudPayments (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own CloudPayments data: Read your CloudPayments (Russia and CIS) payment transactions, order status and recurring subscriptions with your own Public ID and API secret. You bring your own CloudPayments Public ID of the site (login); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one CloudPayments call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.cloudpayments.ru, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If CloudPayments rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What CloudPayments receives. The request we make on your behalf, including the key and the arguments, under CloudPayments's own terms and privacy policy. CloudPayments acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer CloudPayments gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your CloudPayments data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. CloudPayments (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at CloudPayments at any time to end all access.

Children. CloudPayments (BYOK) is a general-audience service operated by the adult using the assistant, under CloudPayments's own age rules.

Changes. We will post changes here with a new effective date.

CloudPayments (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the CloudPayments (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. CloudPayments (BYOK) provides: Read your CloudPayments (Russia and CIS) payment transactions, order status and recurring subscriptions with your own Public ID and API secret. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own CloudPayments credentials and only access data you are allowed to access. CloudPayments's terms apply to your use of CloudPayments; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by CloudPayments. CloudPayments and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data CloudPayments returns, lightly trimmed; it may be incomplete, delayed or changed by CloudPayments. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your CloudPayments account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent CloudPayments's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; CloudPayments may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your CloudPayments key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action CloudPayments takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-cloudpayments

CloudPayments (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-cloudpayments.connectorbay.com/mcp
• REST API: https://byok-cloudpayments.connectorbay.com/openapi.json
• Live status: https://byok-cloudpayments.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. CloudPayments (BYOK) never asks for them.