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

FastLink and Configuration Tool – New Features/Enhancements

FastLink 4 Configuration Improvements

  • Account types for manual accounts can now be customized, i.e., manual account types can either be included or excluded. Configuration Tools page
  • A new currency display format has been introduced and can be configured from the product dashboard in the Launch Tools page → Select a Currency Format. This helps consumers who have accounts linked from multiple countries to differentiate different currencies. For example, the United States, Australia, New Zealand, Canada, and Hong Kong all use the $ symbol. Adding the country abbreviation to the format allows the user to identify the origin. Launch Tools page
  • Kenya local is now supported allowing consumers to link Kenya country sites.
  • Enhancements have been made to handle integration issues related to missing last name for the Matching Service customers. Rather than allowing the consumer to enter their credentials and then discover the issue, the consumer is blocked at the FastLink launch and an appropriate post message is sent to the customer to address the issue.

Credit Accelerator – New Feature

Enriched Credit Accelerator File

The Credit Accelerator file has been enhanced to include the following financial insights of a loan applicant:

  • Net Cashflow Monthly Average
  • Number of negative cashflow months
  • Days since last income
  • Summary of Me2Me transactions
  • BNPL Summary

AU Open Banking – New Features/Enhancements

Consent Screen Enhancement

To enhance the clarity and relevancy of the data cluster content, business account-related text changes have been implemented in the Data Requested section of the Consent screen.

Existing
Existing Data Requested section
Enhanced
Enhanced Data Requested section

Yodlee APIs – New Features/Enhancements

SMB Category Support

Support for 28 SMB categories has been introduced for SMB-enabled customers. The Transactions and Data Extracts APIs have been enhanced to include the new attribute businessCategory in the response.

Method and URLs:

CDR Fields Added

To facilitate customers focused on the lending, business, and verification use cases, additional CDR fields (Bank container) have been added to the following API response:

  • 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:

My Yodlee – New Features/Enhancements

User Permissions for Client Credentials and JWT

In My Yodlee, user permissions for Client Credential and JWT management has been introduced. Authentication is a new user permission that must be assigned to employees by the My Yodlee admin. Inheritance does not apply in this case. To enable or disable view, hide, and edit access for Client Credentials and JWT, navigate Settings → Permissions → Manage role permissions → Sensitive section.

My Yodlee Settings

Batch Data Feed – New Features/Enhancements

Modified Batch Ingestion of UMP Custodian Data

Yodlee ingests the Unified Managed Platform (UMP) custodian data through Batch Data Feed 2.0. Currently, BDF 2.0 picks up the Customer/Account/Transaction and Positions files from UMP in its format and converts it into Yodlee data file format.

To correctly ingest the data, enhancements have been made to process the user information present in the UMP file named Family Member. Rather than using the Customer file, the Family Member file will be utilized to obtain the user GUID, and the Account IDs in the file will then be used to map accounts in the Account Master file/Transaction/Holding.

BDF 2.0 Incremental Mode Enhancement

In BDF 2.0, if customers are sending files in an incremental mode, then deletion happens based on the Action Type value. A new configuration key has been introduced to ignore the Action Type value. If the key is enabled, the accounts and holdings that are not in the Accounts and Holding files will be deleted. So, it is important for customers to always send the complete User, Accounts, and Holding files. User and Transaction will not be deleted based on the key configuration.