Skip to main content
To connect HitPay to Meta Muse, use the official HitPay connector in Muse Connectors (ask Muse to connect HitPay, or Settings → Connectors → HitPay, then authorize when prompted). If HitPay is not listed yet, use the Custom Connector backup with a Business API key and the paste prompt below. Once connected, you can create payment links (including PayNow and other Southeast Asia methods), invoices, products, subscription plans, and list or check charges — not refunds or payouts.
Recommended: Official HitPay in Muse Connectors (Meta-reviewed directory connector). Backup: Custom Connector with X-BUSINESS-API-KEY and the paste prompt — for private setups or when the directory listing is not visible yet. There is no public web URL for the Muse listing; you connect from inside Muse.

How to connect HitPay in Meta Muse

The official HitPay Meta Muse connector is listed in Muse’s Connectors directory. Meta reviews directory connectors; you do not need to paste a system prompt or manage API keys for this path.
1

Open Connectors in Muse

Either ask Muse something like “Connect HitPay”, or go to Settings → Connectors, find HitPay, and choose Connect.
2

Authorize HitPay

Follow the steps Muse shows to authorize HitPay (for example sign-in or approval prompts). Use a HitPay account with access to the business you want to manage.
3

Try an example ask

Once connected, ask Muse to create a payment link, list charges, or create an invoice — see What you can do with HitPay in Muse.
Connector availability can roll out by region or Muse client. If you do not see HitPay under Connectors, use the Custom Connector backup or check again after Meta’s rollout reaches your account.

What you can do with HitPay in Muse

After you connect the HitPay Muse connector, you can use natural language to:
  • Create payment links and checkout URLs (cards and local methods your account supports)
  • Create PayNow and other SEA payment requests — for example PayNow (paynow_online), FPX, QRIS, GCash, and GrabPay (see payment methods reference and online payments)
  • Create invoices, products, and subscription plans
  • List charges and check payment request status
Like other HitPay AI surfaces (MCP Server, AI developer tools), use Muse for creating payment requests, invoices, products, and subscription plans and reading charges and status — not for refunds, payouts, or destructive money moves. For refunds, transfers, team admin, or account settings, use the HitPay Dashboard.

Example asks

  • “Create a PayNow payment link for SGD 25 for a workshop deposit.”
  • “Create an invoice for SGD 150 due in 7 days for [email protected].”
  • “List my last 10 charges.”
  • “What’s the status of my latest payment request?”

Backup: HitPay Custom Connector in Muse

Use the HitPay Muse Custom Connector only when the official HitPay connector is not available or you need a private API-key setup. Muse calls the HitPay REST API using the OpenAPI spec. This path uses X-BUSINESS-API-KEY, not the Muse Connectors authorization flow.

Authentication and environments

Southeast Asia payment methods (via payment_methods on create calls) include PayNow (paynow_online), FPX, QRIS, GCash, GrabPay, cards, and other methods enabled on your account.
Store the API key only in Muse’s Secure Credentials Store when prompted. Never paste the key into chat or into the connector prompt text.

Merchant setup (4 steps)

1

Create an API key

In the HitPay Dashboard, open API Keys. Prefer sandbox first (sandbox dashboard).
2

Add the Custom Connector prompt

Paste the full prompt below into Muse as Custom Connector / system instructions.
3

Save credentials securely

When Muse asks for credentials, add your Business API key to Muse’s Secure Credentials Store only.
4

Try an example ask

Use one of the custom connector example asks. Switch the base URL to live when you are ready for production.
Start in sandbox until payment flows work as expected. See the sandbox guide for test credentials and behaviour.

Allowed operations (safe create + read)

The connector should only call these endpoints: Use the OpenAPI spec for request bodies and response fields. Prefer Content-Type: application/json.

Explicitly forbidden

Do not call or expose tools for:
  • RefundsPOST /v1/refund, GET /v1/refund/{refund_id}
  • Transfers / payouts/v1/transfers, /v1/transfers/*
  • Destructive DELETEs that move or cancel money (for example delete payment request, delete subscription plan, delete recurring billing)
  • Charge saved cardPOST /v1/charge/recurring-billing/{id}
  • Staff / account / settings/v1/staffs, /v1/account-status, location create/update/delete, and similar admin endpoints
If you ask Muse for a forbidden action, it should refuse briefly and direct you to the HitPay Dashboard.

Copy-paste: Muse Custom Connector prompt

Copy the entire block below into Muse:

Example asks (custom connector)

  • “Create a PayNow payment link for SGD 25, purpose: Workshop deposit.”
  • “Create an invoice for SGD 150 due in 7 days for customer [email protected].”
  • “List my last 10 charges.”
  • “What’s the status of payment request {id}?”
  • “Create a monthly subscription plan called Cafe Membership for SGD 29.90.”
  • “List products.”

FAQ

Use the official HitPay entry in Muse Connectors: ask Muse to connect HitPay, or open Settings → Connectors, select HitPay, and Connect, then complete the authorization steps Muse shows. If HitPay is not listed, follow the Custom Connector backup on this page.
No. HitPay is connected from inside Meta Muse via Connectors. There is no separate public web listing URL to share; availability may vary by region and Muse client.
Use the official HitPay connector in Muse Connectors whenever it appears — no paste prompt or API key required. Use the Custom Connector only as a backup when the directory listing is missing or you need a private API-key setup with the OpenAPI-driven prompt on this page.
Usually not on these paths. The official Muse connector uses Muse’s Connectors authorization flow when you connect. The Custom Connector backup uses X-BUSINESS-API-KEY, not OAuth. The separate HitPay MCP Server (https://mcp.hit-pay.com/) is for Muse Code and other MCP clients and uses OAuth via HitPay dashboard login — different from both Muse connector options above.
No — not as recommended behaviour. HitPay in Muse is limited to safe create + read (payment links, invoices, products, plans, listing charges). Use the HitPay Dashboard for refunds, transfers, payouts, and account admin.

Optional: Muse Code and Hosted MCP

For Muse Code or other MCP clients, you can use HitPay’s hosted MCP at https://mcp.hit-pay.com/ (OAuth via HitPay dashboard login). This is separate from the Muse Connectors directory path and from the Custom Connector API-key backup.
The hosted MCP already excludes refunds, payouts, and destructive money moves. See the MCP Server guide for setup and tool list.
Last modified on September 20, 2026