← Back to compare

Local method versus global PSP route

PromptPay vs global card PSP route in Thailand: Merchant Route Checklist

PromptPay vs Global card PSP route in Thailand: compare merchant fit, customer payment behavior, eligibility questions, operational checks, refunds, disputes, and provider route validation.

ThailandPromptPayGlobal card PSP route

Merchant decision question

Should a Thailand merchant include PromptPay alongside a global card PSP route after onboarding path, QR flow, refunds, reconciliation, and support ownership are verified?

When PromptPay may fit

Verify PromptPay first when the merchant needs a local customer payment route in Thailand and can identify a PSP, acquirer, bank, platform, or aggregator that can enable it for the exact entity, industry, and checkout flow.

When Global card PSP route may fit

Verify the global card PSP route when the merchant needs cross-border contracting, card or wallet acceptance, multi-market reporting, and a fallback route while local method eligibility is still being confirmed.

What to verify before integration

  • Confirm whether PromptPay access is through a PSP, bank, acquirer, aggregator, or platform route.
  • Confirm whether the global PSP route supports the merchant's Thailand payment-method and category needs.
  • Confirm refund, dispute, reconciliation, reserve, payout currency, and production support ownership.
  • Confirm whether PromptPay is available directly or only through a PSP, acquirer, bank, wallet operator, platform, or partner route for the merchant case.
  • Confirm whether Global card PSP route is available directly or only through a PSP, acquirer, bank, wallet operator, platform, or partner route for the merchant case.
  • Confirm entity eligibility, restricted categories, onboarding documents, payout currency, reserves, refund handling, disputes, reconciliation, and support ownership in writing.

Contact and verification next steps

  • Open the Thailand country guide and contact filters before asking providers about PromptPay or Global card PSP route.
  • Prepare merchant entity country, product category, customer geography, currencies, expected volume, average order value, refund model, and support requirements before outreach.
  • Ask official provider pages, forms, developer documentation, or written replies to confirm eligibility, pricing, settlement, reserves, refunds, disputes, and reconciliation.
  • Keep a fallback method or provider route until the preferred route is confirmed in writing.

Commercial verification note

Use official provider pages or a written provider response to confirm commercial terms, payout handling, refunds, disputes, account setup, and support ownership for the exact merchant case.

Do not treat country coverage or brand support as proof that a specific merchant entity, industry, payout currency, or operational workflow is available.

Review notes

  • Do not claim PromptPay is mandatory or available for every merchant.
  • Do not state fees, approval likelihood, local entity requirements, or payout timing.
  • Do not rank PromptPay against global PSP routes.
  • Do not treat this comparison as a ranking, recommendation, approval signal, pricing quote, settlement promise, or proof of merchant eligibility.

Questions merchants ask

Should we choose PromptPay or Global card PSP route in Thailand?

Use the comparison to prepare verification questions. The answer depends on customer behavior, merchant entity, industry, provider route, risk review, commercial terms, payout handling, refunds, disputes, and support.

Does this page confirm merchant eligibility?

No. Merchant eligibility must be confirmed with the PSP, acquirer, wallet operator, bank, scheme, or platform route before integration.

Are commercial terms confirmed here?

No. Confirm commercial terms, payout handling, refund handling, dispute ownership, and support commitments with the provider before launch.