Curated market guide
Indonesia PSP routes to verify first
Which PSPs or direct method routes should a merchant ask first for QRIS, e-wallets, bank transfer, and cards in Indonesia?
Indonesian PSP / gateway shortlist
Use when you need QRIS, wallets, bank transfer, and cards through one local integration conversation.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Switch, bank, or network route
Use when your local partner or enterprise setup requires direct network, switch, or bank-led integration review.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Wallet and QR route
Use when mobile-wallet conversion is central and you can verify whether direct merchant onboarding is available.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Regional PSP route
Use when a regional PSP or open-finance provider may simplify Indonesia plus Southeast Asia expansion, subject to local onboarding checks.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, or sponsor merchant is required.
- Confirm KYB documents, tax registrations, signatory documents, website/app review requirements, and restricted-industry treatment.
- Confirm supported payment methods, checkout flow, refund/dispute handling, reconciliation fields, FX, payout currency, reserves, and production support.
Documents to prepare
- Company registration and Indonesian entity question
- Beneficial-owner and signatory ID
- Website/app URL and product category
- Local tax and bank account requirements to verify
- Refund, dispute, and customer-support policy
Questions to ask
- Can my current merchant entity onboard for this market, or is a local company required?
- Which local payment methods are actually enabled for my merchant category and transaction model?
- Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
- Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
- Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
If the official contact route is unclear
If public contact details are not specific enough, ask LocalPayMap to identify the right official form, PSP sales route, or local acquiring partner before committing engineering work.
- Which local payment methods are actually enabled for my merchant category and transaction model?
- Which documents are required for KYB, website/app review, tax review, and beneficial-owner checks?
- Which checkout flows, APIs, plugins, hosted pages, refunds, disputes, webhooks, and reconciliation files are supported?
- Which payout currencies, FX handling, reserves, chargeback process, taxes, and support SLAs should be confirmed before launch?
Route comparisons
Merchant questions before choosing a provider
Use these questions to separate customer payment fit from PSP onboarding, settlement, pricing, support, refunds, disputes, and compliance details.
How customers may pay locally
Expect e-wallets, virtual accounts, bank transfers, QRIS, convenience-store or cash-linked options, and cards to matter by segment. The optimal mix depends on buyer demographics and average order value.
Local entity and settlement checks
Ask whether onboarding requires an Indonesian entity, local bank account, or local sponsor. Settlement currency, payout timing, reserves, tax handling, and FX should be documented before build work starts.
PSP selection notes
Compare local PSPs, regional aggregators, QRIS and virtual-account specialists, acquiring gateways, and global PSPs with Indonesia support. Make sure the provider can support the exact payment flows your product needs.
Documents and KYB checks
Prepare registration documents, shareholder and director information, product and website details, settlement bank information, compliance policies, expected transaction volume, and customer service contact.
Integration checklist
Confirm these items before committing engineering time or signing provider terms.
Merchant checklist before integration
Use these questions before committing engineering time or signing a provider contract.
- Map wallet, QRIS, virtual account, bank transfer, cash, and card needs.
- Confirm local entity and bank-account requirements.
- Ask about IDR settlement, FX, reserves, and payout timing.
- Verify webhook, sandbox, hosted checkout, payment link, and API support.
- Check refund, failed-payment, expiry, and reconciliation behaviour.
- Get official pricing or a written quote before estimating margin.
How customers actually pay here
Indonesia checkout can involve wallets, QRIS, bank virtual accounts, bank transfer, convenience-store cash routes, and cards. No single method should be treated as automatically available or sufficient. Confirm QRIS scenario support, participating apps, virtual-account behavior, wallet coverage, cash expiry, card acquiring, refunds, disputes, settlement currency, payout timing, and reconciliation with the provider.
- Evaluate GoPay, OVO, DANA, ShopeePay, and other wallets by buyer segment and provider coverage.
- QRIS can simplify QR acceptance where the provider supports the exact online or offline scenario you need.
- Bank virtual accounts can matter for ecommerce, but confirmation and expiry behavior must be tested.
- Convenience-store cash routes need unpaid-order, expiry, and reconciliation handling.
- Cards can matter in selected categories, subject to acquiring approval and pricing.
Questions merchants ask
Why is a PSP route important in Indonesia?
Because the customer-facing methods are fragmented across wallets, QRIS, bank transfers, virtual accounts, cash-linked routes, and cards; a PSP or aggregator can combine them into a workable merchant integration.
Should Indonesia checkout include QRIS?
QRIS can matter for many local payment flows, but merchants should confirm whether their provider supports the exact online or offline scenario they need.
Can a foreign company onboard directly?
It depends on the provider and business model. Some routes support cross-border merchants, while local routes may require Indonesian entity or banking details.
What technical details should be checked?
Check sandbox access, API documentation, webhook events, payment expiry, callback reliability, refund support, and reconciliation exports.
Are Indonesia payment fees fixed from public pages?
No. Public pricing is only for first-pass screening; final pricing and settlement terms must be confirmed with the provider.
Do I need an Indonesian company to accept payments in Indonesia?
It depends on provider route, merchant entity, product category, local sponsor model, settlement currency, KYC, risk review, and any registration requirements. Some regional or cross-border routes may support selected foreign entities, while local acquiring or QRIS arrangements may require Indonesia-specific setup. Ask specifically which methods are available to your entity before integration.
Which payment method should I add first in Indonesia?
Evaluate QRIS early when QR or wallet-style checkout matters, then compare bank virtual accounts, cards, direct wallets, and cash routes against buyer segment and provider eligibility. Confirm supported apps, confirmation flow, pricing, payout timing, refunds, disputes, reconciliation, and support ownership before treating any method as the launch default.
How long does settlement take for QRIS and bank transfers in Indonesia?
Do not treat payment confirmation as the payout calendar. Ask the provider to confirm QRIS, wallet, virtual-account, cash-route, and card confirmation timing, payout schedule, settlement currency, FX, reserves, failed-payout handling, refunds, disputes, expiry, and reconciliation files in writing.