OneCaptcha 1.2.0 launched on 15th May 2026, and it is the most significant release since 1.1.0. This update expands integration coverage to over 25 WordPress plugins, introduces a built-in Insights dashboard, adds persistent runtime logging, and ships a number of verification reliability fixes that have been in progress since 1.1.0.
Here is everything that changed, why it matters, and what it means for your site.
17 New Plugin Integrations
The biggest headline in 1.2.0 is integration coverage. OneCaptcha now protects forms across a much wider slice of the WordPress ecosystem, with no manual configuration required on your end.
New integrations in this release:
- Donation & Payments: GiveWP, SureCart, FluentCart
- Form Builders: Gravity Forms, Formidable Forms, WS Form, Met Form, Gutena Forms
- Memberships: MemberPress, Paid Memberships Pro, MemberMouse
- LMS: Sensei LMS, LifterLMS
- Community & Email: FluentCommunity, MailPoet
- Events: The Events Calendar, EventKoi
Every integration follows the same pattern as existing ones: OneCaptcha detects the plugin, loads protection only when that plugin is active, and applies frictionless verification automatically.
If you run a membership site on MemberPress, sell digital products through SureCart, or manage a community on FluentCommunity, your forms are now protected out of the box.
Insights Dashboard
Until now, OneCaptcha worked silently in the background with no visibility into what it was actually doing. That changes in 1.2.0.
The new Insights dashboard gives you aggregated data across three dimensions:
- Provider performance: which CAPTCHA provider is being used, how often, and whether failover has triggered
- Surface coverage: which forms and integrations are actively protected
- Verification outcomes: pass rates, failure reasons, and frictionless vs. challenge escalation breakdown
This is useful in two ways. For site owners, it gives you confidence that protection is actually running. For developers, it gives you the data you need to diagnose edge cases without digging through server logs.
Persistent Runtime Logging
Alongside the Insights dashboard, 1.2.0 introduces persistent runtime logging with configurable retention controls. This means structured verification events are now written to a log you can inspect, rather than disappearing after each request.
You can enable or disable logging from the Advanced settings tab in the OneCaptcha admin panel. Retention is configurable so logs do not grow unbounded over time.
This is particularly useful when diagnosing intermittent failures, testing new integrations in staging, or auditing verification behavior before a site launch.
Hardened Frictionless Verification
The frictionless handshake flow has been rebuilt in 1.2.0 to use REST-compatible token issuance. Every handshake now includes a render token, a request ID, and server-side timing validation. This closes a class of replay and forged proof attacks that were theoretically possible against the previous implementation.
Provider secrets are now write-only across all admin surfaces. Once saved, keys are masked in settings responses, diagnostic output, and hydration payloads. This prevents accidental secret exposure through admin API calls or debug logs.
Integration diagnostics have also been improved. OneCaptcha now reports hook-contract health per integration, so if a third-party plugin changes its hooks in an update and breaks the integration contract, you will see a degraded status in the dashboard rather than silent failure.
WooCommerce Verification Fixes
WooCommerce has always been one of the most complex integrations to get right because it has multiple form surfaces, block-based checkout, and its own authentication flow. 1.2.0 addresses the remaining rough edges.
Verification and rendering are now consistent across checkout, login, registration, lost password, order tracking, and block-based WooCommerce surfaces. If you were seeing inconsistent CAPTCHA behavior on any of these forms in earlier versions, this release resolves it.
Better Failure Messages
Previously, when server-side verification failed, users would see a generic “invalid captcha” error regardless of the actual reason. In 1.2.0, failure messages now reflect the specific server-side error returned by the provider.
This is a small change with a meaningful impact on support volume. Users can now understand why verification failed and take the right action, rather than retrying indefinitely or abandoning the form.
14-Day Free Trial
Starting with 1.2.0, OneCaptcha is available with a 14-day free trial. No credit card required to start.
This applies to all three plans: Starter, Developer, and Agency. You get full access to every feature during the trial, including Smart Captcha routing, all integrations, and priority support.
If OneCaptcha is not the right fit after 14 days, you do not pay. If you do subscribe and change your mind within 30 days, the money-back guarantee covers you.
Under the Hood
For developers, 1.2.0 ships a significant amount of internal refactoring that improves maintainability and extensibility going forward.
- Shared provider metadata has been moved into a centralized registry, eliminating scattered duplication across modules
- Dashboard settings-page state logic has been refactored into reusable abstractions, making it easier to add new settings surfaces without repeating the same boilerplate
- Module wrappers have been consolidated into reusable base classes, reducing the overhead of adding new integrations
- An integration hook contract registry has been added with hook probes and a scheduled smoke matrix workflow to catch broken integration contracts automatically
- PHPUnit, JS unit test, and Playwright coverage has been expanded across observability, provider registry, integration guards, verification messages, and critical admin flows
- Freemius SDK updated to 2.13.1
How to Update
If you are on an active OneCaptcha license, the update is available now from your WordPress dashboard under Plugins. The update is fully backward compatible with 1.1.x installations.
If you are not yet using OneCaptcha, you can start a free 14-day trial with no credit card required.
For the full list of changes, see the changelog. For any questions or issues, reach out via the support page.

Leave a Reply