The official PayPal Payments extension (formerly PayPal Checkout) persists each order's PayPal order ID, capture ID, transaction ID and funding source on the WooCommerce order. Funding source is the most useful signal: it tells whether the customer paid with their PayPal wallet, a card via PayPal, Venmo, or one of PayPal's Pay Later options. The default WooCommerce orders screen rolls all four into a single PayPal bucket with no column for the actual funding path.

SleekView reads wp_wc_orders filtered to PayPal Payments and pulls funding source, transaction intent and capture ID onto every row. Filter to Pay Later orders only for a BNPL audit, sort by funding source to see the wallet-versus-card split, or save a "Stuck at AUTHORIZE" view for B2B and pre-order flows where captures lag.

The plugin keeps owning the PayPal REST API, captures, refunds and webhooks. The table view owns the audit surface, so the funding-source detail PayPal already writes stops hiding inside per-order panels and becomes a sortable workspace.

PayPal Payments writes funding source (wallet, card, Venmo, Pay Later) to every order, but the default WooCommerce admin rolls them all into one PayPal bucket. That hides the most actionable signal: whether the wallet share is rising, whether Pay Later actually moves volume, whether card-via-PayPal is eating into a direct card gateway. SleekView reads the same wc_orders_meta the gateway writes and renders funding source, intent and capture ID as audit columns, so the orders screen finally separates the four funding paths.

Operators see which PayPal angle works, finance reconciles by funding mix, support catches stuck authorizations before customers escalate. The plugin keeps owning the PayPal REST API; the table just renders what it already stores.