So I'm building a payment interface, and we allow customers to pay with Checking or Savings accounts by entering their 'routing number' and 'account number'. The routing number is an identifier that's unique to the specific bank for which the account belongs, and the account number is the identifier of that customer's account in that bank.

A requirement bubbled up that we validate the routing number as the user is typing it (on 'blur'). I like that idea, as it hopefully stops a mistyped routing number from causing an invalid payment. However, the requirement also states that the project owners want the Bank Name to appear once we successfully validate it. (The code for this is pretty easy, btw...)

My problem is, **why would I want to show the user their own bank name?** What value does that have? All users will assume, by default, that they entered the routing number correctly. Its not something you have memorized, and its not something you just guess at, so to enter it, you must be looking at your checkbook or bank statement right there.

I am concerned because for the rest of the app, having text 'appear' as users type **ALWAYS** indicates an error. A malformed field, or a blank required field, etc. So in this case, the bank name would appear but would mean a successful action, not an error, which is kind of going against the grain.

And what value does the bank name add? I already know the name of my bank and I'm already going to assume I typed it right. Furthermore, the likelihood that I'll mistype my routing number, but accidentally get a proper routing number for some other bank is very, very unlikely. In all likelihood, a mistype will just result in the error of 'No Bank Found!' appearing, which matches the pattern of the other errors (being that errors cause labels to appear, and correcting them causes the label to disappear).

**Am I being correct in resisting this requirement of showing the bank name as pointless and potentially confusing?**