This may perhaps sound like nitpicking, but to be quite correct, neither the
Directive (EU) 2015/2366 […] of 25 November 2015 on payment services in the internal market […], already in force since early 2018 (**LINK**),
nor the follow-up
Commission Delegated Regulation (EU) 2018/389 of 27 November 2017 supplementing Directive (EU) 2015/2366 […] with regard to regulatory technical standards for strong customer authentication […], which comes into force on September 14th this year (**LINK** — see p. 23 ff), and will be what Bob referred to in his initial post
actually obliges anyone to use any specific technical solution, such as one-time codes sent to a mobile phone, for two-factor authentication.
What will indeed be required for many (or even most, although there are some exceptions) electronic payment transactions as of this September is what the directive calls strong customer authentication. This is defined as
"an authentication based on the use of two or more elements categorised as knowledge (something only the user knows), possession (something only the user possesses) and inherence (something the user is) that are independent, in that the breach of one does not compromise the reliability of the others, and is designed in such a way as to protect the confidentiality of the authentication data".
For my part, it is already the case that in most instances when I want to pay for something online with my credit card (issued by my bank here in Belgium), at the final stage of the payment process I am redirected to a page (managed, I think, by the banks and/or the various payment and or card providers, but that doesn't really matter), where I have to type in a one-time code that I generate with my credit card and the bank-issued card reader that I also use whenever I log on to the on-line banking services of my bank. No mobile phone is involved at any stage.
However, it is indeed the case that when I use another card, which I have from a different source, I will usually receive a text message to my mobile with a one-time code to authenticate the transaction.
This difference is entirely down to choices made by those who have issued the different cards, and only down to the directive in the sense that they both fulfill the requirement for strong customer authentication by combining at least two elements as defined above.
Likewise, I have myself opted to activate two-factor authentication via text message whenever I log on to my PayPal account, for added security.
It may thus well be, Bob, that the two banks that have communicated with you will actually demand that their customers are able to receive text messages in order to carry out on-line payments, but if so (and obviously I have no idea whether that is really the case, or if there will be alternatives available) that will be because of choices made by those banks, and not because the directive told them that that was how they had to do it.
The technical nitty-gritty and details on solutions are currently being trashed out by several working groups under the aegis of the European Bank Authority (see **LINK**).
That said, I personally think that while the intentions of the directive and what flows from it are on the whole good, and should pose few if any problems for a very large group of people (myself included), as in so many other instances not enough attention has been given in the implementation to workable alternatives for those who, for whatever valid reasons, really cannot (or can only with great difficulty) make use of the mainstream solutions on offer. If a person decides to be a stick-in-the-mud, he or she should perhaps not complain too hard if eventually s/he ends up with rather muddy feet and little change of view, but it is alas the case that market forces (outdated methods, alternative procedures and/or back-up options used by comparatively few are of course more expensive per use to develop and maintain than mainstream solutions) are ever too likely to make a stringent cost/benefit analysis to the detriment of those in a weak bargaining situation.
Mattias