Inconsistent Checkout Process for Credit/Debit Card Payments

Open

#1,685 opened on Jun 15, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 52/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: javascript, react-native
Domain: mobile-dev, payments

Research direction

No files or tests are named. Reproduce the checkout flow from the issue, comparing the credit/debit card path with the PayPal path and reviewing the attached recccc.mp4 and paypal.mp4 references. Done means the card flow consistently collects the required checkout details instead of skipping directly to the Enatega Cash section.

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: JavaScript
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open 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.