No. It writes every Authorize.Net reference (transaction ID, CIM customer profile, payment profile, AVS, CVV) into wc_orders_meta on HPOS, or wp_postmeta on legacy CPT storage. SleekView reads those meta keys as columns, which is the cleanest path because there is no separate plugin schema to join.

No. _wc_authorize_net_cim_credit_card_trans_id is immutable on Authorize.Net's side, so SleekView marks it read-only. Editing it locally would silently desync the order from the actual transaction record. Notes and explicitly-editable meta keys can still be inline-edited and route through WooCommerce's CRUD layer.

Yes. SleekView reads from wc_orders and wc_orders_meta on High-Performance Order Storage. Sites still on legacy CPT storage are also supported; the grid detects the active storage layer and queries accordingly. Saved views and column promotions migrate transparently.

_wc_authorize_net_cim_payment_profile_id appears as a filterable column. Last4 and card brand show as separate columns when the gateway has captured them. PAN is never stored locally because Authorize.Net does not expose it. Per-role masking can hide last4 from staff who do not need it.

Refunds still run through the WooCommerce Authorize.Net CIM gateway's existing order action because they need to update Authorize.Net-side state. SleekView shows refund state inline as a column so finance can see refunded, partially-refunded and pending statuses across the whole order list at once.

Yes. The plugin writes eCheck-specific meta keys like _wc_authorize_net_cim_echeck_trans_id separately from credit card transactions. SleekView surfaces them as their own columns and filters, so eCheck reconciliation runs as its own saved view (slower clearance windows make the split useful for finance).

When paired with WooCommerce Subscriptions, renewal orders flow through the same CIM customer profile and produce new transaction IDs in wc_orders_meta. SleekView treats renewals as normal rows in the grid; filtering to a single CIM customer profile assembles the full renewal history without a custom report.

Yes. Filter by AVS response code (mismatch, partial, unsupported) and export the visible slice as CSV. Column-level masking applies to the export so PII fields hide for users without the right capability. Risk teams typically schedule a weekly export against a saved AVS view.