Understanding the impact of the growing popularity of UPI and looking at consumer needs by redesigning Google Pay to implement an efficient system mirroring the needs of society

This is an attempt to duplicate the well-known UPI payment application and comprehend the current issues with Google Pay.

Google Pay is probably one of the most loved mobile applications in India today, as most people have started replay in the world UPI (Unified Payments Interface) payments with the word Google Pay. The product name being replaced by the brand is the result of a lot of people in the country who use Google Pay to make payments. In a similar vein, Google Pay has developed and expanded to include several client touchpoints for enabling various interactions related to payments and basic money management. Keeping in line with Google’s philosophy Google Pay has a simple yet effective and above all efficient interface with high-end visual touchpoints. But as the path to payment gets more complicated, it becomes important to segregate the payments into different categories, mainly because ‘Searching’ for options becomes easier. The scope of the project is to look at the glaring problems that Google Pay has today and find a solution for these people.

Since the efficiency quotient has taken a fall both functionally and visually due to the unnecessary stack-up of payees, this redesign of G-Pay is necessary.

Most customers who are either working or are small-time business owners and have been using GooglePay as the primary UPI gateway for both sending and receiving payments for a substantial time find it difficult to find payees, especially when they are in a hurry. They find the system complicated, with multiple levels of interactions with payees at different intervals with each payee. They struggle to make the proper connections and make mistakes along the way, and the trust quotation plummets.

The Design process here involves a longer understanding of the problems currently present in the mobile application. So the ‘Discover’ part of the process involves investigating the current pain points both in the visual and system of the application coupled with speaking to consumer baskets who showcase the problems they face.

A look at the main Stakeholders of Google Pay

Stakeholder Analysis of Google Pay

To comprehend the needs of society vs the requirement model that Google Pay presents, a thorough examination of the application is essential.

Understanding the primary problems through some storytelling examples.

Laborde, S. (2023, August 8). The most interesting Google pay statistics in 2023. The Tech Report. https://techreport.com/statistics/google-pay-statistics/#:~:text=4.83%20Lakh%20Cr.-,Google%20Pay%20Statistics%20%E2%80%93%20Market%20Size,which%20is%20leading%20with%2052.69%25.

The Rose Thorn Analysis of Google Pay

Understanding the User

Because Google Pay has such a large user base, user personas that include comparable objectives, desires, and pain points have been built by analysing users in related professions. This would encourage cooperation and coordination among those who have related requirements in order to realise the ultimate goal.

The deep dive into an understanding of User persona through looking at professions and necessary needs and pain points for each of these professions

Understanding the Features of G-Pay

A practical view of how the feature mapping was mapped

Personal Payment System

The Debacle between findability and Discoverability is an argumen that most

The feature mapping for Google Pay is categorised into three groups based on the features that require implementation the most urgently. This feature mapping, which is based on the needs of the person, illustrates the size of the implementation. ‘P1’ features are the most urgent and P3 features are the least urgent in the scale of proximity of implementation vs man power.

Understanding the importance of features through wireframes