No. The official plugin uses wc_orders_meta exclusively (and wp_postmeta on legacy CPT storage). Every Stripe-side identifier, intent reference and card detail lives as a meta key on the WooCommerce order. SleekView treats those meta keys as proper columns, which is the cleanest path because there is no separate table to join.

No. _stripe_charge_id and _stripe_intent_id are immutable references to state on Stripe's side, so editing them locally would silently desync the order from the actual charge. SleekView marks those columns read-only. Custom notes and any meta keys you have explicitly marked editable can be inline-edited and route through WooCommerce's CRUD layer.

Yes. SleekView reads from the High-Performance Order Storage tables (wc_orders, wc_orders_meta) that the modern Stripe gateway writes to. Sites still on legacy CPT order storage are also supported; the grid detects which storage layer is active and queries the right one. Column promotions and saved views carry over across the HPOS migration.

Saved sources stored under _stripe_source_id and the Stripe customer reference on wp_usermeta surface as their own filterable columns. Card last4 and brand are exposed; PAN is never stored locally because Stripe does not expose it. Per-role masking can hide last4 from support staff who do not need it.

Yes. The visible slice exports to CSV with any promoted Stripe meta columns included. Column-level masking is honored on export, so PII fields hide for users without the right capability. A common pattern is finance exporting weekly refund-queue slices with _stripe_charge_id, capture date and customer email.

No. SleekView reads only what the gateway already wrote to your database. There is no outbound call to Stripe at any point, which keeps the grid fast and means SleekView works whether the Stripe API is reachable or not. Actions that need to update Stripe (refunds, captures) still run through the gateway's own order actions.

Yes. The gateway writes _stripe_charge_captured as part of the intent metadata. SleekView promotes that as a filterable column, so a saved view of authorized-but-not-captured orders is one click away. Stores running manual capture (preorders, custom fulfillment) use it to clear orders before the seven-day authorization window expires.

For Stripe Connect marketplaces or multi-account stores, the connected account ID stored as gateway meta surfaces as a column you can group by. Application fees and connected-account splits are also exposed as columns when present, which helps marketplace finance reconcile platform revenue against subaccount payouts.