How orders are created

1. When the shopper taps the button

Your store prices the order on its own server. The browser sends only what to buy (the cart, or one product with its option and quantity). It never sends prices.

The store:

• checks every item can still be bought, and that there is enough stock;
• prices each item from your catalogue, with your automatic promotions;
• works out shipping from your own shipping rules (see Shipping, tax and discounts);
• adds tax if your prices do not include it;
• saves this priced snapshot and signs it for PayU.

Stock is checked here but not reserved. The PayU sheet can stay open for several minutes, so holding stock would block other shoppers.

No order exists yet. The saved session expires after 30 minutes if nothing happens.

2. When PayU answers

The result can reach your store two ways: from the shopper's browser when the sheet closes, and from PayU's return to your store. Your store does not trust either one on its own. It asks PayU directly for the order details, and for a prepaid payment it also confirms the payment with PayU.

• Paid, or a confirmed COD order: the store creates the order (next step).
• Failed or cancelled: nothing is created. The cart is kept.
• Not confirmed yet: nothing is created yet. The next confirmation for the same payment finishes the job.

3. Exactly one order

Both paths can arrive at the same time. Your store locks the session while it works, so only one of them creates the order. The other one simply returns the same order. A shopper who refreshes, or a confirmation that arrives twice, never creates a second order.

4. A normal order

The order is created by the same order process your regular checkout uses. So it shows up in Orders like any other order, with:

• the items and prices from the snapshot taken when the shopper tapped the button;
• the shipping address PayU returned (name, phone, address lines, landmark, city, state and pincode). The billing address is the same, because PayU collects one address;
• the shipping fee and shipping method chosen when the sheet opened;
• any PayU offer recorded as a discount;
• the COD fee, if the shopper chose cash on delivery;
• a note in the payment details that it came from Quick Checkout, with the PayU transaction IDs.

The order is tagged as a Quick Checkout order, and the order records that PayU's OTP verified the phone number.

5. Paid orders and refunds

For a prepaid order, the store records the PayU payment exactly as it does for a normal PayU checkout, then marks the order paid. This means refunds work the usual way: refund a Quick Checkout order the same way you refund any other PayU order.

6. Cash on delivery orders

When the shopper chooses COD:

• the order is created unpaid, waiting for cash on delivery;
• if your store has an active cash-on-delivery payment method, the order uses it. Otherwise the order shows the PayU method;
• your COD fee is added to the total, if PayU added it to the amount;
• if COD is switched off in your Quick Checkout settings but PayU still accepted a COD order, the order is created and flagged for review.

7. Who the order belongs to

Phone numbers are matched on their last ten digits, so "+91 98765 43210" and "9876543210" match. The PayU address is not saved to the customer's address book.

Signed-out shoppers can only start Quick Checkout when your store allows guest checkout.

8. After the order

• Cart page or drawer: the cart is emptied.
• Product page: the cart is not touched.
• The shopper lands on the order confirmation page. A guest can open it without signing in, just like after a normal guest checkout.