HitPay
HitPay is a Singapore-headquartered all-in-one payments platform for small and medium businesses across Asia-Pacific, unifying online checkout, point of sale, and B2B billing. Its REST API creates hosted Payment Requests, runs Recurring Billing on saved cards, and issues Refunds, with first-class Southeast Asian local methods (PayNow, GrabPay, WeChat Pay, Alipay, ShopeePay, Atome) alongside cards. Requests authenticate with the X-BUSINESS-API-KEY header.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles HitPay the way a machine reads it — 34 machine-readable artifacts across 24 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — HitPay scores 68.4/100 (strong), with a separate agent-readiness read of 78/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile HitPay
Each block below is one kind of artifact we hold for HitPay. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 24
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
HitPay Account Status API
The Account Status API from HitPay — 1 operation(s) for account status.
HitPay Balances API
The Balances API from HitPay — 3 operation(s) for balances.
HitPay Beneficiaries API
The Beneficiaries API from HitPay — 3 operation(s) for beneficiaries.
HitPay Charge API
The Charge API from HitPay — 1 operation(s) for charge.
HitPay Charges API
The Charges API from HitPay — 4 operation(s) for charges.
HitPay Customers API
The Customers API from HitPay — 2 operation(s) for customers.
HitPay Invoices API
The Invoices API from HitPay — 2 operation(s) for invoices.
HitPay Notifications API
The Notifications API from HitPay — 1 operation(s) for notifications.
HitPay Orders API
The Orders API from HitPay — 2 operation(s) for orders.
HitPay Payment Requests API
The Payment Requests API from HitPay — 4 operation(s) for payment requests.
HitPay Product Category API
The Product Category API from HitPay — 1 operation(s) for product category.
HitPay Products API
The Products API from HitPay — 2 operation(s) for products.
HitPay Readers API
The Readers API from HitPay — 2 operation(s) for readers.
HitPay Recurring Billing API
The Recurring Billing API from HitPay — 5 operation(s) for recurring billing.
HitPay Refund API
The Refund API from HitPay — 2 operation(s) for refund.
HitPay Refunds API
Refund completed PayNow or card charges.
HitPay Remitters API
The Remitters API from HitPay — 2 operation(s) for remitters.
HitPay Staffs API
The Staffs API from HitPay — 2 operation(s) for staffs.
HitPay Static Qr API
The Static Qr API from HitPay — 2 operation(s) for static qr.
HitPay Subscription Plan API
The Subscription Plan API from HitPay — 2 operation(s) for subscription plan.
HitPay Subscription Plans API
Reusable recurring-billing plan templates.
HitPay Transfers API
The Transfers API from HitPay — 3 operation(s) for transfers.
HitPay Virtual Accounts API
The Virtual Accounts API from HitPay — 2 operation(s) for virtual accounts.
HitPay Webhook Events API
The Webhook Events API from HitPay — 2 operation(s) for webhook events.
Scroll within the panel for all 24 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
hitpay-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Hitpay Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Hitpay Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Hitpay Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Hitpay Events Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for HitPay — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/hitpay · machine-readable index on apis.io