Payment Checkout Flow

Payment Checkout Flow

for www.ebazarway.com

Operated by: Cybersoft

This Payment Checkout Flow describes the standard customer journey on www.ebazarway.com for selection of products, order placement, payment initiation, transaction processing, order confirmation, and post-payment handling.

1. Product Selection

The customer visits www.ebazarway.com and browses the available products listed on the website, including categories such as laptops, mobiles, computers, accessories, electronics, and consumer items.

1. The customer may review:
2. product name;
3. price;
4. product specifications;
5. images;
6. availability;
7. quantity;
8. delivery details; and
9. other product-related information before purchase.

2. Add to Cart

After selecting the desired product(s), the customer clicks “Add to Cart” and the chosen item(s) are added to the shopping cart.

The cart page displays:

1. selected product(s);
2. quantity;
3. unit price;
4. subtotal;
5. applicable taxes, if separately shown;
6. shipping charges, if applicable;
7. discounts, coupons, or promotional adjustments, if any; and
8. final payable amount.

3. Cart Review

1. The customer reviews the shopping cart and may:
2. increase or decrease quantity;
3. remove any product;
4. apply coupon code or promotional offer, if available; and
5. proceed to checkout after reviewing the final order value.

4. Checkout Initiation

The customer clicks “Proceed to Checkout” and is taken to the checkout page.

At the checkout stage, the customer is required to provide or confirm:

1. full name;
2. mobile number;
3. email address;
4. billing address;
5. shipping address;
6. city, state, PIN code;
7. any other delivery-related information required for fulfilment.

If account/login functionality is enabled, the customer may log in or continue as guest, depending upon website configuration.

5. Order Summary Page

Before payment, the website displays a final Order Summary Page containing the complete purchase details, including:

1. product name(s);
2. quantity;
3. unit price;
4. subtotal;
5. shipping charges, if any;
6. taxes, if any;
7. discounts / coupon deductions, if any;
8. total amount payable; and
9. billing / shipping details.

This is an important step, because Paytm’s payment-page documentation specifically describes the payment process as beginning when the customer clicks the Pay button on the merchant’s order summary page. 

6. Customer Proceeds to Payment

After reviewing the order summary, the customer clicks “Pay Now”, “Proceed to Payment”, or similar payment confirmation button.

At this stage:

1. an order is created in the merchant system;
2. a unique order reference / order ID is generated;
3. the payable amount is locked for the transaction;
4. the payment request is initiated with the payment gateway.

Paytm’s official checkout documentation states that, upon clicking the pay button, the merchant first creates the order in its own system and generates the transaction token through the relevant initiation API before showing / invoking the payment page. 

7. Payment Gateway Invocation

After the order is created, the customer is redirected to, or shown, the secure payment interface integrated through the payment gateway.

Depending on the integration selected, the customer may be presented payment options such as:

1. UPI;
2. credit card;
3. debit card;
4. net banking;
5. wallet; and
6. other enabled payment methods.

Paytm’s current official documentation for merchants describes JS Checkout as supporting multiple payment options including debit cards, credit cards, net banking, UPI, and Paytm Wallet. It also notes that the older standard checkout / redirection flow has been deprecated for new use cases in favour of newer checkout solutions. 

8. Customer Selects Payment Method

The customer selects the preferred payment mode and submits the payment credentials / authorization through the secure payment interface.

Depending on the chosen mode, this may involve:

1. entering card details and OTP;
2. selecting net banking and authorizing through the bank;
3. approving UPI collect request or scanning / approving via UPI app;
4. using wallet balance or supported digital payment methods.

9. Transaction Processing

1. Once the customer submits the payment, the transaction is processed by the payment gateway / banking network.
2. During this stage:
3. payment authorization is attempted;
4. the transaction is validated;
5. success, pending, failed, or aborted status may be generated depending on the response.

Paytm’s official integration flow includes payment initiation, invoking the payment page, and then verifying the payment status after the transaction attempt. 

10. Payment Status Response

After the payment attempt, the customer is redirected back to the website or shown a status page reflecting the transaction outcome.

The payment outcome may be:

1. Successful
2. Failed
3. Pending
4. Cancelled / Aborted

The website verifies the payment response from the gateway and updates the order status in the merchant system accordingly. Paytm’s JS Checkout documentation expressly includes a final step to verify payment status after invocation of the payment page. 

11. Successful Payment Flow

1. In case of successful payment:
2. the order is marked as successfully placed;
3. payment confirmation is recorded against the order;
4. the customer is shown an Order Confirmation Page;
5. order ID / reference number is displayed;
6. confirmation may also be sent by email, SMS, or other communication channel.

The order then moves to internal processing, packaging, dispatch, and delivery stages in accordance with the website’s shipping and order-fulfilment process.

12. Failed / Cancelled / Aborted Payment Flow

1. In case the payment fails, is cancelled, or is aborted:
2. the customer is informed that the transaction was unsuccessful or incomplete;
3. the customer may be given the option to retry payment;
4. the order may remain pending for a limited period or may be automatically cancelled, depending on website configuration;
5. if any amount is debited but the order is not confirmed, the case is handled as per payment reconciliation and refund policy.

13. Pending Payment / Reconciliation

1. If payment status is pending due to banking or gateway delay:
2. the order may remain in temporary pending status;
3. backend verification is carried out through payment-status verification;
4. upon confirmation, the order may be updated to success or failed status;
5. in case of non-successful final settlement, refund / reversal is processed as per banking timelines and refund policy.

14. Refund / Failed Transaction Handling

Where payment is received but the order is not fulfilled or is cancelled in accordance with the applicable policy:

1. the refund is initiated to the original payment source, where feasible;
2. refund processing is subject to gateway / bank timelines;
3. the customer may be informed through email, SMS, or account status update.

15. Security and Compliance Features

The checkout flow is intended to operate through secure payment processing mechanisms. Payment authorization is handled through the integrated payment gateway, and payment options are presented through the secured payment interface supported by the gateway. Paytm’s merchant documentation describes its checkout solutions as secure and PCI-compliant, and its JS Checkout as requiring only limited code snippets while supporting web traffic across desktop/mobile.

16. Summary of Customer Journey

In summary, the payment checkout flow on www.ebazarway.com is intended to follow this sequence:

Product Selection → Add to Cart → Cart Review → Checkout Page → Address / Customer Details → Order Summary Page → Pay Now → Payment Gateway Page → Payment Method Selection → Transaction Processing → Payment Status Verification → Order Confirmation / Retry / Refund Handling