MX guide

Software Setup

To use MX with Rutter, you must create an MX developer account. The developer account includes free sandbox testing connections and access to a limited set of MX features.

Rutter does not provide MX API keys. Contact your Rutter customer success representative for introductions to the MX team when you're ready to move to production access.

Developer Account Setup

Create an MX account

  1. Sign up at MX's Dashboard.
  2. Once logged in, you'll be taken to your MX dashboard.

Obtain Your Client Credentials

After registration, MX will provide a client_id and api_key to authenticate your API requests. You can find these in the Developers → Api Keys section of the MX Developer Dashboard.

Share Your Credentials with Rutter

  1. Log in to the Rutter Dashboard.
  2. Navigate to Platforms → Banking → MX.
  3. Enter your MX client_id and api_key.
  4. Select the appropriate environment:
    • Development Mode: For testing with MX’s Development environment, which returns dummy data.
    • Production Mode: For connecting to real financial institutions through MX.

MX’s Development is separate from Rutter’s sandbox. To test MX Development connections, you must be in Rutter’s production mode.

Connect to Your MX App

  1. Generate a Rutter Link URL from the Connections section of the Rutter Dashboard.
  2. Click Create New Connection, then copy the shareable URL.
  3. Append ?banking=true to enable the Smart Banking flow.
    To force MX as the provider, append ?platform=mx to the URL.
  4. Select a financial institution and complete the authentication flow.
  5. For Sandbox testing, use MX’s development credentials.
  6. Upon successful connection, you’ll be redirected to a completion page. The connection will appear on your Rutter Dashboard.

Webhook Setup

Rutter sends real-time webhooks for key banking events such as account updates, new transactions, or connection status changes.

You must register the webhook URL in MX following the instructions below. After registering the webhook URL, Rutter manages all communication with MX, including polling and webhook delivery.

Configure Webhooks in the Rutter Dashboard

  1. Go to Platforms → MX → Webhooks in the Rutter Dashboard.
  2. Rutter will display a Webhook URL that must be registered with MX. This is the endpoint MX will use to send event notifications.
  3. Register this URL in the MX platform by going to dashboard.mx.com/webhooks.
  4. (Optional) If you choose to use Basic Authentication, toggle Use HTTP Basic Authentication when adding the webhook URL in the MX platform, and provide the username and password you configured in the Rutter Dashboard. Rutter will validate incoming webhook requests using these credentials.
  5. Save the configuration.

Once set up, Rutter will receive events from MX and forward relevant updates to your application.

IP Whitelisting (Production Only)

To connect to MX in production, you must whitelist the following Rutter IPs in your MX configuration:

  • 52.5.155.132
  • 52.87.82.133

Failure to whitelist these IPs may result in failed API requests or blocked webhook events.

Where to Set This

You can whitelist IPs in your MX dashboard by going to:

  • Security Settings, or
  • Navigate to Developers → API Key in the MX Dashboard, then locate the Whitelisted IP Addresses section for production.

Make sure both IPs are added to ensure uninterrupted connectivity in production.

Reference

FAQ

What’s the difference between MX’s Development and production environments?
MX’s sandbox returns mock data using test credentials. The production environment connects to real banks and user accounts.

Can I use MX’s Development while in Rutter’s sandbox mode?
No. To test MX Development connections, you must be in Rutter’s production environment.

How often is banking data updated?
MX updates financial data in near real-time. Rutter sends webhooks when new data is available. Use these to trigger incremental syncs via the Rutter API.

What happens if a bank connection fails?
If a connection becomes unhealthy or needs reauthentication, Rutter will send a CONNECTION_NEEDS_UPDATE or CONNECTION_DISABLED webhook. Redirect the user through Rutter Link to reconnect.

Best Practices

  • Start integration in MX’s Development environment
  • Use various test credentials to simulate real-world flows
  • Implement webhook handling for real-time updates
  • Monitor connection health and error states
  • Provide users with a way to reconnect accounts when needed

Supported Data

With MX through Rutter, you can access:

  • Bank account metadata
  • Real-time balances
  • Transaction history

See Rutter’s Banking API documentation for a complete list of supported endpoints.

Next
NetSuite