Retry Strategy

⚠️ IMPORTANT NOTICE

THIS ISSUE FREQUENTLY OCCURS DURING PEAK BANKING HOURS (E.G., END OF MONTH, EVENING TIMES, OR HIGH SYSTEM TRAFFIC).

Real-Time Transfer Delay Notice

In some cases, when a user completes a transaction and immediately scans the slip, the issuing bank's system may experience a processing delay (typically 30–60 seconds, or potentially longer).

As a result, initial API requests may fail and return the following error response:

HTTP Status Code: 400 Bad Request

Error: Transaction Reference does not exist

Client-Side Implementation Guide (Recommended)

To increase the verification success rate, it is recommended that the client implementation handles HTTP 400 errors by using a Retry Mechanism with Exponential Backoff.

⚠️ IMPORTANT NOTICE#

Real-Time Transfer Delay Notice#

Client-Side Implementation Guide (Recommended)#

Example Implementation using Axios#

⚠️ IMPORTANT NOTICE

Real-Time Transfer Delay Notice

Client-Side Implementation Guide (Recommended)

Example Implementation using Axios