PairPay

Inspiration

Everyone in our team has an online banking system for their credit card payments. We brainstormed issues that revolve around online banking and we all agreed on the complexity around having multiple online banking accounts and apps, and having different due dates for the payments. We stumbled across the Wallet App on Apple iPhones and realized that similar to Apple's version of having all cards in one wallet, we can also have the payments of each card available in one spot as well. Therefore, we wouldn't have to navigate through multiple applications to make a payment, and rather, it would be in one application.

What it does

The prototype PairPay shows how the mobile app would look to the users. Because security is a concern with banking, we coded a prototype of how the security questions would be asked to the user trying to log into their accounts. In general, the purpose of PairPay is to have the summary of transactions, balance, and payments of multiple credit cards onto to one application as it would be very time efficient for users.

How we built it

Using VSCode, we coded the security feature using Java. This code specifically demonstrates that only when the security question is answered correctly, will it then allow the user to log into PairPay. The answers to the security questions are Carter, Honda, and 1973, which are based on our user persona. Then, we used Figma to build the prototype for the mobile app. Because one the purposes of PairPay is to be time efficient for the user, we believed that navigating in the app should also be easy and time efficient.

Challenges we ran into

Initially, we wanted to connect the Figma prototype into the code for the security features. We attempted to use the java import packages we believed would help, but the two features would not connect. Therefore, we opted to have a redirect link to the Figma prototype if the security questions were answered successfully.

Accomplishments that we're proud of

We are all very proud of the design of the Figma prototype and of our idea. We are proud of our accomplishments in completing a design for PairPay and executing our ideas completely.

What we learned

We learned that coding and designing requires a lot of preplanning and that there are stages in completing a project. For instance, in design we needed Lo-Fi Wireframes to portray the ideas we had for PairPay before we actually made the prototype.

What's next for PairPay

We believe that PairPay definitely has potential to be used in real life. The next steps of PairPay would be to translate our Figma prototype into code.

Built With

• figma
• java