Currently, we classify a number of banks as having 2FA, when they only require it for certain transactions, not for logging in to their website. My question is whether or not we should change any of the banks listed below to tfa: No, add an exception to each of them, or find a way to include a transactional flag on the website.
Below is a list of banks that do not currently fall under our definition of 2FA, despite having the tfa flag set to Yes. I'm curious as to how everyone feels we should handle these types of situations with these banks and any additional ones going forward.
- Barclays UK's PINSentry doesn't qualify for our definition of 2FA, as their website shows that it is only required for certain transactions.
- Citibank Australia's OTP doesn't qualify for our definition of 2FA, as it seems that they only require it for certain transactions. Their website says:

- Commonwealth Bank of Australia's NetCode doesn't qualify for our definition of 2FA, as their website states that it's only required for certain transactions.
- first direct's Secure Key doesn't qualify for our definition of 2FA, as it can be bypassed using a password to login. Their website says:

- HSBC's Secure Key doesn't qualify for our definition of 2FA, as their website shows how you can choose the "Without Secure Key" tab when logging in to bypass 2FA.
- Nationwide Building Society's card reader doesn't qualify for our definition of 2FA, as the it can be bypassed using a password to login. Their website says:
You can still log in with your memorable data and passnumber, but by using your card reader you may reduce the number of times it's needed to confirm your online transactions.
-
Natwest's card reader doesn't qualify for our definition of 2FA, as they only require the card reader be used for certain transactions. In fact, their website specifically says:

-
Santander's SMS-based OTP doesn't qualify for our definition of 2FA, as they only require an OTP for certain transactions. Their website says:

-
State Bank of India's OTP application doesn't qualify for our definition of 2FA, as they only require an OTP for certain transactions.
Currently, we classify a number of banks as having 2FA, when they only require it for certain transactions, not for logging in to their website. My question is whether or not we should change any of the banks listed below to
tfa: No, add an exception to each of them, or find a way to include atransactionalflag on the website.Below is a list of banks that do not currently fall under our definition of 2FA, despite having the
tfaflag set toYes. I'm curious as to how everyone feels we should handle these types of situations with these banks and any additional ones going forward.Natwest's card reader doesn't qualify for our definition of 2FA, as they only require the card reader be used for certain transactions. In fact, their website specifically says:

Santander's SMS-based OTP doesn't qualify for our definition of 2FA, as they only require an OTP for certain transactions. Their website says:

State Bank of India's OTP application doesn't qualify for our definition of 2FA, as they only require an OTP for certain transactions.