WeTravel_Hero Image.png
 

 
 

COMPANY

WeTravel is a webapp that allows trip organizers to announce the upcoming trips, and manage customer payments.

Duration: 6 weeks

 
 
 

Challenge

The existing app is a single-sided payment platform, allowing tourists to make payments to trip organizers. Organizers then need to transfer the collected amount to their bank account to be able to use it for remitting payments.

WeTravel wants to solve this issue by converting the app into a multi-sided payment platform.

SOLUTION

a) VALIDATING the need and willingness of users for using WeTravel to remit/accept large sum of money.

c) CREATING ui designs focused on three main parameters — acquisition (of vendors), payment system and storing vendor information.

 
 
 
 
 

Role

I worked with a team as a UX and UI designer, having specific focus on Overview, Account Summary and Vendor Profile pages.

 
 

 
 

TL;DR

This is a quick preview of dashboard from final product. The dashboard displays summary of user’s balance and immediate actionable items. More about the process and other pages are detailed below.

 
Overview-04-04.png
 

 
 

USER RESEARCH

Our multiple rounds of interactions with trip organizers and vendors gave us insights into the prime features they sought.

Interviews with organizers

  1. 10/10 wanted easier and cheaper way for making payments

  2. 8/10 wanted to directly make payment to vendors through WeTravel

  3. 8/10 wanted to store/save vendor information for future purposes

Interviews with vendors

  1. 6/7 were willing to accept payment from a trusted and secure online platform

  2. 6/7 did not trust money from unknown senders

  3. 4/7 wanted to use WeTravel to market themselves to other potential trip organizers

 
 

 
 

DESIGN

  1. VENDOR ACQUISITION

    In order to build trust with vendors, we decided to use a familiar document — an email invite sent by the organizer using WeTravel portal. Below are the steps for onboarding:

Email Invite.png
  • Trust:

    An email from a familiar customer will reduce the risk of dismissal by vendor.

  • Information:

    Email would mimic an invoice, providing details of transaction between the vendor and organizer.

  • Security:

    Once the vendor gets onboarded, organizer will get notified. Organizer can then make payment to the vendor. This will ensure secure transfer of funds to the correct vendor.

 

 

2. ACCOUNT SUMMARY

This screen showcases all the transactions done by the user within WeTravel portal.

 
Account Summary-03.png
 
 

Below prototype shows filters that can be applied in the PAST TRANSACTIONS section of Account Summary page. These filters enable users to make a refined search. Click anywhere on the iPad screen to start.

 

 

3. Vendor Profile

Whenever user invites a vendor, a separate profile page for the vendor is created. This page can be revisited by the user by searching for the vendor in either Account Summary page or Vendor Hub page. This profile page stores contact information and pending and past transactions with that vendor.

 
 

 
 

Validation Testing

Validation result.png
 
 

 
 

Final Thoughts

This was a challenging endeavor where users dealt with large amount of transactions. Thus, highlighting trust and security on each page held paramount importance. This could only be achieved by paying attention to every big and small interactions users had on WeTravel website.

Throughout the project, we had to use brand’s style guide, and create pages that had the look and feel of already existing website. I learnt how to work with these constraints, come up with simpler, easily implementable/engineered designs, and meet the deadline.