Encourage use of bank-account-verification-frontend

[lyndsp]

Bank details

Bank account verification frontend (generic service)

Overview

When an HMRC service needs to ask a user for bank details, and the user experience will be very close to the Gov.uk pattern, we recommend HMRC services use the bank-account-verification-frontend instead of building their own frontend.

This provides the benefits of:

• Reduced development cost and lead time.
• Reduced operation and upgrade costs.
• Standardised journey segment across multiple services.
• Integration with the bank-account-reputation service

We've presented this service to London and Worthing design communities and they suggested we put it forward for inclusion/reference in the HMRC Design System to encourage it's use.

Other components or patterns you've tried

HMRC services currently build their own version of the Gov.uk pattern, and then integrate it with the bank-account-reputation service. They often adapt this pattern in various ways. The aim of this new service is provide a standard, but customisable journey for capturing bank details.

Research on this pattern

We've built this service based on the Gov.uk pattern. We've added a page to the journey that encourages the user to confirm the bank details before continuing, if the bank-account-reputation service can't confirm the account exists. We haven't researched this addition, but will explore having this done by the JSS and/or JRB teams.