MX

Overview

Founded in 2010 and headquartered in Lehi, Utah, MX helps providers turn consumer-permissioned financial data into digital experiences and analytics. Consumers can bring accounts together in one view, while providers can use that information in their services. MX combines account aggregation, data enhancement, APIs and mobile banking rather than focusing on account linking alone.

MX says it has comprehensive demand-deposit coverage in the United States and Canada, with more than 75% direct connections to financial providers. That is a useful foundation for products serving those markets, though the coverage claim does not guarantee a connection to every institution. Supported data includes accounts, balances, transactions, investments, statements, identity, ownership and rewards; refreshes are real-time, and statements are in PDF format.

Key features

Open finance APIs support account linking, balance checks, account and identity verification, and permission-based data sharing. MX says its Data Access platform uses consumer-permissioned OAuth connections and is built on FDX standards. Direct OAuth connections can verify bank and other financial accounts in less than five seconds, a potentially useful shortcut for services that need to confirm account details promptly.

MX also cleans and categorizes transaction details into consistent data for digital experiences and analytics, and brings external brokerage and retirement accounts alongside other financial information. Its connection options include OAuth APIs, tokenized and direct connections, whitelisted screen scraping and microdeposits. The variety gives providers multiple ways to connect accounts, while the mix of methods means implementation choices will depend on the use case.

For mobile products, MX offers a banking product and Android and iOS Mobile Banking SDK. That can make it a broader fit than a connectivity-only service, but SDK access requires approval as a third party or a customer contract. MX says it monitors its environment around the clock, uses built-in incident-response alerts, hosts information only in secure U.S. data centers, and maintains SOC 2 Type II and PCI DSS certifications. Its integration with Atomic combines MX data and analytics with Atomic's direct-deposit and bill-pay switching products.

Pricing

Free account: 0.00 USD per free (100 users). The free option gives smaller teams a way to start without a listed charge, but its 100-user ceiling limits its suitability for wider deployment.

MX Platform: custom pricing; request a demo. The platform is the paid route for organizations seeking MX's broader offering, but prospective buyers should expect to discuss requirements rather than compare a published price.

Platforms

MX supports Android, iOS, web and API. Its SDK is specifically for approved third parties or contracted customers, so platform availability does not mean every developer can use the mobile banking components.

Who it's for

MX is a strong candidate for financial institutions and fintechs building services that need account connections, verification, categorized transaction data or a mobile banking component. Its stated North American demand-deposit coverage and investment-account normalization suit products that draw from multiple kinds of financial accounts. It is less suitable for an unapproved developer seeking immediate SDK access or a buyer who needs a published production price before engaging.

Pros and cons

• Pros: Account aggregation, verification, data enhancement and mobile banking sit within one platform, reducing the need to assess each capability as a separate product.
• Pros: Real-time refreshes and multiple connection methods give providers options for account-data workflows.
• Pros: MX states that direct OAuth verification can take less than five seconds, and it holds SOC 2 Type II and PCI DSS certifications.
• Cons: The free account stops at 100 users, so it is not a substitute for a larger production plan.
• Cons: The mobile SDK is gated to approved third parties or contracted customers, restricting access for developers who do not qualify.
• Cons: MX Platform pricing requires a demo request, making upfront cost comparison difficult.

Alternatives

Bank Connectivity Software is a useful starting point for comparing products in the category. TrueLayer Data API may suit teams that want a free mock-data sandbox before production; its sandbox has no production access, while production pricing depends on volume and use case. Powens is another custom API option, with enterprise plans offering dedicated hosting and support.

Brankas is worth considering for buyers evaluating cloud, on-premise or hybrid deployments. Lean Technologies is another paid option on Android, API, iOS and web. Salt Edge Data Aggregation offers a free sandbox or developer trial using simulated bank fixtures, but has no free plan for production. Agicap may fit buyers seeking a subscription with a minimum 12-month term. Cobase Bank Connector ties pricing to bank connections, account volume, modules and ERP integrations. Plaid offers eligible US and Canada teams a free trial with up to 10 production items and most OAuth institutions.

Verdict

Choose MX if you are a financial institution or fintech that needs account connectivity, normalized data and mobile banking capabilities in one platform, and can work within its approval and sales process. Its combination of data tools and stated North American coverage is the central reason to consider it. Look elsewhere if you need open SDK access, a free tier for more than 100 users, or clear production pricing before a demo.