Use WP Full Pay with AI Assistants
WP Full Pay makes selected tools available to compatible AI assistants through the WordPress Abilities API. A connected assistant can read forms, create forms with default settings, and review payment and subscription records.
With the optional WP Full Pay Members add-on, you can also inspect members, protect content, and map existing membership levels to Stripe plans.
In this article
Requirements
- WordPress 6.9 or later, which includes the WordPress Abilities API.
- WP Full Pay installed and active.
- A compatible Abilities API or MCP connector, such as Easy MCP AI, connected to your WordPress site.
- An authenticated WordPress administrator account for reading payment and subscription records.
For connection instructions, see Getting Started with Easy MCP AI.
Connect your AI client and enable WP Full Pay abilities
- In your WordPress dashboard, open Easy MCP AI > Dashboard. In the Connect your AI client area, choose your AI client and follow the on-screen steps to connect it to your site. If you use another compatible connector, follow its connection instructions.
- Open Easy MCP AI > Tools, then select Abilities.
- Find the Full Pay group, enable these abilities, and click Save changes:
fullpay/list-formsfullpay/get-formfullpay/upsert-formfullpay/list-paymentsfullpay/list-subscriptions
- Refresh the available tools in your AI client so it can use the enabled abilities.
Available abilities
| Ability | What it does |
|---|---|
fullpay/list-forms | Lists payment, subscription, donation, and save-card forms. |
fullpay/get-form | Reads a form's stored configuration. Webhook header values are redacted. |
fullpay/upsert-form | Creates a form with default settings. If a matching form already exists, it returns that form unchanged; it does not edit the existing form. |
fullpay/list-payments | Lists payment records or retrieves a payment. Results may include personal data. |
fullpay/list-subscriptions | Lists subscription records or retrieves a subscription. Results may include personal data. |
WP Full Pay Members abilities (optional)
Install and activate WP Full Pay Members alongside WP Full Pay. The WordPress Abilities API, WordPress requirement, and authenticated connector described above also apply to the add-on.
The add-on registers a separate fullpay-members group. Enable the required Members abilities in your compatible connector, save your changes, and refresh the tools in your AI client. Registered abilities are not necessarily available through every connector: a connector may omit destructive abilities such as reconciliation.
| Ability | What it does |
|---|---|
fullpay-members/set-content-protection | Reads protection when you supply only post_id, the WordPress post or page ID. Set protected=true to restrict content or protected=false to make it public. Supply level_id, the membership level identifier, when protecting content that has no level yet; that level and higher-priority levels receive access. |
fullpay-members/list-levels | Lists existing membership levels, their WordPress roles, priorities, and Stripe plan mappings. |
fullpay-members/upsert-level | Requires both level_id and plan_id to map an existing membership level to a Stripe plan. Use an empty string ("") or none as plan_id to clear the mapping. It cannot create new membership levels. |
fullpay-members/list-members | Lists members, optionally filtered by level and status, or retrieves one member by WordPress user_id. Results include personal data. |
fullpay-members/reconcile-membership | Re-checks one user_id against Stripe in the current mode. Returns before and after membership data, plus changed to indicate whether it changed anything. This is a destructive operation; see the warning below. |
For list-members, mode=current (the default) uses the site's current Stripe API mode. You can instead request mode=live or mode=test. Pagination starts at page=1 and defaults to per_page=20, with a maximum of 100 members per page. Check the returned total_pages and request the remaining pages for a complete list.
Plan mappings are validated against existing membership levels and Stripe plans in the site's current API mode. These Members abilities do not accept a dry_run option, and writes are disabled in demo mode.
Permissions and safe usage
The connected user must be a WordPress administrator to read payment or subscription records. The assistant acts through the authenticated connection, and enabling abilities does not bypass the user's permissions.
Payment and subscription records can include customer names, email addresses, postal addresses, and Stripe identifiers. Enable these abilities only for assistants and connectors you trust, and only when the connected account should be able to access this information.
Stripe keeps test-mode and live-mode data separate. Specify the mode you want when asking the assistant to review payments or subscriptions; use test mode for test data and live mode only when you intend to access real transaction records. For more information, see Configuring the Stripe API keys.
To validate a new form before saving it, ask the assistant to use dry_run=true. Review the proposed result before asking it to create the form. Form creation uses default settings; these abilities cannot change an existing form's settings or global WP Full Pay settings.
The fullpay/cancel-subscription ability is available through the REST-visible API but is not exposed through AI Connect because cancellation is destructive. Cancel a subscription through the WP Full Pay admin interface instead.
For Members, listing levels or members, changing plan mappings, and reconciling membership require manage_options, the WordPress capability for managing site settings. Reading or changing content protection requires permission to edit the specified post (edit_post). Enabling a Members ability does not bypass these checks.
Member privacy
Member results include email addresses and Stripe subscription identifiers. Individual member lookups return additional user and Stripe customer details. Enable access only for trusted assistants, connectors, and accounts that should be able to view this information.
Reconciliation can remove access
fullpay-members/reconcile-membership is registered for REST API access and marked as destructive, but your connector may not expose it. It checks one member in the current Stripe API mode and can assign No Access for unpaid, canceled, missing, or unretrievable subscriptions. If Block members with "past due" status is enabled, members with past_due subscriptions can also lose access. Reconciliation never restores a membership level. Confirm the member and current mode before invoking it; there is no Members dry-run option.
Example prompts
- “List my inline donation forms.”
- “Validate a new inline donation form called Spring fundraiser without saving it.”
- “List failed live-mode payments from this month.”
- “Show subscriptions that failed to renew in test mode this month.”
With the optional Members abilities enabled, you can also ask:
- “List my membership levels and their Stripe plan mappings.”
- “Show past-due members in test mode, 20 per page.”
- “Restrict page 123 to the Basic membership level (
wpfs_basic) and higher-priority levels.”