You have a membership site. Someone pays through a SureForms payment form. Their subscription renews. Or they cancel. Or they request a refund.
What happens next on your site?
With SureForms 2.12, the answer is: exactly what you want, automatically.
SureForms now tells your membership plugin, your LMS, and your CRM the moment any of those payment events happen. They respond instantly. No manual steps, no delays, no automation tools in the middle.
That is the headline of this release, and there is more alongside it. Here is everything that is new.
Table of Contents
- Payment Hooks: Connect Payments to Memberships, Courses, and CRMs Automatically
- Entries Shortcode: Display Submitted Entries on Any Page
- Conditional Custom Button: Hide or Show the Button Based on Field Values
- Also in This Release
Payment Hooks: Connect Payments to Memberships, Courses, and CRMs Automatically
A payment form should not stop at collecting money. It should also help your site respond to what happened after the payment.
SureForms 2.12 makes that possible by letting payment events trigger actions across your site. A completed payment can unlock access. A subscription renewal can keep access active. A failed payment, cancellation, or refund can update that access when needed.
For site owners, this means fewer manual steps and cleaner payment-based workflows. You can use SureForms with tools like SureMembers, LearnDash, LifterLMS, CRMs, and automation platforms to build memberships, courses, gated content, and subscription flows that react to payment activity automatically.
What payment hooks do
SureForms 2.12 adds dedicated hooks that fire at each key moment in the payment journey: when a payment succeeds, when a subscription is cancelled, and when a refund is processed. These hooks work for both Stripe and PayPal.
Any plugin that listens for these hooks can now respond automatically. The most immediate use cases:
Membership access. A user pays through a SureForms payment form. SureMembers receives the payment success hook and immediately grants them access to the relevant membership tier. When they cancel, SureMembers receives the cancellation hook and revokes access. No manual intervention, no delay, no support tickets from users asking why they cannot access content they just paid for.
Course enrollment. An LMS plugin like LearnDash or LifterLMS receives the payment success hook and enrolls the student in the course. If they request a refund, the refund hook fires and the LMS can remove enrollment automatically.
CRM updates. Your CRM receives payment events and updates contact records in real time. A successful payment marks the contact as a paying customer. A cancellation triggers a win-back sequence. A refund triggers a follow-up workflow.
All of this happens automatically, triggered by the payment event in SureForms, without needing Zapier, OttoKit, or any middleware.
Why this matters for your existing setup
If you are already using SureForms payment forms alongside SureMembers or an LMS, update to 2.12 and check the available hooks. The integration between SureForms and the rest of your BSF ecosystem just became significantly tighter and more reliable.
If you are a developer building on SureForms, this opens up payment-triggered automation that was not previously possible without custom workarounds.
Entries Shortcode: Display Submitted Entries on Any Page
This is a Pro feature that opens up a category of use cases SureForms could not handle before.
The shortcode lets you display a form’s submitted entries in a fully functional table on any page of your site, visible to the people who submitted them.
This sounds simple. The implications are significant.
What the shortcode displays
Place the shortcode on any page and it renders a paginated, sortable table of entries for the specified form. You choose which columns to display. Users can filter to see only their own submissions. Entries are organised into read, unread, and trash views. Sorting and pagination are built in.
Who this is for and why it matters
Think about the forms you build where the person submitting has a reason to review what they submitted later.
A job application form. The applicant submits their details and later wants to check what they wrote. Normally that information lives in your WordPress admin and they have no access to it. With the shortcode, you put a submissions page behind a login wall and they can review their own application.
A client onboarding form. A new client fills in project details, preferences, and requirements. Later in the project they want to refer back to what they originally submitted. The shortcode gives them a clean page to do that without emailing you to ask.
A support request form. A user submits a support ticket through SureForms. The shortcode lets you build a front-end ticket view where they can see the status and history of their own requests.
An internal team form. Staff submit weekly reports, expense claims, or shift preferences through a SureForms form. The shortcode gives each team member a page showing their own submission history.
In every case, the pattern is the same: the submitter has a reason to see their own data, and until now there was no front-end way to show it to them without building something custom.
The shortcode solves that in one line of code.
Conditional Custom Button: Hide or Show Based on Field Values
The Custom Button block in SureForms lets you add buttons anywhere in a form, not just at the end. They can trigger actions, navigate to other pages, or work as part of custom multi-step form flows.
In 2.12, the Custom Button gained conditional logic support.
You can now set conditions that show or hide the Custom Button based on field values. A button that triggers a specific action can stay hidden until the user has met the conditions that make it relevant. A navigation button can appear only once the user has selected a certain option.
There is also an important piece of logic built into this: when a Custom Button is hidden by conditional logic, it correctly blocks form submission. Previously, hiding the submit mechanism through conditional logic could leave edge cases where submission was still possible through other means. That is now handled correctly.
Pro users also get a fix in this release restoring settings panels for single-tab blocks, which had been missing from the inspector panel in certain configurations.
Also in This Release Page Break block improvements
The progress indicator, label visibility, and Next and Back button text settings for the Page Break block are now directly visible in the block’s inspector panel, with a clear note explaining that these settings apply to the entire form rather than just the selected block. Previously a misleading message referenced a parent block that did not exist, which caused confusion about where to look for these settings.
FluentCRM date format fix
When a Date Picker field was mapped to the Date of Birth field in FluentCRM, the value sometimes arrived in the wrong format and caused a mapping error. The date value is now normalised automatically before it is sent, so birthday data maps cleanly without any manual workaround needed.
PayPal subscription cancellation fix
This was a real problem for any site using PayPal subscriptions. When a user cancelled their subscription, the cancellation request was being routed through Stripe instead of PayPal, which meant PayPal subscriptions were not actually cancelling. This is now fixed. Cancellations go to the correct payment gateway every time.
Cloudflare Turnstile fix for multiple widgets
Forms with more than one Cloudflare Turnstile widget on the same page were failing silently with a generic error. Users would submit the form and see an error with no clear cause. This is now fixed. Multiple Turnstile widgets on a page all validate correctly.
Stripe Payment Element rendering fix
If your Stripe account has Bacs Direct Debit, Link, Cash App, or Buy Now Pay Later enabled, the Stripe Payment Element was failing to render on live accounts. The payment form would appear broken to real customers even though it worked fine in test mode. This is now fixed.
WordPress 6.x editor fix for older-style plugin blocks
If you have plugins like ThirstyAffiliates, Ninja Forms, or Gravity Forms installed on a WordPress 6.x site, the SureForms form editor was breaking on load. This affected anyone using SureForms alongside those plugins. The conflict is now resolved and the editor loads correctly regardless of what other plugins are registered.
Update SureForms from your WordPress dashboard. Version 2.12.0 is available now.
The PayPal cancellation fix, the Stripe rendering fix, and the WordPress 6.x editor fix are all worth updating for immediately if any of them affect your current setup.
If you are on the free plan and the entries shortcode, conditional button logic, and payment hooks sound useful for your site, take a look at what Pro includes.
