Checkout.com (BYOK)

Checkout.com (BYOK) — connector documentation

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

What Checkout.com (BYOK) is for

Checkout.com (BYOK) lets an AI assistant read your own Checkout.com data through the Checkout.com API with a key you supply (Checkout.com secret API key (sk_...)). Read-only: 10 tools (list_payments, get_payment, list_payment_actions, list_disputes, get_dispute, get_balances, list_financial_actions, list_reports, get_report, list_workflows). 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.checkout.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkout.com. Checkout.com 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:

• "Find the Checkout.com payment for order ORD-1"
• "What is the status of Checkout.com payment pay_abc?"
• "Was Checkout.com payment pay_abc refunded?"
• "Which Checkout.com disputes still need evidence?"
• "Show Checkout.com dispute dsp_1"
• "What are my Checkout.com balances?"

What it does

• list_payments: List payments that match a reference (such as your order id), newest first, with amount, currency, status, approval, card scheme and balances.
• get_payment: Get one payment by id with amount, currency, status, approval, reference, card scheme, balances (authorized, captured, refunded, voided) and risk flag.
• list_payment_actions: List the actions on one payment (authorization, capture, refund, void) latest first, with amount, approval and response code.
• list_disputes: List disputes (chargebacks) newest update first, filtered by status, payment or dates, with category, reason code, amount and evidence deadline.
• get_dispute: Get one dispute by id with category, reason code, status, amount, deadline and the disputed payment's id and reference.
• get_balances: Get the balances of each currency account of an entity (available, pending, payable, collateral), optionally as of a past time.
• list_financial_actions: List the financial actions (captures, refunds, chargebacks) of a payment or action with processing dates, response codes, card type and fee breakdown.
• list_reports: List the generated reports with type, description, period and file names, optionally between two creation times.
• get_report: Get one report by id with type, description, period, tags and file names.
• list_workflows: List the event workflows with id, name and whether each is active (webhook URLs and signatures are not returned).

BYOK key

You bring your own Checkout.com Checkout.com secret API key (sk_...) (https://www.checkout.com/docs/developer-resources/api/api-endpoints). 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.checkout.com 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.

Notices

Production keys only; sandbox uses a different host (api.sandbox.checkout.com) and is not covered. Use a secret key with read scopes only.

Data sources

• https://api-reference.checkout.com/ (the API this connector calls, with a BYOK key)

Live from the Checkout.com API (*.api.checkout.com) with a BYOK key; documentation: https://api-reference.checkout.com/. 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 Checkout.com. Checkout.com 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 Checkout.com account.

Built for: Worldwide. Languages: English.

Checkout.com (BYOK) — Privacy Policy

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

What Checkout.com (BYOK) is. Checkout.com (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Checkout.com data: Read your Checkout.com payments, disputes, balances, financial actions and reports with BYOK API key. You bring your own Checkout.com Checkout.com secret API key (sk_...); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Checkout.com 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.checkout.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Checkout.com 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 Checkout.com receives. The request we make on your behalf, including the key and the arguments, under Checkout.com's own terms and privacy policy. Checkout.com acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Checkout.com 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 Checkout.com 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. Checkout.com (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 Checkout.com at any time to end all access.

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

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

Checkout.com (BYOK) — Terms of Service

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

1. The Service. Checkout.com (BYOK) provides: Read your Checkout.com payments, disputes, balances, financial actions and reports with BYOK API key. 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 Checkout.com credentials and only access data you are allowed to access. Checkout.com's terms apply to your use of Checkout.com; 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 Checkout.com. Checkout.com 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 Checkout.com returns, lightly trimmed; it may be incomplete, delayed or changed by Checkout.com. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Checkout.com 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 Checkout.com'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; Checkout.com 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 Checkout.com 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 Checkout.com 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-checkoutcom

Checkout.com (BYOK) support

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

• MCP endpoint: https://byok-checkoutcom.connectorbay.com/mcp
• REST API: https://byok-checkoutcom.connectorbay.com/openapi.json
• Live status: https://byok-checkoutcom.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. Checkout.com (BYOK) never asks for them.