SignIn Widget in mobile apps
The same widget should be used in the mobile applications as in the browser version. The difference is that in the mobile version, you should use the WebView component that simulates the browser and embeds the Widget code in it.
Kontomatik access to banking data may be based on the OAuth standard. In such cases, after the target is selected in the Widget, the end-user is redirected to a web page on the bank’s domain for authentication.
In order for the PSD2 flow to work properly on native mobile apps,
window.close function calls have to be handled by the native WebView or the app code.
Make sure that both the WebView with iframe and the WebView which loads the bank’s page in the popup have these features enabled:
- Multiple windows are supported
- DOM Storage
When the widget is embedded in the native app and the user changes the font size in the system settings on their Android phone, the widget may become unusable. To make it usable but sacrificing the look of the UI, you can set the
true in the widget.
We released an example of integration which shows how to embed the SignIn Widget in an android mobile app. The example focuses on the simplest and most effective way of displaying Widget through the use of WebView.