Skip to main content
The Connect Widget lets end users search for and connect to their accounts. It collects users’ credentials, prompts for multifactor authentication, and resolves connection errors between end users and their financial institutions. You’ll embed the widget into your website or mobile app. We offer a React Native SDK for mobile implementations and a Web SDK for desktop implementations.

Integrate using MX's Connect Widget

UI Walkthrough

image of the Connect Widget

Retrievable Data

The following are example responses for each product.
See Account Aggregation for more info.This sample response shows the data you can expect to get for financial accounts.
This sample response shows the data you can expect to get for transactions.
See Instant Account Verification for more info.This sample response shows the data you can expect to get for account owners.
See Account Owner Identification for more info.This sample response shows the data you can expect to get for account owners.
You can configure the widget to return transactions when its mode is set to verification.This sample response shows the data you can expect to get for transactions.

Connection Errors

When the widget is loaded, it automatically chooses the best course of action for resolving a connection error between a user and their financial institution. For more info, see Member Connection Statuses.

Browser Support

MX supports HTML5-compliant browsers that support TLSv1.2 or higher. Older versions of supported browsers aren’t explicitly tested. MX will review issues as reported, but upgrading may be required if compatibility can’t be ensured.

Supported Desktop Browsers​

MX tests its web applications on the current version and previous version of the following browsers:
BrowserPCMac
ChromeYesYes
Microsoft EdgeYesN/A
FirefoxYesYes
SafariNoYes
BLOCKED BROWSERSMX may actively block some browsers from displaying our products when the results would provide an extremely poor user experience. Browsers in Compatibility or Quirks mode may not function and can be blocked if performance is degraded.

Supported Mobile Browsers​

MX tests its web applications on the current version and previous version of iOS and Android, using the following browsers:
BrowseriOSAndroid
ChromeNoYes
SafariYesN/A
WKWebViewYesN/A
Android WebViewN/AYes
NOTEUIWebView is no longer supported. Apple recommends using WKWebView.

Language Support

To change the display language from English, set the Accept-Language header in the Request Widget URL endpoint to one of these supported languages:
  • en-CA
  • es
  • fr

Widget Dimensions

The Connect Widget uses a responsive design. Layout and styles may adjust based on screen size, and certain elements may become hidden/visible at different widths. The minimum dimensions supported for mobile and desktop platforms are:
  • Height: 550px
  • Width: 320px
Design changes may occur at the following width breakpoints, which are based on common device resolutions:
  • Small: 320px–767px
  • Medium: 768px–1199px
  • Large: 1200px and higher
NOTEBreakpoints and layout behavior are subject to change.

OAuth Support

You must register for OAuth before you can use it with real institutions. For institutions using an OAuth flow, the Connect Widget will redirect to that institution’s page or mobile app, where the end user can authorize the accounts they want to connect. See Connect Widget OAuth Workflows.

Handling Session Timeouts

When integrating our Connect Widget, consider the session timeout built into the widget and the session timeout built into your website or mobile app. The widget automatically times out after 15 minutes of inactivity. Reach out to your account representative to customize this duration. Thirty seconds before the timeout, a No recent activity screen appears and prompts the user to select Continue to avoid timing out. If no user activity is detected within those 30 seconds, the widget will timeout and display a Session expired screen.

Member Use Cases

NOTEWork with MX to enable this functionality.
You can opt in to setting the use_cases field in applicable requests so each member has an associated use_case. This ensures only the data associated with the use case for that member (PFM or Money Movement) is returned. It also lets you filter a user’s data through a single use_case, even if data relating to a different use_case is in our system. If you’ve implemented the Connect Widget and have worked with MX to enable member use cases, you must include the use_cases field when requesting your widget URL to ensure:
  • Each member is associated with a specific use case.
  • Our Personal Finance Management and Financial Insights products reflect data only for members with the PFM use case.
  • Members with "use_cases": ["MONEY_MOVEMENT"] do not aggregate transaction data.
In the Connect Widget, this change impacts the flow of new and existing members. For more info about other changes relating to creating members, updating members, and available query parameters for use cases, see the Platform API docs.

New Members

When you request a widget URL with a widget_type of connect_widget or connections_widget, set the use_cases field. The use cases provided in this request will be saved to any member created inside of the widget. For example, if you:
  1. Set use_cases: ["PFM"] in the widget URL request.
  2. Load the Connect Widget using the URL returned from the request.
  3. Successfully create a member.
  4. Read that member, which will have a use_case of PFM as set in step 1.

Existing Members

The widget won’t remove use cases from an existing member, it will only add new ones. For example, let’s assume a member already exists that has use_cases: ["MONEY_MOVEMENT"]:
  1. You set use_cases: ["PFM"] in the widget URL request.
  2. The end user finds their institution and enters their same credentials as before.
  3. The widget will update the existing member so to have use_cases: [“MONEY_MOVEMENT”, "PFM"].