The SkyVerge Authorize.Net gateway writes transaction ID, CIM customer ID, capture state, payment type, AVS and CVV outcomes against each WooCommerce order in wc_orders_meta. SleekView already promotes those _wc_authorize_net_-prefixed keys into typed columns in a working grid. The dashboard layer answers the aggregate questions: how many orders are sitting authorized-not-captured, what share is eCheck still in ACH clearance, which AVS or CVV outcomes need risk review, which CIM B2B customers are driving revenue this period.

SleekView Charts groups by any Auth.Net meta key. A Donut splits payment type. A Bar ranks AVS outcomes. A Number pins the authorized-not-captured queue. An Area tracks daily card versus eCheck volume.

The grid handles the per-order capture sweep and risk triage. The dashboard becomes the read layer ops opens at start of shift, finance opens for B2B revenue review, and risk opens for the daily AVS-mismatch scan.

Authorize.Net merchants run operational workflows the default WooCommerce admin does not surface. Daily capture sweeps depend on knowing how many orders are sitting authorized-not-captured today, not on walking the order list one row at a time. eCheck clearance windows depend on seeing the ACH-pending share as a single count so fulfillment can hold those orders without slowing card-funded ones.

AVS and CVV outcomes are exactly the data risk needs at a glance to triage borderline orders before warehouse hands a package to a carrier. CIM saved customers represent B2B accounts where lifetime spend is more meaningful than per-order value. The grid handles each row's work; the dashboard handles the aggregate read.

Together they turn Authorize.Net from a per-order metabox into a real operational surface that finance, ops and risk can all open first thing each shift.