The official Stripe gateway plugin (woocommerce-gateway-stripe) writes Stripe-side state to each WooCommerce order through wc_orders_meta. Charge ID, intent ID, customer ID, card brand, last four, 3DS outcome, country, and currency all land as _stripe_-prefixed meta keys. The default WooCommerce order screen reads those as raw meta fields, and Stripe's own dashboard lives off-site, so reconciling a working day means switching contexts between Orders and Stripe to keep statuses aligned.

SleekView Kanban reads wc_orders joined to the Stripe meta keys and groups orders by the consolidated payment status. The board renders one column per state: Authorized awaiting capture, Captured, Refunded, Disputed. Each card shows the customer name, the captured amount and currency, the card brand and last four, the country, and a small 3DS badge for orders that passed the issuer challenge. Finance reads the day in column counts and sees the authorized-not-captured queue without leaving WordPress.

Drag a card from Authorized to Captured and SleekView calls the Stripe API to capture the intent for the meta-attached intent ID, the same call the gateway plugin issues on its admin actions. The order status updates, the captured meta key flips, and any plugin listening for the standard WooCommerce payment-complete hooks reacts as if a click came from the order page. Refunds, disputes, and 3DS-recheck flows keep working because SleekView reads and writes the same meta rows the rest of the gateway uses.

The gateway plugin already promotes a Stripe charge into a set of meta keys on a WooCommerce order. That schema is a kanban waiting to be drawn: a column per charge status, a card per order, a drag for every transition. The default view reads those meta keys as a metabox on the order page, which forces a per-order navigation pattern for work that runs in batches.

The kanban replaces that pattern with column counts and drag-and-drop, and the daily capture sweep collapses from a thirty-row scroll plus per-row clicks into a column drain. The 3DS-authorized badge surfaces issuer-challenge outcomes as a visual cue rather than a hidden meta value, which feeds straight into chargeback-liability reviews. Saved boards per currency and per country make cross-border ops a one-filter switch, so a US lead and a EU lead each work their own scoped board on the same data.

The Stripe API, the gateway plugin, the 3DS handshake, the dispute submission flow, and the WooCommerce order lifecycle all keep working without changes because the kanban reads and writes the same wc_orders_meta rows and calls the same Stripe endpoints the gateway already uses.