Thailand
Payments

Thailand combines PromptPay account payments, Thai QR, card acceptance and several wallet interfaces. A localised checkout should distinguish how the customer authorises payment from how the merchant receives verified funds and reconciles the order.

NITMX reported 82.21 million PromptPay registrations in December 2025. These registrations are not unique people. Keep that metric separate from monthly transaction counts, wallet accounts and card ownership when evaluating reach.

PromptPay — Thailand's Real-Time Rail

PromptPay links supported identifiers such as a mobile number or national ID to participating accounts. For a merchant, QR or API acceptance adds order-reference and confirmation requirements beyond a person-to-person transfer.

Cost comparison: a free consumer transfer is not a universal free merchant gateway. Opn’s Thailand merchant agreement treats PromptPay as a service whose fee is governed by the merchant schedule. Compare the actual percentage/fixed fee, taxes, refund handling and payout terms with the same card order profile.

Cross-border: Singapore’s PayNow linkage and regional QR arrangements are distinct products from domestic transfer. Establish participant, sender/recipient, currency, FX quote and limits for the corridor. Do not apply a domestic limit or merchant QR assumption to every international flow.

For checkout, verify the callback against the order amount and reference, handle duplicate notifications and define the treatment of an expired QR or a late payment. For payouts, test beneficiary validation and failed-transfer resolution.

Card Market

Visa, Mastercard, American Express and JCB acceptance depend on the acquirer and merchant contract. Domestic, foreign-issued and tourism-related traffic can have different costs and authentication paths.

Card instalment programmes depend on the issuer, merchant, amount and promotion. Confirm who funds an interest-free offer, which customers qualify and how refunds affect the instalment balance. Avoid promising a conversion increase or that every issuer offers the same plan.

Compare authentication, approval and disputes by the actual card cohort. An old 3DS1 deployment assumption or national fraud ranking is not a substitute for current processor capability.

E-Wallet Landscape

TrueMoney, LINE Pay and ShopeePay represent different consumer ecosystems and merchant products. K PLUS and SCB EASY are bank applications that can initiate account-based payments; they are not disjoint wallet market shares to add to PromptPay usage.

For each method, test onboarding eligibility, QR/app-switch flow, merchant confirmation, refunds and settlement reports. Wallet top-up can use several funding channels; do not assume every wallet payment or cash-in is universally routed through PromptPay.

Choose methods using the target customer segment and enabled merchant product, with a measured pilot where possible. A messaging-app user count or convenience-store footprint does not itself establish active payment reach.

BNPL

Separate bank/card instalments from a standalone BNPL or deferred-payment product. The credit provider, customer eligibility and merchant responsibilities can differ even when the checkout presentation looks similar.

Evaluate the enabled provider and legal entity, charges, order approval, cancellation, refunds and non-payment allocation. Do not infer that a regional brand, a card promotion or an announced service is available to every Thai merchant. Credit and payment permissions require separate product checks.

Crypto and Digital Assets

Digital-asset investment services and merchant payment acceptance are separate regulatory questions. A licensed exchange or sandbox announcement does not authorise every operator to offer crypto checkout.

For any proposed tourist-conversion or token service, establish the current permission, approved participants, eligible customers and fiat settlement route. Treat a pilot as bounded testing, not proof of a generally available payment method.

Regulatory Environment

The Payment Systems Act B.E. 2560 (2017) and BOT notifications distinguish designated payment systems from designated payment services, with licensing or registration depending on the activity. E-money, electronic receiving/transfer and system operation should not be described as interchangeable “PSP tiers”.

Map the entity, funds flow, safeguarding, governance and AML/CFT responsibilities before choosing direct authorisation or a local partner. Assess foreign-business and ownership requirements for that activity; a partner contract does not automatically cover everything the foreign entity does.

Identity tools such as NDID can support eligible onboarding flows. Establish the required customer checks and authorised data access for the particular product rather than assuming every integration can reuse bank KYC or that a sandbox guarantees a licence.

Fraud Landscape

Impersonation and social engineering can induce genuine customers to authorise fraudulent transfers. Verify beneficiary changes through a trusted channel, make recipient details clear and monitor unusual transaction patterns.

For QR acceptance, verify the displayed recipient and the server-side payment reference; physical QR replacement can redirect funds. For account access, assess phishing and SIM-swap exposure rather than relying on SMS OTP alone. These controls address different risks from ordinary card disputes.

Practical Notes for Operators

Acceptance candidates. Compare 2C2P, Opn and other enabled Thai bank or PSP products for PromptPay, wallets, cards and instalments. Establish the exact contracting entity, merchant eligibility and method support; a regional brand is not a coverage guarantee.

Settlement. Customer confirmation, interbank processing and merchant payout are separate events. Compare cutoffs, reserves, holidays, refunds and the reconciliation reference for the chosen contract.

Structure. Review the Payment Systems Act permission, foreign-business requirements and tax treatment for the actual service. Include bank onboarding and local operational support in the plan without presenting a fixed licensing or account-opening duration as guaranteed.

Integration. Test Thai-language app switches, QR expiration, duplicate callbacks, partial refunds and international-customer alternatives. Keep bank, wallet and merchant-reference identifiers distinct in support tooling.