Get Payment Summary is a WordPress ability from Fluent Forms — usable via Easy MCP AI, which connects Claude, ChatGPT, and any AI assistant to your site.
Install Free Plugin →Get Payment Summary
Read-onlyServer-computed payment totals by status, transaction type, and currency.
Needs the Fluent Forms MCP server switched on in FluentForm → Settings → MCP, and WordPress 6.9+ so wp_register_ability() exists (abilities are only registered when the function is present). Reaching the server also requires a logged-in WordPress user holding at least one FluentForm capability. Each ability additionally checks a specific FluentForm capability (e.g. fluentform_dashboard_access, fluentform_forms_manager, fluentform_entries_viewer, fluentform_manage_entries, fluentform_view_payments, fluentform_settings_manager) via the plugin's own Acl system, and every write ability requires a two-step dry_run → confirm_token round-trip through WriteGuard before anything is persisted. Note (from source comments): a WordPress role granted FluentForm access via the Role Manager passes every per-ability capability check, including delete-submission and bulk delete_permanently — the real boundary for such a user is 'has FluentForm access, restricted to their form scope', not per-tool separation; only individually-assigned 'specific forms' managers are gated the way each ability's declared capability implies.
What it does
Computes revenue totals server-side from the same helper the admin Reports page uses, so the two can never drift: amount and count per payment status (paid, pending, refunded, and so on), split into one-time and subscription transactions, grouped by currency so amounts are never blended across currencies. Scope to a single form with form_id or omit it to aggregate every form in the caller's access scope. Defaults to the trailing 30 days; the date window is not clamped (unlike the trend/report tools) since this is a small grouped SUM rather than a per-day scan, so lifetime totals are a legitimate ask. Fails with a structured error if the payment module is disabled.
See it in action
You ask your AI assistant
"How much revenue came through payments in the last 90 days?"
Inputs
| Name | Type | Required | Description |
|---|---|---|---|
| form_id | integer | No | Optional. Omit to aggregate across all forms in your access scope. |
| date_from | string | No | YYYY-MM-DD (site timezone). Defaults to 30 days ago. |
| date_to | string | No | YYYY-MM-DD (site timezone). Defaults to today. |
Returns
form_id (or null for all forms), the date window, a multi_currency flag, and a currencies array — each entry with currency, currency_symbol, total_paid, and onetime/subscription breakdowns by payment status; single-currency results also surface currency, total_paid, onetime, and subscription at the top level.
Permission
Requires the fluentform_view_payments capability.
More Fluent Forms abilities
Add Submission Note
Attach an internal staff note to one entry; not visible to the submitter.
Bulk Update Submissions
Apply one action — read, unread, trashed, favorite, unfavorite, or permanent delete — to up to 200 entries at once.
Create Form
Create a new form from a title and an ordered list of fields, or a basic contact form by default.
Create or Update Email Notification
Create a new email notification or update an existing one — including its recipient.
Delete Submission
Permanently delete one entry and its uploaded files.
Get Form
Load one form's full detail, including its field schema, so the agent knows the exact field keys used in submissions.