Build with AI

Set up HitPay in Claude Code, Cursor, ChatGPT, or Windsurf in one step: Agent Skills, the Claude Code plugin, the HitPay CLI, the hosted MCP server at mcp.hit-pay.com, HitPay for Vercel, experimental WebMCP tools for browser agents, and LLM-ready docs.

HitPay ships tools that let AI assistants build payment integrations for you and work with your HitPay account. This page brings them together, with a one-step setup for each assistant.

Tool	What it does	Authentication	Works with
Agent Skills	Teaches your coding assistant how to integrate HitPay: payment requests, embedded QR, webhooks, refunds	API key (in your app’s env)	Claude Code, Cursor, GitHub Copilot, Windsurf
Claude Code plugin	28 live API tools, 5 auto-triggered skills, and 4 slash commands for building integrations	API key	Claude Code
HitPay CLI	Create payments, test webhooks locally with hitpay listen and hitpay trigger, and render QR codes in the terminal	API key	Any terminal, scripts, CI, or agent with shell access
MCP Server	Query sales, transactions, payouts, and balances, and create payment links and invoices, at https://mcp.hit-pay.com/	HitPay login (OAuth)	Claude, Claude Code, Codex, Cursor
HitPay for Vercel	Connects your HitPay account to Vercel projects from the Vercel Marketplace, so apps built with v0 or any AI coding tool can take payments without copying API keys	HitPay login (OAuth)	Vercel, v0, and any app deployed on Vercel
WebMCP (experimental)	Structured tools on HitPay’s online store and checkout page that a browser agent can call on behalf of the payer	None: acts as the payer who has the page open	Browser agents in browsers that support WebMCP
LLM-ready docs	llms.txt, llms-full.txt, and a Markdown version of every page	None	Any assistant that can read a URL

The developer tools (Agent Skills, the plugin, and the CLI) use your API key and default to the sandbox. The MCP Server connects an assistant to your live business data with your HitPay login. It can create payment links, invoices, products, and plans, but it can’t issue refunds, move money, or change settings.

One-step setup

Claude Code

Install the HitPay plugin from inside Claude Code:

/plugin marketplace add hit-pay/claude-code-plugin
/plugin install hitpay@hitpay-plugins

Then set HITPAY_API_KEY, HITPAY_SALT, and HITPAY_ENV=sandbox as described in the plugin guide, and ask: “Add PayNow checkout to my Next.js app.”

To connect Claude Code to your live business data as well, add the MCP Server:

claude mcp add --transport http hitpay https://mcp.hit-pay.com/

Run /mcp, select hitpay, and choose Authenticate.

Cursor

Install Agent Skills in your project:

npx skills add hit-pay/agent-skills

Then ask Cursor’s agent: “Add HitPay payments with webhook verification to this app.”

To query your live business data from Cursor, add the MCP Server to ~/.cursor/mcp.json (or .cursor/mcp.json in a project) and complete the sign-in when prompted:

{
  "mcpServers": {
    "hitpay": {
      "url": "https://mcp.hit-pay.com/"
    }
  }
}

ChatGPT

Start a chat with HitPay’s docs index:

Read https://docs.hitpayapp.com/llms.txt and use it to help me accept PayNow in my Node.js app.

ChatGPT can then open the Markdown version of any page it needs. You can also use Open in ChatGPT from the page menu at the top of any docs page.

The hosted MCP Server doesn’t support ChatGPT yet: web-based clients other than claude.ai aren’t currently allowlisted. If you use OpenAI’s Codex, connect it with codex mcp add hitpay --url https://mcp.hit-pay.com/.

Windsurf

Install Agent Skills in your project:

npx skills add hit-pay/agent-skills

Then ask Cascade: “Add a HitPay FPX checkout to my Laravel app with webhook signature verification.”

The MCP Server setup guide covers Claude, Claude Code, Codex, and Cursor. Other clients that support streamable HTTP with OAuth may also connect; see Other clients.

Test webhooks from your terminal

Whichever assistant you use, the HitPay CLI helps you test the code it writes. It needs Node.js 18 or later.

npm install -g @hit-pay/cli
hitpay login
hitpay listen --forward-to http://localhost:3000/api/webhooks/hitpay

hitpay listen tunnels HitPay webhooks to your local server, and hitpay trigger sends test events to it.

HitPay for Vercel

If you deploy on Vercel, HitPay for Vercel connects your HitPay account to your projects with a HitPay sign-in, so there are no API keys to copy. Install the HitPay integration from the Vercel Marketplace and choose your projects. Each project gets a HITPAY_ACCESS_TOKEN environment variable that can create and read payments. Redeploy to pick it up.

If you build with v0 or another AI coding tool, install the integration on the project the app deploys to rather than pasting a token into an environment variable form. You can also point your agent at this llms.txt file, which tells AI coding tools how to get a HitPay token instead of asking you for credentials.

The integration connects live HitPay accounts, so payments made while testing are real. To use scopes the integration doesn’t request, or to avoid storing a token in your project, use Vercel Connect.

WebMCP for browser agents

WebMCP is for agents that act on behalf of a payer in the browser, not for building integrations or reading your business data. WebMCP is a proposed web standard that lets a page register structured tools for an AI agent running in the user’s browser. HitPay registers these tools on two pages:

• HitPay online store: search products, read product details, manage the cart, and fill the store’s checkout form (search_products, get_product, add_to_cart, set_customer_details, and others). No online store tool submits payment.
• HitPay checkout page: read the checkout, list payment methods, fill the payer’s details, select a method, get the QR code while one is on screen, and pay by card (get_checkout_summary, list_payment_methods, fill_checkout_form, select_payment_method, get_payment_qr, submit_payment).

Tools change as the page changes, so agents should discover them at runtime instead of hard-coding names or schemas. submit_payment is marked with the consequentialHint annotation: get the user’s confirmation before calling it. HitPay also asks the payer to confirm the merchant, amount, and currency on the page. Values that come from the merchant carry untrustedContentHint and should be treated as data, not instructions.

WebMCP is an experimental browser capability based on a proposed web standard. Browser support, tool availability, and tool schemas can change, and HitPay can turn the tools off. Agents should fall back to standard browser automation when no tools are registered.

LLM-ready docs

Every page in these docs is available in formats that AI tools can read directly:

• llms.txt: an index of every page with a one-line summary, grouped by section
• llms-full.txt: the full text of every page in one file
• Markdown pages: add .md to any page URL, for example /apis/guide/sandbox.md
• OpenAPI spec: the full API definition

Prompts to try

Goal	Prompt
Embedded PayNow QR	”Add a PayNow QR checkout to my Next.js App Router app using HitPay, with a webhook route that verifies Hitpay-Signature.”
FPX in Laravel	”Create a HitPay payment request for FPX in MYR from a Laravel controller and redirect to checkout.”
Webhook handler	”Write a HitPay webhook handler that verifies the Hitpay-Signature header over the raw request body.”
Vercel checkout	”Add a HitPay checkout route to my Next.js app on Vercel that uses HITPAY_ACCESS_TOKEN from the HitPay integration.”
Business data (MCP)	“What were my total sales last month, and which payment methods did customers use most?”

FAQ

Which tool should I start with?

If you’re building an integration in Claude Code, start with the plugin. In Cursor, Copilot, or Windsurf, install Agent Skills. To ask questions about your own sales and payouts, connect the MCP Server. If your app runs on Vercel, install HitPay for Vercel. See the comparison in the AI tools overview.

Do the developer tools work with the sandbox?

Yes. The plugin and the CLI default to the sandbox, and Agent Skills generate code that reads the API URL from your environment. The MCP Server works with live accounts only.

Can an AI assistant issue refunds or payouts through HitPay?

Not through the MCP Server or the plugin: both exclude destructive operations by design. Code your assistant writes runs with whatever API key you give it, so review it before using a production key.

Where do I find my API key and webhook salt?

The API key is under Settings → API Keys in the dashboard. Each webhook endpoint you create under Developers → Webhook Endpoints has its own salt, used to verify Hitpay-Signature.