CORPAY BATCH PAYMENTS

One of our larger customers was processing batch payment files containing thousands of invoices at a time. Many of our customers were facing the same issue, and as we scaled up, we found that this issue became more common. We discovered that this customer like many others, were making queries to the database separately each time they scrolled through the pages at the bottom of the payment grid. This would cause the database to throw errors if many customers were processing payments at common times. Customers also had to see a loading image and a few seconds up to a minute of time loading the pages. When we heard about this issue, we decided we could solve this problem through a user-centric design process.
View the desktop prototype here, and the mobile prototype here.

 

BEFORE

 

 

 

PROCESS

First, we have to determine what problem we’re trying to solve, and who we’re trying to solve it for. We coordinated with product, sales and marketing to interview customers that were experiencing issues, and engage them in the process. Then, reviewed site metrics to see how the customers navigated the payment grids. Next, we created customer journey maps from the interviews and data. I then assigned the product designer with creating a clickable wireframe which we tested internally with UserTesting.com and revised until we were happy with the results. After a solid wireframe was proofed, we added visual design to the final prototype, and retested. Then we prepped the hand off of the final designs to engineering.

 

 

PERSONAS AND USER JOURNEY MAPS

 

 

 

AFTER

 

 

 

MOBILE VERSION

 

 

 

PROJECT LINKS

 

View the desktop prototype

View the mobile prototype