Instamojo for WooCommerce processes payments through the Instamojo Indian payment gateway. Orders come through with the standard WooCommerce statuses like wc-pending, wc-processing, wc-on-hold, wc-completed, and wc-refunded, plus Instamojo-specific metadata in wp_postmeta for the payment_id, the payment_request_id, and the Instamojo response status. The native WooCommerce orders screen shows them mixed with all other orders, which makes Instamojo-specific reconciliation impractical.

SleekView Kanban reads the same WooCommerce orders you would query with WC_Order, filtered to orders that used the Instamojo 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 Instamojo payment_id, the payment_request_id, and the date placed, so finance has every Instamojo-specific detail directly on the card for the reconciliation.

Dragging a card between columns calls the standard WooCommerce status transition the admin uses, which fires woocommerce_order_status_changed. Instamojo'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.

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

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

A daily payout from Instamojo 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 Instamojo specifically, keeps the team and the books honest. Every drag is a real status change, every column count reflects the real Instamojo pipeline health, and the cards themselves carry enough context for a new finance analyst to handle reconciliation on day one of the job.