Inconsistent Checkout Process for Credit/Debit Card Payments
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- payments
Research direction
Start at the checkout page and trace the credit/debit card payment flow described in the reproduction steps, comparing it with the PayPal flow. The work is done when card payments collect the expected email, contact, location, and billing details through a consistent checkout experience and the reported redirect no longer occurs.
Written by the indexing model from the issue text.
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
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 gray-mueller/full-stack-document-solution
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in gray-mueller/full-stack-document-solution
Similar issues
-
area:docs bug triage:confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Cotal-AI/Cotal#2875 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anomalyco/models.dev#8862 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(data-lake): wizard source step still previews the local slug, not the server-disambiguated oneOpendata-lake
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ready-for-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
konflux-ci/konflux-ui#1596 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day