FunnelKit Stripe Gateway runs WooCommerce checkouts through Stripe and writes _stripe_source_id, _stripe_intent_id, payment_method and capture status onto each order as standard postmeta. The WooCommerce orders screen lists the data row by row, but it's a single column on a generic table, with no payment-specific filters and no way to isolate failed intents from successful captures at a glance.

SleekView reads wp_posts where post_type is shop_order joined to wp_postmeta and exposes payment_method, intent status, capture flag, customer, currency and _order_total as real columns. Filter to orders where payment_method matches the Stripe gateway and intent status is failed to triage the day's recovery list. Sort by _order_total descending to scan the highest-value wallet payments. Group by payment_method to see card versus Apple Pay rows side by side.

FunnelKit keeps owning the gateway, the checkout and Stripe API integrity. The table view owns the audit surface, so the payment data FunnelKit already records on every order becomes a queryable grid for finance, ops and support.

FunnelKit Stripe Gateway records every charge with the method, intent and capture status, but those fields live as one column on a generic orders screen and as scattered notes in the Stripe dashboard. The daily questions are row-level: which intents failed yesterday, which orders are still authorized but not captured, which customers ran a high-value Link payment. SleekView turns shop_order rows joined to Stripe postmeta into a queryable grid that answers those questions on open.

A failed intent becomes a callback, an authorized order gets captured before the hold expires, and a finance role exports a reconciliation slice without copying numbers from the Stripe tab. FunnelKit keeps owning the gateway and the checkout, SleekView just makes the rows it already writes navigable.