If "the PC" or "the IP address" was not contractually agreed to be an authentication factor (that you thus should protect from unauthorized use), it's a terrible idea to use them for authentication, while also (presumably) putting all liability on the customer.
So basically, they can't put liability on the customer unless 2FA is used. The second factor is usually the credit card PIN.
Banks have to maintain a balance between convenience and risk of fraud.
And what is the standard of evidence for that?
> So basically, they can't put liability on the customer unless 2FA is used. The second factor is usually the credit card PIN.
That doesn't sound like a second factor? Or are you talking about POS transactions?
> Banks have to maintain a balance between convenience and risk of fraud.
Really, they don't. The bank should never decide to take on risks for me. There is nothing wrong with offering a feature where the customer can select to allow certain transactions without 2FA. There is everything wrong with forcing that feature on customers.
I'm very interested in your bank and how they do it, I'll see if voice 2FA is something feasible at my place. Could you share the bank's name though? Management likes to have solid evidence that someone else is already doing it when the security team proposes "weird solutions".
[0] https://ec.europa.eu/info/law/payment-services-psd-2-directi... , https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32...