Insights that Protect

This insight notifies users that MX has identified a bill payment that is higher or lower than usual.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • In order for a transaction to be considered a bill transaction, it must meet all of the following requirements:
    • It must have a status of POSTED
    • It must be a debit transaction
    • It must be associated with a merchant
    • It must be in one of the following categories:
      • Bills & Utilities
      • Internet
      • Mobile Phone
      • Utilities
  • The user must have at least one historical debit transaction that is for the same merchant and in the same category as the transaction that is triggering this insight.
  • The user must have at least 3 transactions in the last 4 months from the same merchant with the same category.

  Trigger:

  A transaction is created which meets the requirements above, or a PENDING transaction which meets the defined requirements is updated to a status of POSTED.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title:
    • higher: "Bill higher than usual"
    • lower: "Bill lower than usual"
  • description:
    • higher: "It looks like your most recent bill from {merchant_name} was higher than it normally is. You paid {current_amount}, which is {percentage_change} higher than your recent average payment of {average_amount}."
    • lower: "It looks like your most recent bill from {merchant_name} was lower than it normally is. You paid {current_amount}, which is {percentage_change} lower than your recent average payment of {average_amount}."
  • short_description: [not shown by default]
  • call_to_action: "View Transactions"
  • supporting_action: [not shown by default]

This insight notifies users that they've received a credit related to a charge dispute.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • A transaction must meet all of the conditions below in order for a Charge Dispute Refund insight to be generated:
    • The transaction status must be POSTED
    • The transaction must be a CREDIT
    • The system_transaction_rule_guid is set to one of the following:
      • Final dispute
      • Permanent dispute
      • Permanent credit on dispute
    • The transaction must be held in an account with type CHECKING, SAVINGS, or CREDIT_CARD.

  Trigger:

  A transaction is created which meets the defined requirements, or a PENDING transaction which meets the defined requirements is updated to a status of POSTED.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Disputed charge refunded"
  • description: "On {date}, your {localized_account_name} account was credited {transaction_amount} for a transaction that was disputed recently."
  • short_description: [not shown by default]
  • call_to_action: "View transaction"
  • supporting_action: [not shown by default]

This insight notifies users that they have reached 75%, or a custom percentage, of their credit card spending limit.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • A user's credit card account is considered high when all of the following are true:
    • The user has one or more credit card accounts.
    • One or more accounts has hit or passed a user configurable percentage (defaults to 75%).

  Trigger:

  Whenever an account which meets the specified requirements is updated.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Nearing credit limit"
  • description: "You are {amount_remaining} away from reaching your {localized_account_name} credit limit. If possible, pay down your balance or avoid using this card."
  • short_description: [not shown by default]
  • call_to_action: "View more"
  • supporting_action: [not shown by default]

This insight shows users how much they are spending on interest on their credit cards over the last 90 days.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • The user must have one or more credit cards.
  • The user must have been charged some amount in interest on these credit cards in the last 90 days.
  • There must be an interest charge in the last month.
  • A transaction is considered an interest charge when all of the following attributes are true:
    • The transaction type must be DEBIT .
    • The transaction category must be FINANCE CHARGE .
    • The transaction must include "interest" or "finance charge" in the feed description; the case does not matter.
  • This insight must not already exist for the previous month.

  Trigger:

  This insight is automatically generated once per month.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Interest charges summary"
  • description: "From {start_date} to {end_date}, you have paid {total} in interest on your {localized_account_name}."
  • short_description: [not shown by default]
  • call_to_action: "Learn how to save"
  • supporting_action: [not shown by default]

This insight notifies users that MX has identified that their credit utilization is high. There are two types of insights that can be generated: a warning and an alert.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • A user's credit utilization is considered high when all of the following are true:
    • The user has one or more credit card accounts. We limit this insight to only using a maximum of 15 accounts.
    • A warning is generated when:
      • The user's balance is at least 20% or greater of their total credit limit.
      • The user has not had a previous warning or alert credit utilization beat for the current month.
    • An alert is generated when:
      • The user's balance is at least 30% or greater of their total credit limit.
      • The user has not had a previous alert credit utilization beat for the current month.

  Trigger:

  This insight is created once per week with the scheduler.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title:
    • warning: "Credit card use is nearing 30%"
    • alert: "Credit card use is over 30%"
  • description:
    • warning:
      • one: "Keeping credit utilization at 30% or less protects your credit score. You’ll reach that limit if you spend {threshold_amount} more on your credit card."
      • other: "Keeping credit utilization at 30% or less protects your credit score. You’ll reach that limit if you spend {threshold_amount} more on your {count} credit cards."
    • alert:
      • one: "Lowering credit utilization to 30% or less will protect your credit score. Consider paying {threshold_amount} toward your credit card."
      • other: "Lowering credit utilization to 30% or less will protect your credit score. Consider paying {threshold_amount} toward your {count} credit cards."
  • short_description: [not shown by default]
  • call_to_action: "Learn more"
  • supporting_action: [not shown by default]

This insight alerts users when a possible duplicate payment is detected. When there's a new transaction, we check for transactions that have the same date, amount, and merchant.

• This insights appears based on the following requirements and triggers.

  Requirements:

  In order for a Duplicate Payment insight to be generated, at least two transactions must have either:

  • The same amount and merchant guid, or
  • The same amount and description but no merchant guid

  In addition, the transactions must be debit transactions posted under the same account and have dates (transacted or posted dates) that are no more than 15 minutes apart. Account type should be either CHECKING or CREDIT_CARD.

  Trigger:

  A duplicate transaction is created in the system based upon the requirements above. It then publishes this duplicate payment information which is subscribed to and used to generate the insight. 

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Duplicate payment detected"
  • description:
    • with_merchant: "It looks like you may have a duplicate charge of {amount} to {merchant_name} on {date}."
    • without_merchant: "It looks like you may have a duplicate charge of {amount} {localized_description} on {date}."
  • short_description: [not shown by default]
  • call_to_action: "View transactions"
  • supporting_action: [not shown by default]

An insight to help users identify fees that are charged to their account.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • Debit only transactions
  • Occurs in one of the following categories:
    • Fees & Charges
    • ATM Fee
    • Bank Fee
    • Finance Charge
    • Late Fee
    • Service Fee
  • Limit to five insights each week

  Trigger:

  A transaction is created which meets the defined requirements.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "New fee detected"
  • description:
    • with_merchant: "{merchant_name} charged you {amount}. It’s a good idea to ensure charges are correct and, if needed, make adjustments to avoid fees."
    • no_merchant: "You were charged {amount} for {localized_description}. It’s a good idea to ensure charges are correct and, if needed, make adjustments to avoid fees."
  • short_description:
    • with_merchant: "{merchant_name} charged you {amount}. It’s a good idea to ensure charges are correct and, if needed, make adjustments to avoid fees."
    • no_merchant: "You were charged {amount} for {localized_description}. It’s a good idea to ensure charges are correct and, if needed, make adjustments to avoid fees."
  • call_to_action: "View charge"
  • supporting_action: [not shown by default]

An insight to bring larger than normal transactions to the user's attention.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • The amount is greater than a default threshold of $500, or by a configured amount.
  • Debit only transactions
  • Only spend account types (Checking, Savings, Credit Card)
  • Occurs in one of the following categories:
    • Auto & Transport (not auto payments or auto insurance)
    • Bills & Utilities
    • Business Services
    • Education (not student loans)
    • “Entertainment”
    • Food & Dining
    • Health & Fitness
    • Home (not mortgage or home insurance)
    • Kids
    • Personal Care
    • Pets
    • Shopping
    • Travel
    • Uncategorized
  • Transaction has not been triggered in another insight already

  Trigger:

  A transaction is created which meets the defined requirements.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Large transaction"
  • description:
    • no_merchant: "We detected a large transaction for {amount} in your {localized_account_name} account on {date}."
    • with_merchant: "We detected a large transaction from {merchant_name} for {amount} in your {localized_account_name} account on {date}."
  • short_description:
    • no_merchant: "We detected a large transaction for {amount} in your {localized_account_name} account on {date}."
    • with_merchant: "We detected a large transaction from {merchant_name} for {amount} in your {localized_account_name} account on {date}."
  • call_to_action: "View transaction"
  • supporting_action: [not shown by default]

This insight notifies users when an account balance falls below a certain threshold.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • This insight is account specific.
  • The account balance threshold is tied to the corresponding Notification Profile from MoneyMap associated with the account.
  • This insight does not depend on the top-level Low Account Balance Notification Profile being enabled, it only checks for Notification Profiles being enabled for specific accounts.
  • The account did not trigger a previous Low Account Balance beat within 15 days.

  Trigger:

  This insight is triggered when the specified requirements are met.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Low balance alert"
  • description: "On {date}, your {localized_account_name} account balance fell below {threshold}."
  • short_description: "On {date}, your {localized_account_name} account balance fell below {threshold}."
  • call_to_action: "View more"
  • supporting_action: [not shown by default]

This insight alerts users when micro-deposits have reached their account. Micro-deposits are usually less than $1 and are made to verify that accounts receiving the transaction are actually the accounts the sender intended to reach.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • In order for the Micro-Deposits insight to be generated, two transactions must:
    • Have the is_micro_deposit classifier
    • Have the same merchant_guid
    • Have the same description
    • Be in a deposit account
    • Transactions must be credit transactions posted under the same account and must have occurred within 24 hours of each other. Account type should be either CHECKING or SAVINGS.

  Trigger:

  Two micro-deposits are created in the system based upon the requirements above.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Micro-deposits detected"
  • description: "On {date} we noticed 2 small amounts added to {localized_account_name} that look like micro-deposits. This may be connected to an action you took to verify your account, so check that you recognize the sender."
  • short_description: [not shown by default]
  • call_to_action: "View deposits"
  • supporting_action: [not shown by default]

This insight shows a user their income to spend comparison for the last four months.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • This insight must not already exist for the previous month.
  • The user must have at least 1 Checkings or Savings account.
  • The user must have at least 2 months in the previous 4 months with transactions in Checkings or Savings account(s).
  • The user must have transactions for the previous month in Checkings or Savings account(s).

  Trigger:

  This insight is created once per month with the scheduler.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Spend vs income"
  • description:
    • positive: "In {last_month}, you spent {income_to_spending_percentage} of your income, or {income_to_spending_difference} less than you made. Way to go!"
    • negative: "In {last_month}, you spent {income_to_spending_percentage} of your income or {income_to_spending_difference} more than you made. Try to spend less than you make each month."
    • zero_state: "Due to changes in the data, the information here is no longer relevant."
  • short_description: [not shown by default]
  • call_to_action:
    • positive: "View transactions"
    • negative: "View transactions"
    • zero_state: ""
  • supporting_action: [not shown by default]

This insight notifies users that MX has identified a subscription in one of their accounts that has not identified before for this user.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • A subscription is considered a new subscription when all of the following are true:
    • The transaction status must be POSTED.
    • The transaction is associated with a scheduled payment.
    • The transaction is a debit.
    • The transaction is associated with a merchant.
    • The scheduled payment has scheduled_payment_type set to 1.
    • We are unable to find a previously created transaction for the same Scheduled Payment. We look as far as 13 months ago for a matching transaction.

  Trigger:

  This insight triggers when a transaction is created which meets the defined requirements, or a PENDING transaction which meets the defined requirements is updated to a status of POSTED.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Subscription detected"
  • description:
    • with_annual_amount: "We found a subscription that we haven't seen before. It's from {merchant_name} and costs {annual_subscription_amount_sum} per year."
    • without_annual_amount: "We found a subscription that we haven't seen before. It's from {merchant_name}."
  • short_description: [not shown by default]
  • call_to_action: [not shown by default]
  • supporting_action: [not shown by default]

This insight notifies users that MX has identified a subscription that has increased.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • Two transactions are required in order for a Subscription Price Increase beat to be generated:
    • The first transaction is the transaction that is being created.
    • The second transaction is the previous transaction associated with the subscription. The search range for this transaction starts one second before the date time of the first transaction and goes back 13 months.
  • Both of these transactions must be:
    • Assigned to the same merchant (merchant_guid).
    • Assigned to the same scheduled payment (scheduled_payment_guid)
  • The difference in the amount of the two transactions must be over 50 cents ($0.50).
  • The type of the assigned scheduled payment must be 'SUBSCRIPTION'.

  Trigger:

  This insight triggers when a transaction is created which meets the defined requirements, or a PENDING transaction which meets the defined requirements is updated to a status of POSTED.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Price increase"
  • description: "{merchant_name} charged you {increase_amount} more this month than normal. Did you upgrade your service?"
  • short_description: [not shown by default]
  • call_to_action: [not shown by default]
  • supporting_action: [not shown by default]

This insight warn users of a possible overdraft projected within the next seven days.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • A user must have at least one checking account.
  • Account balance information must be available for the account in question for the current date and each day for one month prior.
  • An Overdraft Prediction must exist with a prediction value of true.
  • The user can't already have a transparent overdraft warning beat for a given account that was active within the last 7 days.

  Trigger:

  This insight triggers when the requirements mentioned above are met.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Overdraft warning"
  • description: "You are projected to overdraft your {localized_account_name} account by {projected_overdraft_amount} in the next seven days, but there's still time to move money around."
  • short_description: [not shown by default]
  • call_to_action: "Transfer funds"
  • supporting_action: "Learn more" by default]

This insight alerts a user that, in 3 days, they have a bill payment due that is not a credit card and is not a subscription.

Click View bill history to see a chart of monthly payments for the bill.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • This insight must not already exist for the ScheduledPayment.
  • ScheduledPayment occurs_on date must be in the future.
  • ScheduledPayment must be for a bill.
  • ScheduledPayment must not be from the same merchant, on the same day, and for the same amount.

  Trigger:

  This insight is triggered when a user's ScheduledPayment(s) is created/updated.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Projected bill payment"
  • description: "We think your {merchant_name} bill will be {amount}, due around {date}. This is based on trends and past transactions."
  • short_description: [not shown by default]
  • call_to_action: "View bill history"
  • supporting_action: [not shown by default]

This insight notifies users that they've made a large number of small purchases within the previous week.

Click View small purchases to see details about the purchases.

• This insight appears based on the following requirements and triggers.

  Requirements:

  • Total of small purchase amounts from the previous week must be at least as high as the Small Purchases Total Threshold set on the client's insight profile (default value is $30).
  • A transaction is considered a small purchase when:
    • the amount is less than the Small Purchase Ceiling Amount configured by the client (default value is $10).
    • it is a Debit transaction.
    • it comes from a Savings, Checking or Credit Card account.
    • the top level category is one of the following:
      • Auto & Transport
      • Bills & Utilities
      • Business Services
      • Education
      • Entertainment
      • Fees & Charges
      • Financial
      • Food & Dining
      • Gifts & Donations
      • Health & Fitness
      • Home
      • Kids
      • Personal Care
      • Pets
      • Shopping
      • Travel
      • Uncategorized
    • the category is not one of the following:
      • Auto Insurance
      • Auto Payment
      • Babysitter & Daycare
      • Baby Supplies
      • Child Support
      • Doctor
      • Groceries
      • Health Insurance
      • Mortgage & Rent
      • Utilities

  Trigger:

  This insight is triggered once per week.

• This is the default text for this insight card. These are customizable. To customize, contact your CSC.

  • title: "Small purchases"
  • description:
    • above_threshold: "Last week, you had {count} transactions that were less than {small_purchase_ceiling_amount}, for a total of {total_amount}. Small purchases add up quickly!"
    • below_threshold:
      • zero: "You had no purchases under {small_purchase_ceiling_amount} last week."
      • one: "You had one purchase under {small_purchase_ceiling_amount} last week."
      • other: "You had {count} purchases under {small_purchase_ceiling_amount} last week."
  • short_description: [not shown by default]
  • call_to_action: "View small purchases"
  • supporting_action: [not shown by default]