So, what, barclaysfoo.bank, barclaysbar.bank, etc.? It's still clunky, and is still training users to accept an even more insecure naming pattern (because now they need to look for the barclays prefix and the .bank TLD; if either of those is off, it could be an attacker's site). Plus, is Barclays supposed to secure some assurance from the TLD operator that the prefix "barclays" is theirs alone, and that no other such domains will be created for other entities? That sure sounds like a namespace of its own at this point, except without the syntax making that obvious.

Never mind that Barclays provides more services than just banking, so a lot of their existing websites aren't suitable for .bank, and now you're gonna have their Web presence scattered to the winds across various TLDs.