Payment Gateway Platform for every channel and every ledger

Most businesses don’t have a payment problem. They have five: a checkout on the website, a QR code at the counter, a pay link in the invoice email, a gateway dashboard nobody reconciles, and an ERP that finds out about all of it at month end. The Payment Gateway Platform puts one payment layer in the middle. Every channel calls the same API, every gateway reports into the same place, and every confirmed payment lands in accounting and tax with no one retyping it.

One Unified Payment API for every channel

Your website, mobile app, bill-payment page, and back-office tools all call one internal API to create a payment, check its status, or issue a refund. Behind it, the platform talks to the gateway or bank you’ve chosen. Change gateways, add a second one for cards, or route PromptPay through a bank directly, and none of the channels need to change.

Which payment methods does it support?

• PromptPay and Thai QR for bills, deposits, and counter payments
• Credit and debit cards, including 3-D Secure and installments where the gateway offers them
• Mobile banking and bank transfer, matched back to the invoice that asked for them
• Pay links attached to an e-Invoice, including partial payments against credit terms

From paid to booked: ERP sync and e-Tax

A confirmed payment is the start of the paperwork, not the end. The platform issues the e-Tax Invoice or e-Receipt in the Revenue Department format the moment a payment is confirmed, posts the receipt to accounts receivable in the ERP, and records refunds and settlements the same way. It connects to SAP, Microsoft Dynamics, Oracle NetSuite, Odoo, or a custom ERP through the integration patterns your finance team already trusts.

Daily reconciliation instead of month-end archaeology

Every morning the platform matches yesterday’s gateway settlements against orders and bank statements, net of fees, and flags what doesn’t line up: a payment with no order, an order paid twice, a settlement short by a fee nobody expected. Finance gets a short exception list instead of a spreadsheet.

Reconciliation should be a report you read, not a job someone does.

PCI-scoped tokenisation

Card numbers are captured inside the gateway’s hosted fields or SDK and come back as tokens. Your servers never store or see a full card number, which keeps your PCI DSS scope to the smallest self-assessment the gateway supports. Webhooks are signature-verified and idempotent, so a retried notification never marks an order paid twice.

HarmonyX deploys the platform alongside your existing systems, whether that’s a new website or a legacy ERP. To scope the integration itself, see our Payment Gateway & e-Payment Integration service.