YITH Stripe handles card payments and Stripe-supported methods (cards, Apple Pay, Google Pay, SEPA, iDEAL, depending on configuration) for WooCommerce orders. Every transaction writes meta to the order: payment method type, card brand, last four digits, transaction status and the Stripe charge ID. The default admin shows that data on a single order's edit screen rather than as a cross-order surface.

SleekView reads the same Stripe meta from wc_orders (or wp_postmeta under legacy storage) and renders every Stripe-paid order as a row. Order, customer, total, payment method, card brand, charge ID and status all sit as real columns. Filter to payment_method = apple_pay to read Apple Pay adoption. Filter to status = failed to triage gateway issues. Sort by total desc to surface the highest-risk transactions for reconciliation.

The plugin keeps owning the gateway integration and the Stripe webhook handling. SleekView owns the audit surface, so the gateway data YITH already records stops hiding inside per-order screens and becomes something finance and operations can actually query.

Every checkout writes payment method, card brand and charge ID into order meta, and almost nobody reads it as a cross-order surface. YITH Stripe captures the data cleanly, the gap is the admin view. Finance teams export CSVs to reconcile, ops teams crawl error logs to triage failures, conversion analysts guess at Apple Pay adoption.

SleekView reads the same Stripe meta YITH writes and renders every Stripe-paid order as a row with method, brand, charge ID and status as real columns. Filters stack into a single query so the failure triage, the method-adoption review and the high-value reconciliation list become saved views rather than weekly exports. The plugin keeps owning the gateway integration and the webhook, while finance and operations finally get the gateway-grade audit surface the dataset always deserved.