Link an Account
Enable your customers to link their bank accounts via Open Banking to fund payments within a payment run.
To link an account, you will need:
- To complete the buyer's onboarding
- A logged-in user with the Controller role
- Configure the Open Banking redirect URL in the portal via Settings > Application Details
With Weavr's solution, you are not required to become a Third Party Provider (TPP) or an Agent of a TPP. Instead you can use our UI components to embed the Open Banking flows in your product.
Embed the Account Information Service (AIS) UI Component
Follow the AIS UI Component integration guide to learn how to embed this Open Banking flow within your product.
For the UI component to work, you must configure the Open Banking redirect URL in the portal. This URL will be used to redirect the user back to your product once they completed the funding process.
The UI component will request the user to select their bank. Once selected, the user will be shown the consent request for Weavr to access their bank account information. If the user clicks on Cancel the component will trigger a decline event which should be handled by the application.
To confirm the consent, the user will be redirected to their Bank's portal to approve the consent request. In the Banking portal, the bank will ask them to authenticate themselves and will confirm the bank account to be shared.
If the user approves, they are redirected to your product on the configured Open Banking redirect URL. If the user clicks on I Don't Consent the component will trigger a decline event which should be handled by the application.
Extend an AIS consent
AIS consents are granted for up to 90 days, after which, users are required to extend their consent to continue using the associated Linked Account.
To extend an AIS consent, you will need to embed the AIS UI Component in your application while also specifying the linkedAccountId parameter of the Linked Account that you want to extend the consent to.
Once consent is extended, Weavr will refresh the date and time of the consent and your end-user will be able to access the Linked Account for a further 90 days.
For further details, follow the Extend AIS consent examples here.
AIS consents can be extended at any point during or after the 90 days window.
Extending an AIS consent before the 90 days pass
When extending the AIS consent before the 90 days pass, the user will be shown a consent renewal request screen for Weavr to continue accessing their bank account information. If the user confirms the consent, the UI Component will trigger an accept event.
If the user clicks on Cancel the component will trigger a decline event which should be handled by the application.
Extending an AIS consent after the 90 days pass
If the user gave their consent more than 90 days ago, the consent would be set to EXPIRED. At this point the consent can still be extended, however the user will be shown an expired consent screen. To renew the consent, the user will be redirected to their Bank's portal to approve the consent request. In the Banking portal, the bank will ask them to authenticate and re-confirm the bank account to be shared.
If the user approves, they are redirected to your application on the configured Open Banking redirect URL. If the user clicks on I Don't Consent the component will trigger a decline event which should be handled by your application.
Providing the linkedAccountId is an optional parameter to be used only when extending an AIS consent.
Linked account update event
Once the user approves the consent, a linked account update event is sent to you with the related bank account details.