One portal, one API, the whole payout lifecycle
From deposit to payout to reconciliation, merchants work inside a single system instead of moving data between tools.
Payout service
Merchants pre-fund an account and pay overseas beneficiaries by bank account or card on demand.
- Payout currencies: Korean won (KRW), Chinese yuan (CNY), US dollar (USD), Malaysian ringgit (MYR); coverage keeps expanding
- Beneficiary fields are driven by the payout currency; the portal and the API share one set of field rules
- Payer (KYC) details are generated by the platform according to the rules and attached to each order; merchants do not fill them in
- Accounting is in USD; a real-time quote before submission shows exactly what will be debited
Merchant portal
Account overview
Available balance, frozen balance, credit line and the full ledger with filters and CSV export.
Deposits and withdrawals
Deposit requests carry a proof of transfer and are credited after two-person review; withdrawals pass review and disbursement separately.
Payouts and order queries
Currency-driven forms with live quotes; orders searchable by many criteria and exportable for reconciliation.
API access and security settings
Register apps, maintain IP allow-lists, read multi-language integration guides; bind two-factor authentication and recovery codes.
Transparent fees
Amount debited = accounting amount converted from the payout amount + platform fee (fixed part + percentage part).
- Fee rates are configured per merchant; the pre-submission quote shows the full breakdown and the reference exchange rate at that moment
- All fees are computed by the platform backend; the UI only displays them, so there is no gap between an estimate and the actual debit
- Per-order fees can be checked in order details and export files
Result confirmation
The platform uses a polling model: once an order reaches a final state, merchants read it from the portal or the query API.
- A successful submission means the platform accepted the order, not that funds have arrived; rely on the final state
- Orders in progress are never paid twice; do not resubmit
- Funds of failed orders are released back to the available balance after the platform confirms no payment was made
Why no push callbacks: pushes depend on the merchant server being reachable and cannot rule out "delivered but not processed" cases. A query API called by the merchant, answered from the platform ledger, is more reliable.