#sukatoa_best-practices

1 messages · Page 1 of 1 (latest)

shut crowBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1413014826883747911

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.

iron current
#

Additional Info, we're able to make it to work properly:

  • Load stripe elements on page inside webview - given the setupIntentId, pubkey, clientSecret
  • We're able to submit
  • It successfully redirect to external page (hosted by us)

But the latest challenge here is that - will this work in prod? We have limited access/permissions playing around their stripe account

wooden charm
#

Hello!, do give me some time to take a look at this

wooden charm
#

We generally advise against using the Payment Element within a web view, and we recommend using our mobile SDKs instead. However, we do have users who use the Payment Element in WebView to accept card payments, and it works for them. Since it works fine in testmode, it should similarly work as expected in production.

Just a quick note: if you're looking to support Google Pay within a web view, you'll want to make sure you go through the steps mentioned in this guide.

wooden charm
#

The reason we usually advise against using the Payment Element in webviews is because we can't guarantee that every payment method will work fine with webviews. Certain payment methods may not have the best UX, or some just simply may not work at all. Unfortunately, we don't have a list of issues/payment methods that we know don't work well on webview that we can share. Even if it works well now, there's no guarantee that it'll work well in the future.

If you do want to use webviews, you should test to ensure that the payment method works fine before offering it as an option.