Skip to main content

Accounts

An account represents a financial account, for example, a user’s checking or savings account. A member may have more than one account associated with it. For instance, a user may have both a checking and savings account associated with one Chase login and would therefore have two accounts associated with that member.

Account Fields

Account Types and Subtypes

Parent Types:
  • ANY (not provided by data partner or invalid number provided)
  • CHECKING
  • SAVINGS
  • LOAN
  • CREDIT_CARD
  • INVESTMENT
  • LINE_OF_CREDIT
  • MORTGAGE
  • PROPERTY
  • CASH
  • INSURANCE
  • PREPAID
  • CHECKING_LINE_OF_CREDIT
Subtypes

Account Property Types

Beats

Beats are deprecated. Use Insights instead. Beats Fields

Beat Feedback

Beats are deprecated. Use insights instead.

Budgets

Budgets represent an end users monthly budget for a given category. Budgets are offered as part of the following MX products and solutions:
  • Mobile Banking
  • Personal Finance Management
  • Nexus API
Budget Fields

Categories

Daily reporting files for categories reflect changes in custom transaction categories created by end users with the following MX products and solutions:
  • Mobile Banking
  • Personal Finance Management
  • Nexus API
  • Platform API
Category Fields

Devices

Devices represent devices using the Mobile Banking app. Device Fields

Goals

Goals represent savings or payment goals created with the following MX products and solutions:
  • Personal Finance Management
  • Nexus

Goal Fields

Goal Meta Types

  • AUTOMOBILE
  • COLLEGE
  • ELECTRONIC
  • EMERGENCY_FUND
  • HOUSE
  • OTHER
  • RECREATIONAL_VEHICLE
  • RETIREMENT
  • SETUP_BUDGETS
  • START_MONEY_MANAGEMENT
  • VACATION

Holdings

Holdings represent a stock, bond, or other type of investment, as found in the following MX products and solutions:
  • Atrium API
  • MDX Real Time
  • Nexus API
  • Platform API

Holding Fields

As of January 1, 2025, CUSIP is no longer supported. Please refer to the most-up-to-date investment documentation.

Equity Classifications

  • UNKNOWN
  • LARGE_VALUE
  • LARGE_CORE
  • LARGE_GROWTH
  • MID_VALUE
  • MID_CORE
  • MID_GROWTH
  • SMALL_VALUE
  • SMALL_CORE
  • SMALL_GROWTH

Fixed Income Classifications

  • UNKNOWN_FIXED_INCOME_CLASSIFICATION
  • HIGH_LIMITED
  • HIGH_MODERATE
  • HIGH_EXTENSIVE
  • MEDIUM_LIMITED
  • MEDIUM_MODERATE
  • MEDIUM_EXTENSIVE
  • LOW_LIMITED
  • LOW_MODERATE
  • LOW_EXTENSIVE

Sectors

  • UNKNOWN_SECTOR
  • BASIC_MATERIALS
  • CONSUMER_CYCLICAL
  • FINANCIAL_SERVICES
  • REAL_ESTATE
  • CONSUMER_DEFENSIVE
  • HEALTHCARE
  • UTILITIES
  • COMMUNICATION_SERVICES
  • ENERGY
  • INDUSTRIALS
  • TECHNOLOGY

Holding Types

  • UNKNOWN_TYPE
  • EQUITY
  • EXCHANGE_TRADED_FUND
  • MONEY_MARKET
  • MUTUAL_FUND
  • HEDGE_FUND
  • ANNUITY
  • UNIT_INVESTMENT_TRUST
  • CASH
  • FIXED_INCOME
  • OPTIONS

Insights

Insights are cards that are personalized for a user and appear on the UI. This relates to our Financial Insights product.

Members

A member represents the relationship between a user and an institution. A user may have multiple members, one each for their bank, their mortgage broker, their credit card provider, etc. Aggregation, verification, and many other processes are centered around a member. Daily change files reflect member changes resulting from background aggregation as well as from the following MX products or solutions:
  • Atrium API
  • Batch API
  • Mobile Banking
  • MDX Real Time
  • Personal Finance Management, including the Connect and Connections widgets
  • Nexus API
  • Platform API
  • SSO API

Member Fields

Member Connection Statuses

The connection_status indicates the state of a member’s aggregation, meaning the state of a user connecting to a particular institution. The connection_status field indicates the current state of an aggregation, meaning the state of a user connecting to a particular institution. For instance:
  • CREATED means the member has just been created.
  • CHALLENGED means the process has run into multifactor authentication.
  • FAILED means the process was unsuccessful.
The connection statuses CREATED, UPDATED, DELAYED, and RESUMED represent transient states for different points in the process and don’t require a specific action or end-user input. They may, however, require you to keep making read requests on the member until an actionable status or an end state appears. The connection statuses PREVENTED, DENIED, IMPEDED, IMPAIRED, REJECTED, EXPIRED, LOCKED, IMPORTED, DISABLED, DISCONTINUED, and CLOSED represent end states that require you to start a new connection, and possibly end-user input, for future success. Here are all the member statuses you might encounter, what they mean, and what to do about them.

Notification Profiles

Notification profiles are related to our PFM widgets.

Notification Profile Fields

Notification Types

Taggings

Taggings represent the association of a tag to a transaction. In other words, with a tagging, a transaction can be assigned a specific tag, either the default business tag, or any other user-created tag. Daily files represent changes resulting from the following MX products and solutions:
  • Personal Finance Management
  • Nexus API
  • Platform API
Tagging Fields

Tags

Tags allow partners and end users to create a custom label for particular transactions. Daily files represent changes resulting from the following MX products and solutions:
  • Personal Finance Management
  • Nexus API
  • Platform API
Tag Fields

Transactions

A transaction represents any instance in which money moves into or out of an account, such as a purchase at a business, a payroll deposit, a transfer from one account to another, an ATM withdrawal, etc. Each transaction belongs to only one account. Daily files represent changes resulting from background aggregation as well as the following MX products and solutions:
  • Atrium API
  • Batch API
  • Mobile Banking
  • MDX Real Time
  • Personal Finance Management, including the Connect and Connections widgets
  • Nexus API
  • Platform API
  • SSO API
Transaction Fields

Users

A user represents an end-user accessing the MX Platform API via your application, be it a mobile app, web app, desktop app, etc. Daily files represent changes resulting the following MX solutions:
  • Atrium API
  • Batch API
  • MDX Real Time
  • Platform API