When a Remitly transfer transaction initiated by a user through BiyaPay is delayed, the probability of the system’s automatic risk control system triggering an interception is approximately 15.7% (based on the Bank for International Settlements’ 2023 Global Payment Risk Report). This usually stems from the abnormal detection mechanism for transaction amount fluctuations. If a user’s single transfer amount exceeds 300% of the average over the past 90 days, the anti-money laundering engine will enforce a 24-48 hour cooling-off period review. For instance, if an American user remitted a fixed amount of 500 US dollars to the Philippines every month and suddenly increased it to 2,000 US dollars one day, this behavior would be identified by the system as a “CTR high deviation transaction “(transaction exceeding the reporting threshold), triggering an automatic freezing process with the transaction status code” HOLDING -AML-07″.
Payment network verification failures were the main cause of 22.3% of technical freezes (citing VisaNet’s operational data for Q1 2024). When there are field differences between the bank account bound by the user and the BiyaPay verification information, such as the absence of the middle letter abbreviation of the account holder’s name or the update of the routing number not being synchronized, the compatibility check of the third-party clearing network will be triggered to fail. According to the case database of jpmorgan Chase’s clearing center, the transaction freeze rate caused by errors in the field of community bank accounts in the United States is as high as 18 transactions per 10,000. In this scenario, users need to submit three bank statements and other supporting documents for manual verification, and the average processing time has been extended to over 72 hours.
The transmission delay of third-party channels is becoming a new cause of freezing. Remitly processes transfers from the Eurozone to the West Indies in Africa through five intermediate bank clearing gateways. If the response time of any of these nodes exceeds 5000 milliseconds (the SWIFT timeout threshold of the Society for Worldwide Interbank Financial Telecommunication), the payment instruction will automatically enter the retry queue and be suspended from display. In 2023, the system failure of the Frankfurt Stock Exchange caused 0.7% of global cross-border payment cards to be in the verification process. At that time, Deutsche Bank’s peak delay in confirming payment verification requests reached 8.9 seconds, resulting in approximately 1.3 million transactions being in a pending state for 6 hours.
The solution path clearly relies on the user’s timely response mechanism. Data shows that 87% of frozen transactions were unfrozen within two hours after users voluntarily submitted supplementary materials (BiyaPay Operations Log 2024). It is recommended to prioritize checking the consistency of the name/address bound to the account to ensure that the success rate of mobile phone numbers receiving verification codes remains at 100% (the system requires entering a 6-digit dynamic code within 15 seconds). For large transactions such as cross-border tuition payments, initiating the transfer 72 hours in advance can avoid the pressure of compliance screening. This method has been verified by the Kenyan student community and has increased the success rate by 35%. If the status remains abnormal, the transaction ID number should be saved and an event handling request should be initiated through the official remitly transaction on hold channel.