iPaybetter

iPaybetter is a fintech product that allows users to transfer money from their debit and credit cards to recipients’ bank accounts.

We collaborated with the client to craft a flexible solution offering single, scheduled, and recurring payments. Users can easily manage their recipients, payments, payment methods, and invoices. Moreover, they can get full payment analytics and participate in the affiliate program.

iPaybetter started as a minimum viable product, and we are still developing it leanly, introducing new features at the end of every two-week sprint.

iPaybetter

We are responsible for

DevOps
Frontend Development
Backend Development
UX Design
UI Design
summary-box-icon

Scope:

Dedicated agile team


Team:

7 people


Duration:

22 months – ongoing

Individual Users

Individual users use iPaybetter to manage all sorts of payments, from rent to utilities, while enjoying all the benefits of their cards, like interest-free days, bonus points, and rewards on payments they could not before. Plus, with international money transfers, they get lower transaction fees as well.

Business Users

Business users can leverage their credit card line’s interest-free days to pay supplier invoices. iPaybetter allows businesses to access additional working capital and improve their liquidity by reducing the time between payables and receivables

Account setup & identity verification

Users set up their accounts through standard registration or using their Google accounts.

After registration, they need to undergo an identity verification process to access the payment features of iPaybetter. Plus, they manage all the relevant information about their and their business profile.



Create and manage recipients and payment methods

Users can create and manage their recipients with all the relevant information to easily transact with them in the future. The recipient can be an individual as well as an organization.

Users can add multiple cards to their accounts. This lets users easily select a suitable card to pay each bill.



Single transactions

Once the users add cards for their payment methods and recipients to the platform, making transactions is straightforward. Users can select an already existing recipient and one of the existing payment methods when making a transfer. If the recipient is not already added to the user’s recipient list, the transaction flow also offers the option to add a new recipient.

Once the user inserts the transaction amount, they get a detailed breakdown of the pricing: the amount the recipient will receive, the processing fee, the transaction fee, and the total amount for the transaction.



Scheduled & recurring transactions

We built the recurring transactions feature to simplify the management of regular payments. Users can select the start and end dates and indicate the time interval for the payments, much like you would schedule recurring meetings on your calendar.

Additionally, users can schedule upcoming payments, and iPaybetter will handle the transfers accordingly.



Managing payments and invoices

Users can browse through their payment history at speed. Searching and filtering transactions by dates, recipient, amount, status, etc., let users quickly find the transaction and the respective invoice they are looking for.

Additionally, users can monitor payment status and export payment history details and individual transfer invoices as PDF and CSV files.



Dashboard

The dashboard gives users an overview of different actions they can take using iPaybetter.

Through the dashboard, users can also set up and manage their goals.

Additionally, users can get detailed analytics of their payments and goals through different charts.

Involvement & Process

We conducted competitor, reference, and user research and leveraged our past experience in fintech products to design the user experience of iPaybetter. Our design team crafted the wireframes and a clickable prototype in Figma.

Once wireframes were approved, we used an existing UI system ANT design and modified its components to comply with the company’s brand guidelines.

Our team used React, Next, and ANT design to build the web application front-end. The development process was test-driven and based on the SCRUM framework with one-week-long sprints. As with any other project at Redberry, the development team worked with pull requests and code reviews. Additionally, the team used ESLint for linting and Jest for unit tests. Plus, we used Storybook for frontend component documentation.

We used Laravel to build the application backend and develop APIs. The development process was test-driven and based on the SCRUM framework with one-week-long sprints. As with any other project at Redberry, the development team worked with pull requests and code reviews. Additionally, the team used CSFixer for linting and Pest for unit tests. Plus, we used Swagger for the API documentation.

We also developed integrations with third-party card payment processing and bank-to-bank payment transfer APIs.

Our team set up CI/CD pipelines with Github Actions. We had separate environments for development, staging, and production. We used Laravel Forge to provision infrastructure and manage configurations. However, we heavily modified the Laravel Forge deploy script to match our branching and environment model.

Additionally, we integrated Github with Jira to automate the process of moving cards on Jira swimlanes. Finally, we integrated Github with Slack to notify the client and us of successful deployments to each environment.

We used the Scrum framework to manage the project. The team started with one-week-long sprints and later moved to two-week-long sprints. Design sprints are one sprint ahead of the development sprints.

Our project manager worked closely with the product owner on the client side to groom the backlog for future sprints on a weekly basis.

We used Scrum Poker to assess the complexity of the backlog items with story points. It helped us measure team velocity and improve performance along the way.

The client was involved with every backlog grooming, sprint planning, sprint review, and sprint retrospective meeting. At sprint review meetings, the team demoed what we had achieved during the sprint, and the product owner on the client side decided what to ship to production.

We configured Jira to support our whole project management process. Project documentation was created and is maintained on Notion.

Tech Stack

Meet the authors

We are a 200+ people agency and provide product design, software development, and creative growth marketing services to companies ranging from fresh startups to established enterprises. Our work has earned us 100+ international awards, partnerships with Laravel, Vue, Meta, and Google, and the title of Georgia’s agency of the year in 2019 and 2021.

Contact us

Similar Projects

E-space

e-Mobility


Lunchoba

Food Delivery Mobile App & Platform