FastLink and Configuration Tool – New Features/Enhancements
Beta Site Search Configurability
At present, the capability to search beta sites is limited to the Aggregation and Aggregation + Verification products and is not offered for other products like Verification, Verification + Aggregation, Asset Transfer Verification, or Credit Matrix. This release introduces beta site search configurability for all the products. The following image shows the option available for the Verification product in the Set preferences screen → Search section.
In the Verification product, if only the bank container is enabled at the instance-config level, beta sites cannot be searched using the FastLink 4 Search screen, even if the bank container is ready and the card, insurance, and investment containers are in beta state. With this enhancement, those sites will become searchable as well. This behavior applies to all the products.
Yodlee APIs – New Features/Enhancements
Synchronize Held Transaction Category Updates
A new API has been introduced to update held transactions using the transactionSourceId. The transactionSourceId should be included in the request body of the API call. Transactions can only be updated when there is a direct one-to-one mapping between the transactionId and the transactionSourceId.
If the transaction is updated successfully, an HTTP Response code is 204 (Success without content) will be returned.
| New API Method and URLs: |
Transaction Data Enrichment – New Features/Enhancements
New Master and Detail Retail Categories
This release introduces two new master and detail retail transaction categories to assist military personnel. While Yodlee will not predict these categories as part of TDE, users can use them during transaction re-categorization. Available in both the 45 and 61 retail category versions, these master categories will serve as placeholders, i.e., keeping the same IDs while allowing for future name updates based on customer business needs.
| Category Type | High Level Category ID | Master Category | Detail Category | ||
|---|---|---|---|---|---|
| ID | Name | ID | Name | ||
| EXPENSE | 10000010 | 232 | Permanent Change of Station | 1729 | Permanent Change of Station |
| INCOME | 10000019 | 233 | Permanent Change of Station Allowance | 1730 | Permanent Change of Station Allowance |
Impacted API Method and URLs:
Credit Matrix – New Features/Enhancements
Re-branding Credit Accelerator to Credit Matrix
The product formerly known as Credit Accelerator has been rebranded as Credit Matrix. This change will be reflected across various platforms and resources, including the company website, sales and marketing presentations, Configuration Tool, My Yodlee application, the credit inquiry webform, the developer portal documentation, and other related materials.
- API Endpoints –
The endpoints will be updated from /creditAccelerator/ to /credit/. For example, the GET Credit Accelerator File API endpoint will change from /creditAccelerator/report to /credit/report. The Credit Matrix API reference page will be updated to reflect this change in this release.
Support for the current API signatures will continue for this release and the next. After the July release, all customers will need to transition to the new API signatures. - Webhook notification –
The webhooks event name will be changed fromCREDIT_ACCELERATOR_REPORT_UPDATEStoCREDIT_MATRIX_REPORT_UPDATES.
Change in Credit Matrix Report ID Structure
To make the report ID more robust and unique for all end-users in the Production environment within the Credit product’s customer segment, the report ID format will be changed from integer to string. The size of the report ID will vary between 9 and 12 characters. Sample report IDs - FRA36QIVV, FRA36QIW2.
This change will be reflected in the API requests and responses, as well as in post messages and webhook notifications that reference report ID. The Credit Matrix API Reference page has also been updated to incorporate this change in this release.
Platform – New Features/Enhancements
Pending Transaction Reconciliation
The current behavior of the platform creates unique transaction IDs whenever a transaction transitions from Pending to Posted during data refreshes. By enabling a specific configuration key, reconciliation for pending and posted transactions in Bank and Card containers is performed. With this enhancement, the ability to reconcile pending transactions has now also been introduced for Loan and Investment containers.