Zip Checkout (formerly Quadpay in the US, Zip across AU and NZ) persists each Zip-paid order's charge ID, order reference and approval state to WooCommerce order metadata. Approval state is the metric that decides whether on-page Zip messaging is worth the floor space: if approvals collapse, the lift evaporates. The default orders screen treats Zip rows like any other gateway, with no column for approval state and no saved "Declined Zip" view.

SleekView reads wp_wc_orders filtered to Zip and pulls approval state, charge ID and refund references onto every row. Filter to declined Zip orders only for the conversion review. Sort by total to see whether Zip carts run bigger than direct-card. Save an "Approval funnel" view that walks through Approved, Pending and Declined values in one workspace.

The plugin keeps owning the Zip API, installment processing and merchant portal sync. The table view owns the audit surface, so the approval signal stops hiding inside per-order panels and becomes a row-level workspace.

BNPL economics are not just about AOV lift: if Zip declines half the attempts, the gateway costs floor space without driving the volume it promised. The plugin records approval state per order, but the default WooCommerce admin treats it as flat meta with no aggregation and no saved view. SleekView reads wp_wc_orders filtered to Zip and renders approval state, charge ID and refund meta as audit columns, so conversion teams see the funnel, support catches declined attempts and finance reconciles approved orders against Zip settlements.

The plugin keeps owning the Zip API and merchant portal; operators get the row-level surface the approval signal has always needed.