Merchant Accounts for Indonesian Companies: Documents, Underwriting and Settlement Checks

Confirm what the merchant account will do

Define the product you need: card acceptance, virtual-account collection, QRIS, e-wallet payments or a combination. Record who sells to the customer, who fulfils the order, and whose bank account receives the proceeds. Here, underwriting means the provider or acquirer's merchant-acceptance and risk review. It is a business decision alongside identity checks.

A payment-provider account is distinct from the company's deposit account at a bank. Xendit's Indonesian gateway terms define an account as a gateway identifier. Opening or approving that identifier does not itself open the bank account used for company funds.

Keep the roles equally clear with the regulator. Bank Indonesia Regulation 10 of 2025 , effective March 31, 2026, requires a party acting as a payment service provider (PJP) to obtain Bank Indonesia authorisation. Using a provider to collect payment for your own goods or services is a different task from operating that service. Collecting for unrelated sellers, controlling their balances or designing a wallet should trigger a separate activity assessment before merchant onboarding is treated as the solution.

If the seller's legal identity is still unsettled, complete the underlying company formation in Indonesia workstream before presenting a different seller name to the provider. The company applying, the commercial seller and the proposed payout beneficiary must form a coherent evidence trail.

Build a file that answers the provider's questions

Use the chosen provider's Indonesian corporate checklist. For example, Xendit's Indonesian document guidance lists owner/director identification and tax identification, the corporate tax ID, NIB or its stated alternatives, the latest director-appointment deed and associated ministry document, plus activity-specific licences where required. Its February 26, 2026 guidance allows a newly established company without changes to submit its establishment documents. These are Xendit's requirements, not a universal list for every provider.

Build the submission around what each file proves . The following cross-checks are preparation controls; the provider decides whether the resulting evidence is sufficient.

Keep a submission index showing file version, relevant name or identifier, responsible person and unresolved discrepancy. Full, readable documents are more useful than cropped extracts. For a Xendit application, assembling Xendit's Indonesian corporate evidence should follow the Indonesian entity route and the current dashboard request.

A foreign shareholder does not turn an Indonesian foreign investment company (PT PMA) application into an application by its overseas parent. Identify the actual contracting entity first. Where a foreign director cannot supply an identification format shown in the local checklist, obtain the provider's written instruction for that person's documents; do not invent a substitute or borrow another director's identity.

Make the business model reviewable

Make the commercial story specific enough to review: what is sold, who buys it, when the customer pays, and when delivery occurs. A reviewer cannot assess a vague description such as “online services” against a checkout selling annual subscriptions or collecting deposits for future delivery. State those features directly and provide supporting material that reflects the proposed live business.

Xendit's current legal terms permit ongoing requests about shareholders, beneficial owners, business activities, source of funds, counterparties and transaction purpose. They also allow delay or withholding where information is incomplete or inconsistent. Treat a follow-up request as a defined question to answer; initial account acceptance does not end the review process.

• Describe the customer journey with a real product page, pricing, payment point and fulfilment evidence that correspond to the application.
• Explain advance payments, subscriptions, cross-border customers or a material gap between collection and delivery. Label forecasts as forecasts and explain their basis.
• Show who handles cancellations, refunds and customer complaints. Identify the records that connect a disputed payment to the customer's order.
• Respond to each discrepancy with the corrected fact, its evidence and the affected application field. Keep the provider's response alongside the submitted version.

These are recommended preparation steps, not a claim that every provider requires the same website, trading history or revenue level. Never describe the business as lower risk by omitting a product or fund-flow feature. If the provider declines the proposed model, ask whether a narrower, accurately described scope is acceptable; uploading a different set of names does not repair that decision.

Document acceptance, service availability and receipt of funds therefore need separate evidence. An unresolved restriction belongs at the point where it interrupts the route.

Agree the settlement route before accepting payments

Agree where settlement first occurs and what happens next. Under Xendit's collection and withdrawal service terms , the aggregator route credits an available balance, while the switcher route pays the nominated account directly. Withdrawal can be a further step. Document the route for each payment method; a dashboard balance and a bank credit should have different labels in the cash forecast.

The Indonesia territory terms take precedence where they conflict with other parts of Xendit's regional agreement. Save the agreement and product schedule accepted by your company, including applicable local amendments. A generic help-centre timing should not replace your account's actual configuration.

Confirm the beneficiary early. Xendit's Indonesian withdrawal-account guidance requires a corporate account name consistent with the registered business and describes evidence for close matches or a former company name. An unrelated account name is not an acceptable workaround for a local corporate merchant. Check spelling, bank name and account number against bank-issued evidence before the first payout.

• Specify the timing trigger: customer payment, successful processing, settlement to the provider balance, withdrawal instruction or bank receipt. Record working-day rules and cut-off treatment.
• Identify the deductions: transaction charges, applicable taxes, withdrawal costs, refunds, disputes and any reserve. Ask how each appears in the transaction and payout exports.
• Record conditions for holds and reserves, including the notice, withheld amount, release condition and person handling further evidence. Do not assume every merchant has a reserve.
• Confirm the first-payout prerequisites, automatic or manual withdrawal setting, supported destination and escalation route for a failed or delayed transfer.

Provider timing is conditional. Midtrans' withdrawal guidance says that, for funds passing through Midtrans, transactions become eligible for a withdrawal request after successful settlement for at least three working days; first withdrawal also requires completed registration documents and a successful transaction. This is a Midtrans condition, not a universal time to bank credit.

Xendit's legal terms permit holds and reserves and provide for notice of a reserve's amount and duration. Available cash after deductions is the useful planning figure. Obtain the terms actually applied to your account before committing receipts to payroll or suppliers; do not substitute an assumed reserve percentage or an advertised instant-payment label.

Verify one complete payment-to-bank trail

Use an operational acceptance record for each channel you plan to offer. The following is a recommended company control, not a provider certification. Separate a sandbox result from a permitted genuine live transaction, and retain the references that connect the customer order to the bank statement.

1. Confirm account and service status. Capture the merchant acceptance result, the specific channel's live availability, approved sales scope and unresolved restrictions. Xendit's legal terms distinguish system registration from activation and onboarding for certain optional services.
2. Record the customer payment. Match the genuine order, amount, currency, channel reference and payment status. Check the provider's authoritative transaction record before marking an order paid; a customer screenshot alone is insufficient evidence for your acceptance record.
3. Trace the amount available. Match the gross transaction to the amount cleared under the agreed route. Record each actual deduction or hold against its reference; investigate an unexplained difference instead of treating it as a fee.
4. Trace the payout. Save the withdrawal instruction or automatic payout reference, amount, date and reported result. If the route settles directly to the bank, record that route and its bank reference.
5. Confirm the bank credit. Locate the actual company-bank entry, match it to the payout reference and reconcile the net amount. Mark the operational route accepted only when the differences are explained and the intended beneficiary received the funds.

Retain an exception log with the affected reference, expected result, actual result, evidence requested and owner. A failed customer payment belongs with payment status; money awaiting availability belongs with settlement conditions; a completed withdrawal missing at the bank requires the transfer evidence and bank trace. This separation makes the support request precise.

Do not repeat a payment or payout merely because a status screen is unclear. First establish the status of the original instruction and use the provider's documented recovery process. Include the transaction or payout reference in the support case and keep the response with the reconciliation record.

Confirm how refunds and disputes will be recorded before launch. Xendit's service terms require trading and delivery evidence and allow refund or chargeback deductions. Assign one owner to preserve the order, fulfilment and payment records, and another to check that the corresponding ledger and bank entries reconcile. The same sale must remain traceable after a later adjustment.

Release the merchant account only with recorded exceptions

Release the intended payment methods when the seller identity, accepted business model, live-channel status and payout record agree. Give each remaining exception an owner and a launch consequence. A resolved document upload is evidence of a repair; the provider's acceptance and the payment-to-bank result establish different outcomes.

Hold the affected launch if authority is unresolved, the provider has not accepted the actual sales model, or the beneficiary cannot be verified. Once the route works, keep the accepted scope and cash conditions under review when products, ownership, transaction patterns or delivery commitments change. The practical decision is whether your company can explain and evidence the complete route today.