Get started

HitPay for AI agents

HitPay provides payment processing, invoicing, and recurring billing for merchants, covering charges, orders, and payouts. Finance teams use it to track this without reconciling numbers by hand at month end. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect HitPaySee the 15 actions ↓
Finance and accountingAPI keyMCP + RESThitpayapp.com
AUDIT LOG · HITPAYPOLICY: acme-support
09:41:07 · claude · u_8f2read
hitpay.list_staff
List Staff✓ allowed · 212ms
09:41:08 · claude · u_8f2read
hitpay.list_orders
List Orders✓ allowed · 164ms
EVERY HITPAY CALL, ON THE RECORD
01 · USE CASES

What agents do in HitPay.

01

Check account balance

Check the merchant account's current balance before deciding on a payout timing.

02

Look up a payment request

Pull the status of a sent payment request to see if a customer has paid.

03

List recent invoices

List recent invoices to reconcile against bank deposits for the month.

02 · ACTIONS

15 HitPay actions, graded by risk.

Every HitPay action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

15

Look things up. Allowed by default.

  • hitpay.list_staff
    List Staff
  • hitpay.list_orders
    List Orders
  • hitpay.get_balances
    Get Balances
  • hitpay.get_location
    Get Location
  • hitpay.list_charges
    List Charges
  • hitpay.list_invoices
    List Invoices
  • hitpay.list_products
    List Products
  • hitpay.list_customers
    List Customers
  • hitpay.list_locations
    List Locations
  • hitpay.get_account_status
    Get Account Status
  • hitpay.get_payment_request
    Get Payment Request
  • hitpay.list_payment_requests
    List Payment Requests
  • hitpay.list_product_categories
    List Product Categories
  • hitpay.list_recurring_billings
    List Recurring Billings
  • hitpay.list_subscription_plans
    List Subscription Plans

write

0

Create and change things. Allow, or ask the user first.

  • No write actions.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

HitPay in three steps.

  1. 01Your users connect HitPayThey add their HitPay api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
  3. 03Any agent can actYour agent calls HitPay through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('hitpay', {
  read: 'allow',
  write: 'ask',        
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How HitPay connects.

Users add their HitPay api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same HitPay connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use HitPay from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More finance and accounting apps.

Stripe433 actions44API4 actionsAirwallex7 actionsAiwyn Tax10 actionsAltoviz67 actionsCoupa384 actionsZoho Books265 actionsMaxio177 actions
ALL FINANCE AND ACCOUNTING APPS →
07 · FAQ

HitPay and Arc0, answered.

Q01

Can I use HitPay with Claude, ChatGPT or Cursor?

Yes. Connect HitPay to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the HitPay actions you allow.

Q02

How do users connect HitPay?

Users add their HitPay api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which HitPay actions can my agent take?

15 in total: 15 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in HitPay?

Yes. Allow read actions and deny writes in the HitPay policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call HitPay too?

Yes. The same HitPay connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug HitPay into your agent.

Your users connect HitPay once, under your brand. Your agent gets 15 actions behind your policies, with every call on the record.

Connect HitPayBrowse all apps →

Free to build · MCP + REST · Audit log on every plan