Skip to main content

FluentForms

#Announcements

Fluent Forms 6.2.15: Apple Pay, Google Pay and Export from Entries

We shipped Fluent Forms 6.2.15 today. It's a regular update with some useful new features and a good set of fixes. Here's a quick overview.

What's new

  • Apple Pay and Google Pay with Stripe. Your Stripe payment forms now show wallet buttons next to the card field, so customers can pay with Face ID, Touch ID or their Google account. The buttons only appear on devices that support them.
  • Export from the Entries page. You can now export entries as CSV, Excel, ODS or JSON right from the Entries screen. The export uses whatever filters you've set, like read/unread, search or a date range.
  • Duplicate integration feeds. Every feed now has a Duplicate button, so you don't have to redo all the field mapping for a similar feed.
  • Browser autofill. There's a new Autocomplete setting under Advanced Options. Browsers can fill in name, email, address and phone for your visitors, and it helps with accessibility too.
  • AI Agents (WebMCP) setting. This is optional and set per form. It describes your form to AI browsers so they fill it in correctly. They still can't submit it on their own.

Improvements

  • CleverReach now has a Resubscribe option, and the list dropdown works properly on accounts with a lot of groups.
  • The Salesforce connection is more reliable, and the "missing required code challenge" error is fixed.
  • Added more security hardening across the free and Pro versions
  • Some other fixes and improvements

Full details are here: https://fluentforms.com/fluent-forms-6-2-15/

Cheers. More cooking 🥳

  • 15 likes
  • 2 comments

Sharad Cholera

When you bringing razorpay update ? When get payment successful still not getting confirm and web hooks don't run automatic

Pascal K

I hope there are plans to integrate payment and payment forms with FluentCart as well? The e-invoicing feature is particularly exciting for us here in Germany. Right now, we have to use webhooks—which work great—but direct integration and processing within the “shop” itself would, of course, be much more convenient and easier :)