FunnelKit Stripe Gateway processes WooCommerce checkout through Stripe Payment Intents, supports Apple Pay, Google Pay, Link, and saves the Stripe charge ID and customer ID to order meta. Each order lives in the standard WooCommerce orders table with post_status values like wc-pending, wc-processing, wc-on-hold, wc-completed, and wc-refunded. The default order list shows the status but hides the payment method and Stripe IDs behind clicks.

SleekView Kanban reads the same orders through the WooCommerce REST endpoints, pulls the Stripe meta with each row, and turns the status column into the natural grouping axis. Each card shows the customer name, the order total, the payment method, the Stripe payment intent ID, and the order date. Columns mirror your WooCommerce statuses, so the queue is legible without filters and a Stripe-specific board shows exactly what is going on with payments.

Drag a card from Processing to Completed and SleekView writes through the WooCommerce REST endpoints. Stripe webhooks continue to flow into FunnelKit Stripe Gateway, refund drags trigger the standard WooCommerce refund flow which in turn calls Stripe through the gateway, and any subscription renewals from FunnelKit Subscriptions stay attached. The board reflects payment reality without breaking the gateway.

FunnelKit Stripe Gateway turns WooCommerce checkout into a modern Stripe payment surface, with Payment Intents, Apple Pay, Google Pay, and Link all running through one gateway. Every order carries useful payment context: the method that the customer chose, the Stripe payment intent and charge IDs, the customer ID that ties back to a Stripe Customer object. The default WooCommerce admin shows the order ID and the total and hides everything else behind clicks.

For a store running fulfilment from the admin, that means staff click in and out of orders just to remember what payment context they are working in, and disputes or refund questions take a tab juggle to resolve. The board view fixes this by lifting the payment context onto the card itself, so a CS rep handling a dispute can click straight to the Stripe dashboard from the payment intent ID, and a picker working the Processing column can see at a glance which orders cleared instantly through Link versus which needed a manual review. Drag updates the WooCommerce order through the standard REST endpoints, the FunnelKit Stripe Gateway sees the same hooks it always has, and refunds route through Stripe exactly as before.