aba-payway-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYWAY_ENV | No | Either 'sandbox' or 'production'. Defaults to 'sandbox'. | sandbox |
| PAYWAY_API_KEY | Yes | HMAC secret ("public_key" in PayWay's docs). Required. | |
| PAYWAY_MERCHANT_ID | Yes | Your merchant key from ABA Bank. Required. | |
| PAYWAY_RSA_PUBLIC_KEY | No | RSA public key PEM for refund and payment-link tools. Optional but required for those tools. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| payway_purchaseC | Create a PayWay Purchase transaction (redirect/QR/deeplink checkout). Returns checkout HTML/JSON depending on payment_option. |
| payway_check_transactionB | Check the status of a transaction created within the last 7 days. |
| payway_get_transaction_detailsB | Get full details/history of any past transaction (any age). Limited to 10 requests/minute by PayWay. |
| payway_get_transaction_listA | List transactions filtered by date range (max 3 days), amount range, and status. Max 50 req/min. |
| payway_get_transactions_by_merchant_refA | Retrieve up to the last 50 transactions matching a merchant_ref (tag 62.01 on KHQR). Max 10 req/min. |
| payway_close_transactionA | Cancel/close a transaction (e.g. flash sale, hotel booking, ticket). Sets status to CANCELLED, no callback sent. |
| payway_refundA | Issue a full or partial refund within 30 days of a COMPLETED transaction. Requires PAYWAY_RSA_PUBLIC_KEY. |
| payway_exchange_rateA | Fetch ABA Bank's current buy/sell exchange rates (same as ababank.com/en/forex-exchange). |
| payway_generate_qrA | Generate a KHQR / WeChat / Alipay QR code (string + PNG image + ABA deeplink) for a payment, without a hosted checkout page. |
| payway_create_payment_linkC | Create a shareable PayWay payment link. Requires PAYWAY_RSA_PUBLIC_KEY. |
| payway_get_payment_link_detailsA | Get details/status of a previously created payment link. Requires PAYWAY_RSA_PUBLIC_KEY. |
| payway_docsA | Fetch ABA PayWay developer documentation as LLM-friendly markdown. Call with no arguments to get the index (llms.txt) listing every doc URL, then pass one of those URLs/paths to read a specific page. No credentials required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes, but there is minor overlap between check_transaction and get_transaction_details, and between create_payment_link and purchase. Descriptions clarify these differences sufficiently.
All tools share the 'payway_' prefix and use snake_case, but the naming pattern is not uniform: 'docs', 'purchase', and 'exchange_rate' deviate from the verb_noun structure. Still, the overall style is consistent and predictable.
12 tools is well-scoped for a payment gateway MCP, covering QR generation, payment links, transactions, refunds, exchange rates, and documentation without being overwhelming or thin.
The surface covers core payment operations (create, check, list, refund, close) and additional utilities like exchange rates and docs. Minor gaps exist (e.g., no payment link update/delete, no webhook management), but these are not critical for typical workflows.