hitpay-api

Endpoint

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

Tool quality observed · not scored

Unhinted state-changing: create_payment_request, update_payment_request, delete_payment_request, create_customer, create_invoice, create_embedded_qr, create_static_qr, update_static_qr …

From an anonymous initialize + tools/list capture measured 2026-10-20; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.

Tools

• create_payment_request — Create a new HitPay payment request. Returns a checkout URL where the customer can complete payment. Supports card, PayNow, GrabPay, FPX, GCash, QRIS, and 10+ other Southeast Asian payment methods. Set generate_qr: true for embedded QR codes — supported methods: paynow_online, shopee_pay, qris, doku_qris, ifpay_qris, wechat, wechat_pay, promptpay, opn_prompt_pay, truemoney, opn_true_money_qr, grabpay_direct, grabpay, grabpay_paylater, upi, upi_qr, gcash, gcash_qr, touch_n_go, atome, vietqr, vietqr_zalopay, zalopay.
• get_payment_request — Get the status and details of a payment request by its ID. Shows payment status, amount, checkout URL, and any completed payments.
• list_payment_requests — List payment requests with optional filters. Returns paginated results sorted by creation date.
• update_payment_request — Update a pending payment request. Only pending requests can be updated. You can change the amount, purpose, or customer details. Currency is required even if not changing it.
• delete_payment_request — Delete an incomplete/pending payment request. Only requests that have NOT been paid can be deleted. This action is permanent and cannot be undone.
• list_charges — List payment charges with optional date, status, and keyword filters. Shows transaction history with amounts, fees, payment methods, and customer details. Uses cursor-based pagination.
• get_charge_detail — Get detailed information about a specific charge by its ID. Shows full transaction details including fees, payment method, and customer info.
• get_balances — Get current account balances grouped by currency. Shows available, deposit, and pending amounts.
• get_account_status — Get account verification status and payment provider availability. Shows bank account status, KYC verification progress, and which payment methods are enabled.
• create_customer — Create a new customer record in HitPay. Customers can be associated with payment requests and invoices.
• list_customers — List customers with optional search. Returns customer names, emails, and contact info. Uses cursor-based pagination.
• get_customer — Get detailed information about a specific customer by ID.
• create_invoice — Create a new invoice. Optionally emails it to the customer. Returns the invoice URL for payment.
• list_invoices — List invoices with optional filters. Shows invoice amounts, statuses, and customer info. Uses cursor-based pagination.
• create_embedded_qr — Create a QR code to collect a payment. Recommended for all QR-based payment collection. Generates a one-time dynamic QR via a payment request — expires after payment. Also supports borderless (cross-border) QR — pass a foreign payment method (e.g., gcash_qr from SG) and the response includes borderless_fx with customer_pays, merchant_receives, fx_rate, and display_rate. Webhook event: payment_request.completed.
• create_static_qr — Create a permanent static QR code. Reusable physical QR where customers manually enter the amount. Best for in-store, donation drives, or multi-location use. Only supports: paynow_online, upi_qr, qrph_netbank. Webhook event: charge.created (includes static_qr.id and static_qr.reference for reconciliation). For one-time payment QR codes, use create_embedded_qr instead.
• list_static_qrs — List all static QR codes. Returns permanent, reusable QR codes created via create_static_qr.
• get_static_qr — Get full details of a static QR code by its ID. Returns name, QR value, payment method, amount, device_id, and location_id.
• update_static_qr — Update a static QR code. You can change the name, amount, currency, device_id, or location_id.
• delete_static_qr — Delete a static QR code permanently. This action cannot be undone.
• list_products — List products in the HitPay product catalog. Shows product names, prices, and stock levels.
• get_account_info — Get account balance summary. Shows available balance by currency.
• list_subscription_plans — List recurring billing / subscription plans. Shows plan names, amounts, billing cycles, and status.
• get_sales_summary — Get aggregated sales analytics for a time period. Shows total sales, fees, average transaction value by currency, top payment methods, and transaction status breakdown. Use period presets or explicit date range.
• estimate_transfer — Preview transfer fees and exchange rate before sending money. Provide either source_amount (how much to send from your account) or payment_amount (how much the beneficiary receives) — not both.
• create_transfer — Send money to a beneficiary. IMPORTANT: This initiates a real money transfer from your HitPay balance. Use estimate_transfer first to preview fees and exchange rates. You can reference a saved beneficiary by ID, or provide inline beneficiary details for a one-time transfer.
• get_transfer — Get the status and details of a transfer by ID. Use this to verify delivery after creating a transfer.
• list_transfers — List transfers with optional filters. Uses cursor-based pagination.
• create_beneficiary — Create a new transfer beneficiary (recipient) for sending money. The beneficiary can be reused across multiple transfers.
• get_beneficiary — Get details of a transfer beneficiary by ID. Account numbers are redacted for security.
• list_beneficiaries — List all transfer beneficiaries. Uses cursor-based pagination.
• create_refund — Issue a full or partial refund for a completed payment. IMPORTANT: Refunds are irreversible — confirm the charge ID and amount with the user before executing. The payment_id is the charge ID (not the payment request ID).
• create_recurring_billing — Create a new recurring billing subscription. Links a customer to a billing cycle. If plan_id is provided, the plan's amount/currency/cycle will be used. Otherwise, provide name, amount, currency, and cycle directly.
• cancel_recurring_billing — Cancel a recurring billing subscription. This stops all future charges. This action is permanent and cannot be undone.
• charge_saved_card — Charge a saved card on demand for an existing recurring billing subscription. The subscription must have a saved card from a previous payment.
• create_webhook_event — Register a webhook URL to receive event notifications. You can subscribe to specific event types like charge.created, transfer.paid, payment_request.completed, etc.
• delete_webhook_event — Delete a webhook event subscription. This stops all notifications to the webhook URL. This action is permanent.
• get_remitter — Get details of a remitter by ID. Remitters are the sending parties in incoming transfers.
• get_supported_qr_methods — Discover which QR payment methods are available for a given country or currency. Cross-references a static country→provider→method map against your live account status to show exactly which QR methods you can use with create_embedded_qr or create_static_qr. Set borderless=true to discover cross-border QR methods (e.g., SG merchant accepting GCash PHP payments).

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/hitpay-api"

curl "https://apis.io/api/v1/mcp?limit=25"