When integrating Onramper’s widget inside a WebView (e.g., Android, iOS, React Native, Flutter), you might encounter issues with payment methods like Google Pay and ACH bank transfers.

These issues typically stem from limitations in how WebViews handle browser APIs required for modern payment flows.

This guide will help you:

• Understand why payment issues occur in WebViews
• Diagnose and optimize your WebView setup
• Implement fallback strategies when needed

🧠 Why These Issues Happen

Payment methods such as Google Pay rely on browser technologies like the Payment Request API and other wallet-related browser features. WebView environments often lack full browser capabilities, resulting in:

• Missing or non-functional payment buttons
• Incomplete or failed payment flows
• Inability to initiate wallet-based payments

These limitations can be caused by:

• APIs that are disabled or unavailable in the embedded browser
• Platform restrictions, such as limited feature support on iOS
• Security settings or permissions that block payment integrations

Understanding this root cause can help you decide how to configure your app or how to guide users toward a successful flow.

🛠 Step 1: Understand and Configure Your WebView

If your app uses a WebView, the first step is ensuring it has the capabilities needed to support external payment providers.

While every platform differs, key things to evaluate include:

• JavaScript support: Payment widgets require JavaScript to function properly
• Browser engine version: Older or limited WebView implementations may lack needed APIs
• Security settings and permissions: Platform policies may restrict WebView behavior
• Custom configurations: Some platforms require explicitly enabling advanced browser features

📌

Tip: Refer to your development framework’s documentation (e.g., for Android, iOS, Flutter, React Native) to learn what’s needed to enable modern browser functionality within a WebView.

🔍 Step 2: Understand Your Limits — No Feedback from the Widget After Handoff

Once a user selects their preferred payment method and inputs their purchase details, Onramper routes them to the provider’s payment interface. This flow always opens outside the widget — typically in a new browser tab, in-app browser, or WebView — and is fully controlled by the provider.

As such:

• Onramper’s API and Widget do not have visibility into what happens after the user is redirected
• There are no Onramper callbacks or events that indicate whether a payment method failed or succeeded
• The provider’s page is not embedded within the Onramper widget — it opens externally

✅ What You Can Do

Because this handoff is outside Onramper’s scope, you’ll need to monitor or manage the user’s environment at the app or platform level, especially if you're opening the provider flow in a WebView.

Here’s how to approach it:

• Test how the provider’s payment page behaves in your environment
  • Does it open correctly in your WebView or in-app browser?
  • Does the payment method (e.g., Google Pay) load and respond as expected?
• Be mindful of device/browser limitations
  • Some environments will silently block required APIs (like the Payment Request API), causing payment flows to fail without explanation
• Refer to the provider’s own documentation
  • Some may offer readiness checks or environment requirements to help you detect unsupported flows early
  • Not all providers offer this, so fallback strategies are often your best safety net

🚪 Step 3: Fallback to External Browser When Needed

If it becomes clear that a payment method (like Google Pay) cannot be processed inside your WebView, the best approach is to open the flow in an external browser, where the required features will be available.

Recommended strategies include:

• Redirecting the user to their default system browser
• Using a built-in browser tab or view controller that offers full browser capabilities
• Implementing fallback logic that only triggers when payment flows fail or buttons don’t render

🔄

This ensures that users can complete their payment even if the in-app flow fails.

🧾 Summary

📣 Need Help?

If you’re still having trouble, reach out to Onramper Support with the following details:

1. Your integration environment (e.g. platform, WebView or browser type)
2. hat’s working and what’s failing
3. Any relevant screenshots or error messages

We’ll help evaluate your current setup and recommend the best path forward for your users.