No. The 2Checkout (Verifone) gateway plugin writes everything (sale ID, payment method, fraud score, recurring flag, INS responses) into wc_orders_meta on HPOS or wp_postmeta on legacy storage. SleekView reads those meta keys as columns, with no extra schema to join.

Yes. Promote _2checkout_fraud_score to a numeric column and sort or filter by threshold. A saved view of "fraud score above 50 in the last 7 days" gives the risk team a daily review queue without per-order clicks.

Yes. SleekView reads from wc_orders and wc_orders_meta on High-Performance Order Storage. Sites still on legacy CPT order storage are supported too; the grid auto-detects the active layer. Saved views carry over across the HPOS migration.

Yes. _2checkout_recurring is written on renewal orders and exposed as a boolean filter. A saved view of "renewals only" separates subscription cycles from one-off purchases for reporting and retention work.

No. _2checkout_order_number is immutable on Verifone's side; editing it locally would silently desync the order from the gateway. SleekView marks it read-only. Notes and editable meta keys can still be inline-edited and route through WooCommerce's CRUD layer.

Currency is its own column with locale-aware formatting. 2Checkout supports cross-border payments in many currencies, so currency as a filter lets finance split EUR, GBP, USD and other flows for separate reconciliation against Verifone's per-currency payouts.

Fraud score, payment method and recurring status together flag the riskiest cohorts. A saved view of "high fraud score on first-time card orders, shipped" surfaces the orders most likely to dispute. Pre-collecting shipping evidence for that view shortens dispute response time later.

Yes. Filter to whatever finance or risk asked for, then export the visible slice as CSV. Column-level masking applies on export, so PII fields hide for users without the right capability. Common exports include daily fraud-flagged orders and monthly recurring-renewal failures.