Release Notes

OAuth Connections - 8/10/2020

Since Finicity announced the initiative to establish OAuth connections at all financial institutions (FIs), we’ve been hard at work with a few of our clients, helping them move from a standard (legacy) connection to an OAuth connection. Through their feedback, we’ve improved our services and streamlined the processes required for OAuth.

The following changes now make it possible for all clients to more easily manage and migrate customer accounts from an existing legacy connection to a new more secure OAuth connection.

  • New OAuth documentation: New OAuth content has been added to our online help website. There, you’ll find information about the migration processes, new APIs services, and options to manage migrating your customer accounts to an OAuth connection. See OAuth Connections.

  • New app registration end: Previously, clients had to send in their app registration information through forms or email to our account management and onboarding team for registration.

    Now, we’ve created API endpoints for App Registration and App Modification to simplify the application registration process.

    There’s also a new API named: App Registration Status Check. This self-service endpoint lets you check the status of your application registration.

  • Support multiple applications: Many of clients have requested support to register multiple applications. We responded to that request by creating two new APIs: Add Customer (V2) and Set Customer Application ID. These endpoints let you assign your customers to any of your registered applications.

  • Support multiple applications: Many of clients have requested support to register multiple applications. We responded to that request by creating two new APIs: Add Customer (V2) and Set Customer Application ID. These endpoints let you assign your customers to any of your registered applications.

  • Simplified migration service: We’ve created a new version 2 of our migrations service which uses an internal database to automatically migrate customer accounts to the correct OAuth institution. Now, you only have to code the migration process one time without having to add any additional mapping.

  • New values in financial institutions services: We added new reference fields to our financial institution services to identify which legacy institutions map to each of their corresponding OAuth institutions.

Coming soon

  • Watch for the official launch and migration date announcements for some of our largest financial institutions.

  • We’ll soon announce the names of some of our newest financial institution clients.

Lending Solutions - 04/23/2020

Currently, when you generate a verification report, the constraints you enter are used in the reporting process. When you refresh the same report for a customer a second time, the constraints aren’t used in the new report, and you’d have to reenter the constraints again. In most cases, this behavior isn’t wanted.

Now, if you request a report, for the same report type and customer, the constraints you entered for the first report are used for all subsequent new reports.

The following conditions apply to new reports and what constraints are used to create them.

Examples:

  • Customer A
    • Runs report 1 with constraints
    • Runs report 2 with no constraints
      • Report 2 will use the constraints from report 1
  • Customer B
    • Runs report 3 with no constraints
    • Runs report 4 with no constraints
      • Report 4 won’t use any constraints, same as report 3
  • Customer C
    • Runs report 5 with constraints
    • Runs report 6 with constraints
      • Report 6 will use the constraints included in request for report 6
    • Runs report 7 with no constraints
      • Report 7 will use the constraints used in report 6

If you intentionally want to remove all constraints on a second report, when you have included constraints on the first report, this is not possible.

  • Customer D
    • Runs report 8 with constraints
    • Runs report 9 with no constraints (on purpose)
      • Report 9 will use the constraints used in report 8

However, including ANY constraint in a second report, will overwrite ALL constraints in the first report.

Example:

  • Customer E
    • Runs report 8 with account constraint
      • Specified Account 1 only
    • Runs report 9 with FromDate constraint
      • Specify FromDate only
      • Report 9 will ONLY use the fromDate constraint, and will NOT use the account constraint.

These new changes will be implemented tonight, April 23, 2020

Finicity Reports - 04/21/2020

The following updates have been made to Finicity Reports:

Features

ReCaptcha authorization has been implemented on the company info page of the sign up process.

ReCaptcha authorization has been implemented in the log in process.

Additional changes on the sign up page – Company Information Page:

  • Removed the “http//: or https//:” requirement from website URL

  • NMLS field UI changes : Removed the “arrows” on this field and updated it as a short textbox.

Issues addressed in this release:

  • Loan Officer did not have the following options available: View, Download, Resend Request and Refresh Report. This has been addressed and are now available.

  • Admin user can change their own role even if there is no secondary user/admin in same organization.  This has been fixed so that there will always be an admin user.

  • There was an issue with uploading a Company Brand Logo. This has been fixed.

  • During login, if the password is expired, the user was not being redirected to the update password screen. This has been fixed.

OAuth - 04/15/2020

Finicity is migrating our connections to Direct API which uses OAuth authentication processes.

Currently, your customers log in to their Financial Institution (FI) and select the type of data they want to share, but many customers aren’t selecting all the fields required and their request fails.

Now, before customers log in to their FI, the launch window displays the data types required to complete their request, which increases their success rate.

New: Updated Launch Displays

  • Capitol One

  • Chase

  • Wells Fargo

There are two types of displays: generic, and specific requirements. All FI’s with Direct API connections only receive the generic launch display.

The following FI’s will receive the display with specific requirements listed on your custom display.

Sample Displays

The new launch window displays are for FIs with Direct API connections.

Generic

Wells Fargo FI

Chase FI

Capital One FI

The new launch window displays will be implemented tonight: April 15, 2020 between the 11:00pm – 1:00am MDT 

Student Loans - 04/08/2020

This message is to inform you that Finicity will be enhancing the student loan FI connection for a specific institution, thus expanding the Student Loan FI coverage.

Affected institution:

FI ID – 102165
FI Name – Educational Computer Systems, Inc. (Heartland ECSI)

As a result of this change, any existing student loan accounts on your platform at Educational Computer Systems, Inc. (Heartland ECSI) will be disconnected. To indicate this, their aggregationStatusCode will be marked as 950. End users will need to re-add these accounts in order to connect them to their customerId.

Deployment of these changes will occur on 8th April 2020.

Please reply with any questions you have regarding this transition.

Student Loans - 01/20/2020

We’re writing to let you know about some additional updates that Finicity is making to several of our student loan FI connections. As part of our efforts to provide the most accurate reports, we are adding transactions and statement support.

Transactions will be available for the following Student Loan FIs:

  • Great Lakes Educational Loan Services Inc.

  • NelNet Student Loan

  • EdFinancial Services

  • Navient Customer Loan Service

  • FedLoan Servicing

  • Firstmark Services

  • Oklahoma Student Loan Authority (OSLA) – Direct Loan

  • Granite State Management and Resources

  • American Education Services

  • Sallie Mae Loan Service

  • Mohela (SoFi Layout)

  • MOHELA – SoFi (Mohela Layout)

  • Wells Fargo

  • Cornerstone Education Loan Services

PDF Statements will be available for the following Student Loan FIs:

  • Great Lakes Educational Loan Services Inc.

  • NelNet Student Loan

  • EdFinancial Services

  • American Education Services

  • Navient Customer Loan Service

  • Oklahoma Student Loan Authority (OSLA) – Direct Loan

  • Granite State Management and Resources

  • Sallie Mae Loan Service

  • FedLoan Servicing

  • Firstmark Services

  • Wells Fargo

  • Cornerstone Education Loan Services

Please feel free to reach out with any questions you might have about this update or the rollout process. We want this transition to be as smooth as possible for you.

Student Loans - 01/15/2020

We’re writing to let you know about some updates that Finicity is making to several of our student loan FI connections. As part of our efforts to provide the most accurate reports, we are adding nine new data fields. This change will impact the following 14 student loan institutions:

  • Great Lakes Educational Loan Services Inc.

  • Mohela (SoFi Layout)

  • Wells Fargo

  • Oklahoma Student Loan Authority (OSLA) – Direct Loan

  • Granite State Management and Resources

  • Sallie Mae Loan Service

  • MOHELA – SoFi (Mohela Layout)

  • NelNet Student Loan

  • EdFinancial Services

  • American Education Services

  • Navient Customer Loan Service

  • FedLoan Servicing

  • Firstmark Services

  • Cornerstone Education Loan Services

The new data fields are as follows:

  • Next Payment Amount

  • YTD Interest

  • YTD Principle

  • Monthly Payment

Please feel free to reach out with any questions you might have about this update or the rollout process. We want this transition to be as smooth as possible for you.

Verification Reports - 05/18/2020

Currently, the Account Owner Name and Account Owner Address for each account in a Verification of Assets Report and Verification of Income Report are included in the JSON/XML versions of the report.  However, the PDF version only includes the Account Owner Name.

This release is adding the Account Owner Address to the Verification of Assets report and the Verification of Income report.  This will be displayed as a new column in the Accounts Summary table in each report as shown below.

We hope this new version of the VOA and VOI report PDF will make things even easier for you.

Feel free to reach out to your contact here at Finicity if you have any questions or concerns about this feature update. We’re here to help.

RealAccountNumberLast4 In API Calls - 07/09/2020

We have added a new data field called realAccountNumberLast4 to the following API endpoints:

  • Get Customer Account

  • Get Customer Accounts

  • Get Customer Accounts by Institution

  • Get Customer Accounts by Institution Login

  • Refresh Customer Accounts

  • Refresh Customer Accounts by Institution Login

  • Accounts Object

Historically, the only field returned which would contain any account number information in the Finicity account record was the “number” field. This field’s purpose is for the end user to properly identify accounts when there are multiple accounts.  It could contain many different values including an actual account number, the last 4 of an account number, bank product name information, account numbers with suffixes such as 12345678-09, as well as obfuscated account number values such as XXXX5678.

In contrast, the new “realAccountNumberLast4” will always be only the last 4 digits of an account number based on the full ACH account number for the account. This should give more consistency to those that would like just account number information when needed. As there are not always ACH account numbers for accounts available this field will not always be populated.

Example
 {
"id": "1023622376",
"number": "XXXX8008",
"realAccountNumberLast4": "8008"
}

Discontinued field effective July 13, 2020:

Inside the Categorization Record of all transactions, the bestRepresentation field is redundant data that will be discontinued going forward.  This is the same data that is provided in the Description and Memo fields on each transaction.

Example
 {
"normalizedPayeeName": "Mad Science Research",
"category": "Paycheck",
"bestRepresentation": "MAD SCIENCE RESEARCH PR PAYMENT PPD ID 098749",
"city": "Murray",
"state": "UT",
"postalCode": "84123",
"country": "USA"
}

Archive

We have a list of older releases that can be found below. We update archived release notes once a year.