You could use a password vault on your PC or mobile device that has a master password and stores all of your other passwords in an encrypted container. You could use a service in the cloud that does just about the same thing. All of these have one flaw in common: They are storing a static password. MYDIGIPASS.COM does not store static passwords.
Functionally, the user logs into a web app, which in turn queries the MYDIGIPASS.COM server. The server then logs in for the user. But there's a bit more going on in the background. First, the user has put an app on their mobile device that reads a QR code on the site to which the user wishes to login. There is a first-time authentication ritual and after that the user simply navigates to the target website and clicks on the MYDIGIPASS.COM secure login button.
The website redirects the browser to the authorization endpoint and the user then enters the MYDIGIPASS.COM password and authenticator and a one-time password is generated. The website then conducts a backend dialog with MYDIGIPASS.COM and exchanges the one-time authentication for a one-time token, which the website uses to authenticate the user. Users are then enrolled using a self-service model and if a user tries to login without pre-registering at the site, they are redirected to a registration page. The whole system is supported at the website - the bank, online merchant, etc. - and the cost of the service usually is passed on to the consumer.
Adding MYDIGIPASS.COM to a website or application is also straightforward. VASCO has a complete developer website that uses an API that is easy to assimilate.
Real two-factor, one-time passwords, simple to use and solid strong authentication.