Yes. WPForms Stripe stores payments in wpforms_payments with columns for total, currency, status, gateway, form_id, customer_email, and date_created. SleekView reads them all and pivots wpforms_payment_meta for Stripe-specific fields like payment intent and subscription ID.

Numeric aggregation treats total as a number regardless of currency, so a naive sum mixes EUR, USD, and GBP into one figure. Group or filter by currency to keep per-currency sums separate, which is what finance teams need for clean Stripe reconciliation.

Yes. The Stripe addon writes subscription IDs into wpforms_payment_meta. Group by whether the meta is present or null and you get a clean Pie of one-off versus recurring revenue, or sum total filtered to recurring for an MRR-style card.

Aggregations run as SELECT ... GROUP BY against indexed columns on wpforms_payments. Card render time depends on the index on the group-by column more than total row count, so hundreds of thousands of payments stay responsive when grouping by status or date_created.

Yes. status stores processed, failed, refunded, and partial-refunded values. Build a Pie or filter to refunded and put a Number on the sum of total next to it so the team sees the refund footprint in one view.

Cards re-query on view load and filter change. Set a refresh interval per view if finance needs near-live counts during a campaign. Idle dashboards don't poll, so closed views don't add database load.

Yes. Save views and scope them per WordPress role or capability. Finance sees a multi-currency revenue dashboard, form admins get a failure-rate view, marketing gets a per-form attribution dashboard. Personal filters stay scoped to each user.

Each card exports aggregated rows as CSV with the group-by labels and the aggregate values. Useful for sending finance the underlying numbers behind a refund-rate Pie or archiving a quarter-end snapshot of revenue per form.