Unify Your Fintech Stack

Access best-in-class data providers through one seamless integration.
Zane Pickett
CTO
Zane Pickett
CTO
January 2025 Product Updates

Features

Account Taxonomy

One of the recurrent issues with trying to understand account data is determining the type of accounts across providers. To aid with this, we've started to roll out our taxonomy. Unlike upstream providers that use either a flat or 2 dimensional list, we expose a full taxonomic list that can be refined with more precision over time.

For example, a checking account is expressed as [asset, depository, spending] while a savings account is shown as [asset, depository, savings]. In this example, if you can naturally see how to split out assets from liability. As you step down, you can select accounts that have ACH numbers, and finally you can split down unto the regulatory framework of the account.

Generally when using this field, avoid matching the entire path or matching on the end as these are likely to change overtime. Instead focus on checking the inclusion of your desired node. The taxonomic type mappings will be expanded over time, based on your feedback. If you have a use case that's not currently mapped, let us know.

Features

Webhook Event Metadata

Certain webhook events will now publish useful context on the event, allowing you to programmatically decide what and when to query for data.

For example, connection.synced events will now emit the following optional fields via a metadata property:

startDate indicating the start of the date range synced on the Connection

endDate indicating the end date of the date range synced on the Connection

Example

 {
  "id": "evt_12yWPilTeMTUEt4wYdhxEC", 
  "type": "connection.synced.successful", 
  "profile": { ... }, 
  "record": { ... }, 
  "metadata: {
    "startDate": "2024-12-20", 
    "endDate": "2025-01-20" 
  }
}


Improvements

Connector

  • [Beta] Ensure that Finicity Search Results Correctly Filter by OAuth Registration Status
  • Raise error when attempting to embed Connector from a non-http/https protocol
  • Ignore unsupported Redirect settings when launching Connector from Mobile SDKs
  • Introduce a Mock OAuth Flow

Platform

  • Make Profile legal names safer for programmatic use by preventing partial names
  • Standardize schema definitions across GraphQL and REST.
  • Improve MX's Account nickname vs name selection
  • Added MX as a supported data source for Transactions.logo
  • Filter out Finicity Shadow transactions
  • Automatically put Mock connections into error_repairable after 30 days.
  • Remapped MX's DEGRADED status to ConnectionStatus.ERROR_INSTITUTION

Dashboard

  • Added clear error messaging when attempting to use an existing organization name
  • Remove hollow styling from Integration's Enable Button to make it a clearer CTA
  • Automatically setup Finicity for new Enrollments in Sandbox
  • Add a Preparing Status for newly enabled Integrations
  • Speed up delivery of Quiltt Dashboard passcodes.

Documentation

  • Improved GraphQL Query and Mutation field documentation


Bug Fixes

  • Fixed issue syncing a limit only balances from Plaid
  • Fixed compatibility issue with sending raw MX data to FinGoal
  • Fixed Hubspot Chat in Dashboard
  • Removed gray background appearing behind Hubspot chat in dark mode
  • Fixed regression with Connector modal affecting page scroll behavior
  • Fixed syncing when encountering unknown Finicity error codes.
  • Fixed bug with statements selection not working correctly for overlapping dates
  • Fixed handling of ERROR_INSTITUTION Connection errors for Finicity