Paymattic 4.6.25: Stripe Card Update, Feed Mapping, Square Verification, and More

Hey Paymattic users, here’s Paymattic 4.6.25.

This release focuses on giving subscribers more control, tightening payment security, and shipping a targeted round of bug fixes.

What’s new in Paymattic 4.6.15?

Update Stripe payment cards from the User Dashboard

Previously, a subscriber with an expired/replaced card often needed to contact support to keep their subscription active. Now, Stripe subscribers can update their saved payment method directly from the Paymattic User Dashboard; no admin intervention and no interruption to the subscription.

Under the hood, the flow uses Stripe SetupIntent to attach the new card and set it as the subscription’s default payment method. The subscription remains active; the updated card is used on the next billing cycle.

Use cases

• Nonprofits collecting recurring donations where cards expire mid-campaign
• Membership sites where subscribers want to switch payment methods
• Subscription businesses where renewals must not fail due to outdated cards
• Agencies managing client subscriptions without touching the Stripe dashboard

Payment item field mapping in Integration Feeds

Integration feeds now support payment item field mapping with conditional logic. You can map specific payment line items to CRM fields, webhook payloads, or automation triggers, and apply conditions so only certain item types, tiers, or amounts trigger a given integration.

This is especially useful for multi-tier donation forms, bundled product forms, and event registrations where a single form needs to drive different downstream workflows.

Square webhook signature verification per mode (Live/Test)

Square webhooks now use separate signature keys for Live and Test modes, aligning with how Stripe and PayPal verification already works in Paymattic.

This closes a gap where test-mode webhook events could previously be replayed against a live-mode handler.

Improvements: Paymattic 4.6.25

Here, we made some notable improvements in this update.

Stronger Stripe renewal failure handling

When a Stripe subscription renewal fails expired card, insufficient funds, bank decline, Paymattic now processes the failure more reliably:

• Subscription records update consistently
• Renewal transactions reflect the correct failed state
• Retry logic is no longer blocked by edge cases in the webhook flow

JSON export now streams results (lower memory usage)

For forms with large submission volumes, the JSON exporter previously loaded all records into memory before writing the export file. It now streams results in chunks, significantly reducing peak memory usage on shared hosting and large datasets.

There’s no behavior change from the user’s perspective, just a faster, safer export.

Fixes: Paymattic 4.6.25

This release includes a focused set of bug fixes:

• User Dashboard access – Permitted roles with dashboard capabilities were missing access due to a capability-check ordering issue.
• Stripe renewal webhooks – Updated invoice schema from Stripe’s API wasn’t parsed correctly, causing sync failures on renewal events.
• Duplicate coupon AJAX – Elementor popup re-initialization triggered a second coupon validation request, leading to confusing UX and potential double-discount edge cases.
• Phone field script error – Classic utils.js enqueue caused a script error during phone field initialization; load order corrected.
• FluentCommunity endpoint – An integration endpoint was accessible without authentication; now requires a valid nonce and user session.
• Webhook and Zapier feed scope – Feed mutations weren’t scoped to the authorized form, allowing cross-form edits. Ownership checks are now enforced.
• PayPal IPN security – The option to bypass IPN verification has been removed. IPN is always verified and debug logs are redacted to safe fields only.
• Subscription cancellation – Cancellation could proceed without verifying the requester owns the subscription. Ownership is now verified before cancellation.
• Predefined donation amounts – When custom amount input is disabled, submitted amounts are now validated server-side against configured options to prevent tampered submissions.

Update Paymattic now

Paymattic 4.6.25 is rolling out to all sites today.

Update via WordPress Dashboard → Plugins → Updates, or download the update from your account at paymattic.com.

Have questions about any of these features or run into anything unexpected, our support team is one ticket away.

Happy collecting!