WooPayments is the only major gateway that adds its own custom tables on top of WooCommerce orders. wc_payments_transactions, wc_payments_disputes, and the order-meta keys it writes give a much richer dataset than gateways that only persist a charge ID on the order. Out of the box that data is split across the WooPayments tab, the Stripe dashboard, and the order edit screen.

SleekView Charts reads those tables directly and exposes their columns as groupBy and aggregation targets. Charge volume per day, decline reason distribution, dispute rate by card brand, refund value by reason code, all become chart cards on a saved dashboard. Order meta written by WooPayments (charge ID, intent ID, payment method type) joins back to the order for combined views.

The result is a single in-WordPress dashboard that mirrors the slices finance and risk teams ask for, without exporting to a spreadsheet. WooPayments still owns the gateway and reconciliation; SleekView owns the chart layer over the data it produces.

WooPayments is unusual among WooCommerce gateways because it writes its own custom tables for transactions and disputes, which means a richer dataset than gateways that only persist a charge ID on the order. The current admin surfaces transactions as a list and disputes as a sub-list, but it does not let an operator slice charges by card brand or decline reason on a saved dashboard. SleekView Charts fills that gap by reading those tables directly and exposing their columns as chart axes.

Finance teams get reconciliation charts, risk teams get dispute-reason charts, founders get a single revenue and risk view. The gateway still owns the API, the payouts, and the dispute responses; SleekView just charts what it stores.