No. Unlike WooPayments, the official Stripe gateway plugin uses wc_orders_meta exclusively. 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 way to query them — there is no separate table to join, just a wider view of the order table itself.

No. Charge IDs, intent IDs and other Stripe-side references are read-only because they map to immutable state on Stripe's side. Editing them locally would silently desync the order from the actual Stripe charge. Internal notes, custom tags and any meta keys you have explicitly marked editable can be modified inline. The grid clearly marks which columns are read-only versus editable so the distinction is obvious.

Yes. SleekView reads from the High-Performance Order Storage tables that the modern Stripe gateway writes to. Sites still on the legacy custom-post-type order storage are also supported — the grid checks which storage layer is active and reads from the right one. Migrations from CPT to HPOS happen transparently; column promotions and saved views carry over without reconfiguration.

Saved sources stored as Stripe customer meta on the user (or order, depending on your configuration) show up as their own filterable column. Card last4, brand and country can each be promoted separately. PAN is never stored locally — only last4 and brand — so the exposure surface is limited to what Stripe lets you cache. Per-role masking can hide last4 from support staff who do not need it.

Yes. The visible slice exports to CSV, including any Stripe meta columns you have promoted. The export honors column-level masking, so PII fields hide from users without the right capability. A common pattern is finance exporting refund-queue slices weekly with charge ID, capture date and customer email columns; risk exporting 3DS-fallback slices monthly for compliance review.

No. SleekView reads only what the Stripe gateway plugin already stored in your database. There is no API call from SleekView to Stripe at any point — that keeps the grid fast and means SleekView works whether the Stripe API is reachable or not. If you need to take action on Stripe (refund, capture, dispute response), you do that through the Stripe gateway's existing actions on the order itself.

Yes. Stripe writes capture status as part of the intent metadata, and SleekView promotes that as a filterable column. A saved view of "authorized but not captured" lets stores running manual capture (preorders, custom fulfillment) see exactly which orders need a capture call before the seven-day authorization window closes. The same view is useful for spot-checking accidental capture-on-creation orders.

Currency is its own column with the right formatting per locale. For Stripe Connect setups (marketplaces, multi-account stores), the connected account ID surfaces as a column you can group by, so each subaccount's transaction stream is one filter away. Application fees and connected-account splits are also exposed as columns when present in the meta, which helps marketplace finance reconcile platform revenue against subaccount payouts.