Indonesia payment troubleshooting.
From a pending order to a useful investigation.

QRIS, VA or wallet payment made, but not credited

First establish what “not credited” means: the provider order is still pending, the merchant did not receive a callback, or the merchant application did not update the customer balance. These are different parts of the payment flow.

Collect the merchant order number, provider reference where available, payment method, amount, currency and approximate payment time. Review the documented status-query process and callback logs. If the result remains unclear, send the relevant references and a redacted successful receipt when requested by PAYJN support.

A receipt is investigation evidence, not permission to override the documented final status. Keep the order pending until it is resolved through the agreed verification process.

If your application receives the same payment callback more than once, use the duplicate payment webhook guide to check whether the order was credited once and test how your integration handles retries.

Why is the collection success rate lower?

Begin with the measurement. Does “success rate” mean confirmed successful payments divided by all created orders, or a different denominator? Unpaid and abandoned checkout orders can lower the first measure without demonstrating a channel fault.

PAYJN can coordinate a route-status review and provider investigation where needed. Investigate the evidence before attributing the change to a bank, upstream route or customer behavior. Do not describe every unsuccessful order as a processing failure.

Does an unavailable LinkAja route mean the bank code is wrong?

Not necessarily. Check the current approved method code and required format, but also confirm whether the wallet payout route is enabled and available for your merchant. A method-name or channel-unavailable message by itself does not identify the root cause.

Use the current approved documentation rather than guessing an alternative code. Contact support with the intended method, time, order reference and sanitized response if configuration or availability needs verification.

Invalid field format and no channel available: what should I check?

Review the exact message and the point where the request failed. An invalid field may concern a required value, code or format. No channel available requires checking the requested method, merchant configuration and current route status. More than one check may be necessary.

Do not assume bank maintenance from the wording alone. Share a redacted request outline and the exact response with support through the agreed channel; never include API secrets or a complete customer banking history in a public chat.

Payout successful, but the recipient says nothing arrived

Match the order amount, destination and timestamp to the final recorded payout result. Ask support to review the provider reference or transfer evidence where available, and identify whether a bank or wallet investigation is needed.

Further evidence and expected timing depend on the case and provider requirements. Do not apply a universal 24-hour waiting rule to every route or assume a full bank-statement video is always necessary. If recipient-side evidence is requested, agree the minimum relevant period and the secure submission method.

Prepare a useful support request

• Merchant order reference and provider reference, if available.
• Market, payment direction, exact bank or wallet method.
• Amount, currency, timestamp and timezone.
• Current order status, sanitized error and whether a callback was received.
• Relevant redacted payment evidence if requested.

Existing merchants should use their agreed support channel. For a new integration, review Indonesia payment gateway coverage, VA collections and bank and wallet payouts. These checks help scope the investigation; they do not promise an outcome or a fixed resolution time.