← Back to compare

PSP comparison

Xendit vs Midtrans in Indonesia: Merchant Shortlist Review

Xendit vs Midtrans in Indonesia: compare merchant fit, customer payment behavior, eligibility questions, operational checks, refunds, disputes, and provider route validation.

IndonesiaXenditMidtrans

Merchant decision question

Which Indonesia PSP conversation best matches our checkout channels, payment mix, and operating ownership?

When Xendit may fit

Choose Xendit if the merchant wants to evaluate an API-led PSP route across cards, wallets, virtual accounts, and local methods.

When Midtrans may fit

Choose Midtrans if the merchant wants to evaluate a locally established gateway route for Indonesia checkout and reconciliation.

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 Indonesia country guide and PSP contact filter before contacting Xendit or Midtrans.
  • 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

  • Do not assume equal coverage across wallets, bank transfers, cards, and retail flows.
  • Provider fit can depend on category, ticket size, and channel mix.
  • Rates, payout timing, and account requirements need official confirmation.
  • Technical documentation should be checked against the exact integration path.

Questions merchants ask

Should we choose Xendit or Midtrans in Indonesia?

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.