About HitPay MCP Server
HitPay MCP Server connects Claude Code to HitPay for payment operations and payment-integration guidance. It combines live account tools with skills and commands for scaffolding and testing integrations.
Key features
- 01Read account, balance, payment, and customer data
- 02Create payment requests, invoices, and QR codes
- 03Set up recurring billing and webhook events
- 04Scaffold and test HitPay integrations
- 05Look up market payment methods
Use cases
- 01Check payment and account status during development
- 02Create a checkout link or invoice
- 03Generate a QR payment page
- 04Test webhook handling
MCP support
The MCP server exposes HitPay account and payment tools to Claude Code, including read operations and selected creation operations. It does not expose refunds, deletions, transfers, or cancellations.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.hit-pay.com/claude mcp add --transport http com-hit-pay https://mcp.hit-pay.com/{"mcpServers":{"com-hit-pay":{"type":"http","url":"https://mcp.hit-pay.com/"}}}Open in Cursor{"servers":{"com-hit-pay":{"type":"http","url":"https://mcp.hit-pay.com/"}}}Open in VS Code{"mcpServers":{"com-hit-pay":{"type":"http","url":"https://mcp.hit-pay.com/"}}}{"mcpServers":{"com-hit-pay":{"serverUrl":"https://mcp.hit-pay.com/"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEHitPay Plugin for Claude Code
Zero-config SEA payment integration for Claude Code. Gives Claude deep knowledge of HitPay's payment gateway plus live API access — so when developers ask for payment integration, Claude scaffolds production-ready code with the right payment methods, webhook handling, and checkout flows.
What's Inside
| Layer | What It Does | Files |
|---|---|---|
| MCP Server | Live API access — create payments, check statuses, query account | .mcp.json |
| Skills | Teach Claude correct code patterns for HitPay integration | skills/ (5 skills) |
| Commands | Developer actions — scaffold, lookup, test, QR checkout | commands/ (4 commands) |
Installation
Via Marketplace (recommended)
/plugin marketplace add hit-pay/claude-code-plugin
/plugin install hitpay@hitpay-plugins
Local Development
git clone https://github.com/hit-pay/claude-code-plugin.git hitpay-plugin
claude --plugin-dir ./hitpay-plugin
Setup
Set your HitPay API credentials:
export HITPAY_API_KEY=your_api_key_here
export HITPAY_SALT=your_webhook_salt_here
Get these from your HitPay Dashboard under Settings > Payment Gateway > API Keys.
Skills
Skills are auto-invoked when Claude detects relevant context in your conversation.
| Skill | Triggers On | What It Teaches |
|---|---|---|
| payment-integration | "add HitPay", "payment checkout", "accept payments" | API routes, redirect/QR/selector flows, auth headers, test cards |
| webhook-handler | "webhook signature", "payment notification", "verify webhook" | HMAC-SHA256 verification, event types, IP allowlisting, idempotency |
| payment-methods | "methods in Malaysia", "which payment methods", "supported methods" | Country-to-method mapping, API values, currencies, unavailable methods |
| drop-in-ui | "embed payment form", "HitPay.js", "checkout popup" | HitPay.js script, init options, Next.js integration, event handling |
| qr-checkout | "QR checkout page", "QR payment page", "show QR code for PayNow" | Pre-rendered QR images, local HTML page, offline-capable, no CDN |
Commands
| Command | Description | Example |
|---|---|---|
/hitpay:init | Scaffold a complete integration | /hitpay:init nextjs sg,my |
/hitpay:methods | Look up payment methods by country | /hitpay:methods ph |
/hitpay:webhook-test | Generate test webhook payload + curl | /hitpay:webhook-test charge.created |
/hitpay:qr-checkout | Generate QR payment page with scannable codes | /hitpay:qr-checkout 100 sgd paynow,qris |
MCP Tools
When HITPAY_API_KEY is set, Claude can use these tools during development:
Read Operations
get_account_status— Check KYC and enabled providersget_balances— Current account balancesget_payment_request— Payment request detailslist_payment_requests— List payment requestslist_charges— List charges with filtersget_charge_detail— Charge detailslist_customers— List customersget_customer— Customer detailslist_invoices— List invoiceslist_subscription_plans— Subscription planslist_static_qrs— Static QR codesget_supported_qr_methods— Available QR methodsget_account_info— Account summary
Create Operations
create_payment_request— Create payment with checkout URLcreate_customer— Create customer recordcreate_invoice— Create invoicecreate_embedded_qr— Generate QR for payment collectioncreate_static_qr— Create permanent QR (POS)create_webhook_event— Register webhook URLcreate_recurring_billing— Set up subscription
Supported Markets
| Market | Currency | Key Methods |
|---|---|---|
| Singapore | SGD | PayNow, GrabPay, ShopeePay, Cards |
| Malaysia | MYR | GrabPay, ShopeePay, Touch 'n Go, FPX |
| Philippines | PHP | QR Ph, GCash, ShopeePay |
| Thailand | THB | PromptPay, TrueMoney |
| Vietnam | VND | VietQR, ZaloPay |
| Indonesia | IDR | QRIS |
| India | INR→SGD | UPI |
| Australia | AUD | PayTo |
| Cross-border | Auto FX | 9 borderless QR methods |
Security
This plugin follows a safe-by-default approach:
- Included: Read operations + payment creation (reversible/safe)
- Excluded from skills: Refunds, deletions, transfers, cancellations (destructive/financial operations)
- Webhook verification: All generated webhook handlers include HMAC-SHA256 signature checks
- API keys: Never exposed client-side in generated code
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.