I could see "identity verified" being a valuable thing from a UI perspective. You want to avoid an experience where people are being told "send the money to tr

I could see "identity verified" being a valuable thing from a UI perspective. You want to avoid an experience where people are being told "send the money to trustmereallytheaccountspayabledeptnojoke@company.com", or worse yet, a context-free account number. It's too easy to typo or have tampered malicious data on there. Some form of "identity verification" service solves that problem. Your commercial recipients can register their accounts, and when you put their contact info or account number in the "send to" field, the client can pull up and display the associated data. The customer can feel much more confident he is sending to the right firm. If you limit it to being opt-in, solely for registered legal entities with a documented paper trail, you can preserve consumer anonymity to a degree, and the exclusivity helps to make it part of the normal customer flow: all your major bills are going to go to validated recipients, so anything asking to be paid to an unvalidated account, or where the name doesn't match the expected one, calls for extra scrutiny. Yes, it can be manipulated, but I suspect gaming a federal payments system is the sort of thing that 1) leaves a hell of a paper trail and 2) would get prosecuted aggressively.