Yes for the relational schema (edd_orders, edd_order_transactions, edd_customers). Those tables landed in EDD 3.0 and most stores have migrated by now. On older EDD versions PayPal references lived in edd_payment postmeta and need a different mapping.

Status changes through EDD CRUD trigger the gateway's refund handlers as configured. The actual PayPal API call goes through EDD PayPal Pro's hook chain, not a SleekView shortcut, so the behaviour matches manual admin edits exactly.

If your store uses EDD Recurring Payments with PayPal billing agreements, subscriptions live in edd_subscriptions with payment history linking back to orders. SleekView can render subscriptions as their own view with PayPal payer id inline, or join them to customers for a subscriber workspace.

Yes. Status edits route through EDD CRUD so completion notifications, refund notifications, and the hooks EDD PayPal Pro listens to all fire as expected. Bulk operations iterate per row through CRUD so side effects match manual edits.

If EDD PayPal Pro stores IPN reference ids or webhook event ids in edd_ordermeta or as part of a transaction record, SleekView surfaces them as a column. The column picker lists meta keys actually present in your install.

Queries hit indexed columns on edd_orders directly. Joins to edd_order_transactions use order id, which is indexed. Aggregate columns (refund count, lifetime spend) are opt-in per view since they're heavier than direct columns.

SleekView exports to CSV with the visible column set. The column order and headers are configurable per view, so you can shape an export to mirror PayPal's activity-download fields for easier line-by-line reconciliation.

Yes. Gate columns containing payer email or shipping address to roles that need them (support, finance) via WordPress capabilities, and exclude them from views other staff can access. The PayPal transaction id alone is a pseudonymous reference.