Release Notes - September 2015 Update A

September 28, 2015

We have added three new services and made other changes to significantly improve the customer experience while activating accounts in the Finicity system.

New Service: Add All Accounts

New Service: Add All Accounts (with MFA Answers)
These new services combine functionality from Discover Customer Accounts and Activate Customer Accounts v2 (without Aggregation) to simplify and accelerate the process of adding accounts to the Finicity system.

A client app should use the new service Add All Accounts if the app intends to activate all accounts that are available using the given credentials at the given institution. A client app that needs to select specific accounts for activation should continue using the detailed activation sequence (Discover Customer Accounts followed by Activate Customer Accounts v1 or v2).

These new services may return an MFA challenge (HTTP 203). They do not invoke aggregation. Upon return all accounts available using the given credentials at the given institution are active for daily aggregation, but no transactions have been retrieved from the institution for these accounts. To be able to see transactions, clients must call Refresh Customer Account sometime after calling this service.

After this service returns, the app can decide whether to call Refresh Customer Account immediately, or execute Refresh Customer Account in the background, or even skip aggregation completely if the app is only interested in account-level details. (Note that the added accounts will still participate in regular daily aggregation on the standard Finicity schedule.)

New Service: Activate Customer Accounts v2 (without Aggregation)
This service is the same as the existing service Activate Customer Accounts except that it returns quickly, does not invoke aggregation, and will never return an MFA challenge (HTTP 203). Upon return the accounts are active for daily aggregation, but no transactions have been retrieved from the institution for the account. To be able to see transactions, clients must call Refresh Customer Account sometime after calling this service.

This new service significantly reduces the amount of time required for account activation. After activation is complete, the app can decide whether to call Refresh Customer Account immediately, or execute Refresh Customer Account in the background, or even skip aggregation completely if the app is only interested in account-level details. (Note that the activated account will still participate in regular daily aggregation on the standard Finicity schedule.)

Discover Customer Accounts
Two changes:

  • <account> records returned from Discover Customer Accounts now include <balance>, the cleared balance of the account.
  • If <loginForm> contains repeated fields, the call will return HTTP 400 (Bad Request). Repeated fields have never been supported, but the error is now handled explicitly in the service. This is a programming error which much be fixed in the client app.

Discover Customer Accounts (with MFA Answers)
The element <credentials> is no longer required in this request, and any credentials provided in the request will be ignored. The credentials that were sent in the initial call to Discover Customer Accounts are used throughout the discovery and activation process.

Deprecated Services

A reminder of changes partners should make in their code:

These services are deprecated and will be removed from the API after January 2016:

These deprecated services have been removed from the API:

These services may continue to function for some time, but they are not supported and may break at any time:

 

Have more questions? Submit a request

Comments

Powered by Zendesk