Thailand, the Philippines or Malaysia: choose by the complete payment cycle

Choosing a payments market by a familiar wallet is like choosing a warehouse by its signboard. A lawful merchant needs the complete cycle: can the correct legal entity onboard, confirm a particular order, receive proceeds and refund funds without manually hunting for the recipient? Thailand, the Philippines and Malaysia give different answers.

This is not a universal “best P2P country” ranking. It compares three operational arrangements using official rules and specific interfaces. Technical availability does not establish permission to serve gambling or another restricted category. Verify applicable authorization before the pilot rather than after the first account restriction.

Thailand: choose transfer or merchant bill payment first

Bank of Thailand’s Thai QR guidance assigns Tag 29 to PromptPay transfers and Tag 30 to businesses registered with a biller or merchant ID. Merchant workflows need the recipient identifier and references, rather than merely a phone number. A personal proxy transfer should not be presented as a product with proven order-level accounting.

SCB documentation provides a concrete confirmation-recovery example: Tag 30 inquiry uses eventCode, transactionDate, billerId and reference1, with reference2 and amount serving their defined parameter roles. It describes this query when a customer reports successful payment but the partner has not received payment confirmation. That is more useful than “PromptPay is instant.”

For a Thai pilot, ask the provider to link one order to a specific reference1, show its callback and recover that payment through inquiry. Then verify the bank statement and approved refund process. A shared collection account supported only by screenshots cannot fairly be price-compared with a complete bill-payment product: the manual workload differs materially.

The Philippines: app, merchant QR and banking rail

GCash and Maya should not simply be contrasted with InstaPay as three equivalent wallets. InstaPay enables interoperable transfers between participating institutions; apps and merchant products occupy another layer. Distinguish personal transfers from merchant QR Ph payments. An app logo at checkout does not prove that every receipt follows identical reconciliation rules.

Maya Dynamic QRPh creates a paymentId; webhooks report results, with retrieval by ID or reference available when notification is missing. Its checked documentation describes a one-use code valid for an hour. Separate webhook guidance distinguishes receipt references: payment ID for maya-wallet and the issuer’s receiptNumber for qrph. These are Maya product characteristics, not rules for every Philippine QR.

The team’s test is to pay the same approved scenario from Maya and another participating app. Confirm that support can locate both transactions using information the buyer actually sees. When the buyer’s receipt and the merchant panel expose different numbers, show their mapping instead of asking the customer to “find the right receipt.”

Payouts: a universal PHP 50,000 ceiling is now misleading

BSP’s FAQ dated 29 July 2026 describes InstaPay for Business: B2C and B2B disbursements from business or corporate accounts, up to PHP 500,000 per transaction, subject to institution limits and participating-provider availability. This does not automatically raise every consumer transfer, wallet or merchant QR limit to PHP 500,000. BSP FAQ.

Ask separately about acceptance and payouts when evaluating the Philippines. A company may have a suitable checkout without the corresponding corporate disbursement product. Liquidity planning must use the approved outgoing channel, its availability, recipient limits and failed-credit investigation process.

Malaysia: DuitNow is a product family

DuitNow Transfer allows businesses to use a linked BRN identifier. DuitNow QR uses bank or e-wallet acquiring and separate merchant registration. DuitNow Pay has its own onboarding; the checked registration guide specifies local-entity support. Conditions for one product should not be generalized across everything branded DuitNow.

For QR, establish the acquirer, enterprise merchant ID and confirmation channel. PayNet’s public specification distinguishes ordinary success from a store-and-forward scenario following a recipient-side timeout. The customer screen can show success while the message is retained for further delivery. That is neither grounds for accusing the buyer of lying nor a reason to replace merchant-side confirmation with a screenshot.

The practical implication is that the provider must explain how its merchant API exposes this situation, when status is queried and what permits fulfilment. National infrastructure specifications do not always map directly to an aggregator’s simplified statuses. Obtain the mapping and a test incident rather than guessing what ACCEPTED means.

DuitNow Reversal supports refunds, but PayNet places their validation responsibility on the acquirer: RPP does not compare all refund parameters, including amount, against the original transaction. The servicing implementation must therefore explicitly control aggregate refunded amounts, original-payment linkage and duplicate requests. A national refund mechanism does not remove merchant controls.

Legal screening should eliminate unsuitable options

In the Philippines, GCash reports removing licensed gaming top-up and withdrawal services from 16 August 2025 in compliance with M-2025-029. The BSP memorandum itself concerns in-app gambling access and links; it should not be recast as a prohibition on every payment in the country. This is a specific customer-journey restriction that changes product availability even for licensed businesses.

Bank of Thailand separately describes preventing accounts and e-money from serving illegal merchants and sharing online-gambling information. PromptPay access provides no exemption. Likewise, Malaysian company registration and DuitNow access do not replace local permission for restricted activities. Exclude a market without an established legal basis, even when a test transaction technically succeeds.

Make the decision without an invented ranking

Build one comparable record per offer: contracting entity, accepted category, account type, order identifiers, authoritative confirmation, pay-in and pay-out limits, settlement schedule, refunds and exception support. Then run the same tests: ordinary payment, browser closure, missing callback, delayed confirmation and an approved refund.

The winner is not the market with the loudest method name. The suitable market gives your lawful enterprise the functions it needs and lets the team prove that every financial obligation is closed. Compare fees afterward, adding manual investigation cost and time during which proceeds remain unavailable. That turns country selection into an evidence-based operational decision.