WP Simple Pay persists more locally than its admin surfaces. The wp_wpsp_* tables hold cached charges, customer records, coupons, and every webhook event the site received from Stripe. The default reports view is thin, and webhook events live behind a separate screen, which leaves finance teams reconciling against the Stripe dashboard alone.

SleekView Charts uses the same local cache and turns it into a four-card finance dashboard. A KPI card sums revenue (succeeded charges, live mode) for the selected period. An Area card plots revenue per day. A Pie card shows status distribution (succeeded, refunded, failed, pending) so refund and failure rates are visible at a glance. A Bar card ranks WP Simple Pay forms by revenue, which highlights which offer is moving the most volume.

Mode (live vs test) is a filter chip on every card so accountant exports never include test charges. Webhook events get a second tab with their own event-type mix chart for triage.

Stripe is canonical for payments, but the WordPress cache only adds value when it is queryable and visual. WP Simple Pay's persistence is sound and the dataset is rich, yet the admin surfaces it thinly: a flat list, a separate webhook screen, no chart-level filtering by mode. Finance teams end up reconciling against the Stripe dashboard alone or exporting and pivoting in a spreadsheet.

A four-card chart layer changes the daily rhythm. Revenue as a KPI plus daily trend covers the cash-flow question without ambiguity. Status mix surfaces the rising failed slice that points at a webhook or card-network issue.

Top-form ranking puts the offer that carries the business in plain view. Mode as a filter chip prevents the accountant export from ever including test charges, which is the failure mode that costs hours to clean up. The plugin still owns gateway operations; SleekView Charts owns the queryability and the visualisation, which the local cache always implied without ever quite delivering.