Moneris is the dominant Canadian card processor and its WooCommerce extension stores receipt id, reference number, ISO response code, AVS, and CVD per order. On HPOS stores these land in wc_orders_meta as keys like _wc_moneris_receipt_id, _wc_moneris_reference_num, _wc_moneris_iso_response_code, and _wc_moneris_avs_response. The default Orders screen does not surface any of them.

SleekView reads those keys as columns alongside the WooCommerce order data. Daily Moneris Merchant Direct reconciliation becomes a saved view filtered by capture date with totals visible inline. Declined transactions filter by ISO response code, and AVS mismatches get their own audit table. Authorisations approaching the Moneris settlement window get a sort-by-auth-age view so they don't expire silently. Tokens in woocommerce_payment_tokens joined to woocommerce_payment_tokenmeta expose saved card data for customer-rooted token-management workflows.

Inline status edits route through WooCommerce CRUD, so woocommerce_order_status_changed fires and the Moneris extension's own capture, void, and refund handlers continue to run from the order context. SleekView gives ops a row-level view of the data the plugin already writes; the plugin still owns the gateway communication.

Moneris is the largest Canadian card processor and its WooCommerce extension covers a large share of Canada-based stores. The card lifecycle through Moneris has the usual auth-capture-void-refund states plus ISO response codes, AVS results, and CVD codes that the gateway returns on every transaction. The plugin records all of that into order meta.

The default WooCommerce Orders screen reads almost none of it. A merchant sees the order status and CAD total, not the ISO response, not the AVS result, not the receipt id needed to reconcile against Merchant Direct. Finance teams reconcile by hand, risk teams spot AVS mismatches only after the chargeback notification, support teams hand dispute evidence to ops one order at a time.

SleekView reads the meta the plugin already writes and exposes it as columns ops can filter, sort, and bulk-update. The plugin's gateway calls and webhook handlers continue unchanged. The gain is row-level visibility of data the WooCommerce admin has always stored but never shown.