#binary-android-webview

1 messages ยท Page 1 of 1 (latest)

wheat pilot
#

Can you share a bit more details: like exact code, how you integrated (Android SDK? React Native? Just pure Stripe.js?) etc

tiny canopy
#

Sure

First :
The App itself is built on ReactNative and the webview use the package react-native-webview

#

Second :
StripeJS directly is used, we built the form in bare html (well, via reactJS) and the final iframe opening is trigered by the js method confirmBancontactPayment

#

on frontend web, to be more specific, we use the package [@]stripe/react-stripe-js

wheat pilot
#

someone on my team says it's likely because of that third-party package you use for the webview on RN

tiny canopy
#

thx! looking into it

wheat pilot
#

Our advice would be to either use our official React Native library: https://github.com/stripe/stripe-react-native and our well defined integration guide, which would support Bancontact and many other payment methods, or open the view in a real browser on the device

tiny canopy
#

agreed in theory, but browser is less "premium" and using the official library is too soon for us as the app is not mature yet and we are continuously makng improvements and updating all apps is... well slow

wheat pilot
#

Honestly you are going to spend days if not weeks building this yourself

#

Our library comes with a UI element, it just works, you get all existing payment method types out of it and never have to think about it again

tiny canopy
#

we are reusing frontend web views, it is currently in prod and running well ๐Ÿ™‚

#

sorry for the wild tagging

#

mistake

wheat pilot
#

all good happens a lot :p

#

and yeah I mean you are, but now you hit that weird bug, and fixing it is a lot of work

tiny canopy
#

ah much interesting, it is a lot of work only for a very specific PM ๐Ÿ˜ฆ

#

"lot"

#

thanks i think we have all what we need here, much appreciated