Klarna Payments for WooCommerce supports the full Klarna product range across the markets Klarna serves: Pay in 30 days, Pay in 3, Pay Now, and the financing options. The plugin writes Klarna-side state to each WooCommerce order through wc_orders_meta: Klarna order ID, reservation reference, payment category, environment flag (playground vs production), and market. The default WooCommerce order screen renders those as raw meta, so the question 'how many reservations are expiring today' or 'how is Pay in 3 share trending in Sweden' demands a manual filter and a scroll.

SleekView Kanban reads wc_orders joined to the Klarna meta keys and groups by the Klarna order status: AUTHORIZED, PART_CAPTURED, CAPTURED, CANCELLED. The board renders one column per state, with a virtual Expiring Soon column for authorizations approaching the reservation expiry. Each card shows the customer name, the amount and currency, the payment category as a badge (Pay in 30, Pay in 3, Pay Now), the market flag, and an expiry countdown for reservations.

Drag a card from Authorized to Captured and SleekView calls the Klarna capture API for the reservation reference stored in meta, using the plugin's stored Klarna credentials. The WooCommerce order status updates, the capture ID writes back to meta, and the warehouse sees a green card ready to ship. Reservations not captured before expiry land in a 'Expired' column automatically when Klarna's webhook fires, so the working queue stays accurate without manual sweeps.

Klarna runs on reservations with strict expiry windows, and the cost of missing the window is a fresh checkout the customer may not finish. The default order screen treats Klarna state as raw meta on individual orders, which means the daily pre-expiry sweep depends on someone remembering to filter and scroll. The kanban turns the same data into four columns with counts, a reservation-expiry countdown on every Authorized card, and a one-drag capture action that calls the same Klarna API the plugin uses today.

Cross-market work becomes one saved board per market, scoped by _wc_klarna_market, so a Swedish lead and a German lead each work their own column counts without context switching. Pay in 30, Pay in 3, Pay Now, and Financing each get a badge on the card, and a board filter answers cohort questions like 'how is Pay in 3 trending' from a glance instead of a Klarna Merchant Portal session. The Klarna capture API, the refund endpoint, the webhook stream, and the WooCommerce order lifecycle all keep working without changes because SleekView reads and writes the same meta rows the gateway already uses.