I suspect a great deal of peoples' annoyance with KYC isn't anything which is actually *required*, but is hitting poor *implementations* of it, sometimes with no clear path forward, which prevent them from doing the thing they actually want to or have to do.
This is often times because post-opening KYC is generally coming from exception handling in the financial system, and because (for the types of transactions likely to cause that in the lives of "typical people commenting about KYC") it is an edge case and not very designed for.
You often see (or worse, don't see) cracks in the abstractions, too, where you are dealing with someone passing a message from someone passing a message from someone passing a message from the underlying call site which generated the exception.
And it is very, very possible that the person you're calling (or faxing) has no idea how to get a message to the original source of the exception or what sort of information, specifically, would let it proceed forward.
But this can all be designed around, and should be.
But this can all be designed around, and should be.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
