Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `amp_init` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `schema-and-structured-data-for-wp` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/u885321871/domains/fintechinshorts.com/public_html/wp-includes/functions.php on line 6114

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `amp_init` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `schema-and-structured-data-for-wp` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/u885321871/domains/fintechinshorts.com/public_html/wp-includes/functions.php on line 6114

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `init` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `schema-and-structured-data-for-wp` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/u885321871/domains/fintechinshorts.com/public_html/wp-includes/functions.php on line 6114

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `init` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `schema-and-structured-data-for-wp` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/u885321871/domains/fintechinshorts.com/public_html/wp-includes/functions.php on line 6114
UK’s PRA fines HSBC £57m for “historic depositor protection failings” | Fintech InShorts: Latest fintech news, analysis by experts

UK’s PRA fines HSBC £57m for “historic depositor protection failings”

BankingBusinessFinTech

Less than 1 min.Read

UK’s PRA fines HSBC £57m for “historic depositor protection failings”

February 3, 2024

HSBC was fined £57.4 million by the UK’s Prudential Regulation Authority (PRA).
Fine issued to HSBC’s European holding company (HBEU) and UK subsidiary (HBUK) for historic depositor protection failures.
Depositor Protection Rules by the Bank of England were violated, leading to improper implementation over many years.
PRA found HSBC failed to provide information for Financial Services Compensation Scheme (FSCS) reimbursement and misidentified eligible deposits.
Failures occurred between 2015-2022 for HBEU and 2018-2021 for HBUK.
99% of beneficiary deposits were incorrectly marked as ineligible for FSCS protection.
HBEU failed to promptly inform PRA about problems, undermining the firm’s readiness for resolution.
HSBC’s cooperation in the investigation led to a reduced fine of £57.4 million from the original £96.5 million.
Deputy governor for prudential regulation, Sam Woods, emphasizes the importance of banks complying with resolution requirements.
HSBC is “pleased to have resolved” the matter, citing cooperation and efforts to address issues.
Bank of England and PRA introduced revised policies for faster investigations, establishing incentives for early cooperation and admissions.

Hot this week

Topics

Related Articles

Popular Categories

FinTechBankingBusinessFundingAIPaymentsPartnership

spot_img

spot_img

Previous article

Google’s Bard chatbot gets the Gemini Pro update globally

Next article

The Bank of Missouri looks to bring digital banking products to fintechs with i2c partnership