Personal Finance Management
Our Personal Finance Management (PFM) solution includes a comprehensive set of widgets that help your users visualize, understand, and manage their financial health.
Available Widgets
You can integrate the Money Dashboard Widget, which contains all PFM widgets, or embed PFM widgets individually.
Legacy Widgets are older versions of our widgets which are only available for existing integrations and don't appear in the Money Dashboard.
View all available widgets
- Accounts Widget – Displays connected accounts and their balances
- Budgets Widget – Helps users create and manage budgets
- Cash Flow Widget – Shows income, expenses, and projected balances
- Connections Widget – Manages financial institution connections
- Debts Widget – Tracks and helps manage debt accounts
- Goals Widget – Assists users in setting and tracking financial goals
- Money Dashboard Widget - Houses all of the PFM widgets in one unified interface
- Net Worth Widget – Shows users' total financial position
- Recurring Transactions Widget – Identifies and manages recurring income and expenses
- Settings Widget – Allows users to personalize their PFM experience
- Spending Widget – Visualizes spending patterns and categories
- Transactions Widget – Displays a list of transactions
- Trends Widget – Visualizes financial trends over time
Quick Links
Accessibility FAQs
With the mission of empowering the world to be financially strong, MX is focused on providing a robust experience for clients and end users of our products and guided by the WCAG 2.1 A and AA recommendations.
For more info, see Accessibility at MX PDF.
WCAG Status
MX's web-based application that hosts our Personal Finance Management and Financial Insights products is made up of smaller parts called widgets, all of which align with WCAG 2.0 recommendations when accessed through the most recent versions of Chrome, Edge, Firefox, and Safari browsers. All enhancements and new features are designed to have strong conformance to WCAG 2.1 A & AA guidelines.
MX no longer supports IE11 as Microsoft has stopped supporting their browser on August 17th, 2021.
While the WCAG guidelines are focused on web accessibility rather than native applications, MX products have been upgraded to have strong conformance with the WCAG 2.0 A and AA guidelines when used on iOS and Android devices. Continual enhancements prioritize WCAG 2.1 alignment based on feedback received through user testing.
MX leverages LevelAccess solutions for education, evaluation and testing.
Current Work
MX has adopted a phased approach to development, guided by WCAG’s four key foundations: perceivability, operability, understandability, and robustness through which legacy systems are progressively improved as we endeavor to meet the needs of end users. New features are designed for accessibility improvements from conception through completion.
Future Work
Evaluation and accreditation
Our goal is to improve both our knowledge and users’ experiences by working with experts in the field. We will accomplish this through internal education and external engagement with a11y community. We are also evaluating automation software that can improve the speed of solutions development and verification for all users.
Several MX clients have provided 3rd party evaluations of our services. We will continue to respond to these reports as a means to improving our solutions. We continue to assess the merit of formal accreditation through a third party in the future.
User testing
Given the unique nature of some features, we recognize the value and insight that user testing provides. In our pursuit of achieving the best overall digital experience, we have begun to incorporate user testing in development and are continuing to refine and expand our testing efforts.
Background on Guidelines
The Americans with Disabilities Act (ADA) does not include any language specific to websites or web-development. However, Title II of the ADA mandates that all “places of public accommodation” (all businesses open to the public) are required to remove “access barriers” that would hinder a disabled person’s access to that business’s goods or services.
The World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines (WCAG 2.0 AA) is seen as the world standard for defining what an “accessible” website is. While these are only guidelines, they have been adopted as the standard by court precedence, and any future regulation will likely point to this standard.
In June 2018, W3C adopted the WCAG 2.1 guidelines (which are backward compatible with WCAG 2.0 recommendations) with the additional goal of improving accessibility for users with disabilities on mobile devices.
Additional Info
Here are some other useful links:
Security & Privacy FAQs
Your users' data is safe inside MX's personal financial management (PFM) tools. Because PFM is embedded inside online banking, access is protected by banking-level encryption, just like an online banking account. In addition, PFM and the Mobile Banking application use their own additional layer of security when transmitting data.
When users add all of their accounts to PFM, they can monitor them in one place, and are much more likely to catch potential fraudulent transactions.
Does MX Sell User Info to 3rd Parties?
No. Financial information is never sold to third parties.
When a User Adds an Account Who Can See It?
No one at a user's financial institution has the ability to access user's information in PFM. The MX Support Team (who powers the tools) may view an account, for the purposes of providing support. No one has access to a user's account credentials.
User data may be aggregated for trends analysis and target marketing, but no one at a financial institution can look for a specific individual’s account, or at any individual’s complete account information.
Some financial institutions may allow account impersonation for the purpose of providing support.
Privacy Policy
We’re committed to keeping your user's information secure, and as such we implement privacy standards to guard against identity theft and unauthorized access to user's information. We also regularly monitor and reevaluate our privacy and security policies and adapt them as necessary to deal with new conditions.
We use industry-accepted standards, protocols and precautions to protect personally identifiable information from loss, misuse, unauthorized access or disclosure, alteration or destruction. We maintain physical, electronic and procedural safeguards for personally identifiable information, including using firewall barriers, encryption techniques, authentication procedures, SSL (secure socket layer) encryption, and physical safeguards. In addition, we do not sell any personally identifiable information.
We will post changes to the policy in the PFM tool so that users will always know what information we gather, how we might use that information, and when we will disclose that information to third parties, if at all. We may also inform users of any changes to this policy by a prominent notice within the services or by email. In addition, and at our discretion, in the event of an update or material change, users may be required to agree to the new privacy policy as a condition precedent to your continued use of the services.
Theming Your Widgets
You can use the following theming options for all non-legacy widgets.
| Customization | Default | Enablement |
|---|---|---|
| Primary color | #2C64EF | Contact your MX representative with the desired hex value. |
| Font | Inter | Use the style parameter in the request widget URL or contact your MX representative with the font name. |
| Card corner radius | 0px | Contact your MX representative with the radius pixel value. |
| Button corner radius | 8px | Contact your MX representative with the radius pixel value. |
| Mode | Light mode | Use the color_scheme parameter in the request widget URL or contact your MX representative with your mode preference (light mode for all users, dark mode for all users, or respect each user's browser settings). |
| Language | English | Use the Accept-Language header to set the language in your widget URL request. You may also contact your MX representative to have them set the language or set your integration to respect each user's browser settings. See the list of supported languages |
Notifications
Keep users informed and engaged with notifications that support multiple delivery channels including email, SMS, in-app, and push notifications. These notifications help users stay on top of their finances with timely information about account activity, spending patterns, and important financial events.
Supported Browsers
MX supports HTML5-compliant browsers that support TLSv1.2 or higher (required since March 20, 2017).
Supported Desktop Browsers
MX tests its web applications on the current version and previous version of the following browsers:
| Browser | PC | Mac |
|---|---|---|
| Chrome | Yes | Yes |
| Microsoft Edge | Yes | N/A |
| Firefox | Yes | Yes |
| Safari | No | Yes |
MX doesn't support Internet Explorer and won't address related issues.
MX may actively block some browsers from displaying our products when the results would provide a 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:
| Browser | iOS | Android |
|---|---|---|
| Chrome | No | Yes |
| Safari | Yes | N/A |
| WKWebView | Yes | N/A |
| Android WebView | N/A | Yes |
UIWebView is no longer supported. Apple recommends using WKWebView.
Older Browsers
Older versions of supported browsers aren't explicitly tested. MX will review issues as reported, but compatibility is not guaranteed and you may be required to upgrade.
Supported Dimensions
PFM widgets have a responsive design. Page styles and layout will change and elements may become hidden or visible at different widths.
Recommended Dimensions
Set the widgets to load at 100% height and 100% width. The widgets respond to the size of their container.
The design changes at the following width breakpoints based on typical industry device resolutions:
- X-Small: 444px
- Small: 600px
- Medium: 900px
- Large: 1200px
- X-Large: 1536px
Don't restrict the browser width by adding margins or padding around the widget container.
Mini Widget Dimensions
Mini Widgets use the following dimensions, with the pixel height and width as the container dimensions. Non-Legacy widgets respond to their containers.
| Mini Widget | Recommended Width x Height |
|---|---|
| Mini Accounts | 710px x 296px |
| Mini Budgets | 320px x 341px |
| Mini Cash Flow | 710px x 180 px or 320px x 324 px |
| Mini Connections | 320px x 265px |
| Mini Recurring Transactions | 710px x 348px |
| Mini Spending | 320px x 328px |
| Mini Trends | 710px x 329px |
| (Legacy) Mini Finstrong | 400px |
| (Legacy) Mini Net Worth | 400px |
| (Legacy) Mini Spending Plan | A scroll bar will appear at any height if there's more content to view. |
| (Legacy) Mini Spending | 300px |
Supported Languages
Request widgets in a specific language (defaults to en-US) in four ways:
-
Recommended: Use the
Accept-Languageheader in the widget URL -
Ask your MX representative to set the language for all users
-
Ask your MX representative to configure your integration to respect each user's browser setting
-
Pass the
localeparameter through the body of the widget URL
The locale parameter doesn't affect the Connect Widget if you embed it by itself, but it applies to the Connect Widget contained in the Money Dashboard Widget.
We support PFM widgets for both the Platform API and the SSO API in the following languages:
en-CAen-USesfrfr-CA