Sorry, you need to enable JavaScript to visit this website.
Skip to main content

FastLink and Configuration Tool – New Features/Enhancements

Upload and Associate Supporting Documents with Aggregated Accounts

Enhancements have been made to enable consumers to upload supporting PDF documents like bank statements for the Aggregation or Verification flow. Based on their specific business needs, Aggregation or Verification customers can offer this feature to their consumers. Once the feature is enabled, consumers can upload documents seamlessly, and customers can perform the following using APIs:

  • Retrieve the list of documents uploaded by the consumer.
  • Retrieve the document.
  • Delete the document.

For more information about the APIs, click here.

FastLink User Workflow

The document upload process begins after the consumer has successfully linked their financial institution’s accounts. On the Account Summary screen, the consumer must click or tap the Upload Document link under a specific account to initiate the process. In the next set of screens, the consumer must select the PDF documents and upload them.
The uploaded document(s) will be displayed in the Associated document list section under the account. Consumers can delete any incorrectly uploaded document by clicking or tapping the delete button next to the document.

Deep-link Flows

Customers can deep-link to the Add Document screen by passing the extra parameter flow=uploadDocuments while launching FastLink. Deep-link functionality supports the following three scenarios:

  • Customers can pass the account ID to which the uploaded document should be associated.
  • Customers can pass the provider account ID, where the consumer can select the aggregated accounts of that provider account to which the document has to be associated, as shown in the following screen: 
  • If the customer does not pass an account ID or provider account ID, then the consumer will get an option to associate the document with any of their aggregated accounts.

Feature Enablement

The document upload feature can be enabled in the Configuration Tool by navigating to GLOBAL SETTINGS → Select additional features → Select the appropriate options in the Add additional data section.

To display the Upload Document link, navigate to ACCOUNT SUMMARY (for the Aggregation flow) or ACCOUNT SELECTION (for the Verification flow) and select Display upload document link in the Add additional data section in the respective pages.

Open Banking – New Features/Enhancements

US Open Banking

Webhook Notification for OB Verification

A new webhook notification has been created to address a specific business case where the OB consumer has removed accounts from the consent given to customers or has revoked the overall consent. Consumer can either take this action on the Provider side or by editing the consent through FastLink. 
When such a change happens for Aggregation customers, the same is notified through the DATA_UPDATE notification after data refresh. But Account Verification only customers generally may not subscribe for DATA_UPDATE notification as nightly data refresh is not enabled, due to which they are not notified about such changes. Hence, a webhooks notification has been introduced for Account Verification customers to get notified when a consent is revoked or expired, or when an account is in set To be closed or Closed status.
The new webhook notification OB_ACCOUNT_STATUS_UPDATES will be triggered when:

  • The status of the Provider Account changes to:
    • CONSENT_EXPIRED
    • CONSENT_REVOKED
  • The status of the Account changes from:
    • ACTIVE → TO_BE_CLOSED
    • ACTIVE → CLOSED
    • TO_BE_CLOSED → ACTIVE

It is recommended that only Account Verification customers should subscribe to the OB_ACCOUNT_STATUS_UPDATES notification for account status changes. The information in the new notification will also be part of the DATA_UPDATES notification. For more details, click here.

AU Open Banking

Consent Date Enhancement

The consent date currently shown on the consent screens reflects the date when the consent was initially given. The Consent and Consent Dashboard for active consents screens have been enhanced to display the latest or renewed consent start date, providing consumers with the most up-to-date or accurate information.
This enhancement is primarily a compliance requirement for AU OB and the consent date-specific change is made available to all FastLink 4 OB-supported regions. Changes to the following dates have been made:

  • Consent created date – The date when the consent was initially authorized/granted will be displayed in the consent PDF (only for AU OB) and will also be included in webhooks (for all FastLink 4 OB-supported regions).
  • Consent start date – The date when the consent was renewed. If the consent has not been renewed yet, both the consent created and start dates will be the same. To display the Consent start date, API enhancements have been made to return the consent renew date. For more information, click here.

Account Deletion Flow Enhancement

The account deletion process has been enhanced to address data access issues, such as when all the consented accounts and their details are not provided by the provider as part of data calls. The lack of notification or information about service issues or unavailability leads to unexpected account deletions during the automatic or system refresh flow. Changes to the account deletion process have been implemented, where only unconsented accounts are deleted during the consent edit or amendment flow. During the automatic or system refresh flow, if the consented accounts are not returned in the provider data calls, the accounts will be marked with a To be closed status. If the account's data is received within the next 30 days, the account status will be changed to Active; otherwise, the account will be deleted based on the applicable consent deletion preferences.

Label and Help Text Changes

The following label and help text changes have been implemented in the OB application onboarding flow:

  • In the Data Requested screen, the label name has been changed:
    • From Account and Balance Details to Your Account Details.
    • From Name, Occupation and Contact Details to Name, Occupation, Organisation and contact Details.
  • An explanatory help text has been added to the Third Parties screen to help customers understand when the third parties and questions will be displayed to their consumers. The help text is highlighted in the following screen:

Yodlee APIs – New Features/Enhancements

Document Search and Delete APIs

Customers now can utilize the following new and enhanced APIs for searching and deleting the PDF documents uploaded by consumers or users using FastLink 4 for the Aggregation and Verification product flows:

  • Search Documents API – This new API allows retrieving and downloading documents by passing the document IDs or account IDs in the body of the API request.

    Method and URL:

  • Delete Documents API – Documents can be deleted using this new API by passing the document IDs in the API request.

    Method and URL:

  • Delete User API – This API has been enhanced to delete the documents associated with the user when the user is deleted or unregistered from the Yodlee platform.

    Method and URL:

The GET Consents and GET Consents History APIs have been enhanced to include the new attribute renewedDateTime in the API response. The new attribute returns the date and time when the consent was renewed.

Note: This field will mainly be available for AU OB sites, and for other regions/providers, it will depend on data availability.

Method and URLs:

CDR Fields Added

Additional CDR fields have been added for the card container to facilitate customers focused on the lending, business, and verification use cases. 
The CDR fields that have been added to the API response are as follows:

  • Accounts and Data Extracts APIs –
    • sourceProductName
    • isOwnedAtSource
    • sourceAccountOwnership
    • businessInformation.businessName
    • businessInformation.legalName
    • businessInformation.acn
    • businessInformation.abn
  • Transactions API and Data Extracts APIs –
    • sourceMerchantCategoryCode
    • typeAtSource
    • sourceBillerCode
    • sourceBillerName
    • sourceApcaNumber

Note: These fields will primarily be available for AU Open Banking sites, and for other regions/providers, the population will depend on the availability of data.

Method and URLs:

Account Verification – New Features/Enhancements

Disable Customer-specific Routing Number

In this release, the option to restrict customer-specific routing numbers has been introduced. This option is intended for customers who do not want their consumers to verify the routing numbers associated with them as they have an alternate way to verify such accounts. 
To enable the option, in the Configuration Tool, navigate to the respective product configuration → Set Preferences → PRODUCT & FEATURES – Verification section → select Restrict own Routing Numbers.

Once enabled, if the consumer attempts to initiate account verification using the customer-specific routing number(s) the following message will be displayed in FastLink.

Consumers can be requested to contact the respective customers if they wish to verify the account using the customer-specific routing numbers.

Transaction Data Enrichment – New Features/Enhancements

New Merchant Type

Due to the growing importance of the BNPL (Buy Now Pay Later) market, a new merchant type BNPL has been introduced. On identifying a BNPL merchant, the GET Transactions API response will return the merchantType attribute value as BNPL.

Method and URLs:

In the TDE batch data output file or the Enricher file, the following new ID for BNPL merchants has been introduced:

Merchant Type IDMerchant Type Name
4BNPL

New Merchant Source – Foursquare

From the November release, Foursquare reference data will be used for merchant and category prediction in TDE. The transactions already filed in the system will continue to display Factual as the merchant source unless they are refreshed. Migration will commence with US merchants, followed by coverage of the remaining TDE-supported regions.
In the GET Transactions and GET User Data API responses, a new merchant.source value FOURSQUARE has been introduced and the merchant.id attribute will return the Foursquare merchant ID.

Method and URLs:

Site-specific Simple Description Customization

The transaction simple description customization capability was introduced in the July release. The customized simple description logic based on the site-specific patterns has been introduced in this release.

Batch Data Feed – New Features/Enhancements

Merchant Name Support

BDF 2.0 has been enhanced to accept merchant name. Customers can now send the merchant’s name along with the existing merchant address-related fields in the BDF transaction file for Bank, Card, and Loan containers. This new field will be optional. A configuration must be set to read the merchant name field along with the merchant address attributes from the input file.