The Formidable PayPal Standard add-on writes each transaction to frm_payments, with an amount, a status, a paysys set to paypal, a foreign key to the entry in frm_items, and metadata for the txn ID and IPN response. Formidable's own Payments listing shows rows, and PayPal's dashboard knows the charges but not the form. Per-form revenue and per-currency mix sit in two places that never join up.

SleekView Charts treats frm_payments as the dataset, joins frm_forms for readable form names through the item_id link to frm_items, and lets you group by form_id, status, or created_at. Sum amount for revenue, count rows for volume, average for typical order size. frm_item_metas exposes the rest of the entry fields so you can split revenue by a custom dropdown answer captured at checkout.

Charts share the dataset and saved filters with Table view, so jumping from a refund-rate KPI back to the actual payment rows is one tab. The same indexed paths the Formidable payments admin uses keep cards fast on tens of thousands of payment rows across years.

Formidable PayPal Standard is the gateway many donation and event-driven Formidable sites lean on because it stays inside the existing entry workflow. The data is rich. Every transaction carries a status, an amount, a paysys code, and a foreign key back to the entry, but the Payments listing only paginates rows.

Finance teams reconciling a PayPal payout cycle need the sum of complete amounts over a date range. Fundraising ops wants per-campaign revenue. 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 frm_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.