No. The Authorize.Net for WooCommerce gateway stores all transaction state as order meta on the WooCommerce order tables. Every _wc_authorize_net_-prefixed key (transaction ID, CIM ID, capture status, payment type, AVS, CVV) lives in wc_orders_meta. SleekView reads those keys as proper columns, which works against legacy CPT order storage and modern High-Performance Order Storage transparently.

Capture still happens via the Authorize.Net plugin because it needs to call the gateway's API to capture against an authorization. SleekView surfaces the auth-only queue as a sortable, filterable list — which orders are still in the authorization window, which are about to expire, which have already been captured — but the capture action itself runs through the existing order action so audit logs stay consistent.

Yes. Payment type is exposed as its own column with canonical values (CC for cards, ECHECK for ACH/eCheck). A saved view of eCheck orders pending ACH clearance becomes the no-ship list — fulfillment runs against captured cards only, while the eCheck queue waits for clearance status to flip. The clearance window is tracked via the standard ACH timeline, not gateway-side.

Yes. WooCommerce Subscriptions renewal orders flow through the same Authorize.Net meta keys, including the CIM customer reference for stored payment methods. Filtering to renewal-only orders becomes a saved view, useful for tracking renewal failure rates and identifying customers whose stored cards are expiring soon. CIM customer IDs persist across renewals which makes per-customer renewal history straightforward.

Yes. SleekView reads from High-Performance Order Storage tables Authorize.Net writes to in modern WooCommerce. Sites still on legacy CPT order storage are also supported. Migrations from CPT to HPOS happen transparently from SleekView's perspective; column promotions and saved views carry over without reconfiguration after the migration.

Yes. Saved views can be scoped private to one user or shared by capability. Common patterns include a shared "Daily capture sweep" view for ops, a shared "AVS mismatch review" view for risk and private analyst views for one-off questions. Sharing respects per-role row scoping so a shared view never bypasses anyone's read permissions.

Authorization timestamp is its own column with the right datetime formatting. Sort by authorization age and the orders nearest to gateway-window expiry surface at the top, which is exactly the order ops should run the capture sweep in. Some merchants build a saved view filtered to authorizations more than five days old as a final-call list before the window closes.

Yes. Column-level read-only flags and per-role row scoping let support see CIM customer IDs for lookups without granting them the capability to modify the reference. The CIM ID is read-only by default because editing it would silently desync the order from the actual saved customer profile on Authorize.Net's side. Internal notes remain editable so support can annotate without breaking data integrity.