Skip to content
Digital Transformation

Payment gateways in Indonesia: how to choose for your store

  • Written by Andhika R Saputra
  • Published:
  • Updated
  • 5 min read
Illustration of a shop owner and developer discussing payment options for an online store
Contents
  1. Start with how customers pay
  2. Compare the payment products you need
  3. Calculate costs using your store's transaction patterns
  4. Distinguish payment status from money available for payout
  5. Test payment notifications and order updates
  6. Check onboarding and support after activation
  7. Choose from testing results and operational needs
  8. References

To choose a payment gateway in Indonesia, match payment methods to your customers, then check store integration, total costs and the payout process. Ask your developer to test order status changes before using the service. Your store and finance teams need a choice they can work with every day.

Problems often appear after a customer pays: the order still shows as pending, staff ask for payment evidence or transaction reports are difficult to reconcile with the bank account. Assess what happens after checkout as well as the payment selection screen.

Start with how customers pay

List the methods your customers need, such as virtual accounts, QRIS, digital wallets or cards. Check their availability for the merchant account you will use. Do not assume every method becomes active as soon as you register.

If your store serves business customers, discuss how the team will match payments to order or invoice numbers. Finance staff need to know which transactions customers have paid and how to investigate discrepancies. Define these requirements alongside the design of your B2B online store.

Compare the payment products you need

Midtrans and Xendit can be candidates for evaluation, but neither should become the default winner for every business. Choose a suitable integration approach, such as a provider-hosted payment page or an API integration. Ask your developer to explain what needs building and who will maintain it.

The official Xendit documentation separates options such as Payment Links and Subscriptions, alongside integration guidance. Refer to the documentation for the product you need when asking questions. Receiving payments and sending money out are separate requirements to discuss.

If you use WooCommerce, check that the integration works with your website version. An installable plugin is only the start. Have the developer test order statuses and failure scenarios before the website accepts customer transactions.

Calculate costs using your store's transaction patterns

Compare payment method charges, processing fees, tax and any relevant refund or dispute terms. Read the Midtrans pricing page and the Xendit pricing page when preparing your budget. Confirm the terms for your business type and account before accepting the service.

Use your own expected order values and payment method mix. Fixed fees and percentage fees affect different order values in different ways. Do not treat a single fee range as representative of all providers or payment methods.

Separate transaction charges from integration work and website maintenance. Ask for a proposal that distinguishes payments to the payment provider from the developer's work. Your team can then compare equivalent scopes.

Distinguish payment status from money available for payout

In the Midtrans transaction status documentation, pending means a payment is still awaiting processing, while expire means the payment period has ended. Your store team needs an agreed action for each status, including when to hold or continue order processing.

Do not assume that a transaction status means the money has reached your business bank account. Ask about payout schedules, the effect of operating days and how to investigate unreconciled transactions. Avoid promising one payout schedule for all methods without the provider's confirmation.

Test payment notifications and order updates

A payment gateway can send notifications to the store's server through webhooks. The Midtrans HTTP notification documentation explains server responses and retries in certain conditions. Ask your developer to test notification handling so the team does not rely only on the page customers see after paying.

Illustration of a developer and shop manager checking the order, payment and confirmation flow

Prepare scenarios for successful payments, incomplete payments and expired payment periods. Test repeated notifications too, so the store does not process an order twice. Record the results with test transaction references and the expected order statuses.

If you use refunds, test the process and its records for supported methods. Decide who can issue a refund and who reviews the reports. This work connects to the wider store setup, including your choice of WooCommerce or Shopify.

Check onboarding and support after activation

Request the registration document list and the requirements for activating payment methods. Do not assume all business categories follow the same process. Confirm the provider's legal entity and the authorisation relevant to its service, without assuming every product requires the same combination of licences.

Record how to report incidents and the information support needs, such as transaction references and the time of the problem. Make sure the team knows who investigates website integration faults and who contacts the payment provider. That division helps when the store's server works but order statuses do not match.

Choose from testing results and operational needs

Before deciding, collect written answers about active methods, costs, payouts and support limits. Choose a service the store and finance teams can use without a confusing checking process. Review the decision when transaction patterns or integration needs change.

To discuss your website and payment workflow, Book a Consultation. Prepare the platform you use and the checkout problems you want to resolve.

References

Frequently asked questions

Who should control the merchant account?

Use the business’s details and access arrangements that remain manageable when staff change. Assign roles according to responsibilities, and document account recovery and the contacts authorised to speak to the provider.

What should we prepare before changing payment gateways?

Record outstanding transactions, refund needs and integrations that depend on the old provider. Test the new service and agree a migration plan with your developer before retiring the old flow.

Do we need to store card data on our own website?

Do not add card data storage to your website without understanding the need and its security obligations. Ask your developer to explain the integration flow and which data the payment provider handles.

Topics:Online StoresEcommerceMidtransPayment GatewaysQRIS

Share

Written by

Andhika R Saputra

Founder, Webzoo ID