🛠️ Potential Solutions
Note: this section should be short and sweet, documenting notes about different solutions that were considered during ideation. Can just be a link to a whiteboard for example. Expected outcome: one solution is chosen and documented in more detail under Proposed Solution.
✅ Proposed Solution
Description of the proposed solution.
Figma Link (still WIP): https://www.figma.com/design/wEeYkRHLwLdMJHKvQJOdd0/%5BIBFEC-1795%5D-Remove-Pre-filled-Name-On-Card-field?node-id=7913-1549
Technical refinement
This change will be just to Paycomet (IBERIA)
The payment page is one of the most critical steps in a customer's purchasing journey.
Any difficulty faced at this stage may result in errors or, even worse, dropouts, directly impacting conversion rates and customer satisfaction.
We recently carried out a technical analysis and identified points for improvement that can reduce possible errors and dropouts.
One of the points observed is the close button on the payment pop-up.
If the user chooses to close it, the payment page enters an infinite loading state, with no completion.
This behavior forces the customer to take drastic actions, such as closing the page and redoing the flow, which interrupts the purchase flow and can potentially cause frustration.
To solve this problem, we will recover the user's action of closing the popup and when this happens, they will be redirected to the cart page and a new OrderId will be generated and consequently a new TransactionId.
There is also the possibility of closing the popup inside the iframe (Bizum and Paypal), in this case, the PSP (Paycomet) returns an error code that will be used to validate this scenario and consequently, execute the same flow mentioned above.
This change will be doing just the link payments (Bizum, Waylet and Paypal), being that, the cancel payment action inside of the iframe by the user, will be just (Bizum and Paypal).
At this moment, Waylet there isn’t the possibility to manually cancel payment action inside of the iframe.
Another point of improvement found is the button to close the payments page.
This button remains enabled throughout the transaction process, which may allow the user to cancel (by clicking this button the user is redirected to the cart) the purchase for any reason, a simple delay in payment processing, or any other non-apparent reason.
This may leave the impression that the payment has been canceled or the impression that the payment has been made but the order has not, which no longer occurs due to account of the new changes to the intl-transactions team.
This change is more focused on the user experience since ghost order errors have already been resolved as mentioned above.
With these changes, we hope to not only minimize errors and dropouts but also provide a more fluid and satisfactory purchasing process for customers.
This change will be to all payment methods by Paycomet
Potential Challenges
List here potential challenges that have come across the opportunity definition or from the potential solutions so far.
💰 Cost
Describe any additional cost this solution may imply.
🎛️ Configuration
Include here any configuration required (Sanity, LaunchDarkly flags, etc.) required to enable the solution.
📈 Metrics
Describe the metrics that will be used to measure the solution’s success, as well as how to measure those KPIs.
🗓️ Delivery Plan
Link to the task or list of all the tasks required to deliver the solution, along with its progress.
🧑🚒 QA Plan
Testing scenarios. See example /wiki/spaces/EGMT/pages/4080861189.
⚠️ Call-outs
Tip: Document here any improvement or discussion regarding the feature
Add Comment