Margaret-Petersen / Margaret-Petersen/uber-eats-clone-android
Lack of User Confirmation Message and Inconsistent Notification on Stripe Payment Process
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description:
Upon proceeding with the Stripe payment on the Enatega Food Delivery website, users encounter two issues. Firstly, there is an absence of a user confirmation message after entering payment details. Secondly, the notification displayed appears inconsistent, leading to potential user confusion.
Steps to Reproduce:
Log in to the Enatega Food Delivery website.
Add items to the cart and proceed to the checkout page.
Select Stripe as the payment method.
Enter valid credit/debit card details.
Click on the "Submit" or "Pay Now" button.
Expected Result:
After successful payment submission, a clear user confirmation message should be displayed, ensuring users are aware of the completed transaction.
The notification displayed should be consistent, providing a clear indication of the payment status.
Actual Result:
After completing the payment, there is no user confirmation message displayed, leaving users uncertain about the transaction's success.
The notification displayed is inconsistent, making it challenging for users to interpret the payment status accurately.
stripe.mp4
Activity
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Stripe checkout flow from the payment method selection through the Submit or Pay Now action, then reproduce the steps in the issue while observing the existing notification behavior. Done means a successful payment produces a clear confirmation message and the payment-status notification is consistent; also verify unsuccessful or unclear outcomes are not presented as successful.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- payments
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100