WooPayments is unusual: it persists charges in wc_payments_transactions and chargebacks in wc_payments_disputes, on top of the order-meta keys it writes (charge ID, intent ID, payment method type). The richer dataset is exactly what finance and risk teams need, but the default UI splits it across the WooPayments tab, the Stripe dashboard and the order edit screen.

SleekView reads wc_payments_transactions and wc_payments_disputes directly and joins back to wp_wc_orders on the WooPayments charge ID. Card brand, transaction type, decline reason and dispute reason all surface as columns on the same row. Filter to declined charges from the last 24 hours, sort by amount descending, or filter wc_payments_disputes by reason to find chargeback clusters.

The plugin keeps owning the Stripe API calls, captures, refunds and dispute responses. The table view owns the audit surface, so the data WooPayments already writes locally becomes a single screen instead of three.

WooPayments is the gateway that gives WooCommerce the richest local dataset: its own transactions table, its own disputes table, plus the order-meta keys it writes per charge. The default admin surfaces all of that as three separate lists, with no column for card brand, no aggregated reason for declines and no saved "open disputes" filter. SleekView reads wc_payments_transactions and wc_payments_disputes directly and renders them as a queryable audit table joined back to wp_wc_orders, so finance can reconcile by payout period, risk can triage by dispute reason, support can chase the last 24 hours of declines.

The plugin keeps owning the Stripe API and the dispute responses, while operators get the per-row surface the data has always deserved.