Skip to main content

Breaking Change (March 2025) Open Banking Fallback - Manual Account Linking and Funding

· 6 min read

As mentioned in our previous update, we are introducing another way for your customers to link an account and fund their payment runs to cover instances when their bank is not supported via Open Banking. This initiative involves a number breaking change to the current AIS, PIS and Linked Account Declaration UI Components.

Effective:

  • 11 February 2025 on Sandbox
  • 04 March 2025 on Live

Open Banking Fallback - Link an Account​

Users with the Controller role can now manually link their bank accounts, depending on the jurisdiction, without relying on Open Banking.

1. Updated UI component to include the manual option​

To link an account manually, you can still load the current AIS UI Component, were the component has been updated to include a new URL, "Can't find your bank?" at the end of the UI Component as pictured below:

AIS UI Component

Breaking Change

To support manual account linking in addition to Open Banking, we have renamed the AIS UI Component weavrComponents.prompt.ais to weavrComponents.prompt.linkAccount. This change ensures our UI component reflects its broader functionality and aligns with evolving user needs.

2. Entering the bank account details​

When the "Can't find your bank?" option is selected, the user will be directed to a new screen where they must enter their bank account details. The following key fields will be required:

  • Business Account Name: The registered owner’s name of the account at the external bank or PSP. This should match the name on the external account to ensure successful linkage and compliance with verification steps.
  • Bank Name: The name of the bank.
  • Bank Country: The country in which the bank or financial institution holding the account is located. This is essential for regulatory and compliance purposes.
  • Account Information: The IBAN or the combination of the Account Number and Sort Code of the account at the external bank or PSP. This uniquely identifies the account within the financial institution and is necessary for processing transactions.
webhook information

Once the bank account details are submitted, a Linked Account Update Webhook event will be triggered. This event will include the new id of the Linked Account and its status will transition to PENDING_CHALLENGE.

3. Declaration of Ownership via SCA Challenge​

Ensuring that the registered linked account belongs to the Identity attempting to link it is crucial. As part of this process, declaration of ownership is conducted through a Strong Customer Authentication (SCA) challenge, which must be completed by a user with the Controller role.

Upon initiating the Linked Account registration, the Controller user must successfully complete the SCA challenge to confirm ownership.

webhook information

After successful completion, a Linked Account Update Webhook event will be triggered updating the linked account status to PENDING_FUNDING.

4. Control Check through a test funding Transaction​

After successfully completing the SCA process, user must demonstrate control over the external account by performing a test funding transaction. The UI component will redirect the user to the final screen, displaying the following details:

  • Amount to be sent
  • Account number
  • Sort Code
  • Reference Code
danger

This step is critical to verify that the registered identity controls the account. It is essential that users include the reference code in the funding transaction. Failure to complete the test funding transaction will result in the linked account remaining in the PENDING_FUNDING state.

The funding transaction will not be needed for a Linked Account linked via Open Banking.

simulator to test on Sandbox

To assist you with testing the funding test transaction, we have created a new simulator accessible via our API here.

Webhook information

Once the plugin receives and validates the test funding transaction a Linked Account Update Webhook event will be triggered, updating the linked account status to LINKED.

Open Banking Fallback - Fund a Payment Run​

Your users with the Controller role will be able to use the newly created manual linked account to fund the payment run.

1. Updated UI component to allow funding using a manual linked account​

To use the manually linked account, the user can load the current PIS UI Component, were the component will have a new screen

Breaking Change

To support funding of a payment run with a linked account in addition to Open Banking, we have renamed the PIS UI Component weavrComponents.prompt.pis to weavrComponents.prompt.paymentFund. This change ensures our UI component reflects its broader functionality and aligns with evolving user needs.

Linked Account Declaration UI Component​

When adding a Linked Account via Open Banking a user with the Controller role. of the Identity must complete an Strong Customer Authentication (SCA) challenge to confirm ownership of the Linked Account.

Currently, the SCA declaration process is handled using the Linked Account Declaration UI component.

State of the Linked account

The state of the linked account will to be SCA challenge will remain at PENDING_CHALLENGE.

What's Changing?​

The SCA ownership declaration will now be managed through the new Linked Account UI component, formerly known as the AIS UI component.

This change offers a more streamlined and efficient solution for linking accounts.

When loading the new Linked Account UI component, you must provide the following parameters:

  • callbackUrl
  • state
  • linkedAccountId
danger

Previously, only linkedAccountId was required. Please ensure your integration reflects these changes:

webhook information

Linked Account updates will remain intact, and you will continue to receive the Linked Account Update webhook event with updates to linked accounts.

Breaking Change Updates​

To make the UI component more generic and to support the Open Banking fallback of the manual account linking and funding initiative, we have renamed the below UI Components:

You will also need to start handling the new PENDING_FUNDING state. This state will be sent to you via an event in the UI component and in the Linked Account Update webhook event.

Also, the SCA ownership declaration will now be managed through the new Linked Account UI component, formerly known as the AIS UI component.

When loading the new Linked Account UI component, you must provide the following parameters:

  • callbackUrl
  • state
  • linkedAccountId

Action Required​

Rename the UI Components as follows:

If no action is taken​

Although this is a small change, if no action is taken, you application will not be able to load the AIS and PIS UI Components accordingly, resulting in your customers not being able to link an account or fund a payment run.

Also, your application will no longer support SCA declarations for Linked Accounts through Open Banking, potentially disrupting account link functionality.

Detailed instructions are available in our documentation on how to: