No. The plugin writes all Braintree-side references (transaction IDs, payment method tokens, customer references, risk decisions) into wc_orders_meta on HPOS or wp_postmeta on legacy CPT storage. SleekView reads those meta keys as columns, no extra schema to join.

Yes. The plugin writes _wc_braintree_paypal_-prefixed keys for PayPal-funded orders and _wc_braintree_credit_card_-prefixed keys for card orders. SleekView surfaces both as their own column groups, so a single filter can separate the two funding sources for reporting and reconciliation.

Yes. _wc_braintree_risk_decision exposes the Approve, Review and Decline outcomes from Braintree's Fraud Tools (Kount or Risk Threshold). SleekView promotes it to a filterable column; a saved view of "Review-flagged in the last 30 days" sits permanently next to the orders list for the risk team.

Yes. SleekView reads from wc_orders and wc_orders_meta on High-Performance Order Storage. Legacy CPT storage is also supported; the grid detects the active layer. Migrations between the two storage models are transparent to saved views and column promotions.

No. _wc_braintree_credit_card_trans_id and the PayPal equivalent are immutable on Braintree's side, so SleekView marks them read-only. Editing them locally would silently desync the order from the real transaction. Notes and explicitly-editable keys can still be inline-edited and route through WooCommerce's CRUD layer.

No. SleekView reads only what the gateway already wrote to your database. There is no outbound call to Braintree at any point. Actions that need to update Braintree state (refunds, voids, captures) still run through the gateway's existing order actions, which keeps the two systems consistent.

When 3D Secure is enabled, the gateway writes the 3DS status and liability shift result as meta keys. SleekView promotes those to filterable columns, so a saved view of "3DS attempted but not verified" or "3DS liability shifted" gives risk and finance the splits they need without custom reports.

Yes. Filter to whatever risk or finance asked for, then export the visible slice as CSV with only the Braintree-relevant columns. Column-level masking applies on export, so PII fields like payment method tokens hide for users without the right capability.