Release Notes - January 2017

'Dynamic Integrations Project' introduces more efficient methods for troubleshooting issues with connecting to Financial Institutions.

To help us get closer to accomplishing our goal of better and more consistent data delivery, we have been working on some innovations regarding how we handle changes to security methods and policies at financial institutions as well as how we solve and communicate about problems with connections. This project has been aptly named the “Dynamic Integrations Project” and as you can guess it is focused on providing ways for our engineering and support teams to more dynamically fix and create connections to financial institutions. You may have already seen some tickets using this terminology as we have been working through testing the new tools and processes that have been part of this project. (sorry for any confusion and frustration as we have been testing things out!) As part of this project, any time a connection breaks and requires additional authentication in order to resolve the issue (like passwords, security questions, or One-Time-Passcodes) we will now be able to collect the data necessary to troubleshoot by using a combination of new aggregation status codes to specify what is needed as well as updated documentation that will help you inform your customers of what they need to do. In addition, customers’ add account attempts and refreshes will collect information needed to solve their problems without much extra effort. Here are those new codes with their explanations:

 

900

903

904

FI Connection currently under maintenance.

HTTP 500; AGG

Gathering additional authentication information in order to proceed with fix. Customer should check back every several days and attempt to refresh or add accounts again. Each attempt will store information needed by engineering to continue to fix the connection. One attempt every 3 to 5 days should be sufficient.

901

FI Connection currently under maintenance.

HTTP 500; AGG

Gathering additional authentication information in order to proceed with fix. Similar action to (900 / 903 / 904 / 915), but user should attempt to log-in up to 5 attempts in a row if possible in order to store all the additional authentication information needed since this is related to an MFA type where security question information needs to be stored.

915

FI not working for a specific user or group of users.

HTTP 500; AGG

Gathering additional authentication information in order to proceed with fix. Customer should check back every several days and attempt to refresh or add accounts again. Each attempt will store information needed by engineering to continue to fix the connection. One attempt every 3 to 5 days should be sufficient.

916

FI not working for a specific user or group of users.

HTTP 500; AGG

Gathering additional authentication information in order to proceed with fix. Customer should check back in every several days and attempt to refresh or add accounts again. Each attempt will store information needed by engineering to continue to fix the connection. Customer should attempt every 3 to 5 days and make up to 5 attempts in a row if possible in order to store all the additional authentication information needed.

 

As we were using this process for solving instances where we needed more authentication information we also found that this new process could be helpful in other instances to communicate more specific information regarding customer actions that need to be taken. We have added some more user action status codes to the existing ones we already have. Here are those new codes and their explanations:

 

931

Bank security requires a one time passcode for every connection

HTTP 500; AGG

The bank requires a one time passcode every time the customer wants their financial information. Inform the customer of this situation and facilitate them refreshing every time they use the app to enter the one time passcode so they can get the latest financial info.

936

Customer's language preference is not supported for aggregation

HTTP 500; AGG

The customer has a language preference other than English. This could potentially cause issues with the integration for this specific institution. Have the customer change their language preferences to English for their accounts in order to get the best experience.

 

We took things even further setting up a few new codes we will begin to utilize where appropriate to better communicate when a connection is having problems and in some cases why it is having problems. Take a look at these new codes:

 

910

Institution connection is currently down and is being worked on

HTTP 500; AGG

Inform the customer that we are aware that the connection is down and we are working on fixing it. Have them check back every 3 to 5 days.

920

to

929

This institution does not currently support aggregation

HTTP 500; AGG

There could be multiple reasons that an institution does not support aggregation. We recommend the customer reach out to their financial institution and tell them to contact Finicity by emailing ryan.christiansen@finicity.com in order to resolve the issue and become a supported institution.

 

As we now have the new process established we will continue to add more codes and instructions where it provides value. As our partners utilizing our services to provide aggregation to your customers you may know some scenarios that we have not yet thought of. If you have any scenarios you run into often that could used some enhanced error code handling please let us know the details by emailing us at support@finicity.com and we will pass that on to our integrations product team.

 

Now that we have these new error codes and processes to collect authentication information, we will not need the form on the developer portal that was used in the past to securely collect additional authentication information. This will be removed from the developer portal.

An additional benefit of the new changes will be that we should be able to start processing requests for new institutions in a more timely manner. There is still quite a bit of a backlog as we have lots of new institutions we would like to add so the turn around times could still be lengthy. We have changed our procedures to better track and execute on our requests which includes some changes to what information is required on the "Request A New FI" form on the developer portal. For further details on requesting a new institution including cost and time to complete requests please contact your account manager.

 

We took the time to make some fixes and changes to TxPush as well during the last few releases since TxPush is critical in our vision to providing real time data. You should see general stability improvements so events will be delivered faster and more reliably.

 

In the area of support it is important to note that we will be disabling the auto creation of 'add account error tickets' into the system. Every time a customer had an error while adding an account we would create an escalated ticket in the system that we would then try to process. However, we found many times that the customer was no longer engaged. To better manage our escalation process we decided it would be better to stop the auto creation of these tickets. Internally, we have processes to fix connection issues related to add account errors by highest to lowest volume (which is how we manage tickets related to already added accounts as well). If customers contact you about financial institutions they are struggling to connect to that aren’t getting resolved you are welcome to submit an escalated ticket on behalf of your customer to support@finicity.com as is the normal process. The disabling of auto tickets will happen within the next several weeks.


For any questions about the release please email us support@finicity.com with your questions. If you would like to schedule a walk through with one of our systems engineers to talk through the changes in more detail and how these changes should be applied in your applications please contact your account manager and ask them specifically for an appointment with systems engineering to go over your questions.

Have more questions? Submit a request

Comments

Powered by Zendesk