Onion Pay

Onion Pay

Money management for businesses

Money management for businesses

Visit website

Sector:

FinTech

FinTech

role:

App Design, Branding,
User Experience (UX) Designer.

App Design, Branding,
User Experience (UX) Designer.

tool:

Figma, Figjam

Figma, Figjam

duration:

3 weeks

3 weeks

Overview

Overview

Onion Pay is a fintech company that provides a payment infrastructure for merchants and businesses
in Africa.

Payment and money management infrastructures have existed to solve the problems attached to businesses' and their money for a long time now, but with continuous rise in the number of businesses and rise in customer base, there is increase competition among such infrastructures. Onion Pay is ought
to take up some of that responsibility and solve the problem that leads to such competition.

Objective

Objective

To design a product that successfully helps businesses and merchants manage their money.

How we approached the problem

How we approached the problem

  1. RESEARCH & OPPORTUNITIES

Competitive Audit (What are other payment & money management infrastructures doing?)

Competitive Audit
(What are other eCommerce stores doing?)

Of all money management solutions in Africa, Flutterwave and Paystack have been at the forefront creating a name for themselves and solving users problems effectively. Flutterwave offers a wide range of payment solutions, including a payment gateway, a consumer payment app, and a merchant app, which is the primary focus of Onion Pay.

I carried out an audit of Flutterwave's merchant app services to gather better insight on what Onion Pay needs to be. Here is what Flutterwave's merchant app offers:

  1. Payment Processing: Merchants can use Flutterwave to process payments from customers securely. This can include online payments, in-person transactions, and more.

  1. Wallet: Merchants have a wallet to make and receive money transfers to/from both bank accounts and other flutterwave merchants.

  1. Transaction Monitoring: Allows merchants to track and monitor their transactions in real-time. They can view transaction history, check payment statuses, and manage their cash flow effectively.

  1. Integration with Business Systems: The app offers integration capabilities, allowing businesses to connect their payment processing with their existing systems and platforms for seamless operations.

  1. Currency Conversion: Merchants can use Flutterwave to manage transactions in different currencies and perform currency conversions when necessary, catering to a global customer base. This feature has recently been removed from countries like Nigeria due to new policies and regulations.

  1. Payment Links and Invoicing: Enable merchants to create payment links or generate invoices that can be shared with customers for easy and convenient payment collection.

  1. Refunds and Chargebacks: The app typically allows merchants to initiate refunds for transactions when needed and manage chargebacks in compliance with payment industry standards.

  1. Reporting and Analytics: Merchants can access analytical tools and reports within the app to gain insights into their sales performance, transaction trends, customer behaviour, and more.

  1. Subscription: Enables merchants to make airtime purchases and TV subscriptions from the apps wallet.

  1. Inventory Management: Some versions of the service may include features for basic inventory management, helping merchants keep track of their products and stock levels.

  1. Test Mode: Flutterwave offers merchants with a test mode to let them use the service to understand and trust the service.

  1. Customer Support: Provides channels for merchants to access customer support and seek assistance with any app-related issues or inquiries.

How we solved the problem

How we solved the problem

  1. USER NEEDS & PRIORITIZATION

Prioritization

Prioritization

The stakeholders, my team and I considered all features provided by Flutterwave and prioritised some over others based on,

  • Time - how much time is required to build and implement the feature?

  • Effort: - what amount of effort needed to implement the feature?

  • Value: - how valuable is the feature to the product and what effects will its presence of absence have on the business and its customers?

  1. DESIGN

Information Architecture

Information Architecture

Screens

Screens

Website

Website

Transactions

Transactions

Refunds

Refunds

Chargebacks

Chargebacks

Customers

Customers

Balances

Balances

Transfers

Payment Links

Payment Integration

  1. TESTS

Usability Tests

Usability Tests

Tests for Onion Pay was scheduled to be conducted after implementation by the developers. Development of the product has been completed but with the presence of bugs, tests have been postponed until all bugs have been fixed.

Conclusion

Conclusion

A good chunk of the products features were removed by the stakeholders in the MVP build so the eventual test to be done on the product will be limited to a smaller and more product market.

Visit product website

Visit product website

Let’s work together

Let’s work together

I would love to hear from you.

Reach out via email at nathanumarjamil@gmail.com, and let’s create something extraordinary together. 👋

I would love to hear from you. Reach out via email at nathanumarjamil@gmail.com, and let’s create something extraordinary together. 👋

Copyright @ 2023 Jamil Black