WooPayments is the WooCommerce in-house payments stack. Intents, charges, refunds, disputes, and payouts land in WooPayments-prefixed tables, while the WooCommerce-side data (order totals, status, customer references) sits in wc_orders and wc_orders_meta through High-Performance Order Storage. The default Payments dashboard renders charges as a report grid with filters by date, status, and currency. That report-grid format is fine for browsing but bad for the rhythm finance actually runs: a daily walk through authorized-not-captured, today's refunds, and the open dispute queue.

SleekView Kanban reads the WooPayments charge records and groups them by their canonical status field. The board renders one column per status: Authorized, Captured, Refunded, Disputed. Each card shows the customer name joined from the WooCommerce order, the captured amount with currency, the country and card brand from the intent metadata, and a small badge for high-risk fraud outcomes. Finance reads the day in column counts: 412 captured, 8 authorized awaiting capture, 14 refunded, 3 disputed.

Drag a card from Authorized to Captured and SleekView triggers the WooPayments capture API, the same call the dashboard issues today when a finance user clicks Capture. The order status updates, the payout schedule picks up the new captured amount, and the WooCommerce order status reflects the change. Refunds, disputes, and chargebacks keep flowing through their existing WooPayments endpoints because SleekView never invents shadow tables, it reads and writes the same records the rest of the plugin uses.

Payments work runs on a status-transition rhythm: an intent is authorized, a capture happens, a refund posts, a dispute lands. The default WooPayments dashboard renders all of that as a flat report grid optimized for browsing rather than daily ops. A kanban swaps the metaphor: each status is a column with a count, each transition is a drag, and the manual-review queue, the capture sweep, the refund follow-up, and the dispute triage room all become saved board views over the same tables.

Finance sees today's exposure as a sum across columns. Ops sees the authorized-not-captured queue draining. Chargeback specialists scope to Disputed only and work the deadline column.

The capture API, the refund endpoint, the dispute submission flow, and the payout schedule all run unchanged because the kanban only calls the same WooPayments endpoints the dashboard uses today. The result is a payments reconciliation surface that reads in seconds instead of a report grid that demands a filter for every question.