Payment Gateway Thailand: An Evidence-Led Selection Guide

This guide is for international ecommerce, gaming, digital-content, software-as-a-service (SaaS), subscription and other low-ticket, high-frequency merchants selling to customers in Thailand. It uses dated primary sources and a field-by-field evidence method. It is not a guide to large-value business-to-business (B2B) collection or a consumer tutorial for opening a Thai payment app.

Disclosure: HaiPay publishes this guide and offers payment services. The framework applies to any provider. No provider is ranked, and a missing provider fact is not treated as a favorable answer. This is operational selection guidance, not legal, tax or investment advice.

What a Thailand payment gateway needs to support

A useful shortlist starts with the customer’s payment action, but it cannot end there. The provider also has to fit the merchant’s legal entity, transaction profile and operating model.

Use these six tests:

1. Shopper fit: Can the intended customer complete the correct card, bank-app, quick-response (QR) or wallet flow?
2. Merchant fit: Will the provider underwrite the actual contracting entity, business model and transaction profile?
3. Currency fit: Is Thai baht (THB) the presentment currency, the processing currency, the settlement currency—or only one of them?
4. Integration fit: Is there a current production route for the merchant’s checkout, not merely a logo or old documentation page?
5. Operational fit: Can the team identify payment states, handle refunds and disputes, and join orders to settlement reports?
6. Commercial fit: Does the written quote cover every fee, conversion point, tax treatment and settlement condition for the same route?

This evidence standard matters because the same public page can be accurate at a broad market level and still be insufficient for one merchant account.

Thailand’s card and local-payment landscape

For gateway selection, it is more useful to separate payment categories than to count logos.

• Cards are a distinct checkout and acquiring route. A provider’s Thailand card scope, foreign-issued card handling, authentication, failure diagnostics and settlement must be verified together.
• Bank-app and QR payments can involve a customer scanning a code in a mobile-banking application. That market experience does not identify which provider route, bank applications or merchant accounts are enabled.
• PromptPay is payment infrastructure in Thailand. It is not an ordinary wallet.
• TrueMoney is a wallet product with a different customer and merchant flow.

The Bank of Thailand describes PromptPay as payment-system infrastructure and describes Thai QR Payment separately as a service in which users scan a QR code through a mobile-banking application. TrueMoney’s own materials describe a wallet and merchant experience. Those primary sources establish the market categories. They do not establish a provider endpoint, route, callback, refund rule, settlement cycle or merchant eligibility.

Source: Bank of Thailand — PromptPay and TrueMoney — Merchant Wallet, verified 2026-09-02. Limitation: market-layer evidence only.

PromptPay and Thai QR Payment

The Bank of Thailand says PromptPay has operated since 2016 as payment-system infrastructure that expands transfer options through linked identifiers and bank accounts. Its page lists Thai QR Payment as a related service that lets a user scan a QR code through a mobile-banking application.

That relationship does not make the two terms interchangeable. PromptPay names the infrastructure. Thai QR Payment describes a QR payment experience within Thailand’s payment environment. A gateway may expose a QR-based checkout that connects to a particular route, but only the provider can document how its implementation behaves.

Before integrating a PromptPay route, ask for written answers to these route-specific questions:

• What does the shopper scan or open?
• Which customer account or application types are eligible?
• How is the amount supplied and confirmed?
• What event tells the merchant that an order is paid?
• What happens when the shopper abandons or the payment remains pending?
• Does the route allow cancellation or refund, and who initiates it?
• Which identifiers reach the settlement or reconciliation report?

Do not fill those blanks from a central-bank description. The central bank explains the market infrastructure, not a gateway’s implementation.

Source: Bank of Thailand — PromptPay, verified 2026-09-02. Limitation: no provider-specific technical or commercial behavior is inferred.

TrueMoney wallet payments

TrueMoney belongs in a separate lane. It is a wallet product, not another name for PromptPay and not a generic label for Thai QR.

TrueMoney’s merchant page describes its own direct merchant experiences. Those materials can help a merchant understand the wallet category, but they cannot be used as evidence for a gateway’s checkout, price, settlement, refund or activation terms. A wallet’s direct offer and a gateway-mediated wallet route may have different contracting parties, customer actions and operational rules.

For a TrueMoney route, verify:

• whether the customer remains in a wallet experience or moves through a redirect;
• what account, device and authentication conditions apply to the intended shopper;
• which payment states are available to the merchant;
• whether refunds or cancellations are supported for that route;
• how the transaction appears in reconciliation and settlement reporting;
• whether the merchant’s entity and account are approved for production.

The important comparison is therefore not “PromptPay versus TrueMoney” as logos. It is bank-linked/QR infrastructure versus a wallet flow, followed by a separate provider-route and merchant-activation check for each.

Source: TrueMoney — Merchant Wallet and TrueMoney Support — What is TrueMoney Wallet?, verified 2026-09-02. Limitation: direct TrueMoney terms are not gateway terms.

Market availability, provider evidence and merchant activation

Every payment-method claim should pass three layers in sequence.

For HaiPay, the current pricing page publicly lists Thailand coverage categories, and the current Thailand application programming interface (API) page includes PromptPay and TrueMoney rows. That is useful screening evidence. It does not, by itself, show that a particular contracting entity, merchant account, currency path or production route has been enabled.

The written activation answer should identify at least:

• the legal entity contracting with the merchant;
• the merchant entity and business model being approved;
• the exact payment method and production route;
• presentment and settlement currencies;
• the shopper action;
• payment-state and server-notification behavior;
• refund, cancellation and dispute handling;
• settlement convention and destination account;
• reconciliation output;
• the commercial quote and its effective period.

If one of these is missing, the correct result is not a softer marketing sentence. It is an open item to resolve before integration.

Source: Current pricing and Thailand API documentation, verified 2026-09-02. Limitation: the reviewed public API page contains cross-country example inconsistencies, so this guide does not publish its field mappings or limits.

Cards for Thailand-facing international merchants

International merchants should test card evidence as one joined route, not as a collection of unrelated promises.

HaiPay’s current pricing coverage table lists Visa and Mastercard in its Thailand row. A separate current generic card document places Thailand in an unsupported-region list. The reviewed public sources do not explain the scope difference. This guide therefore does not treat Thailand card activation as established from public pages alone.

That conflict is exactly why a card shortlist needs written answers:

Do not use a marketing table to answer these operational questions. Conversely, do not treat a generic restriction list as proof about every possible product configuration. Ask the product owner and engineering owner to reconcile the two public surfaces for the exact merchant route.

Source: Current pricing and Generic v2 card documentation, verified 2026-09-02. Limitation: the sources conflict on Thailand card scope; no activation claim is made.

Thai baht, fees, tax, foreign exchange and settlement

These are separate commercial and operational questions. A checkout can display THB without guaranteeing THB settlement. A public starting price can be real without being the price for PromptPay, TrueMoney or a particular Thailand entity.

What current public pricing establishes

The current public pricing page states that card pricing starts at 2.5% + US$0.30 per eligible transaction. It also states that local payment methods are available from 0.8%, priced by market. The local-method starting point is not a PromptPay or TrueMoney rate.

For both statements, the actual quote depends on the contracting entity, market, payment method, volume, transaction quality and risk profile, contract and final quote. Compare providers only after every quote uses the same merchant profile and representative order value.

Source: Current pricing, verified 2026-09-02. Limitation: public starting points are not a Thailand method-specific merchant quote.

Thailand Quote Decoder

Tax, conversion and settlement checks

• Tax: Thailand’s Revenue Department publishes general value-added tax (VAT) rules for the market. Those rules cannot tell a merchant whether a provider fee quote includes tax, excludes it or applies tax to a particular line. That treatment must come from the controlled merchant quote.
• Foreign exchange (FX): Ask where conversion occurs, which currency is presented, which currency settles, what reference is used, what markup applies and whether a separate outbound fee exists. Do not infer the provider’s applied FX from a public bank rate.
• Settlement: Ask the provider to define the counting unit, working-day execution, weekend and holiday behavior, destination account and controlling contract. A public schedule is context; the merchant’s written quote and contract are the operating evidence.

Source: Thailand Revenue Department — Value Added Tax and Payment settlement time, verified 2026-09-02. Limitation: market tax rules and a public settlement guide do not replace merchant-specific commercial terms.

• Related reading: For a broader route comparison, read Local Acquiring vs Cross-Border Acquiring. For current public starting points, use pricing and then request the controlling quote.

Merchant entity and underwriting requirements

There is no responsible universal answer to “Do I need a Thailand company?” without naming the provider, product and route. A provider may serve one foreign entity or business model and decline another. Public market availability cannot answer an underwriting question.

Before engineering begins, send the provider a compact eligibility brief:

• legal name, registration country and entity type;
• ultimate owners and available Know Your Business (KYB) documents;
• business model and customer journey;
• product or service sold;
• target customer countries;
• expected order value, volume and frequency;
• card/local-method mix;
• subscription, stored-value or digital-goods features, where relevant;
• expected refund and dispute profile;
• requested presentment and settlement currencies;
• settlement-account country, holder and currency;
• planned website/app, terms, refund policy and customer-support path.

Ask for the response in writing and ensure that it covers the same entity and use case later named in the quote. An approval for a different group company, currency or route is not interchangeable.

This is especially important for low-ticket, high-frequency models. The provider needs the real transaction pattern; the merchant needs to know whether pricing, risk controls, refund operations and reporting fit that pattern.

Checkout, status, refunds, disputes and reconciliation

The payment logo is the smallest part of day-to-day operations. A production decision should include a route runbook.

For the reviewed Thailand application programming interface (API) documentation, version and cross-country example inconsistencies make it inappropriate to reproduce codes, endpoints, callbacks, states or limits here. The safe next step is a versioned implementation confirmation from engineering, followed by an account-specific test plan.

Use International Payment Gateway for the broader provider-selection framework, Local Payment Methods for the provider’s category overview and Credit Card Acceptance for its general card product. None of those pages replaces a Thailand account decision.

Source: Thailand API documentation, verified 2026-09-02. Limitation: implementation details are deliberately omitted until the reviewed documentation conflict is resolved.

Thailand Payment-Method Evidence Matrix

This matrix is a screening asset, not an activation certificate. “Not established” means the reviewed public sources do not provide aligned evidence for a publication claim.

Matrix A — availability, route and shopper evidence

Source: Bank of Thailand — PromptPay, TrueMoney — Merchant Wallet, Current pricing, Thailand API documentation and Generic v2 card documentation, verified 2026-09-02.

Matrix B — merchant operations and commercial evidence

Source: Bank of Thailand — PromptPay, TrueMoney — Merchant Wallet, Current pricing, Thailand API documentation and Generic v2 card documentation, verified 2026-09-02.

Copy these fields into any provider comparison. A provider with fewer logos but complete, aligned evidence may be a safer operational fit than one with a larger unqualified list.

PromptPay vs TrueMoney Merchant Flow Boundary Map

The text version of the boundary map is intentionally simple:

• PromptPay / Thai QR lane: Shopper with an eligible mobile-banking experience → scans or follows the provider’s confirmed Thai QR flow → provider route reports a confirmed payment state → merchant reconciles the order.
• TrueMoney lane: Shopper with the relevant wallet experience → follows the provider’s confirmed wallet flow → provider route reports a confirmed payment state → merchant reconciles the order.

The shared boxes are only the boxes that must be verified: route activation, status, refund, settlement and reconciliation. The customer account, checkout behavior and method rules must remain in separate lanes.

Source: Bank of Thailand — PromptPay and TrueMoney — Merchant Wallet, verified 2026-09-02. Limitation: arrows after the market-level shopper action are verification requirements, not claims about the provider’s implementation.

Thailand Gateway Selection Flow

Run this flow in order:

1. Define the merchant case. Name the entity, business model, order profile, customer countries and settlement account.
2. Match the shopper flow. Decide whether cards, PromptPay, TrueMoney or another route is needed for the intended customer.
3. Verify the current provider listing. Save the dated page and its scope.
4. Confirm the production route. Obtain versioned product/engineering evidence and account-level activation.
5. Decode the quote and operations. Fill every field in the Quote Decoder and operations table.
6. Test and approve. Prove payment state, refund behavior and reconciliation with the intended route before launch.

If the evidence breaks at steps 3–6, stop. Obtain the missing route, eligibility, quote or operating term in writing. A public logo can start an evaluation; it cannot finish one.

Where HaiPay may fit—and what still needs written confirmation

The provider may belong on the shortlist for an international merchant evaluating Thailand because its current public pricing page lists Thailand categories and its current Thailand documentation lists PromptPay and TrueMoney. Those are reasons to start a scoped conversation, not reasons to assume activation.

The reviewed public record still leaves material questions:

• Thailand card scope is not aligned across current public surfaces.
• The Thailand API page contains cross-country examples, so mappings and implementation behavior need engineering confirmation.
• A broad bank-app category does not establish bank/application coverage, shopper flow or route eligibility.
• The merchant’s contracting entity and account approval are not public facts.
• Method-specific THB handling, settlement currency, refund behavior and reconciliation output are not established.
• Public pricing starting points are not a Thailand route quote.
• Tax treatment, FX basis and settlement terms need the controlling quote and contract.

To evaluate the platform, send your legal entity, business model, expected THB order profile, volume, customer countries and intended methods. Ask the provider to confirm in writing:

1. merchant and entity eligibility;
2. the exact PromptPay or TrueMoney production route;
3. card scope, if cards are required;
4. THB presentment and settlement currency;
5. checkout and payment-state behavior;
6. refunds, cancellation and disputes;
7. settlement convention and destination account;
8. reconciliation fields or a sample report;
9. the complete final quote, including tax and FX treatment.

Contact HaiPay only after the checklist is specific enough to produce a written, route-level answer. A useful answer identifies the entity, method, currency, operations and quote together.

Sources

1. Bank of Thailand. “PromptPay.” https://www.bot.or.th/en/financial-innovation/digital-finance/digital-payment/promptpay.html. Accessed 2026-09-02. Supports PromptPay as infrastructure, Thai QR as a QR-scanning service and the separation of e-wallet context.
2. TrueMoney. “Merchant Wallet.” https://www.truemoney.com/merchant-wallet/. Accessed 2026-09-02. Supports TrueMoney’s wallet/merchant-product category only.
3. TrueMoney Support. “What is TrueMoney Wallet?” https://support.truemoney.com/en/knowledge-base/what-is-truemoney-wallet/. Accessed 2026-09-02. Supports the wallet definition.
4. HaiPay. “Payment Gateway Pricing & Fees.” https://www.haipay.net/pricing. Accessed 2026-09-02. Supports current public starting prices, quote qualifiers and country-table observations; it does not prove account activation.
5. HaiPay Docs. “Thailand.” https://doc.haipay.net/docs/zh/api/version2/Thailand. Accessed 2026-09-02. Supports that a current public Thailand page lists PromptPay and TrueMoney; cross-country examples limit technical use.
6. HaiPay Docs. “International Credit Card (VISA/MASTER).” https://doc.haipay.net/docs/zh/api/version2/creditcard. Accessed 2026-09-02. Supports the public card-scope conflict only.
7. HaiPay. “Payment Settlement Time.” https://www.haipay.net/blog/payment-settlement-time. Accessed 2026-09-02. Supports the need to distinguish a counting convention from working-day execution and a merchant quote; no Thailand schedule is reproduced here.
8. Thailand Revenue Department. “Value Added Tax.” https://www.rd.go.th/english/6043.html. Accessed 2026-09-02. Supports general market tax context, not HaiPay quote treatment.