For the last several months, eTransfers initiated from my desktop browser (Firefox on Linux, same as you) have required confirmation via the RBC app on my iPhone. Definitely seems like they have multiple scales of trustworthiness for people/devices/activity. Kind of wish they'd be more transparent about what they are, but I guess that sort of transparency can easily become a vulnerability.
replyMy phone app isn't verified, so it just sends an RCS message to my phone number. Works for now, but who knows what'll happen.
replyThese are also obnoxious - RBC has checked whatever box makes Google's RCS web app refuse to render them, so if I'm am my computer, now I have to get up and go find my phone so that I can manually input the code.
replyCreate a separate firefox profile, all defaults, no addons, and use that only for RBC/banking.
replyThis can easily be launched from the command line via args, when needed.
Unless you let all the tracking scripts, and auth scripts load, it thinks you're evil.
Similar experience. No real problems. However, RBC limits the amount I can transfer to 2k per day from browser and like 5k per day from the app.
replyI don't send anything from TD, but if I buy anything online half the time it forces a 2FA which requires signing into the app and confirming the transaction. I imagine signing into the app might not work nicely if I was on LineageOS.
I've never used the TD app, but the TD website seems to be designed to be as inconvenient as possible, down to disabling pasting on 2FA input fields.
replyUsed to be the case, yes. However even web-initiated EMTs trigger device confirmation. RBC seems to have made this mandatory for at least my account as of this summer.
reply