Mad Student Banking

Inspiration

As college students that constantly spend money, we look for ways to save money and extract rewards from any and every student discount or student reward program we encounter. We often struggle to save money and find it difficult to budget. But what if there was a way to enable minute savings on a daily basis while also giving back to the community? Mad Student Banking provides college students with the ability to achieve individualistic and societal welfare by encouraging college students to save and fund community-service organisations at the same moment. Our target audience is college students and our goal is to increase funding for social and community service based organisations.

What it does

Mad Student Banking is a banking system website that takes the total price of a purchase made by a student and rounds the price to the next whole number. This whole number is then withdrawn from the student’s checking account. Of this whole number, the price of the purchase is paid to the vendor and the remaining amount is used for savings and donation. The client may decide what percentage of the remaining amount may be saved and what amount may be donated. The client may also decide what type or organisation they would like to donate to – educational, homeless shelters, soup kitchens, etc.

How we built it

This website uses HTML, CSS, and Javascript to design and implement the website from scratch. The website creates a new bank account in the bank that employs our service. Upon creation of the bank account, a checking and savings account is setup. This employs the implementation of a BankAccount object, a CheckingAcconut object and a SavingsAccount object, which are interconnectedly coded to provide optimised functionality.

Challenges we ran into

We originally coded in java in backend and javascript and HTML for frontend. We hoped to employ Spring Boot to connect the backend with the frontend, but we encountered errors with the database that stores all client’s bank accounts as the database constantly reset when a new client utilised our service. Additionally, we had trouble implemented the functionality of the backend, which eventually we converted to frontend implementation. This occurred because of the difference in coding languages without a relevant server.