2022

November

Connect Widget

Invalid Credentials View

The Connect Widget now displays an error message on the same screen when the end user inputs invalid credentials. Previously, if invalid credentials were provided, the user was directed to a different screen which provided the error message. If users wanted to re-enter the correct credentials, they had to select the back button. To simplify the user experience, the additional screen has been removed. The error message remains unchanged.

No action is required by clients or end users to experience this change, it has been automatically updated in the Connect Widget experience.

Search Institution User Experience

In the Connect Widget, if an end user is searching for their institution, the Select your institution screen displays a list of the most popular institutions. This update enables the search bar to remain visible when a user is scrolling through the list. Previously, if the end user scrolled down the list, the search bar would disappear and the user would need to scroll up to access it. Now, if a user does not see their institution in the list, they can access the search bar quickly and easily.

No action is required by clients or end users to experience this change, it has been automatically updated in the Connect Widget experience.

October

Connect Widget

We are removing the disclosure screen from the Connect Widget on Oct. 11 in an effort to increase conversion rates and reduce user drop-off rates. Clients who would like to keep the disclosure screen can reach out to their MX delivery team or to MX support to have it re-added.

Currently, users see the below disclosure screen before searching for their institution or entering credentials. They are required to select Continue to move forward.

Instead of showing the disclosure screen, we will show a disclosure that says “Data access powered by MX” with a link to the privacy policy. This will be displayed on either screen that prompts users to login, as shown below.

We will automatically implement this change on Oct. 11. It will not break the Connect Widget and will not require clients to do any additional coding, so clients do not need to do anything unless they want to keep the disclosure screen.

September

Mobile Banking

Mobile Banking SDK

MXmobile is a fully-featured digital banking platform that empowers financial institutions and fintechs to deliver data-driven, contextual, and personalized experiences. The MXmobile SDK empowers clients to build their own experiences, instead of using MX development teams.

By extending the core MXmobile solution, clients can experience an accelerated speed to market and implementation time. After installing the MXmobile SDK and integrating it with the Path SDK, clients can configure their features, add plugins that extend MXmobile’s core functionality, and customize their app’s colors, fonts, images, icons, user interface text, buttons, and components. By using the MXmobile SDK, clients can create their own mobile experience that’s powered by MX and true to their brand.

Learn more about how the MXmobile SDK works at docs.mx.com/mobile-sdk/guides/getting-started.

Ask questions or get started with the MXmobile SDK by reaching out to your delivery team.

Path SDK

As a part of the MXmobile offering, the Path SDK is a sub offering of the MXmobile SDK. This software development kit enables MXmobile clients to use the MX Path platform to quickly build connections between their mobile applications, the MX Platform, and other data sources. Path connects MXmobile to the MX platform and any other data source MX clients may rely on and translates between both of these connections, despite how disparate those systems are.

Historically, Path’s connections have been built only by MX, and MXmobile clients were unable to make changes on their own to the back-end connections their mobile application required. Using the Path SDK, MXmobile clients are empowered to define these connections and switch between them as needed without relying on MX to do it for them.

Learn more about how the Path SDK works at docs.mx.com/path-sdk or visit the MX GitHub at github.com/mxenabled/path-sdk.

Ask questions or get started with the Path SDK by reaching out to your delivery team.

iOS version

MX now has the ability to limit use of an iOS version, based on SDKs that are incorporated into the MXmobile app. If an SDK is not supported back to iOS 11, MX can prevent users on older iOS versions from downloading an incompatible app. MXmobile will still support back to iOS 11, but MX can modify this on an individual client basis, depending on the client needs and SDK compatibilities.

MXcommunity

MXcommunity is an online space for MX clients and partners to engage with other MX product users by exploring topics of interest, asking questions, and collaborating. Clients can discuss challenges, post reviews, submit product ideas, and engage with one another to democratize knowledge and improve client experience and outcomes. As the MXcommunity professional network grows, it will become the go-to place for clients to get advice from experts in the industry as they integrate and expand their portfolio of MX products.

Explore and join MXcommunity at community.mx.com.

August

Connect Widget

We are enhancing the information we collect and analyze through Google Analytics to track in more detail where users drop off in the MX Connect Widget, instead of knowing only that they drop off at some point during the process. This will help us understand where we can improve.

We’ve made some visual changes to the step when users manually add an account. These changes offer design consistency, improve accessibility (a11y), and provide information in English, Spanish, and Canadian French.

MXinsights

We have added or updated several insights:

• The new Green Statement Fee insight shows a recent paper statement fee and reminds users they can save money — and the planet — by opting out of paper statements.
• The new Green Gas Purchases Summary insight explains gas spending frequency and patterns.
• The new Unexpected Subscription Payment insight informs users when a payment occurs for a subscription they have marked as canceled.
• The Weekly New Merchants insight is now dynamic, so it will update if users make changes to it. It notifies users that MX has identified one or more merchants they had not interacted with the previous week.

We have also created a new feedback flow in the Upcoming Subscription and Subscription Detected insights that allows users to tell us we got something wrong. And, to protect users who are still getting charged for a subscription they say they’ve canceled, we created the Unexpected Subscription Payment insight that recommends they double-check.

July

Processor Token

We have introduced Processor Tokens to the Instant Account Verification feature within the MX Platform API. Processor Tokens enable tokenized access for processors working with MX clients. Processors can exchange a token for the information, including payment account information, transaction history, identity data, and real-time account balance information. This reduces the need for clients to gather, store, and exchange sensitive data with processors.

Processor Tokens will be live July 18 for clients to use. Clients must have the MX Instant Account Verification feature to use Processor Tokens. For more information on how Processor Tokens work, review MX’s developer documentation or talk to your MX contact.

Connect Widget

We have made several enhancements in MXconnect:

• Not all clients use standard credentials for authentication through MXconnect. For clients that require an API key, we have added a feature that allows us to present information about the authentication requirements for that institution. These instructions will guide users to successful connections.
• There is now a prompt that asks users for feedback about their connection experience. This feedback will help MX improve the experience for all users. This feature is live for all clients.
• We have enhanced the MXConnect interface in several ways to improve the user experience, including making a seamless framing experience, updating a title page, and tweaking some spacing and visuals.

We’ve launched a quickstart app called MXquickconnect. Use MXquickconnect to try our MXconnect widget. It's a great way to learn about integrating with the MX Platform. The app, coupled with sample code, demonstrates adding new users and members (connecting a user to their financial account) and making additional requests for a number of use cases. It’s available in our Github repository at https://github.com/mxenabled/mx-quickconnect. You’ll need an API key and a client ID to use it.

Developer Documentation

We have been redesigning the MX Developer Documentation website at docs.mx.com to improve its usability. It will have simplified navigation options, including a list of all guides under Use Case buttons in the left navigation. You will see these changes soon.

June

In the Connect widget, aggregation clients will no longer have to manually set the wait_for_full_aggregation field to true, as that will now be the default.

This means that the widget will wait until any aggregation process is complete before firing a connected postMessage. As such, clients will have transactional data by the time the widget is closed. This change will reduce issues around data availability after the widget session.

MX will automatically implement this change Tuesday, June 21, so clients will not need to do anything on their end.

March

MXinsights 1 Year Sweeper Worker

Summary

Technically, MXinsights users can scroll all the way back to the first insight that was ever created for them. In practice, no users are doing this. An unnecessary pileup of insights in our databases will lead to performance issues if not addressed. On Tuesday, March 1st, we implemented a sweeper worker that will automatically delete insights that are 1 year old or older for all end users on the platform. This sweeper worker will continue to delete insights that are older than 1 year. This impacts all MXinsights clients and MXinsights end users. However, we anticipate that the impact will go unnoticed because our analytics suggest nobody is scrolling back further than 1 year.

What Is Happening?

We are implementing a sweeper worker that will automatically delete insights that are 1 year old or older for all MXinsights users on the platform. This sweeper worker will continue to delete insights that are older than 1 year

Why is this Happening?

Our databases are being bogged down by millions of insights that are no longer relevant. If we don’t do something about it, we anticipate we will run into performance issues. This sweeper protects the user experience by protecting speed and performance.

When Is This Happening?

Code was pushed on Tuesday March 1st, and the deletion process will be completed by Thursday March 3rd. The deletion process will then continue happening in the background for insights 1 year old or older.

Who Does This Impact?

All MXinsights end users that scroll back 1 year into their insights (usually scroll back a couple of weeks)

What Are the Impact(s)?

End users

This will only impact insights that are older than 1 year.

The only way the end user would see an impact is if they scrolled back 1 year in their feed. We anticipate no users are doing that but we are working on implementing tracking mechanisms to know for sure.

Clients/Partners

None

What Does the Partner/Client Need to Do as a Result of This Change?

No action needed on the part of partners or clients. 

FAQ

Will analytics for clients be affected?

No, clients will continue having access to all the end user insights even after they are deleted from their feed.

February

Updates

• For clients using Connect inside a WebView, we've improved the process of redirecting users back to their native app. The new client_redirect_url parameter should be used instead of the ui_message_webview_url_scheme parameter. You can learn more in our API reference or integration guide. ui_message_webview_url_scheme is still supported, however.
• We have expanded behavioral metrics to improve research on the user journey through the widget.

Fixes

We made some minor updates to capital and lowercase letters, Spanish translations, and accessibility functions.