Managed Webview policies restricting external payment redirect gateways

Have you confirmed whether the flow is using an embedded WebView or Chrome Custom Tabs (CCT)? In many payment and banking scenarios, embedded WebViews can encounter issues with session persistence, cookie handling, redirects to external apps, and authorization callbacks. Chrome Custom Tabs generally provide better compatibility because they leverage the user's default browser, share browser state such as cookies and saved credentials, and tend to handle authentication, deep-link callbacks, and external payment redirects more reliably than embedded WebViews. 

From the description, this sounds more like a session or callback handoff issue during the redirect rather than a managed Google Play or EMM domain allowlist restriction. If the payment provider or banking service supports deep links or app links for the authorization callback, that may also be worth validating. Has the same flow been tested using Chrome Custom Tabs instead of an embedded WebView? It would be interesting to see whether the behavior changes.

Restricting external payment redirects in managed WebView environments can create problems for legitimate payment flows. It would be useful to clearly distinguish between unsafe redirects and trusted payment gateways, with policy options that allow administrators to control approved domains without breaking normal checkout processes.