PawaPay (BYOK)

PawaPay (BYOK) — connector documentation

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

What PawaPay (BYOK) is for

PawaPay (BYOK) lets an AI assistant read your own PawaPay data through the PawaPay API with a key you supply (production API token). Read-only: 9 tools (get_wallet_balances, get_deposit_status, get_payout_status, get_refund_status, get_remittance_status, get_checkout_status, get_statement_status, get_provider_availability, get_active_configuration). 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.pawapay.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PawaPay. PawaPay 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:

• "What are my PawaPay wallet balances?"
• "Was PawaPay deposit 8917c345-4791-4285-a416-62f24b6982db completed?"
• "Did PawaPay payout 8917c345-4791-4285-a416-62f24b6982db go through?"
• "What is the status of PawaPay refund 8917c345-4791-4285-a416-62f24b6982db?"
• "Has PawaPay remittance 8917c345-4791-4285-a416-62f24b6982db completed?"
• "What is the state of PawaPay checkout afb57b93-7849-49aa-babb-4c3ccbfe3d79?"

What it does

• get_wallet_balances: List PawaPay wallet balances per country, currency and provider, optionally for one country.
• get_deposit_status: Get the status of one deposit (customer payment) by id: status, amount, currency, country, mobile money provider, your client reference and failure reason. The payer's phone number is not returned.
• get_payout_status: Get the status of one payout by id: status, amount, currency, country, provider, your client reference and failure reason. The recipient's phone number is not returned.
• get_refund_status: Get the status of one refund by id: status, amount, currency, country, provider and failure reason.
• get_remittance_status: Get the status of one remittance by id: status, amount, currency, country, provider and failure reason.
• get_checkout_status: Get the state of one hosted checkout by id: status, redirect URL, creation time and the deposits attempted through it.
• get_statement_status: Check a previously requested wallet statement by id: status, wallet, period and, when completed, a short-lived download link. Statements cannot be requested with this connector.
• get_provider_availability: Show whether mobile money providers are operational, delayed or closed per country and operation type, optionally for one country or operation.
• get_active_configuration: Show your account configuration: company name and the countries, providers, currencies and operation types enabled, optionally filtered by country or operation.

BYOK key

You bring your own PawaPay production API token (https://docs.pawapay.io/dashboard/other/system_conf/api_tokens). 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.pawapay.io 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.pawapay.io/v2/docs/welcome (the API this connector calls, with a BYOK key)

Live from the PawaPay API (api.pawapay.io) with a BYOK key; documentation: https://docs.pawapay.io/v2/docs/welcome. 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 PawaPay. PawaPay 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 PawaPay account.

Built for: Worldwide. Languages: English.

PawaPay (BYOK) — Privacy Policy

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

What PawaPay (BYOK) is. PawaPay (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own PawaPay data: Read your PawaPay mobile money account across Africa: wallet balances, deposit, payout, refund and remittance status, checkouts and provider availability with your own API token. You bring your own PawaPay production API token; the assistant sends it to us with each request.

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

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

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

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

PawaPay (BYOK) — Terms of Service

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

1. The Service. PawaPay (BYOK) provides: Read your PawaPay mobile money account across Africa: wallet balances, deposit, payout, refund and remittance status, checkouts and provider availability with your own API token. 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 PawaPay credentials and only access data you are allowed to access. PawaPay's terms apply to your use of PawaPay; 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 PawaPay. PawaPay 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 PawaPay returns, lightly trimmed; it may be incomplete, delayed or changed by PawaPay. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your PawaPay 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 PawaPay'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; PawaPay 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 PawaPay 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 PawaPay 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-pawapay

PawaPay (BYOK) support

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

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