#binary-android-webview
1 messages ยท Page 1 of 1 (latest)
Can you share a bit more details: like exact code, how you integrated (Android SDK? React Native? Just pure Stripe.js?) etc
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
someone on my team says it's likely because of that third-party package you use for the webview on RN
they also mentioned https://stackoverflow.com/questions/41693263/android-webview-err-unknown-url-scheme/53059413#53059413 is a good read to start
thx! looking into it
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
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
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
we are reusing frontend web views, it is currently in prod and running well ๐
sorry for the wild tagging
mistake
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
https://github.com/react-native-webview/react-native-webview/blob/a2a2d0af92aec989a58b57a191c7c738b38517b9/docs/Custom-Android.md#L135 my colleague mentioned you'd likely want to look at what we're doing here in our own SDK