Inconsistent Checkout Process for Credit/Debit Card Payments

Nobody has claimed this yet.

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

Start by locating the checkout screen and the credit/debit card and PayPal payment flows in the React Native application. Reproduce the card flow described in the issue, then compare its sequence and collected billing details with PayPal. Done means the card flow consistently prompts for the required information and no longer skips directly to the Enatega Cash section.

Written by the indexing model from the issue text.