Without the plugin
4+ hours of setup
Read 47 pages of API documentation
Copy-paste webhook examples from Stack Overflow
Manually look up payment method codes per country
Debug HMAC signature verification for hours
Test with trial and error
Repeat the whole cycle for every new market
⏱
Estimated time: 4+ hours
With the plugin
Production-ready in minutes
Tell Claude: "Add GCash and PayNow to my Next.js checkout"
Claude scaffolds API routes, webhook handlers, and payment method selection
Webhook HMAC-SHA256 verification is built in automatically
Test with
/hitpay:webhook-test
Production-ready code, reviewed and committed
Works for any market — just change your prompt
⚡
Estimated time: Under 5 minutes
Claude connects to HitPay's API in real time. Create payment requests, check balances, manage customers, and register webhooks — all from your conversation. No separate API client needed. When Claude creates a payment request, it hits the real API — sandbox by default, production when you're ready.
Five built-in skills activate automatically when you ask about payments, webhooks, payment methods, drop-in UI, or QR checkout. Claude generates production-ready code with proper HMAC-SHA256 verification, error handling, and method selection — without you reading a single doc page.
Four slash commands to jumpstart your integration. /hitpay:init scaffolds a complete checkout. /hitpay:methods looks up payment methods by country. /hitpay:webhook-test generates test payloads. /hitpay:qr-checkout creates scannable QR payment pages.
01
What is it
02
Why use it
03
How it compares
Install the plugin
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
# From the Claude Code marketplace
/plugin marketplace add hit-pay/claude-code-plugin
# Or from the plugin registry
/plugin install hitpay@hitpay-plugins
Set your API key
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
export HITPAY_API_KEY =your_api_key_here
export HITPAY_SALT =your_webhook_salt_here
export HITPAY_ENV =sandbox # default — safe to test
Get your API key and Webhook Salt from HitPay Dashboard → Settings → Payment Gateway → API Keys. Don't have an account? Sign up free — no setup fees, no monthly fees, pay only when you process payments.
Start building
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
# Tell Claude what you need in plain English
"Add PayNow checkout to my Next.js app"
# Or scaffold instantly with a command
/hitpay:init nextjs sg,my
That's it. Claude handles API routes, webhook handlers, success pages, and environment variables.
Refunds, deletions, transfers, and cancellations are intentionally left out of the plugin's capabilities. These financially impactful operations stay in human hands.
Every webhook handler Claude generates includes HMAC-SHA256 signature verification. Not optional, not a TODO comment — built in and enforced by the skill.
All generated code keeps API keys as server-side environment variables. Claude never puts credentials in client-side code — by design, not by convention.
The plugin defaults to sandbox mode. You explicitly set when you're ready to go live — never the other way around.
Payments processed
Business partners
Payment methods
Markets
Compliant
Is the HitPay Claude Code plugin free?
Yes. The plugin is open source under the MIT license. HitPay's standard per-transaction pricing applies when you process real payments — there are no additional fees for the plugin itself.
Does it work with sandbox or test mode?
Yes. The plugin defaults to sandbox mode. Set HITPAY_ENV=sandbox (the default) to use test credentials, then switch to production when you're ready to go live.
What frameworks does it support?
The plugin generates code for any JavaScript/TypeScript framework. The skills are optimised for Next.js (App Router), but Claude adapts the patterns to Express, Fastify, Remix, SvelteKit, or vanilla Node.js based on your project.
Can Claude access my live payment data?
Only if you set your production API key. The plugin uses a safe-by-default model — it can read payment data and create new payment requests, but it cannot issue refunds, delete records, or initiate transfers. Destructive operations are excluded by design.
What's the difference between this and the HitPay API docs?
The API docs are a reference. This plugin makes Claude an expert on HitPay's API so you never need to read the docs at all. Claude knows the correct payment method codes, webhook verification patterns, and country-specific quirks — and generates working code directly in your project.
How do I get my API key?
Sign up for a free HitPay account at dashboard.hit-pay.com/register. Go to Settings → Payment Gateway → API Keys. Copy your API Key and Webhook Salt — that's everything the plugin needs.
Is my API key secure?
Your API key is stored locally as an environment variable and passed to the MCP server via HTTPS headers. The MCP server proxies requests to HitPay's API and does not store your key or any payment data. All generated code keeps API keys server-side only — never exposed to the browser.
Why HitPay instead of a global gateway for SEA?
HitPay is purpose-built for Southeast Asian payment integration. While global gateways offer broad coverage, HitPay provides native support for local methods — PayNow, FPX, GCash, PromptPay, QRIS — the primary ways consumers pay in these markets. The Claude Code plugin encodes this regional expertise directly into your AI assistant.
Still have questions?
Contact our team.
