gray-mueller / gray-mueller/ride-sharing-solution-application

Inconsistent Checkout Process for Credit/Debit Card Payments

Open
#285 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
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

Open the contributing guide

Research direction

No files or tests are named. Start by tracing the checkout flow from payment-method selection and compare the credit/debit card path with the PayPal path shown in the attached videos. Done means the card flow consistently collects the required customer and billing details instead of going directly to the limited Enatega Cash section.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, payments
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.