PayU Money for WooCommerce processes payments through the PayU India payment gateway. Orders come through with the standard WooCommerce statuses like wc-processing, wc-on-hold, wc-completed, wc-cancelled, and wc-refunded, plus PayU-specific metadata in wp_postmeta for the transaction ID, the payment method (UPI, card, netbanking, wallet), and the PayU response code. The native WooCommerce orders screen shows them mixed with all other orders, which makes PayU-specific reconciliation hard.

SleekView Kanban reads the same WooCommerce orders you would query with WC_Order, filtered to orders that used the PayU Money gateway. Pick post_status as the group column and every order becomes a card slotted under Pending, Processing, Completed, or Refunded. Card fronts show the customer name, the order total in INR or store currency, the PayU payment method (UPI, card, netbanking, wallet), the transaction ID, and the date placed, so finance has every PayU-specific detail directly on the card.

Dragging a card between columns calls the standard WooCommerce status transition, which fires woocommerce_order_status_changed. PayU's refund webhook fires for refund transitions when configured, the customer notification email goes out through WooCommerce's email module, and any extension subscribed to the WooCommerce hooks reacts, exactly as it would after a manual admin status change from the order edit screen.

Indian e-commerce stores running PayU Money process hundreds of transactions every day across UPI, card, netbanking, and wallet payment methods. Some clear instantly, some take a few minutes for UPI confirmation, some get stuck in Pending when the customer abandons the PayU page. The default WooCommerce orders screen mixes them with COD, prepaid, and bank transfer orders, which makes PayU-specific reconciliation a CSV export exercise every single day.

The disconnect between what the PayU dashboard shows and what WooCommerce shows is the source of most accounting headaches for Indian merchants. A successful UPI payment lands in PayU but the WooCommerce order stays Pending because the webhook failed. A refund shows in WooCommerce but never appears in the PayU dashboard because the integration was misconfigured.

A daily payout from PayU shows ten thousand rupees more than WooCommerce reports as Completed and nobody knows why. A kanban view that reads and writes the same WooCommerce orders the gateway processed, filtered to PayU Money specifically, keeps the team and the books honest. Every drag is a real status change, every column count reflects the real PayU pipeline health, and the cards themselves carry enough context for a new finance analyst to handle PayU reconciliation on day one of the job.