WooPayments is the official WooCommerce payment platform powered by Stripe. Orders come through with the standard WooCommerce statuses like wc-pending, wc-processing, wc-on-hold, wc-completed, wc-cancelled, and wc-refunded, plus WooPayments-specific metadata in wp_postmeta for the Stripe charge ID, the WooPayments intent ID, the payment method (card, Apple Pay, Google Pay), and the WooPayments transaction status. The native WooCommerce orders screen shows them mixed with all other orders.

SleekView Kanban reads the same WooCommerce orders you would query with WC_Order, filtered to orders that used WooPayments. Pick post_status as the group column and every order becomes a card slotted under Pending, Processing, Completed, or Disputed. Card fronts show the customer name, the order total in store currency, the Stripe payment method, the charge ID, the date placed, and the WooPayments status, so finance has every WooPayments-specific detail directly on the card for the daily reconciliation against Stripe.

Dragging a card between columns calls the standard WooCommerce status transition the admin uses, which fires woocommerce_order_status_changed. WooPayments listens for the change to update its own dashboard, the customer notification email goes out through WooCommerce's email module, the Stripe Dashboard reflects the change, and any extension subscribed to the WooCommerce hooks reacts, exactly as it would after a manual admin status change.

Stores running WooPayments process hundreds of transactions every day across card, Apple Pay, and Google Pay payment methods routed through Stripe. Some clear instantly, some take a few minutes for 3D Secure confirmation, some get stuck in Pending when the customer abandons the Stripe redirect. The default WooCommerce orders screen mixes WooPayments transactions with COD, prepaid, and other gateway orders, which makes WooPayments-specific reconciliation a CSV export exercise every single day.

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

A daily payout from Stripe shows revenue that does not match WooCommerce. A kanban view that reads and writes the same WooCommerce orders the gateway processed, filtered to WooPayments specifically, keeps the team and the books honest. Every drag is a real status change, every column count reflects the real WooPayments pipeline health, and the cards themselves carry enough context for a new finance analyst to handle reconciliation on day one of the job.