Flexible APIs, diverse payment methods, and transparent fees to power global expansion.
Unified collection and payout to avoid high FX conversion costs and reduce exchange‑rate risks.
For businesses managing multi‑currency funds, the API-based treasury model is an ideal choice.
One API covers global credit card acquiring and global mass payouts.
Mobile App
Official Website
POS Terminal
Settle and pay directly in local currencies. Use your account balance for fund settlement to avoid unnecessary foreign‑exchange fees.
Transfer funds seamlessly between internal accounts. Move balance from Account A to Account B to enable shared liquidity across teams or business units.
Manage all acquiring funds through the HaiPay management plugin, with full visibility and traceability for every transaction.
Settle and pay directly in local currencies. Use your account balance for fund settlement to avoid unnecessary foreign‑exchange fees.
Transfer funds seamlessly between internal accounts. Move balance from Account A to Account B to enable shared liquidity across teams or business units.
Manage all acquiring funds through the HaiPay management plugin, with full visibility and traceability for every transaction.
A wide range of operational channels to support business growth.
Banking or fintech? See our payment solutions for financial institutions.
For endpoint and callback details, use the Common API reference. For implementation planning, read the payment API integration guide and payment gateway integration guide.
Standardized REST endpoints, 2048-bit SHA256WithRSA mutual signing, automated webhook retries, and an isolated UAT sandbox for end-to-end payment and payout integration.
Obtain currency-paired appId credentials in the Merchant Portal, configure IP whitelists and callback URLs, and upload your 2048-bit RSA public key.
Sort non-empty payload parameters alphabetically (excluding sign and sign_type), append your merchant secret key, sign with SHA256WithRSA, and POST over HTTPS (TLS 1.2/1.3).
Validate the platform signature on synchronous responses and asynchronous callbacks (status 2/3/4/5). Return HTTP 200 to acknowledge webhook delivery.
Simulate order state transitions and manual callbacks in the UAT environment before switching keys to production and pulling daily statement files.
All requests use HTTPS POST with UTF-8 application/json payloads and currency-scoped paths.
| Endpoint Path | API Operation | Integration Mode | Technical Behavior & Payload Notes |
|---|---|---|---|
| POST /{currency}/collect/apply | Collection Apply | Global Cashier / Local Cashier / Direct API / Card | Creates a pay-in order and synchronously returns redirect URLs, QR payloads, or direct payment parameters. |
| POST /{currency}/collect/query | Collection Query | Pay-in Status Inquiry | Queries real-time collection status when network timeouts or system codes (1003/1004) occur. |
| POST /{currency}/pay/apply | Disbursement Apply | Global Payout API | Initiates single or batch payouts to local bank accounts and e-wallets using currency-matched appId. |
| POST /{currency}/pay/query | Disbursement Query | Payout Status Inquiry | Retrieves payout execution status (status=2 success, status=3 failure) and upstream failure reasons. |
| POST /{currency}/refund/apply | Refund Apply | Card & Supported Channels | Submits full or partial refund requests against settled collection orders with signature verification. |
| POST /{currency}/account/ledger | Account Balance Inquiry | Multi-Currency Treasury | Returns total balance (bal), available balance (availableBal), frozen (frzBal), and unsettled funds (unSettleBal). |
| POST /common/document/download | Statement File Retrieval | Automated Reconciliation | Downloads daily statement links (type 20 collection, 15 payout, 40 details), generated after 13:00 next day. |
A dedicated integration mode for card payments and Apple Pay, allowing users to enter payment information directly on the merchant's checkout page for a smooth, one-click payment experience.
A payment gateway API is the set of secure endpoints your code calls to authorize, capture, refund and reconcile payments, without handling raw card data yourself. HaiPay's REST API covers both pay-ins and payouts in one integration, with SDKs, webhooks and a sandbox.
Typical flow: create sandbox credentials, install the SDK or call the REST endpoints, build the payment request and webhook handlers, run test transactions, then switch to production keys. Hosted checkout or payment links need little to no code if you want to launch faster.
The API itself is usually free — providers charge per transaction, not for access. Your real costs are transaction fees plus engineering time, which depends on the integration depth: payment links and hosted checkout are near zero-code, full API integration takes the most effort.
Yes. HaiPay exposes global collection and global payout capabilities through the same API and account, including internal balance transfers between them — so funds collected from customers can fund supplier or creator payouts without leaving the platform.
Transactions are collected in the shopper's currency, and balances can be held, converted and settled across multiple currencies from one account. The API and dashboard give a unified view for reconciliation across markets.
Yes. HaiPay provides a sandbox with test credentials, simulated payment states and webhook events, so you can verify the full payment and payout lifecycle before going live.
Tell us your markets, methods and volume. We map the payment stack and come back with a written quote.
Or compare our payment gateway pricing.
