Widget for webviews

Fully responsive widget for mobile applications 📱.


Widget Overview

If you'd like to have a general overview of how the widget works, make sure to check out our Connect Widget Overview article.

For mobile-native applications, we've created a hosted version of our widget that significantly simplifies your development and integration process. All it requires is for you to create a webview in your application and some knowledge of handling deeplink redirects.

On this page, we'll provide you with reference documentation on what information to pass when starting your webview as well as the possible events you can receive from the widget.

Start Widget via webview

When you initiate your webview, in order to start the widget correctly, you need to pass your access_token in the URL string.

Webview URL with access tokenWebview URL with access token

Webview URL with access token

You can also pass the configuration parameters, such as the language of the widget and what institutions to display, in the call. For detailed information about these parameters, please see our widget Startup Configuration article.

Possible widget configuration parametersPossible widget configuration parameters

Possible widget configuration parameters


Widget responses

We make use of deep link redirects in order to pass information about what happens in the widget. The structure of our deep links is:

You'll need to be able to handle success, exit, and error events.

Success event

You'll receive a Success event when your end user has successfully connected their account to their institution using the widget.

Success event structureSuccess event structure

Success event structure




The link ID for the user. You'll need this ID to be able to make further requests for the user.


The institution that the link was created with.


Exit event

You'll receive an Exit event when your end user exits the widget:

  • before connecting their account.
  • after they have selected an institution.
  • due to an error.
Exit event structureExit event structure

Exit event structure


The last_encountered_error query string is only sent if an error occurred. See the table below for a list of possible error codes and their messages.

Error code

Error message


Link already exists.


The financial institution is down, try again later


The possible error messages for a login_error are:

  • Invalid credentials provided to login to the institution
  • The user account is locked, user needs to contact the institution to unlock it
  • The user account access was forbidden by the institution
  • Impossible to login, something unexpected happened while logging into the institution. Try again later.


Impossible to login, a session is already opened with the institution for these credentials


Belvo is unable to process the request due to an internal system issue or to an unsupported response from an institution


The meta_data query string is sent whenever a user exits the widget. See the table below for a list of possible values.




Sent when the user exits the widget at the initial screen. The value of the parameter is always abandon-survey.


Sent when the user exits the widget after selecting an institution. The value will be Belvo's institution code, for example banamex_mx_retail.


Error event

You'll receive an Error event whenever an error occurs during the use of the widget.

Error event structureError event structure

Error event structure

See the table below for a list of possible error codes and their messages.

Error code

Error message


The access token was not provided or is not valid


Platform Guides

To aid your development, we've created guides on how to set up deep links and listen for events for the following platforms:

Did this page help you?