Rimtang - Phone-as-Till QR and Tap-to-Pay App with an Operations Console

Ops dashboard, transaction monitoring, transaction detail, settlement runs and settlement run detail with its batches, holds and exceptions.

Every QR confirmation matched, card host totals agree, no batch for a frozen merchant, held batches excluded. Approve and send must come from a different person from the one who started the run.

Only the ITMX credit confirmation marks a QR payment paid. One that arrives after expiry lands in Pending confirmation, to be matched by hand with the ITMX reference and a second approver.

20 merchants with shops, devices and bank accounts, payments by domestic and cross-border Thai QR, 5 card schemes and cash, 3 refunds and 10 settlement runs.

A Slip Is Not a Payment

A transfer slip on the payer's phone proves nothing. The app may show Paid only when Klong Thong receives the credit confirmation from National ITMX, so each charge needs a dynamic QR with its own reference, and a confirmation that arrives after the QR expires needs a person to match it.

Card Data on a Commercial Phone

Tap to pay on a merchant's own phone must follow the card schemes' programmes and PCI MPoC. Card data is read and encrypted inside a certified SoftPOS kernel, so Rimtang works with only the last four digits, approval codes and kernel and acquirer references.

Money Out Every Morning

Each night's run pays thousands of merchants from paid charges minus refunds, fees and 7% VAT on fees, plus adjustments such as lost chargebacks. Frozen merchants, risk holds and pending bank account changes must be held back, and failed payouts handled the next day.

Controls a Licence Expects

Under the Payment Systems Act the provider is supervised by the Bank of Thailand for risk and merchant due diligence. AML risk tiers become transaction limits, payer phone numbers fall under the PDPA, and every refund, hold, manual match and approval must record who, when and why.