PayMongo’s Disbursements Beta

TL;DR (too long; didn’t read)

My foundational UX research on Disbursements helped it become a potential product of PayMongo. And now on its beta, I led the design of new features (Bulk Upload and Saved Recipients) to improve the product—helping increase our TPV (Total Payments Volume) since its release and lay the design foundation on what to build next.

Context and problem

When disbursing, merchants such as Enterprise have several-to-many recipients. The use cases vary from paying suppliers, employee salaries, and even operational expenses. Given the size of enterprises, the features (Bulk Upload and Saved Recipients) enables them to do so to fulfill their demands such as convenience. We're moving away from uploading the CSV in ClickUp (which is too laborious or manual for merchants) and instead enabling merchants to upload it to our Disbursements dashboard for ease of use and speed, plus enabling them to save recipients (Saved Recipients) for future use.

Meeting users’ need and solving pain points

The goal is to make the product enable merchants to easily send money to multiple banks and e-wallets faster. This means adding features and making changes to the disbursement process in order to make it faster, more efficient, and more effective at meeting the needs of our merchants.

Instead of having to process each transaction individually, a Bulk Upload feature allows a user to upload and handle several disbursement transactions in a single task.

This can save users time and effort when making a large number of disbursements, as well as make it faster.

The Bulk Upload feature normally entails using a spreadsheet or similar file format to input all disbursement information, which is subsequently sent to the system for processing. Once uploaded, the system will handle all of the transactions in the bulk upload, saving time and effort that would otherwise be necessary to complete individual disbursements. For enterprises and organizations, this feature may significantly increase the efficiency of their disbursement process.

On the other hand, a “Saved Recipient” is a recipient of a disbursement payment whose information has been saved in the system for future use. This feature enables a user to swiftly and efficiently disburse payments to a previous recipient without having to enter the recipient's information every time.

This can save users time and effort when making payments to the same recipients on a regular basis, as well as increase the accuracy and consistency of the payout process.

The user may simply access and use saved recipient information for subsequent transactions, making the disbursement process more effective and simplified. This feature is especially beneficial for enterprises and organizations that make repeated payments to the same people or entities.

Results

• Increase in TPV. An upward trend of increase in the overall value of payments processed since the release.
• Highly usable. The usability test reported that the new designs are highly usable to merchants.

Designs

My role

I worked with our UI designer to design the interface, and UX researcher to test our designs. As a Product Designer, my focus was on designing the UX and executing our product strategy with our Product Manager.

❤️ Shoutout to Regine, Jenni, and the Disbursements team for making this project a success

‍