Back in October last year, fscom director Alison Donnelly wrote a blog on the FCA’s consultation on new rules for payment and e-money institutions. As explained in that blog, due to FCA concern with how some e-money and payment institutions have communicated with their customers in the past, certain sections of the FCA Handbook are being applied to payment and e-money institutions.
With only four months to go to the final PSD2 implementation date of 14 September 2019, all payment service providers must make sure they are urgently progressing plans to meet the additional regulatory obligations or to confirm that their obligations are met.
In my previous blog, I outlined the basic requirements of the new obligation, brought in under PSD2 (the second Payment Services Directive), for all payment service providers to apply strong customer authentication (SCA) in certain circumstances. SCA has to be applied both when accessing payment account information and when initiating a payment transaction meaning that a customer checking their account and then paying a couple of bills would have to go through SCA multiple times in one session, which is far from ideal on the user-experience scale. To avoid this, you, as a payment service provider (PSP) can apply one of nine exemptions, if circumstances permit.
Strong customer authentication (SCA) is a valid attempt by the EU to curb electronic payment fraud, including ‘card-not-present’ fraud. From a glance the concept is fairly simple, it will be a regulatory obligation to apply two factor authentication (2FA) to the electronic payment process. However, it’s not all quite as simple as that as SCA has more requirements than just the frequently touted 2FA. This blog will provide the basics on SCA and subsequent blogs will go into more detail on the exemptions and how SCA differs from simple 2FA.
Better customer service, cleaner user interfaces, simpler language, spending insights and even gambling blocks…digital banks or ‘challenger banks’ as they are commonly referred to, have taken the UK banking market by storm and with features like these, no wonder they are signing up thousands of new customers every day. However, as the large incumbents awaken from their slumber, are they starting to realise they must fight back no matter how much they make light of these new players?
Jamie Cooke, Managing Director of fscom, gives his opinion...
As we marked the first anniversary of PSD2 implementation (at least, in the UK!) this week, there will doubtless be numerous conversation pieces and reflections about the success of PSD2 so far – and its relationship with Open Banking – and what more delights both have to offer in 2019, the year the UK is supposed to leave the European Union.
Under PSD2, all payment services providers, including credit card providers, money remitters and e-money issuers, account information service providers (AISP) and payment initiation service providers (PISP) are required to file reports in relation to confirmed fraudulent activity, known as the REP017 report.
The REP017 report provides the means for firms through Gabriel to provide the FCA with statistical data on fraud related to different means of payment which in turn is aggregated and shared with the European Banking Authority and European Central Bank.
The first submission for REP017 is scheduled for 31st January 2019 covering the period from the 13th January 2018 to 31st December 2018. For this period, the FCA have published an interim REP017 report to be completed.
This blog aims to give a high-level overview of who REP017 applies to, what transactions it captures and how the data on fraudulent transactions need to be categorised.
Assurance, or the use of auditors to search for problems at firms, can be very useful to the regulated community in all manner of ways, especially during the authorisation process or in respect of the EU's Payment Services Directive.