1.The initial version of the website used third party payment gateways. This was a bootstrap solution for the payment procedure.
2.The users weren’t able to view the details of their order before payment / users had no way of checking what have they placed an order for.
3. Customer had to fill in excess personal information and additional steps which was tedious.
4. The order confirmation was in the form of a text giving very few details.
1. We came to the conclusion that users like to have multiple payment options available.
Most e-commerce sites today host multiple payment options. We wanted to provide that convenience to our customers.
2. Most sites have a segregated page for the user to review and edit their order.
3. You see your order summary before you reach the payment page.
Instead of being directed straight to the payment page without being able to access you cart feels like you are being left in the dark. You don't want to keep going back to check if your order is correct or worse, go back and order all over again.
- User to be able to decide the quantity of tickets on the event details page itself and have order summary there itself.
As we began designing solutions for the payment page we realised that changes needed to be made in the Event Detail Page as well for a smooth cohaesive user journey.
Reduced the number of steps to get to the payment page.
1. Prioritising the information the user needs to provide to make payment
2. Creating a universal and adaptable design.
We created a design where the user is not unfamiliar with the journey instead the journey is intuitive. Since it is adaptable to multiple devices, it is more accessible.
3. User to be able to review and edit the orders at payment page also.
To create a solution where user can view all the details of their purchase without having to shuffle between different pages to make changes.
As we were drawing up the brief for this page, we realised that to make the whole flow seamless, first changes need to be made on the page with event information. The 2 projects were being worked on simultaneously because of their interdependence. Stakeholder’s individual attention to either would lead to changes in both.
Received positive response for the time saving user experience
Receive fewer complaints regarding payments and receiving tickets.
When multiple people are working on cross dependant pages and assets overlap, user journey and design updates should be communicated.
To have a universal system of organising components so that they can be shared and are comprehensive to the whole design team.