MX Bank Connection — Overview, Setup, and FAQ

MX Bank Connection — Overview, Setup, and FAQ

Notes
Overview
MX is LedgerSync's second full bank data aggregator, available alongside the Mastercard API. MX is fully deployed and actively used across the platform — it is not a beta feature. If your bank is not supported by the Mastercard API, or if you need a reliable fallback for banks where Mastercard has coverage limitations, MX may be the right connection to use.

What MX Supports

CapabilityAvailable via MX
Transaction aggregation (live bank transactions)Yes — fully available
Statement aggregation (monthly bank statement PDFs)Yes — available for supported institutions
MFA / multi-factor authenticationYes — fully supported (security questions, OTP codes)
Broken connection fix notificationsYes — "Fix Bank Connection" button and text-client reconnect work the same as Mastercard
Check or deposit imagesNo — use Premium Bank Connections for check images
Rules Engine compatibilityYes — MX transactions appear in the Rules Engine alongside Mastercard transactions
QBO / Accounting CS syncYes — MX transactions can be categorized and synced to QuickBooks and Accounting CS
Nightly transaction refreshYes — MX accounts refresh automatically overnight

How to Add an MX Bank Connection

  1. In LedgerSync, select the client you want to connect a bank for
  2. Click Add Bank Connection (top-right)
  3. Select the MX Connection option
  4. In the search box, type the name of your bank and select it from the results
  5. Follow the prompts to enter the client’s bank login credentials
  6. If the bank requires MFA (a security question or one-time code), you will be prompted for it on screen. Complete the MFA step to finish the connection
  7. Once connected, LedgerSync will pull statements and transactions automatically

InfoUnified API: When LedgerSync connects through MX, it uses MX’s Unified API, which requests transactions and statements together in a single login session. This means you are only prompted for MFA once — even if the bank requires authentication for both services. You will not be asked to log in a second time for statements.

How to Check if Your Bank is Supported via MX

Not every bank is available through MX. To see which banks are supported for MX-based statement and transaction aggregation, visit the MX Supported Banks page inside LedgerSync, or contact support@ledgersync.com.

You can also check Mastercard support independently at: Mastercard Open Finance Supported Institutions. If your bank is not listed there, MX may be the right alternative — contact support to confirm.

MFA — What to Expect

Many banks require multi-factor authentication when connecting or refreshing a connection. MX handles MFA the same way LedgerSync handles it for Mastercard:
  • If a bank requires a security question, you will see the question on screen and can type your answer
  • If the bank sends an OTP code (text message or email), enter the code when prompted
  • For multi-step MFA (multiple questions or codes), each step appears in sequence on screen
  • Once MFA is completed, the connection continues and data begins pulling automatically

If a client’s MX bank connection breaks and requires re-authentication:
  1. Go to the client’s Bank Summary page
  2. Click Fix Bank Connection next to the broken MX account
  3. Choose to send the client a reconnect link via SMS or email, or complete re-authentication yourself if you have the credentials

Statement Refresh — How It Works

Once an MX connection is established, LedgerSync runs a daily scheduled refresh to check for new statements and pull them in automatically. You do not need to manually trigger a refresh each month. If a bank requires MFA at refresh time, you or the client will be prompted the same way as during the initial connection.

Transactions are also refreshed nightly — LedgerSync triggers MX to aggregate the latest data from the bank before pulling transactions, so your transaction list stays up to date without manual action.

MX vs. Mastercard — Which to Use?

SituationRecommended connection
Bank is listed in the Mastercard supported institutions directoryMastercard API
Bank is not listed in Mastercard but is available through MXMX Connection
You need check or deposit imagesPremium Bank Connections (regardless of aggregator)
Both Mastercard and MX are available for the bankEither works — Mastercard is preferred if both fully supported
Mastercard connection is breaking frequently for a specific bankTry MX as an alternative

Frequently Asked Questions

Q: Is MX still in beta?
No. MX is fully deployed and actively used across the LedgerSync platform. It supports both transactions and statements for all institutions where MX has coverage.

Q: Why does my MX bank show transactions but no statements?
Not all banks that MX supports for transaction aggregation also support statement aggregation. LedgerSync checks each bank’s capabilities and requests what is available. If statements are not appearing, the bank may not offer statement access through MX. Contact support to confirm.

Q: I deleted an MX-connected account and it reappeared. What happened?
This was a known issue that has been resolved. Deleted MX accounts no longer reappear after deletion. If you experience this, contact support.

Q: Can I invite a client to connect their bank through MX from the Communication Center?
Yes. LedgerSync’s Communication Center and Task Center both support MX bank connection invites. When sending a reconnect or add-bank invitation, LedgerSync routes to the correct aggregator (Mastercard or MX) based on the bank.

Q: Will MX transactions appear in the Rules Engine?
Yes. MX transactions appear in the Rules Engine transaction grid alongside Mastercard transactions, each tagged with their data source. All Rules Engine actions (categorize, accept, exclude, sync) work the same for MX transactions as they do for Mastercard transactions.

Need Help?

Contact LedgerSync Support at support@ledgersync.com

Related Articles:
    • Related Articles

    • MX Statement Aggregation — Which Banks Support Statement Downloads via MX?

      Overview LedgerSync supports bank statement aggregation through two aggregators: Mastercard Open Finance and MX. Not every bank that supports transaction aggregation via MX also supports statement aggregation. This article explains how MX statement ...
    • Common Bank Connection Questions

      Bank Connections, Data Access, and Connection Stability Q1 — When a client opens an additional account, must the existing connection be deleted and re-added? Yes — and this is required by the bank, not LedgerSync. When a bank connection is first set ...
    • How to Add a Bank Feed Connection in LedgerSync

      Overview Adding a bank feed connection in LedgerSync allows you to aggregate bank statements, transactions, and check images for a client. LedgerSync offers five connection types. This article explains when to use each one and how to add the ...
    • Bank Connection Notes — How to Add Shared Notes to a Bank Connection

      Overview The Notes feature lets you attach persistent, shared notes to any bank connection in LedgerSync — whether it is connected via Mastercard, MX, or FDE (document-based extraction). Notes are visible to all users in your firm and are a great way ...
    • Copying a Bank Connection Between Clients & Hiding Accounts (One Login, Multiple Businesses)

      Overview Many business owners run several companies under a single bank login. Banks only allow that login to be connected once — so how do you split the accounts across separate LedgerSync clients? Two features solve this: Copy Connection and ...