...
[Insert here Confluence page on solutions tested or figma designs]
Potential Solutions
To avoid the user from closing the payment process, we explore different options:
New loading page informs the user about the processing payment and prevents them to take any action that can interfere with the process.
2- Alert the user about the importance of keeping on the page until the payment is complete. If the user wants to go back/ leave the process, a modal is displayed as doble check.
...
3- Disabled all the actionable items in the page, including the arrow to go back.
Milestone | Output | Owner | Approver(s) | Reviewer(s) | Status |
|---|---|---|---|---|---|
Ideation & wireframing |
| ||||
Design & prototype |
| ||||
User testing |
| ||||
Design review with stakeholders and franchisees |
|
...
| Info |
|---|
Note: the term “Deliver” refers specifically to the delivery of solution design artefacts. There will be no software development in this phase. |
Solution Description
...
Figma Link (still WIP): https://www.figma.com/design/wEeYkRHLwLdMJHKvQJOdd0/%5BIBFEC-1795%5D-Remove-Pre-filled-Name-On-Card-field?node-id=7913-1549
To avoid the user from closing the payment process, we explore different options and finally decided that the most convenient is to add a new loading page (option 1) because:
· We prevent the user from interrupting the process and therefore having errors in the future regarding erroneously charged or duplicate orders.
· The user has the feeling they are progressing because they are not stuck in the same page, they “have moved” forward to another one.
· The message displayed informs the user about what’s going on and we think that can prevent the user from leaving the process or going back.
To check all of them up, visit: https://www.figma.com/design/wEeYkRHLwLdMJHKvQJOdd0/%5BIBFEC-1795%5D-Remove-Pre-filled-Name-On-Card-field?node-id=7913-1549
Alternative Payments User Case
Important: There is a user case regarding alternative payments in which we must ensure the user finds a way to go back to the Checkout, because if we remove the “X” the user will be stuck in a “loading loop”.
Current PayPal User Case in App:
The only way the user has access to select a new payment method is pressing the ”X”. When closing this page, the user comes back to the Checkout because the platform needs to generate a new Transaction ID for the order before selecting a new Payment option.
Current PayPal User Case in Desktop:
...
DoD
In Whitelabel-app (WIP):
· Ensure the final solution works for all payments methods: Card, Cash, Card on Delivery, Online Mobile Payment Apps.
· Ensure the final solution works for Pick Up and Delivery service modes. In Pick Up mode, have in consideration both Store Confirmation after and before payment.
Milestone | Output | Owner | Approver(s) | Reviewer(s) | Status | ||||
|---|---|---|---|---|---|---|---|---|---|
Feature (MVP) agreement |
| ||||||||
Tech solutioning review |
| ||||||||
Development Handoff |
| ||||||||
Analytics tagging |
| ||||||||
User story breakdown |
|
...