PRODUCT DESIGN | SPRING 2021
SNAPCHECK BATCH PAYMENTS
Increasing efficiency by empowering SMEs to send batch payments, thus reducing the time and effort spent on sending payments in a large volume.
MY ROLE
User Research
UX/UI Design
Interaction Design
Prototyping
TEAM MEMBERS
Ken Kruszka (CEO)
Ajay Singh (CTO)
Emily Yu (Developer)
Shabana Shakhi (QA)
Chengyu Zhao (Designer)
TIMELINE
4 weeks
METHODS
A/B Testing
Competitive Analysis
I led the design of SnapCheck's Batch Payments experience for SME (Small & Medium-sized Enterprise) users, with a focus on delivering a streamlined process for sending or preparing multiple payments at once. Our efforts resulted in a highly successful batch payment solution that led to a high adoption rate, accounting for 31.6% of the payments made by business accounts.
Intro
SnapCheck is a B2B payments platform that provides a digital checks solution for SMEs to pay vendors & suppliers, reimburse employees, and make any business related payments.
What is snapcheck?
problem
Businesses were facing a growing demand in making contactless payments.
The 2020 pandemic has significantly shifted the demand for sending contactless payments for SMEs. Our data indicated the average payments per week made by a business account has increased by 160%. As a result, it takes more time & efforts to send/ prepare the payments.
Feature requestSending checks one by one is too slow. Thus, many of our existing clients such as Azlo has challenged us to provide a batch payment solution in response to this rise on demand.
Our goal
Reduce task completion time of processing payments in a large volume.
The goal is to provide a cost-effective payment solution to expedite the payment preparation process of plentiful payments. To make it easy for us to design and measure, we specifically aim to help business users who send 10+ payments at a time.
HMWHow might we reduce reduce task completion time of sending massive payments?
Research
Preparing on a spreadsheet is common and effective.
It was hard for us to recruit business users for user research. Luckily, I was able to hop on 3 sales call with the potential clients and got a chance to ask questions in person. Below were what we found:
Insight #1: They list out upcoming payment details on a spreadsheet.
Insight #2: They usually send payments on a spreadsheet altogether at once.
Insight #3: They need a simple & quick way to input bulk entry.
Look at existing technology
CSV upload perfectly suited our need.
Batch payments is not a new concept in the fintech space. Major payment softwares use a spreadsheet to make bulk entry. During my exploration, I found the CSV upload method a suitable option for our current need:
It imports bulk data from a spreadsheet.
It skips manual inputs on the platform.
It’s simple & quick.
Ideate
Loop stakeholders in the ideation process
I shared the research findings with the team in a 60 min meeting, with first half walking through the insights and the second half ideating the batch payments flow in CSV upload.
Collaborated as a team, we identified the required information needed to put on a spreadsheet and prepared a CSV template to upload data easily and minimize input errors.
design
Create a familiar interface with minimum development efforts
I strategically leveraged existing components throughout the flow. This approach not only streamlined technical complexities but also enabled us to test the feature in the most efficient timeframe possible.
My goal was to create an experience that not only delighted our clients and their users but also earned the appreciation of our development team.
AB Testing
Task completion was significantly reduced
We compared the task completion time of sending 10 payments using Batch Pay vs. Single Pay. (Note: Batch Pay testing still required the users to type all the payment information on a spreadsheet).
Payments sent in Batch Pay were completed 1m 16s faster (30.2% reduction) than payments sent in Single Pay during our testing
SuccessThis difference will only get larger when more sending more payments at a time.
launch
Skip manual entries…Upload a batch payments CSV in just one click
The Batch Payments experience starts with a simple step-by-step instructions, including a link to download the CSV template.
Users just need to prepare the payments using the template, upload in a snap, and then we take care of the painful bulk data entry.
Review uploaded data to prevent system processing errors
Not only the feature lists payments uploaded from the CSV, additional data such as the payment date (which must be today’s date) and total payment amount are automatically displayed for the user. It gives users one last chance to spot out any error.
Each payment is individually traceable in payment history.
Payments sent in Batch Pay are no different than other payments. They will be listed individually in payment history and having a transaction details for payment tracking.
ImpactsThe launch of batch pay has helped the company securing a new partner client 🎉
During Q2 2021, 31.6% of total payments among business accounts were made using batch pay.
Takeaways
Leverage existing technology & design to achieve the goal.
Over the course of this month, I learned how to leverage existing technology and design to create impact for both the company and its users. Particularly in situations with tight deadlines, adopting technologies and designs that users are already familiar with can reduce both product development costs and the learning curve for users.