Paystack for WooCommerce processes payments through the Paystack African payment gateway. Orders come through with the standard WooCommerce statuses like wc-pending, wc-processing, wc-on-hold, wc-completed, and wc-refunded, plus Paystack-specific metadata in wp_postmeta for the paystack_txn_ref, the payment_channel (card, bank, USSD, mobile money), the gateway_response, and the date_paid. The native WooCommerce orders screen shows them mixed with all other orders, which makes Paystack reconciliation hard.

SleekView Kanban reads the same WooCommerce orders you would query with WC_Order, filtered to orders that used the Paystack gateway. Pick post_status as the group column and every order becomes a card slotted under Pending, Processing, Completed, or Refunded. Card fronts show the customer name, the order total in NGN, GHS, KES, ZAR, or store currency, the Paystack payment_channel, the paystack_txn_ref, and the date placed, so finance has every Paystack-specific detail right on the card.

Dragging a card between columns calls the standard WooCommerce status transition the admin uses, which fires woocommerce_order_status_changed. Paystack's refund webhook fires for refund transitions when configured, the customer notification email goes out through WooCommerce's email module, and any extension subscribed to the WooCommerce hooks reacts, exactly as it would after a manual admin status change from the order edit screen.

African e-commerce stores running Paystack process hundreds of transactions every day across card, bank, USSD, and mobile money payment channels routed through the Paystack gateway. Some clear instantly, some take a few minutes for bank confirmation, some get stuck in Pending when the customer abandons the Paystack page. The default WooCommerce orders screen mixes Paystack transactions with COD, prepaid, and other gateway orders, which makes Paystack-specific reconciliation a CSV export exercise every single day.

The disconnect between what the Paystack dashboard shows and what WooCommerce shows is the source of most accounting headaches for African merchants using Paystack. A successful card payment lands in Paystack but the WooCommerce order stays Pending because the webhook failed. A refund shows in WooCommerce but never appears in the Paystack dashboard because the integration was misconfigured.

A daily payout from Paystack shows hundred thousand Naira more than WooCommerce reports as Completed and nobody knows why. A kanban view that reads and writes the same WooCommerce orders the gateway processed, filtered to Paystack specifically, keeps the team and the books honest. Every drag is a real status change, every column count reflects the real Paystack pipeline health, and the cards themselves carry enough context for a new finance analyst to handle reconciliation on day one of the job.