The Authorize.Net Payment Gateway for WooCommerce (Auth.Net) is the long-running US-focused gateway plugin originally maintained by SkyVerge. It writes Auth.Net-side state to each WooCommerce order through wc_orders_meta with _wc_authorize_net_-prefixed keys: transaction ID, capture state (auth-only, captured, voided, refunded), CIM customer profile ID, payment type (credit card or eCheck/ACH), AVS result, and CVV result. The default WooCommerce order screen reads those as raw meta, so the daily authorize-not-captured queue and the AVS-mismatch risk review both run as manual filters.

SleekView Kanban reads wc_orders joined to the Auth.Net meta keys and groups orders by capture state. The board renders one column per state: Authorized (auth-only awaiting capture), Captured, Voided, Refunded. A virtual eCheck column surfaces ACH transactions still in clearance windows, where the WooCommerce-side status sits in a holding pattern until the ACH settles. Each card shows the customer name, the amount, the payment-type badge (Visa, Mastercard, Amex, or eCheck), the AVS and CVV outcomes as small chips, and a CIM-customer link for repeat B2B accounts.

Drag a card from Authorized to Captured and SleekView calls the Auth.Net prior-auth-capture endpoint for the meta-attached transaction ID. The WooCommerce order status updates, the captured meta key flips, and the storefront sees a paid order without a separate Authorize.Net merchant portal session. Voids, refunds, and the eCheck-clearance reconciliation all keep running because SleekView reads and writes the same meta rows the gateway plugin uses today.

Auth.Net's authorize-then-capture flow is exactly the kind of two-step transition a kanban handles well: the Authorized column drains into Captured as cards pass fraud review, AVS mismatches drag to Voided, eCheck ACH transactions sit in the clearance column until they settle. The default WooCommerce order screen treats every Auth.Net meta key as a metabox value on a single order, which means the daily sweep is a row-by-row click. The board replaces that with column counts and drag-and-drop, with AVS and CVV chips visible on the card front for risk triage.

CIM-aware B2B work is a one-filter switch instead of a customer-profile search, because the CIM customer profile ID rides on every card. The priorAuthCapture, void, refundTransaction, and ACH-clearance flows all keep running because SleekView reads and writes the same _wc_authorize_net_ meta rows the gateway uses today, and the same merchant credentials. The merchant portal stays the canonical surface for chargebacks and detailed receipts; the kanban is the daily working surface for the captures, voids, and refunds that drive the storefront.