Enatega Customer App: Delivery Fee Not Included in Stripe Checkout Payment
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, react-native
Research direction
Start in the customer app checkout flow and follow the Stripe payment integration from the displayed order total to the Stripe checkout session. Reproduce the issue with a cart that has a delivery fee, then verify that the Stripe total includes the same delivery fee shown in the app.
Written by the indexing model from the issue text.
Description
Describe the bug
When placing an order using Stripe, the delivery fee is correctly shown on the app checkout page. However, after redirecting to Stripe’s checkout, the delivery fee becomes 0 and is not included in the payment total.
To Reproduce
Steps to reproduce the behavior:
Add items to the cart.
Proceed to checkout page.
Select stripe as the payment method
Note the total amount which includes the delivery fee.
Continue to Stripe's checkout page.
Observe that the delivery fee is set to 0 and not charged.
Expected behavior
The delivery fee should be included in the Stripe checkout total exactly as shown on the app checkout page.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone:
Device: [Infinix]
OS: [Android]
Browser [app]
Labels: Enatega Multivendor Customer App, Bug
- 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/uber-eats-app-clone-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2069 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raymondjames090/uber-eats-app-clone-using-react-native#2002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#1979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
raymondjames090/uber-eats-app-clone-using-react-native#1978 ·
All issues in raymondjames090/uber-eats-app-clone-using-react-native
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