Lack of User Confirmation Message and Inconsistent Notification on Stripe Payment Process
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- payments
Research direction
Start by reproducing the Stripe checkout flow described in the issue, from the checkout page through the Submit or Pay Now action. Trace the payment submission and notification entry points, then verify that successful payments show a clear confirmation and a consistent payment-status notification.
Written by the indexing model from the issue text.
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
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from raymondjames090/food-ordering-system-java-eclipse
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
All issues in raymondjames090/food-ordering-system-java-eclipse
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100