Paystack for WooCommerce records each successful payment with the Paystack transaction reference (often called txn_ref) and the channel (card, bank, USSD, mobile_money, qr) stored in the order's meta. On HPOS stores those values land in wc_orders_meta; on legacy stores they live in postmeta. The default Orders screen shows order number, status, total, and customer, but the gateway-side fields stay invisible until you click into each order.

SleekView reads the order tables alongside the Paystack meta keys and presents one row per order with the transaction reference, the payment channel, and the gateway response status where stored. Filter to Paystack-paid orders for a date range, group by channel to see what proportion of orders came in via card versus bank versus mobile money, scope to refunded orders to reconcile against the Paystack refund report. Inline-edit order status routes through WooCommerce's CRUD layer where supported, so the WooCommerce-side status stays consistent with the gateway-side hooks.

The view stops at what's stored against the order. Paystack's authoritative settlement and chargeback data still lives on the Paystack dashboard. SleekView's job is to make the WooCommerce side legible enough that reconciliation against Paystack becomes a side-by-side comparison rather than a per-order spelunking exercise.

Paystack-powered WooCommerce stores in Nigeria, Ghana, South Africa, and Kenya end up doing the reconciliation work that gateway-paid stores everywhere do, with one extra dimension: channel mix. Card, bank, USSD, mobile money, and QR each behave differently in settlement timing and in customer experience, and the share of each channel shifts as the local payments market evolves. WooCommerce knows the order, the customer, the total, and the WooCommerce-side payment status.

Paystack knows the transaction reference, the channel, the settlement timestamp, and the refund state. The plugin stores Paystack's view of the world against each WooCommerce order, but the default order list keeps those fields invisible. So reconciliation becomes "open every Paystack-paid order from yesterday, copy the reference, paste into the Paystack dashboard, confirm match" and channel mix becomes a quarterly export.

SleekView's job is to expose the meta as columns and let the team filter to the day's Paystack-paid orders, group by channel, and read the mix in one screen. The Paystack dashboard stays the source of truth for settlement and chargebacks. The WooCommerce side becomes legible enough that the side-by-side match is the only step finance has to perform manually.