python-vipaccess VS standards

Yes, but it’s a minor hassle. I do it for every VIP Access site though. https://github.com/dlenski/python-vipaccess

My apologies, I guess I read these lines wrong.

https://github.com/dlenski/python-vipaccess/blob/cc4366f7bce...

On fidelity you can use the symantec vip option, but use a normal TOTP application (I use Keepass + yubikey). You can generate the SYM number using this https://github.com/dlenski/python-vipaccess

The project and more info and instructions can be found at this github repo: https://github.com/dlenski/python-vipaccess

I recommend putting everything behind software two factor. This option is only available via Symantec VIP access. If you have your own preferred 2fa management software there are ways to extract the Symantec VIP access. See https://github.com/dlenski/python-vipaccess. Definitely vet the project before using it, which should be easy since its open source.

You simply need to enroll in with https://github.com/dlenski/python-vipaccess and then you can import the 2FA secret in literally any 2FA app.

You can use https://github.com/dlenski/python-vipaccess to generate standard 2FA tokens you can add to Google Authenticator, etc.

UP is the Australian only financial institution that I'm aware of which does open banking correctly. The Big 4 literally torpedoed the attempt to provide consumers freedom over their own data when the matter was raised. It's everything you don't want in an open data scheme, and it's certainly not there to empower consumers.

I’ve been reading about the Consumer Data Rights standard https://github.com/ConsumerDataStandardsAustralia/standards which provides programmatic access to bank accounts of supporting banks.

https://github.com/ConsumerDataStandardsAustralia/standards

This is a problem discussed here as well. Generally big banks are advocating getting rid of screen scraping and moving to API but most fintechs are smaller and they don't want to change and there is little appetite from Govt. to force them.