# Payment Providers in Thailand: What Happens to QR When an Order Changes?

When comparing payment providers in Thailand, test what happens when an order changes after the customer receives its QR code. A cancelled purchase, a replacement amount and an old code on a customer's phone can create different payment outcomes. Your business needs to know which purchase was paid, through which channel, and what to do with an unexpected receipt. PromptPay and Thai QR make this a practical provider-selection question. The useful comparison goes beyond displaying a code: it follows the order reference through payment confirmation, cancellation and reconciliation, then assesses THB payouts separately.

## A numerical starting point for the provider comparison

We reviewed **14 unique historical payment offers** linked only to this country: 8 collection offers and 6 payout offers. They provide a structured starting point for comparing payment costs, access to funds and operational requirements. 75 additional offers linked to several countries are excluded from the country-only calculations below.

The source is the PayStar export dated 14 September 2026, supplied by payment gateways. We recomputed its aggregates, but did not independently verify its commercial statements. This is a historical sample, not a market survey, a count of PSPs or methods, or proof of active connections and current availability. Conditions can change weekly or more often. Independent country, currency and method associations do not establish every possible payment route. Direction counts and settlement-label charts cover all recorded currencies. Only the percentage comparison below is restricted to explicit THB fee records.

14 unique offers linked only to this GEO, across all recorded currencies; not methods, providers or live connections. [Download SVG](https://paystar.uk/thailand-payment-solutions/media/2026-10-08-v2/charts/offers-en-desktop-download.svg)

## What the recorded THB percentage components show

We calculate the arithmetic mean of explicit percentage components stated in THB, giving each comparable offer equal weight. A record qualifies only when its structured percentage matches one unambiguous percentage in the original fee description. Offers in another fee currency, missing percentages and ambiguous descriptions are excluded.

We also exclude bound or conditional percentages such as “from”, tiers and explicitly restricted customer categories. Exact nominal percentage components with fixed minimums or caps can remain in the sample; those minimums and caps still affect the final charge.

| Direction | n | Mean | Median | Range |
| --- | --- | --- | --- | --- |
| Collections | 8 | 4.09% | 4.25% | 2.7–5.5% |
| Payouts | 5 | 1.32% | 1.5% | 0.5–2% |

Explicit THB percentage components only. n is the comparable sample in each direction; missing fees are excluded, not zero. [Download SVG](https://paystar.uk/thailand-payment-solutions/media/2026-10-08-v2/charts/fees-en-desktop-download.svg)

**These are percentage components, not all-in payment prices.** Fixed charges, FX, tax, reserves, minimums and charges for refunds or other exceptions must be assessed separately. This sample is not weighted by payment volume, contains no measured conversion rate and cannot rank provider quality. Small or insufficiently independent groups are withheld.

### A hypothetical payment calculation

Take an illustrative payment of 1,000 THB; this is not a typical market ticket. Applying the rounded means shown above gives:

- Collections: 1,000 THB × 4.09% = **40.9 THB**.
- Payouts: 1,000 THB × 1.32% = **13.2 THB**.

Each line is a separate direction, not a combined service quote. The arithmetic shows only the percentage part. Ask for an actual quote at your ticket size, volume, business model and settlement currency before calculating net proceeds.

## When money becomes usable matters

Collection offers across all recorded currencies. T/D labels are recorded as supplied, without assuming calendar or business days. Other includes complex labels and pooled groups below 3 records. No guaranteed settlement time. [Download SVG](https://paystar.uk/thailand-payment-solutions/media/2026-10-08-v2/charts/timing-en-desktop-download.svg)

A successful payment notification and money available to your business are different events. Treat recorded settlement labels as questions for a provider: what starts the clock, which cut-off applies, are weekends counted, which account is credited, and can a reserve or review delay availability?

For payouts, agree prefunding, beneficiary validation, rejection handling and how returned funds appear in your balance. An incoming-payment settlement label does not prove payout completion time.

### A cash-buffer planning example

If a business must fund 100,000 THB of obligations per day, a one-day gap requires 100,000 THB; a three-day gap requires 300,000 THB. The additional buffer is 200,000 THB. This is a hypothetical constant-flow model, excluding fees, reserves and volatility, not an observed settlement promise.

## Start with the payment behind the Thai QR code

The Bank of Thailand describes PromptPay as payment infrastructure with several services, including corporate transfers, cross-bank bill payment and Thai QR Payment. A provider's “PromptPay supported” label therefore needs a more precise explanation of the proposed merchant service. [Bank of Thailand: PromptPay](https://www.bot.or.th/en/financial-innovation/digital-finance/digital-payment/promptpay.html)

The BOT's published Thai QR standard distinguishes PromptPay credit-transfer data from bill-payment data. The bill-payment structure includes a biller identifier and reference fields. It also distinguishes reusable static codes from dynamic codes generated for individual transactions. [BOT: Thai QR policy guideline and technical attachments](https://www.bot.or.th/content/dam/bot/fipcs/documents/FPG/2562/EngPDF/25620084.pdf)

For an online order, ask who creates the reference, how it identifies the purchase and where it appears in the provider's reports. A dynamic code can carry useful transaction context, but its appearance alone does not establish your cancellation policy or prove that the customer paid.

## Cancellation can depend on the payment channel

KASIKORNBANK's QR API page provides a specific example. It describes dynamic Thai QR and QR credit-card acceptance, with generated codes valid for ten minutes. Its cancellation explanation says a code supporting credit-card payments can still be paid through that channel until expiry after cancellation, while ThaiQR payment through the cancelled code is blocked. This is that product's published behaviour, not a universal rule for Thai providers. [KBank: QR API](https://www.kasikornbank.com/th/business/sme/financial-services/pages/qr-api.aspx)

That distinction changes the questions to ask. Does the cancellation response refer to the code, the order or a particular payment channel? What happens to a payment already in progress? Can staff identify a receipt against the old order after a replacement request has been issued?

Request the answers for the exact service you intend to use. If your proposed route accepts only ThaiQR, do not import card-channel behaviour into its specification. If it combines channels, insist that the demonstration covers each one.

## A hypothetical changed-order test

Suppose a customer receives a payment request for THB 1,200, then removes a THB 200 item. The merchant cancels the first request and creates a replacement for THB 1,000. This is a synthetic evaluation scenario, not a customer case or a claim about every Thai payment service.

Use distinct references for the original and replacement requests. Ask the candidate PSP to demonstrate the following outcomes in its test environment:

| Test | What your team should establish |
| --- | --- |
| Customer tries the original code | Whether payment is possible through each supported channel, and which reference is returned |
| THB 1,000 reaches the replacement request | How the revised order is matched and released for fulfilment |
| THB 1,200 reaches the original request | How the unexpected receipt is identified and reviewed |
| Both requests receive payment | How the THB 2,200 total is detected without fulfilling the order twice |

In the last case, the business has THB 1,200 beyond the revised purchase amount to resolve. Do not silently treat it as additional sales. Agree who investigates, what refund operation is available and how its outcome reconnects to the original receipt. Refund timing and eligibility require confirmation with the PSP.

## Confirm the receipt independently of the customer screen

KBank separately lists payment-notification callbacks, payment inquiry, void and settlement operations. Their separation is a useful reminder to request evidence for each stage; a QR-generation response is not a payment result. [KBank: QR API service functions](https://www.kasikornbank.com/th/business/sme/financial-services/pages/qr-api.aspx)

Ask how your system verifies a notification, retrieves a result when notification is delayed, and avoids recording the same receipt twice. Finance should be able to connect the order reference, received amount, transaction identifier and account entry. A customer's screenshot can help an investigation, but should not be the sole trigger for fulfilment.

Also distinguish cancelling a payment request from returning money already received. Ask for a report covering both successful payments and exceptions, with fees and the amount available to the merchant explained separately.

## THB payouts and overseas customers need separate checks

For business payouts, provide recipient types, payment purposes, amounts and frequency. Confirm supported beneficiary details, funding requirements, limits, approval controls and item-level completion evidence. A working collection demonstration does not establish those capabilities.

For international customers, the BOT describes cross-border QR purchases and cross-border funds transfers as separate use cases, with participating applications and institutions. Confirm the particular customer application and merchant acceptance arrangement. Overseas customer acceptance does not establish your company's onboarding eligibility or settlement to an overseas account. [BOT: cross-border payment linkages](https://www.bot.or.th/en/financial-innovation/digital-finance/digital-payment/cross-border-payment.html)

## The role of PayStar

PayStar provides information for comparing payment solutions and, where agreed, a technical layer for connecting and operating them. PayStar is not a bank or payment service provider and does not accept, hold or settle customer or business funds in its own name.

You select the payment provider and enter into a direct agreement with it. The provider processes payments and performs settlement under that agreement. Local eligibility, required authorisations and commercial terms must be confirmed for your company and use case. A method described in this article is not a promise that it is available through PayStar for your business.

Information about payment options is free. Payment processing and any agreed technical services have separate commercial terms.

## Official sources and research scope

- [Bank of Thailand: PromptPay](https://www.bot.or.th/en/financial-innovation/digital-finance/digital-payment/promptpay.html)
- [Bank of Thailand: Thai QR guideline](https://www.bot.or.th/content/dam/bot/fipcs/documents/FPG/2562/EngPDF/25620084.pdf)
- [KASIKORNBANK: QR API](https://www.kasikornbank.com/th/business/sme/financial-services/pages/qr-api.aspx)
- [Bank of Thailand: cross-border payment](https://www.bot.or.th/en/financial-innovation/digital-finance/digital-payment/cross-border-payment.html)

Research check: 8 October 2026. The export date remains 14 September 2026. Local scheme descriptions are context, not confirmation of a particular provider’s capabilities.