The Multi-Currency Payment API (v2) gives you a single, unified API schema to accept and send payments across multiple currencies throughout APAC and beyond. Whether you’re collecting payments from customers in Vietnam, Malaysia, Japan, or Australia — or paying out to bank accounts, mobile money wallets, and QR-based networks — v2 handles the full lifecycle through one consistent interface.

​
What v2 covers

PayIn

Accept payments via bank transfer, e-wallet, QR code, mobile money, and more. Supports refunds, cancellations, and OTP-based mobile money flows.

Payout

Send funds to recipients across supported currencies. Includes scheduled payouts, branch code lookups, and QR-based bank account resolution.

Customers and Contacts

Create and manage customer records and contacts. Submit KYC documents for methods that require identity verification before transacting.

Balance

Query your available, incoming, outgoing, rolling reserve, and withdrawable balances across all currencies.

​
Supported currencies

The v2 API supports all currencies configured in your Hello Clever Merchant Dashboard, including AUD, VND, MYR, PHP, JPY, KRW, THB, BRL, NGN, KES, GHS, ZAR, and more. Contact support@helloclever.co to enable additional currencies.
GST should only be set to true for AU merchants processing AUD transactions. Set it to false for all other currencies.

​
Base URLs

​
Authentication

All v2 API requests require two header-based API keys issued from the Hello Clever Merchant Dashboard.
​
app-id
string
required
Your application identifier, registered and managed within Hello Clever. Required for all requests.
​
secret-key
string
required
Your client secret, used to authenticate server-side requests. Never expose this in client-side code.
Example request

​
Integration overview

A typical payin integration follows four steps:
1

Get payin methods

Call GET /v2/payins/payin_methods to retrieve the list of payment methods available for your configured currency.
2

Get required fields

Call GET /v2/payins/payin_method/params with the chosen method code to learn which fields you must collect from your customer.
3

Create the payin

Call POST /v2/payins with the method code, required fields, and customer details to initiate the payment.
4

Simulate (sandbox only)

In the sandbox environment, call POST /v2/payins/simulate to complete a pending payment for testing.
Payout flows follow the same pattern: get methods → get required fields → create payout. You only need to discover methods and required fields once per method — after that, you can reuse the same configuration for future transactions.

​
Resources

​
Contact and terms