Inconsistent Checkout Process for Credit/Debit Card Payments

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 tracing the checkout payment-method flow in the TypeScript project and compare the credit/debit card path with the PayPal path described in the issue. Verify the card flow's email prompt and required billing details. Done means card payments follow the expected sequence and collect the necessary information consistently.

Written by the indexing model from the issue text.