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.

PSD2 flow

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, and 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:

Iframe WebView:

Popup WebView:

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 dynamicHeight to 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.


For technical documentation, refer to our unified documentation that offers comprehensive support for customers integrating with AIS services, our PDF parser, and Data Analysis solutions. Discover detailed guidance on seamless integration with Kontomatik services and explore their full range of capabilities.



Do you need help in explaining our products, costs, and cooperation?

Technical Support

Do you have technical questions about our services or API integration?