Essential Attributes
Non-secret: An alias should be non-secret so that it can be openly communicated to the party who is making a payment
Works Independently: An alias should work on a standalone basis – the address alone should be enough to receive payments from payers without having to provide additional information
Desirable Attributes
Durable: An alias should be durable i.e., something that doesn’t have to change frequently
Changeable: An alias should be easily and instantly changeable by the end user
Accessible: An alias can be easily shared by end user (either because it is easy to remember or to copy and paste)
Participant Agnostic: An alias should be participant agnostic, i.e., customers belonging to different service participant should be able to make payments using their alias
Supports Multiple Use Cases: An alias should be usable for multiple types of payments