#nerder
merry harness
exotic viper
Unfortunately not -- the test payment methods are simulated via Stripe-hosted pages in general, as developers should not need to have access to local payment apps to test their flows. These flows working through should indicate that the real behaviour will work.
We can't really offer any guidance on why this might no be happening with flutter_stripe though -- I'd suggest reaching out to the developer of that via github. Most likely the best course is opening an Issue with detailed reproduction steps for a minimal app.
hot hull
to be clear, that's a common issue when using Android in webviews, the code that opens the webview has to specifically catch and handle intents.
We already do this in our SDK at least :, and I thought that plugin wraps our SDKs, I don't know the context in which that Flutter plugin would open its own WebView https://stackoverflow.com/questions/41693263/android-webview-err-unknown-url-scheme/53059413#53059413
tacit veldt
hey
thank you so much for the info!
@hot hull is because i'm redirecting to checkout, which opens in a webview
hot hull
ah. This is one of many reasons why I don't suggest building a payment integration that way(Checkout in a WebView). The better options are :
- open your website in the system browser and handle payments there outside of the app using e.g Elements/Checkout
- use our native SDKs and components integrated directly into your app rather than a webpage. I thought flutter_stripe wraps our 'mobile Checkout' PaymentSheet component?
tacit veldt
maybe the second option is actually best yes
hot hull
if you do use a WebView then you need to customise them a lot in Android to work since for example these intent:// links to other apps don't work by default like they do in the system browser, you have to explicitly write code to support them. Also as far as I know Google Pay will not work inside a WebView either which is a loss in a mobile app
tacit veldt
yes, consider that this was an MVP to quickly support iDeal payments