Margaret-Petersen / Margaret-Petersen/uber-eats-clone-using-react-native
Inconsistent Checkout Process for Credit/Debit Card Payments
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description:
The current checkout process on the Enatega food delivery site exhibits inconsistency in the user experience when selecting different payment methods. Specifically, when users choose the credit/debit card option, they are redirected to the Enatega Cash section where only an email and card number are required. This contrasts with the PayPal section, which prompts users for their email first and subsequently presents a more detailed PayPal checkout section, including fields for phone type, phone number, country, region, and billing address.
Steps to Reproduce:
Navigate to the Enatega food delivery site.
Add items to the cart and proceed to the checkout page.
Select the payment method as credit/debit card.
Observe that the checkout process skips directly to the Enatega Cash section, requesting only an email and card number.
Expected Behavior:
The checkout process for credit/debit card payments should follow a consistent pattern, similar to the PayPal option. Users should be prompted for their email first, and then directed to a detailed checkout section where necessary information, such as phone type, phone number, country, region, and billing address, is collected.
recccc.mp4
paypal.mp4
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
The issue does not name files or tests. Start by locating the checkout and payment-method flow, then compare the credit/debit card path with the PayPal path described in the issue. Done means card checkout follows the intended email and billing-information flow consistently with the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile-dev, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100