← Back to compare

Provider route comparison

2C2P vs PromptPay in Thailand

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

Thailand2C2PPromptPay

Merchant decision question

Which route should this merchant contact first for Thailand: 2C2P, PromptPay, or both in parallel based on entity fit, checkout needs, and operating workflow?

When 2C2P may fit

Choose 2C2P if a PSP-led route across cards, wallets, banking, and cash methods is needed and confirmed.

When PromptPay may fit

Choose PromptPay if Thai QR/bank-transfer behavior is the priority; confirm the bank or PSP route that enables merchant acceptance.

What to verify before integration

  • Confirm local entity, local bank account, KYB documents, supported merchant categories, and foreign merchant eligibility with each provider.
  • Ask for supported checkout flows, refunds, chargebacks, reconciliation exports, webhooks, plugins, and production support commitments.
  • Confirm settlement timing, payout currency, FX handling, reserves, tax invoices, and all contract fees in writing before launch.
  • Validate the exact payment methods needed for the market instead of assuming country coverage equals method coverage.

Contact and verification next steps

  • Open the Thailand country guide and PSP contact filter before contacting 2C2P or PromptPay.
  • Write down the merchant entity, industry, target customers, currencies, refund model, dispute owner, reconciliation needs, and support escalation path before outreach.
  • Ask official provider pages, forms, documentation, or written provider replies to confirm eligibility, pricing, settlement, reserves, refunds, disputes, and support ownership.
  • Keep a fallback provider or payment method in the shortlist until the first 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.

Public sources to verify

Review notes

  • Public brand visibility does not confirm merchant onboarding fit for every entity, industry, or channel.
  • Payment-method labels can hide different checkout, refund, dispute, reporting, and support workflows.
  • Commercial terms, limits, reserves, taxes, and payout details should be confirmed in writing with the provider.
  • Do not start engineering work until entity fit, required documents, test access, and fallback routes are clear.

Questions merchants ask

Should we choose 2C2P or PromptPay 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.