@Julien Berthomier: yes. 100%. Definitely Station. I can only get into the account once I disable the Station extension. I agree it's weird..I would not have expected that considering its functionality to the end user, but I don't know the actual implementation so....

@Julien Berthomier: Just a note. It's the screens after a successful login. The login screen itself is not the problem.. It's the screens afterwards.

I can recreate it by disabling ALL my extensions in Chrome, and enabling just Station, and trying to log into capitalone.com. If I disable Station and try again, I'm able to login.

@Julien Berthomier: Let me know how I can help - I can do a screen share if needed.

@Taka Torimoto: Thanks that information helps a lot already. Can you send us a screenshot of your console?

To do that, right after trying to log in to Capital One, right click on the page -> click "Inspect" -> then open the tab "Console". A screenshot of what it shows would help a lot (see my screenshot as for what it looks like)

@Julien Berthomier: Here you go. I hope this helps!

@Taka Torimoto: Thanks this helps a lot. What happens is that the Capital One app when logging in tries to communicate with our extension (for a reason we ignore, it's a very unusual behaviour for an application, it's the first time we see something like that). We will need to fix it by making sure our extension isn't active when you try to log into. It's quite a big change to make in our code. I have added it to our list of bug fixes but it seems like a really rare bug unfortunately.