When members authenticate for MFA, they use a one-time passcode, which also gives them the opportunity to register their device. The next time they log in on a registered device, they may not be required to use a one-time passcode.

Situations where a one-time passcode WOULD be needed include the following:
  • Your configuration for MFA in Tool #569 Online/Mobile/Text Banking VMS Config requires a one-time passcode be sent for authentication each time the member logs in. 
  • Your credit union has set the number of days for this passcode to be valid, and that number of days is expired. Therefore, a new passcode sign in is now required by the system.
  • Your credit union changed your settings in the MFA configuration in Tool #569 to now require a passcode, for example, shortening the number of allowed days.
  • The member changes to use another browser on their device. For example, they authenticated with Chrome, and then login with a Firefox browser session. Registration is per browser.
  • The member authenticates via the mobile app and then uses a browser or vice versa. (These different environments can have a different number of expiration days in the MFA configuration in Tool #569, so this can also play a factor.)
  • The member gets a new device, such as a new phone or authenticates with a device they have not authenticated with already.
  • The member downloads the app on their phone and authenticates with the new app.
  • Updates to browsers, operating systems, and other network or workstation components may also have an effect.
  • A member authenticates using MFA to one membership and then (on the same device) authenticates with MFA to another membership. When they then log into the original membership, they will be required to authenticate with a one-time passcode again.  (See further notes in knowledgebase item below.)