Our website displays multiple payment bank options, each linked to a corresponding native mobile application using deep links (e.g., app://q?qPay_QRcode=...). The functionality was working seamlessly across all browsers, including Safari, Chrome, and in-app browsers like Messenger’s, up until August 2024.

Deep links to native banking apps still work flawlessly in Safari and Chrome. However, in the Messenger in-app browser, clicking on a deep link to open a native banking app does not trigger the native app as expected. Instead, the user is redirected to the app store, even if the application is already installed on their device. Notably, the Messenger-specific fb:// deep links continue to function properly in the same environment, indicating that the issue is isolated to third-party app deep links (such as banking apps).

This issue disrupts the payment flow for users who access our website from Messenger, leading to confusion and inconvenience. Users are unable to seamlessly transition from our web interface to their native banking apps, negatively impacting their overall experience. As the issue persists only in the Messenger in-app browser and does not affect other browsers, we believe this to be a change or restriction introduced specifically within Messenger's handling of external deep links.