Plugin-owned tables include wp_wpsp_coupons, wp_wpsp_webhooks, plus payment cache tables that mirror Stripe charge metadata. SleekView reads them directly. Stripe customer IDs and charge IDs are captured so cross-referencing with the Stripe dashboard works without any custom export job.

Yes. Stripe is canonical. The local cache is for fast queries, audit, and reconciliation inside WordPress. SleekView is honest about that and shows charge IDs as columns so you can cross-reference. If a row in WordPress doesn't match Stripe, Stripe wins; the cache exists for query speed, not for resolving disputes.

Refunds are a Stripe API operation. SleekView can surface a refund button that calls the WP Simple Pay refund flow, but the actual refund happens through Stripe. The button is a convenience for support teams who already work in WordPress; the API call and money movement stay on the gateway side as they should.

Yes. Subscription metadata is in the same WP Simple Pay table family. A subscriptions view with status, next-charge date, and customer columns works well. Pair it with a churn filter (status = canceled, last 30 days) and you get a recovery queue without any custom analytics integration.

WP Simple Pay flags rows by mode. SleekView lets you filter on it so finance ops never accidentally includes test transactions in a reconciliation export. Make the default view live-only with a chip override for staging or QA work, and the failure mode of 'wait, those charges aren't real' goes away.

Yes. Every webhook event lands in wp_wpsp_webhooks with type, status, and timestamps. SleekView surfaces that as a filterable view. Replays from the Stripe dashboard land as new rows in the table, so the audit trail stays intact and you can see how many times a particular event was retried.

Yes. The payment cache includes failed attempts with the failure code Stripe returned. Filter by status = failed, sort by date, and you get a list of card declines, insufficient funds, and 3DS challenge failures. Useful for spotting patterns like a particular issuer rejecting your charges or a webhook config that's silently dropping confirmations.

Queries hit indexed columns where WP Simple Pay has indexes (date, status, mode) and SleekView's cache duration controls keep dashboard loads cheap on stores with hundreds of thousands of charges. Pagination and saved filters do the rest. Inline edits stay rare on payment data so write-path concurrency isn't an issue in practice.