WPForms PayPal Standard writes each completed transaction to wpforms_payments, with a total, a currency, a status, a gateway set to paypal_standard, and a foreign key to wpforms_entries. The default Payments screen lists rows, and PayPal's own dashboard groups by account but not by WPForms form. Per-form revenue, status mix, and currency split sit in two systems that don't talk to each other.

SleekView Charts treats wpforms_payments as the dataset, joins wpforms for readable form names, and lets you group by form_id, status, currency, or date_created. Sum total filtered to gateway paypal_standard for revenue, count payments for volume, average for typical order size. wpforms_payment_meta stores PayPal-specific fields like txn ID and payer email so customer-side breakdowns work out of the box.

Charts share the dataset and saved filters with Table, Kanban, and Feedback views, so jumping from a refund-rate KPI back to the actual payment rows is one tab change. The same indexed queries powering the WPForms admin keep cards fast even with 100k payments across years of donation history.

WPForms PayPal Standard is the gateway many donation and event sites lean on because it stays inside the existing form workflow without a separate checkout build. The data is rich. Every payment carries a status, a currency, a total, and a form ID, but the Payments screen only paginates rows.

Finance teams reconciling a PayPal payout cycle need the sum of completed totals over a date range. Fundraising ops wants per-campaign volume. Form admins want to spot pending entries that never converted, often because of IPN delivery delays.

None of these are exotic analyses, they are numbers the gateway already wrote into wpforms_payments. SleekView Charts surfaces them as configurable cards on the same payments table the admin already uses, so PayPal reporting becomes one saved view instead of a CSV ritual at month end.