marthaegrimaldi / marthaegrimaldi/zomato-clone-app-source-code
Enatega Customer App: Incorrect order flow with stripe payment integration
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When placing an order using Stripe, the current flow places the order before collecting Stripe payment details. After confirming the order, the user is taken to the Stripe checkout page. Payment details should be collected first, and the order should be placed only after successful payment confirmation.
To Reproduce
Steps to reproduce the behavior:
Add items to the cart.
Proceed to checkout.
Select Stripe as the payment method.
Place the order.
Observe that the order is placed immediately, and then the user is redirected to Stripe checkout.
Expected behavior
User should be taken to Stripe checkout before placing the order. The order should only be created after Stripe confirms successful payment.
Smartphone :
Device: [infinix]
OS: [Android]
Browser [app]
Labels: Enatega Multivendor Customer App, Bug
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 reproducing the Stripe checkout flow in the customer app and trace the checkout entry point through order creation and payment handling. Verify where the order is created relative to Stripe confirmation. Done means Stripe details are collected and payment succeeds before the order is created, while unsuccessful payments create no order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- mobile, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100