The official PayPal Payments plugin (PPCP) handles every PayPal flow that runs inside a WooCommerce store: Pay with PayPal, debit and credit cards, Pay Later, and Venmo. PPCP writes its state to each WooCommerce order through wc_orders_meta with _ppcp_-prefixed keys: PayPal order reference, funding source, payer email, seller-protection eligibility, capture ID, and order status. The default Orders screen treats those as raw meta values, so the question 'how is funding-source mix shifting today' or 'how many orders are sitting authorized awaiting capture' answers only through a manual filter and a scroll.

SleekView Kanban reads wc_orders joined to the PPCP meta keys and groups orders by their PayPal order status. The board renders one column per state: Pending, Approved awaiting capture, Captured, and Refunded. Each card shows the customer name, the captured amount and currency, the funding source badge, the payer email, and a seller-protection chip. Cards in Approved sort by authorization expiry so the daily capture sweep starts with the orders that need the fastest attention.

Drag a card from Approved to Captured and SleekView calls the PayPal capture endpoint for the PPCP order reference stored in meta, the same call the order page's PPCP action issues today. The WooCommerce order status updates, the capture ID writes back to meta, and the storefront sees a paid order without a PayPal Dashboard round trip. Refunds, voids, and the seller-protection review flow all keep running because SleekView reads and writes the same meta rows the gateway uses.

PPCP already turns a PayPal order into a set of meta keys on a WooCommerce order. That schema is exactly the kind of status-keyed data a kanban surfaces well: a column per PayPal state, a card per order, a drag for every transition. The default order view reads those meta values as a metabox per order, which forces a per-order navigation pattern for work finance and ops actually do in batches.

The kanban swaps that for column counts and drag-and-drop, and the daily capture sweep against authorization expiry becomes a column drain rather than a row-by-row click. Funding-source badges and seller-protection chips surface PPCP-specific signals as visual cues rather than hidden meta, so the Pay Later AOV review, the card-only chargeback queue, and the shipping-decision triage all live as saved boards on the same underlying data. The PayPal capture API, the refund endpoint, the void flow, the webhook stream, and the storefront order lifecycle all keep working without changes because SleekView reads and writes the same wc_orders_meta rows and calls the same PayPal endpoints the gateway uses today.