**Design your own Payment Gateway / Payment wallet / Payment ecosystem [ even you can assume you are the Bank but not mandatory ]\nThere can be many aspects and variations of payment systems.  A Payment System is very broad , you can play a role of gateway/3rd Party/ provider/merchant...etc. Cook up your requirements and choose your approach** \n\n**Note**:\n\n Choose your role and MVP. Drag to your conclusive system design. Your design should be Technical ( not on UI  ) and around following topics :   \n           a. Functional Requirements(in short)  -   description of the service , activities each user role can perform , features the system supports\n           b. Non-Functional Requirements (in short)  -   Performance / Availability / Scalability / Security Encoding / Maintainability / Extensibility\n           c. Any Extended Requirements you can think of is essential(in short) - Double spend / transaction timeout / Fraud detection\n           d. Design consideration  - \nIimpose size limit on any data ? \nRead and Write volumes and based on latency throughput , any trade-off you might choose to build your system \nAuthentication models best fitting your system and why ? How your system prevents anti-money laundering ?\n           e. Capaity , Traffic & Storage Estimation\n           f.  Exposed and Internal APIs + Parameters\n           g. Entities & their attributes - e.g User: userId, name, email, address, dob, creationDate, lastLogin, etc.\n           h. Database Schema +  description of essential relationship\n           i.  Choice of your storage and tradeoffs - Metadata storage / File Storage / Cloud Storage, Transient Data Storage, Object Storage\n           j. Any special Data Structure or Algorithm needed for any specific purpose ? \n           k. Any specific service we need as a - BackGround/Off-line/Pipeline Services for Synchronization OR Message-durability-scalability-delivery\n\t\t   l. Component Interaction diagram\n\t\t   m. Data Partitioning , Sharding,  Replication     -      Range Based / Hash Based / or any custom key scheme \n           n. Pull/Push/Hybrid the Notification\n           o. what you would Cache ? Justify your caching strategy ?\n           p. Reason you choices for  Encodings , Permissions and Securing your aplication -  Double spend / transaction timeout / Fraud detection\n\nRelated blogs / topics / architecture diagrams are enncouraged\n\n  \n\n\n\n

Design your own Payment Gateway / Payment wallet / Payment ecosystem [ even you can assume you are the Bank but not mandatory ]\nThere can be many aspects and v