#alphako5_financial-connectiosn-webview
outer kernelBOT
đź‘‹ 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/1299391034689589279
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
coarse cedarBOT
fallow fossil
Hi đź‘‹ can you help me understand where you're seeing the error you referenced? The provided request ID seems associated with a request that was successful.
wind rock
Hello.
so, after clicking "share my data" from banking web(chrome) it does not return to the my webview
it was working when i tested only website like chrome
but it does not work from react native webview
laptop => chrome (works)
android => webview => chrome (not working)
fallow fossil
Okay, trying to understand. So you create an Account Link and direct to it, within the onboarding UI you provide all details, then you try to use Financial Connections to associate an external bank account with the Connected Account and that surfaces this error?
wind rock
correct
after external bank account with the Connected Account, it's not going back to onboarding ui
fallow fossil
Yeah, I do see a warning here, though it's for Financial Connections for payments, about how using webviews may not work consistently and we recommend avoiding that approach:
https://docs.stripe.com/financial-connections/other-data-powered-products?platform=webview#:~:text=Available in%3A-,Caution,-Stripe doesn’t recommend
wind rock
can you kindly check this to better to understand
fallow fossil
That's in a webview right? So seems like the warning applies there:
Stripe doesn’t recommend using the Webview API unless the alternative integration methods aren’t feasible. The Webview API requires additional per-platform (Android and iOS) work to make sure authentication with institutions is handled on a secure browser instance, and doesn’t provide support for app-to-app, resulting in reduced conversion. If a secure browser isn’t used, certain financial institutions block traffic to their websites.
wind rock
okay thank you!
outer kernelBOT