WebView parameter
Addwebview=true to your Flinks Connect iframe URL when loading it inside a native WebView. This changes the event communication method: instead of using window.postMessage, Flinks Connect emits events to window.ReactNativeWebView.postMessage (React Native) or the native WebView message handler.
iOS (WKWebView)
Setup
Android (WebView)
Setup
React Native
Using react-native-webview
Event sequence (happy path)
Flinks Connect emits the same ordered events in a WebView as on the web, delivered to youronMessage handler. For the full sequence and the REDIRECT payload, see A successful connection journey. Listen for the REDIRECT event to capture the loginId and proceed with your backend flow.
Deep link configuration
If you use aredirectUrl parameter, ensure your app is configured to handle the redirect URL as a deep link. This allows the WebView (or OS) to route the user back to your app after a successful connection.
For iOS, register a URL scheme or Universal Link. For Android, configure an intent filter in your AndroidManifest.xml.
When using
webview=true, Flinks Connect sends events via postMessage instead of redirecting the URL. You can listen for these events directly in your WebView’s message handler rather than relying on URL-based redirects.OAuth popup handling
Some financial institutions use OAuth for authentication, which opens a popup window. WebViews block popups by default. Solutions:- Set
javaScriptCanOpenWindowsAutomatically = true(required on all platforms) - Use the
oauthWindowRedirect=trueparameter to replace popups with full-page redirects within the WebView
Responsive CSS for iframe embedding
If you’re embedding Flinks Connect in a hybrid app using an iframe inside a WebView, use responsive CSS to ensure it fills the viewport:Testing
Usedemo=true in your URL to display the test institution Flinks Capital. This allows you to test the full connection flow without using real banking credentials. See Test Users for available test credentials.