Skip to main content

Disbursement FAQ

This section is designed to answer common questions related to the integration for and use of Flip for Business Disbursement API.

Why am I receiving a 500 Internal Server Error while making Disbursement API requests ?​

A 500 Internal Server Error typically indicates an intermittent issue, such as a network or database error. If you receive a 500 error while creating a disbursement, it may mean that the transaction has not been created in Flip because the transaction ID has not been received. We recommend retrying the transaction using the same Idempotency Key. Since you're using the same Idempotency Key, it will not result in a duplicate transaction. More information about idempotent requests can be found here.

If you successfully create a disbursement transaction and receive a transaction ID in the response, but you encounter a 500 Internal Server Error when checking the transaction status using the Get Disbursement API, we suggest retrying after some time. At this point, the transaction has already been created in Flip.

If you continue to receive a 500 Internal Server Error after retrying, please contact the Flip team at [email protected] and provide the following information:

  • Flip for Business Company ID :
  • Environment :
  • API Endpoint :
  • Issue :
  • Log request and response :

Why am I receiving a 403 Forbidden Error while making Disbursement API request?​

For the Money Transfer APIs (Bank Account Inquiry, City List, Country List, City and Country List, Create Disbursement, Get All Disbursement, Get Disbursement, Create Special Money Transfer) and all International Transfer APIs, you must include X-Signature in the header to protect your request payload from tampering. To set it up, email your public key as a password-protected archive to [email protected] with the subject Request setup Public Key and Enable signature feature, and send the archive password in a separate email to [email protected].

A 403 Forbidden error usually happens when the request is sent with a missing or incorrect signature. For setup steps and a troubleshooting checklist, see Signature (X-Signature), and use the Signature Simulator to check your signature against your public key.

Why is my Disbursement transaction status is still PENDING?​

After creating a disbursement, Flip will respond with a transaction status of PENDING, and the final status will be sent via a callback. The time it takes for the funds to arrive depends on the bank's processing time. While most disbursements are completed within the estimated timeframe, delays can occur due to connectivity or other issues in the disbursement process.

If your disbursement remains pending for more than one business day, please contact our support team at [email protected] for assistance in checking the transaction.

Can we cancel a PENDING disbursement?​

No, Flip processes the disbursement immediately after the request is received, and once the funds have been sent, unfortunately, the transaction cannot be reversed. While the status remains PENDING, a refund cannot be issued. We also advise against refunding your user or initiating the same transaction again, as there is a risk the first disbursement could eventually succeed, leading to duplicate payments.

The safest approach is to wait until the status is updated to its final state, either DONE or CANCELLED.

Why am I getting error 1074 "DAILY_LIMIT_EXCEED" while creating disbursement?​

This error occurs when your account has reached its daily disbursement limit. By default, the daily limit for disbursements is IDR 10,000,000,000.

If you need to process transactions beyond this limit, please contact your Sales PIC for further assistance.

Why is the Bank Account Inquiry API returning an incorrect beneficiary name when I try to verify a bank account in Flip?​

If the Bank Account Inquiry API returns an incorrect beneficiary name, it could be due to the following reasons:

  • The account details provided may be incorrect. Please verify the bank account information you're sending in the request.
  • If the account number is correct and the beneficiary name has recently been updated at the bank, you can contact the Flip team to re-verify the account to match the updated name. Since our API doesn't always make real-time requests to the bank, if the account is cached in Flip's system, we will return the beneficiary name based on our stored data.

Is there a rate limit on the Bank Account Inquiry API?​

Yes. The endpoint enforces three layered per-company limits, per-minute and per-hour cap on invalid (non success status) inquiry attempts, plus a per-hour cap on total inquiry volume. The invalid-attempt caps exist to protect our upstream banks from repeated bad-account lookups; the total cap is an overall ceiling.

When you hit any of them you'll get a 429 Too Many Requests response with a Retry-After header indicating how many seconds to wait. Every successful response also returns X-RateLimit-Limit, X-RateLimit-Reset, and X-RateLimit-Bucket headers so you can monitor your headroom proactively.

See Bank Account Inquiry — Rate limits for the full breakdown, header reference, and handling guidance.

Did this answer your question?