Data Access and FastLink – New Features/Enhancements
Cryptocurrency Account Aggregation Support in FastLink 3
Enhancements have been done to FastLink 3 to support cryptocurrency account aggregation. This feature will be disabled by default. It will be enabled in phases, and customers will be notified accordingly.
Account Verification Matching Service Flow Enhancement
The Account Verification Matching Service has been enhanced to proactively show an error if a user launching FastLink is registered without a last name listed. If the user has not provided their last name while registering, the following error message will be displayed while launching the matching service account verification flow in FastLink.
Open Banking Sites Searchable in the Stage Environment
Open Banking (OB) sites can now be searched in the stage environment. OB sites can be configured but the FastLink add account flow for OB provider sites can only be completed in the production environment once the OB app is registered with the providers.
Early Access to New Feature Support in the Configuration Tool
Early access to view and play around with new features prior to launch has now been introduced in the Configuration Tool. When early features are enabled in development, changes cannot be pushed to production.
Users will need to disable the view before pushing changes to production. As a best practice, all users should double check edits made to existing features to make sure those changes are intended, prior to publishing.
UI Enhancements
As an ongoing effort, updates have been made to standardize the treatment given to elements that appear on multiple FastLink pages; namely, button size and spacing. The Cancel and Close buttons are now suppressed when Exit icons are configured as buttons, effectively removing the redundancy.
Account Verification – New Features/Enhancements
Verified Accounts API Enhancement
The get verified accounts API will now return a new attribute accountAgeClassification. Based on the actual account opening date or through an internal computation, the age of the account at the financial institution will be classified into one of the values:
Old– Account age is greater than six months.New– Account age is greater than one month but less than six months.Recent– Account age is equal to or less than one month.Unclassified– The account opening date is not available and the customer has not opted to retrieve transactions.
| Impacted API URL: |
GET /verification/verifiedAccounts |
Yodlee APIs – New Features/Enhancements
Real-time MFA Status
A new boolean attribute, isRealTimeMFA, has been introduced in the providerAccounts APIs and data extracts API response that gets updated based on the previous successful refresh status. This attribute lets the customer know beforehand if a providerAccount requires MFA. Customers can then invoke FastLink only for the MFA sites to get the user’s inputs; else, account refresh can be done using the API.
| Impacted API URLs: |
This would also be part of refresh notification.
Introducing the State Parameter
A new request attribute, state, has been introduced for the providerAccounts APIs. Passing the state parameter is mandatory during the update account process only for the REDSYS or PSD2 sites.
The state parameter key can be found in the authParameter attribute of the get provider or the get provider details APIs’ response. The value for the state parameter is present in the Authorization URL. The callback URL will be appended to the state parameter while updating an account.
| Impacted API URL: |
Open Banking – New Features/Enhancements
Manage Providers Enhancement
The provider registration screen in the Configuration Tool allows managing providers is an existing option available only after completing OB onboarding of any region or country. It can be accessed from the Settings drop-down menu of the OB application in the Open Banking dashboard. The provider registration option is currently unavailable for the development environment applications for all OB customers and the production environment applications for developer portal customers.
With this enhancement, all customers can access the provider registration screen by clicking Manage Providers for both development and production environment OB applications after onboarding. The Manage Providers screen will allow customers to register UK-manual providers and AU providers on a self-serve basis. This feature applies to all regions.
Sync Extract to include Migrated Containers
Sync extracts are not sent for the accounts only present in secondary provider account IDs. For example, if a user has multiple provider account IDs for the same credentials. As part of migration for multiple credential sites, if any account is part of the secondary provider account ID and not part of the primary provider account ID, the account is moved or re-associated from secondary to primary provider account ID.
To avoid missing notifications for this scenario and to ensure customers or users are notified of all the relevant changes, sync extract will include the notification for these migrated containers of secondary provider account IDs that were not included so far. This change applies to all OB providers across region and to customers that have OB enabled, inclusive of FastLink 2, FastLink 3, FastLink 4, and Yodlee API.
Proactive Sync Notifications during Runway
Sometimes, the sync notification is not sent for provider account IDs during the runway period. The notification only went out as part of runway completion or mass migration, due to which customers or users were not notified about the changes. The current notification is sent as part of a refresh done for the provider account IDs, and if the refresh does not happen, the notification is not generated. It could be blocked due to multi-factor authentication, non-refreshable error scenarios, or scheduled refresh being disabled for site/customer.
To avoid missing notifications, changes have been implemented where the sync notification would be proactive and not based on refreshes. Once the runway migration period begins, all the provider account IDs associated with the provider ID will be updated with the TO_BE_MIGRATED migration status. This will be done in phases to avoid an overflow of notifications for these provider account IDs.
This change applies to all OB providers across regions and applies to customer that have OB enabled, inclusive of FastLink 2, FastLink 3, FastLink 4, and Yodlee API.
Intent to Consent Screen - Transaction Duration Change
The transaction duration shown in the Intent to Consent screen is not in sync with the customer configured value. If the provider supports a higher number of transaction duration than the customer requested, the higher duration is displayed in the Intent to Consent screen, giving an incorrect user experience.
Enhancements have been done to verify the number of days of transactions requested by the customer and the transaction duration supported by the provider. Based on this, the least of these values will be displayed in the Intent to Consent screen, as that is the ideal duration supported for the aggregation attempt. This enhancement will be available to FastLink 3, FastLink 4, and Yodlee API customers.
Design Changes
Design changes have been implemented in FastLink 3 and FastLink 4 to ensure users do not add a new login during the edit connection flow.
- Button text updated:
- Existing: Edit Connection
- Updated to: Manage Accounts
- Link and text updated:
- Existing: Edit Credentials link
- Updated to: Update Login button
- Warning text updated:
- Existing: Click below if you would like to make a new login with new or other credentials.
- Updated to: Click below if you would like to add a login with new or other credentials. Make sure you aren’t duplicating any account login listed above.
US Open Banking
Review Existing Logins Screen Removed if Open Banking Migration is Complete
During the Open Banking edit account flow, the Review Existing Logins screen will no more be displayed if the Open Banking migration is complete. The Review Existing Login screen displays the previously linked credential-based accounts.
UK Open Banking
Renew Certificate
For UK Open Banking, the certificate renewal feature has been enhanced in the Configuration Tool. In the Configuration Tool, customer will now be able to view a notification in the Open Banking Dashboard the certificates are about to expire or has expired. Customer can renew not only an expired or about-to-expire certificate but also on a need basis even though the certificate has more time to expire. Based on this notification, customers can take appropriate actions to upload fresh certificates.
90 Day Consent - FastLink Enhancement
The UK regulatory body enforced a change in how consent and tokens expire and need to be renewed. The platform was enhanced to handle this change earlier in the March release; however, changes in the FastLink user experience are introduced as part of this release. A new consent status, Consent Repealed, has been added in the GET consent API response and Renew on the FastLink Manage Consent screen.
Should a provider decides to repeal existing consents before its expiry, such user consents will be displayed as Renew in the FastLink Consent Dashboard, and the user will be redirected to the bank for authentication and authorization.
AU Open Banking
Renew Certificate
In the Configuration Tool, customer will now be able to view a notification in the Open Banking Dashboard when a particular region’s certificates are about to expire or has expired. Customer can renew not only an expired or about-to-expire certificate but also on a need basis even though the certificate has more time to expire. Based on this notification, customers can take appropriate actions to upload fresh certificates.
Configuring Hard Deletion for ADRs
Currently, end users can choose if the accredited data recipient (ADR) can hard-delete the data or merely revoke the consent. Now, vide CDR rule 4.17(1)(A) – an ADR customer can choose during onboarding whether the users’ data needs to be deleted per their policy or Yodlee’s deletion policy. If the ADR customer decides to have their own data deletion policy, then FastLink would no longer give the option to the end users to hard-delete the data. This rule applies only to ADR customers at present.
Automatic Provider Registration
Once onboarded, customers have to register all available or supported providers manually. This enhancement gives an option to the customer to choose at the time of onboarding if they want to register all the available or supported providers automatically. When selected, within 24 hours of the approval or completion of onboarding, the auto-registration will be triggered, and providers will be registered without any manual intervention. This option will be available to both ADR and CDR Representative customers.
Notification Dashboard Enhancements
In the Notifications dashboard screen, a new Expiring Soon label has been introduced to indicate that the said consent will expire and the user has to act on it by renewing the consent.
CDR Representative Customer Engagement Model
A new customer engagement model CDR Representative Model has been introduced. This is for those customers registered in the AU region who do not have an accreditation in the region or are not an ADR (Accredited Data Recipient). As a CDR Representative, the customer would use Yodlee’s Accreditation (and the ADR number) to onboard to the open banking ecosystem and use Yodlee’s services as a Provider. The choice of the engagement model (ADR or CDR Representative) has been made available to the client during onboarding.
EU Open Banking
EU Open Banking Platform Support
The Open Banking support has been extended to European banks or providers. A new OB region EU has been introduced in the onboarding workflow that will facilitate multi-country customers to onboard and aggregate EU providers.
At present, only Agency/Coserve engagement model is offered that facilitates access to EU OB providers through Yodlee’s accreditation. Customers looking to onboard to EU OB with their own EU accreditation are NOT supported.
Redsys Support for EU
EU OB also supports Spanish providers, technically known as Redsys standard. All Spanish providers adhering to Redsys standard will be available to aggregate.