Curated market guide
Thailand PSP routes to verify first
Which PSPs or bank routes should a merchant ask first for PromptPay, TrueMoney, local wallets, cards, and BNPL in Thailand?
Thai PSP / gateway shortlist
Use when you need cards, PromptPay, wallets, and local alternative methods through a PSP conversation.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Bank or acquiring route
Use when a bank relationship, direct acquiring, or corporate cash-management review is preferred.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
PromptPay and wallet route
Use when local QR/wallet adoption is a core checkout requirement and direct access can be verified.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Regional PSP route
Use when a regional PSP or cross-border specialist may fit a multi-market Southeast Asia rollout.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Documents to prepare
- Company registration and Thai entity or foreign onboarding question
- Beneficial-owner and signatory ID
- Website/app URL, product category, refund policy
- Bank account and settlement-currency requirements to verify
Questions to ask
- Can my current merchant entity onboard for this market, or is a local company required?
- Which local payment methods are actually enabled for my merchant category and transaction model?
- Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
- Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
- Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
If the official contact route is unclear
If public contact details are not specific enough, ask LocalPayMap to identify the right official form, PSP sales route, or local acquiring partner before committing engineering work.
- Which local payment methods are actually enabled for my merchant category and transaction model?
- Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
- Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
- Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
Route comparisons
How customers actually pay here
Thailand has strong transfer, QR, wallet, and card payment habits. PromptPay is a major phone-number, tax-ID, and QR payment route, but merchants should confirm provider-level payment confirmation, payout timing, refund handling, reconciliation, and support ownership before launch. Thai QR, TrueMoney, Rabbit LINE Pay, cards, and convenience-store routes can each fit different buyer segments, so the launch mix should be verified by provider and use case.
- PromptPay is a major Thailand transfer and QR route, but merchants should confirm provider-level payment confirmation, payout timing, refunds, reconciliation, and support ownership before relying on it.
- Ask providers which QR flows, wallet apps, cards, and foreign-user scenarios are actually supported.
- Verify TrueMoney availability, merchant access route, refunds, reconciliation, and support ownership.
- Verify Rabbit LINE Pay availability and whether it is direct, PSP-enabled, or platform-enabled.
- Keep card acceptance in scope when higher-ticket, cross-border, or tourist buyers matter.
Payment methods to prioritise first
Evaluate PromptPay, TrueMoney, cards, Rabbit LINE Pay, and convenience-store cash against your buyer segment and provider route. PromptPay may be important for local transfer or QR behavior, wallets may matter for stored-balance buyers, cards may matter for higher-ticket or cross-border buyers, and cash routes may matter for selected categories. Confirm provider support, pricing, payout timing, refunds, disputes, reconciliation, and support ownership before ranking the launch mix.
- Evaluate PromptPay early when local transfer or QR behavior matters, then verify provider support and costs.
- Evaluate TrueMoney when wallet behavior matters for the target buyer segment.
- Evaluate cards when higher-ticket, cross-border, or tourist buyers matter, and verify 3D Secure and dispute handling.
- Evaluate Rabbit LINE Pay if the audience and provider route justify it.
- Evaluate convenience-store cash only when buyer behavior and provider operations justify it.
How merchants usually connect
Thailand has multiple gateway, PSP, wallet, and regional provider routes. Merchants should verify which provider can enable the required methods for the exact entity, industry, checkout surface, and support model. Confirm how QR codes, wallets, cards, refunds, disputes, reconciliation, settlement currency, and support escalation work before choosing one provider or several.
- Ask PSP or gateway routes which Thailand methods are live for your merchant case.
- Ask regional PSP routes which Southeast Asia markets, methods, instalment flows, and enterprise support options are available.
- Ask whether TrueMoney access is direct, PSP-enabled, acquirer-enabled, or platform-enabled.
- Ask simple-checkout or payment-link providers which QR, wallet, card, refund, and reconciliation features are live.
Operating without a local company
Do not assume a foreign entity can use the same Thailand payment route as a local merchant. Some regional PSP routes may support cross-border contracting, while direct wallet, QR, acquiring, or local settlement routes may require Thailand-specific documents, tax information, banking, local representation, or licensed intermediaries. Confirm entity eligibility, contract model, payout currency, KYB, category review, refunds, disputes, and reconciliation in writing.
- Ask whether cross-border contracting is available for your entity, industry, methods, and payout currency.
- Ask whether PromptPay, wallet, or QR routes require local documents, bank accounts, tax data, or a local partner.
- Ask which collection and payout currencies are supported and when conversion happens.
What to ask a provider before you sign
Ask whether PromptPay is available to your merchant entity and whether QR codes are generated dynamically per order. Ask how payment confirmation reaches your system, how refunds work, and how reconciliation maps to order IDs. Ask for written per-method pricing, settlement currency, payout schedule, reserve policy, FX terms, card acquirer, 3D Secure support, dispute ownership, and support escalation.
- Confirm PromptPay is available to a foreign entity and generates per-order QR codes.
- Ask how PromptPay or QR pricing is calculated and whether provider markup, minimums, or payout fees apply.
- Get a written per-method price list plus settlement currency and FX spread.
- Ask how PromptPay refunds are handled, because they are not automatic.
Fees, settlement and FX
Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms. Confirm against the provider's official pricing page or a written quote before you go live. Do not assume one Thailand method is cheapest or fastest from public summaries. Ask for written quotes, payout calendars, reserve policy, FX terms, refund and dispute rules, and reconciliation exports for each route, then model the blend across your real payment mix.
- Public pricing is only a first filter, so confirm real numbers in a written quote.
- Verify PromptPay pricing, confirmation, payout, refund, and reconciliation terms in writing.
- Verify card pricing, 3D Secure, dispute exposure, refund handling, and reconciliation in writing.
- Include FX spread and payout fees when you model your blended cost.
Industry notes
Ecommerce teams should compare PromptPay, wallets, cards, and cash routes by buyer behavior and provider support. Digital goods, games, and media should verify small-ticket payment confirmation, fraud controls, refunds, and reconciliation. SaaS and subscriptions should confirm recurring support, mandate options, manual renewal flows, dunning, refunds, and fallback methods. B2B and services should confirm transfer references, invoice data, reconciliation exports, and support ownership. Tourism-facing businesses should verify card and wallet options for visitors.
- Ecommerce teams should compare PromptPay, wallets, cards, and cash routes by buyer fit and provider support.
- Digital goods and media should verify small-ticket transfer, wallet, card, refund, and fraud handling.
- SaaS should confirm recurring support, manual renewal routes, dunning, refunds, and fallback methods.
- Tourism-facing businesses should verify card and visitor wallet options alongside local QR routes.
Risks, compliance and common mistakes
The most common mistake is assuming one Thailand method fits every buyer segment. The second is treating PromptPay or QR as free without checking provider markup, minimums, payout fees, refund handling, and support ownership. Card fraud and disputes are live risks, so verify 3D Secure and evidence requirements. Payment and e-money activity is supervised by the Bank of Thailand, and data protection rules apply to buyer information. Do not ignore FX; baht conversion cost can compound quietly.
- Do not assume cards, QR, wallets, or cash routes are the default for every Thailand buyer segment.
- Ask how PromptPay or QR pricing, refunds, buyer details, and support ownership work before launch.
- Enable 3D Secure on cards, because fraud and disputes are real risks.
- Payment and e-money activity sits under Bank of Thailand supervision.
Questions merchants ask
Do I need a Thai company to accept payments in Thailand?
It depends on the provider route, merchant entity, product category, risk review, payout currency, and contract model. Some regional PSP routes may support foreign entities, while direct wallet, QR, acquiring, or local settlement routes may require Thailand-specific documents, bank accounts, tax data, local representation, or licensed intermediaries. Confirm the requirement in writing.
Which payment method should I add first in Thailand?
Evaluate PromptPay early when local transfer or QR behavior matters, then compare TrueMoney, cards, Rabbit LINE Pay, and convenience-store cash against your buyer segment. Confirm provider support, pricing, payment confirmation, payout timing, refunds, disputes, reconciliation, and support ownership before treating any method as the launch default.
How long does settlement take for PromptPay and card payments in Thailand?
Do not treat rail-level payment confirmation as the merchant payout calendar. Ask the provider when PromptPay, card, wallet, or cash transactions are confirmed, when funds become available, which payout cycle applies, and how pending, refunded, disputed, or failed payments appear in reconciliation.
What does it cost to accept payments in Thailand?
Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms. Confirm against the provider's official pricing page or a written quote before you go live, and include provider margin, FX spread and payout fees.
Can I get paid in USD or EUR instead of Thai baht?
Some provider routes may support foreign-currency payout or conversion, but supported currencies, rate lock, FX spread, payout fees, reserves, and settlement account requirements must be confirmed in writing.
What chargeback and refund risks should I plan for in Thailand?
Ask how PromptPay or QR refunds are handled, what buyer details are required, and who owns support. Cards carry dispute exposure, so verify 3D Secure, evidence requirements, chargeback workflow, and fees with the provider.
Can tourists pay with Thailand's QR codes?
Ask your provider which foreign wallets, cards, and QR scenarios are actually supported for visitors. If you serve tourists, keep a verified card or wallet fallback rather than relying on QR alone.