Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

MultiSafepay (BYOK) — connector documentation

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

What MultiSafepay (BYOK) is for

MultiSafepay (BYOK) lets an AI assistant read your own MultiSafepay data through the MultiSafepay API with a key you supply (MultiSafepay API key (live account or website)). Read-only: 8 tools (list_gateways, list_payment_methods, get_order, get_transaction, list_closing_balances, get_site, list_terminals, get_terminal). 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.multisafepay.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by MultiSafepay. MultiSafepay 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:

  • "Which payment gateways are enabled on my MultiSafepay site?"
  • "Which payment methods can a Dutch customer use for a 50 EUR order?"
  • "What is the status of MultiSafepay order ORDER-1001?"
  • "What was the net amount of MultiSafepay transaction 123456789?"
  • "What were my MultiSafepay closing balances last month?"
  • "What are the settings of my MultiSafepay site 12345?"

What it does

  • list_gateways: List the gateway identifiers of the payment methods activated for your site, with their descriptions.
  • list_payment_methods: List the payment methods activated for your site with allowed currencies, countries, amount limits and brands, optionally filtered by amount, country or currency.
  • get_order: Get one order by its order id or transaction id: status, financial status, amount, refunded amount, currency and dates. Customer and payment details are not returned.
  • get_transaction: Get one transaction by id: type, status, financial status, amount, net amount, fees, currency, payment method, site and dispute status. Customer data is not returned.
  • list_closing_balances: List your closing balance history per currency: balance, uncleared amount, payout amount, closing date and status. Bank account numbers are not returned.
  • get_site: Get one of your MultiSafepay websites: name, URL, notification URL, order price range and support contacts. The site's API key is not returned.
  • list_terminals: List the point-of-sale terminals bound to your MultiSafepay account with provider, serial number, group, country and active flag.
  • get_terminal: Get one point-of-sale terminal by id.

BYOK key

You bring your own MultiSafepay MultiSafepay API key (live account or website) (https://docs.multisafepay.com/docs/sites). 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.multisafepay.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.

Data sources

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

Built for: Worldwide. Languages: English.