Easypay (BYOK)

Easypay (BYOK) — connector documentation

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

What Easypay (BYOK) is for

Easypay (BYOK) lets an AI assistant read your own Easypay data through the Easypay API with a key you supply (Easypay account id). Read-only: 12 tools (check_connection, get_account_config, list_single_payments, get_single_payment, list_subscription_payments, list_captures, list_refunds, list_settlements, list_chargebacks, list_ledger_entries, list_payment_links, list_terminals). 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.prod.easypay.pt. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Easypay. Easypay 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:

• "Are my Easypay credentials valid?"
• "Which payment methods are enabled on my Easypay account?"
• "What single payments did my Easypay account receive recently?"
• "Show the details of Easypay single payment c6056234-a3f9-42de-b944-3ed793fcb6bb"
• "Which subscriptions are set up on my Easypay account?"
• "What captures did Easypay record this month?"

What it does

• check_connection: Check that the account id and API key are accepted and show which environment answered.
• get_account_config: Show the account configuration: Easypay client id, the account id and the payment methods enabled.
• list_single_payments: List single payments of the account, newest page first, with status, amount, method and creation time (customer details are not returned).
• get_single_payment: Get one single payment by id with its status, amount, currency, method type and the captures made against it.
• list_subscription_payments: List subscription payments with frequency, value, number of captures allowed and the payment method type (customer details are not returned).
• list_captures: List captures (money collected for payments) with status, amount, payment type and capture date, newest first.
• list_refunds: List refunds with status, amount and the capture they belong to (bank account and contact details are not returned).
• list_settlements: List settlements (bank transfers grouping paid-out transactions) with status, total amount and number of items.
• list_chargebacks: List chargebacks (reversals started by a customer's bank) with reason code, amount and the capture they reverse.
• list_ledger_entries: List reconciliation ledger entries (captures, refunds, fees, transfers) with type, amount and transfer batch.
• list_payment_links: List Pay By Link payment links with type, status, expiry and the public link URL (customer details are not returned).
• list_terminals: List the card payment terminals registered on the account with model, status and last transaction time.

BYOK key

You bring your own Easypay Easypay account id (https://docs.easypay.pt/docs/authentication). 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.prod.easypay.pt 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://docs.easypay.pt/openapi.md (the API this connector calls, with a BYOK key)

Live from the Easypay API (api.prod.easypay.pt) with a BYOK key; documentation: https://docs.easypay.pt/openapi.md. 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 Easypay. Easypay 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 Easypay account.

Built for: Worldwide. Languages: English.

Easypay (BYOK) — Privacy Policy

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

What Easypay (BYOK) is. Easypay (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Easypay data: Read your Easypay payment reports (single payments, subscriptions, captures, refunds, settlements, ledger, payment links) with your own account id and API key. You bring your own Easypay Easypay account id; the assistant sends it to us with each request.

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

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

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

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

Easypay (BYOK) — Terms of Service

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

1. The Service. Easypay (BYOK) provides: Read your Easypay payment reports (single payments, subscriptions, captures, refunds, settlements, ledger, payment links) with your own account id and 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 Easypay credentials and only access data you are allowed to access. Easypay's terms apply to your use of Easypay; 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 Easypay. Easypay 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 Easypay returns, lightly trimmed; it may be incomplete, delayed or changed by Easypay. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Easypay 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 Easypay'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; Easypay 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 Easypay 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 Easypay 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-easypay

Easypay (BYOK) support

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

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