Why Webview Checkout is Problematic
Users seem to utilise web checkout within webviews rather than integrating with our SDKs. While this allows you to reuse your existing web integration and avoid re-implementing cart/checkout in the SDK, it introduces multiple issues and is not recommended. Integrating web checkout within webviews can result in several critical issues including but not limited to:- Popup Restrictions: Flows requiring popups may be disabled or may not function as expected.
- UPI Intent Configuration: Additional configuration is required to make UPI intent work within webviews.
- Bank Transfers and Downloads: Payment methods like bank transfer, which rely on downloads, will fail as webviews do not support downloads by default.
Recommended Approach
We strongly recommend migrating to our SDK instead of using webviews to ensure full compatibility and a smoother experience. If you still decide to proceed with webview-based checkout, please consider the below adjustments to minimise issues, including but not limited to.Webview Integration Guide (For Users Proceeding Anyway)
- Implement Callback URL Handling: Ensure your integration correctly handles callback URLs to receive payment status updates reliably.
- Configure UPI Intent: Follow additional steps to ensure UPI intent payments function correctly on Android or iOS.
- Handle Download Restrictions: Implement solutions for payment methods that require file downloads. For now, you will need to manage downloads on your end.