Description
Naimur Email OTP Verification for WooCommerce confirms that a customer really owns their email address. A one-time code (OTP) is emailed and must be entered before the action completes.
The OTP is used for:
- New customer registration
- Password reset (Forgot Password)
- Checkout (optional, off by default): the order is placed only after the billing email is verified
The plugin does not add OTP to login.
Key features
- 6-digit email OTP for WooCommerce customer registration
- OTP-based Forgot Password flow with a single-use, short-lived reset authorization (no automatic login after a reset)
- Optional checkout email verification for the Checkout block and the classic checkout, for guests and (optionally) logged-in customers. Verification is enforced on the server before the order is created, so no payment is taken from an unverified checkout
- Accessible verification popup at checkout: 6-digit input with paste support, countdown, resend with cooldown, change email, mobile bottom-sheet layout
- Three responsive email templates (registration, password reset, checkout) that use your store logo, name and brand colour
- HTML template editor with syntax highlighting, placeholders, a sandboxed live preview (desktop and mobile) and test emails
- “Naimur OTP” admin area: overview with setup checklist, one Verification page with Registration, Password Reset and Checkout tabs, email templates, security limits, branding, activity and diagnostics, searchable help and a settings finder
- Server-side protection: hashed codes, attempt limits, expiry, single use, per-IP and per-email rate limits, purpose and session binding
- Compatible with WooCommerce High-Performance Order Storage (HPOS) and the Cart and Checkout blocks
- Translation-ready, with developer filters such as
ceovw_otp_expiry,ceovw_checkout_auth_ttl,ceovw_rate_limitandceovw_client_ip
How it works
- Registration: the customer fills in the registration form and receives a 6-digit code by email. The account is created only after the correct code is entered.
- Password reset: the customer requests a code, verifies it and sets a new password, then signs in with it.
- Checkout (when enabled): after clicking Place order, a popup asks for the code sent to the billing email. Once verified, the order is placed automatically. Changing the email requires a new code.
Documentation
Built-in documentation is available under Naimur OTP → Help & Documentation. More guides: https://naimurrahmannahid.com/naimur-otp-plugin/
Video tutorial:
Source code
The JavaScript file assets/js/main.js is a compiled/optimized build used in production.
A human-readable source version of this script is bundled with the plugin under:
assets/src/js/main.js
All other JavaScript and CSS files (assets/js/checkout-otp.js, assets/admin/admin.js and the stylesheets) are shipped unminified.
Installation
- In your WordPress admin, go to Plugins → Add New, search for “Naimur Email OTP Verification for WooCommerce”, then install and activate it. WooCommerce must be installed and active.
- Open Naimur OTP → Verification. In Step 1, turn on the customer login and registration forms and select your My Account page.
- Open Naimur OTP → General Settings and set your sender name, sender email and logo.
- Review the emails under Naimur OTP → Email Templates and send yourself a test email.
- Optional: turn on Naimur OTP → Verification → Checkout OTP after placing a test order yourself.
- Make sure your site can send email. Using an SMTP plugin is recommended for reliable delivery.
FAQ
Where is the OTP used?
For new customer registration, for password reset and, if you enable it, at checkout. The plugin does not add OTP to login.
Does checkout verification work with the Checkout block?
Yes. It supports the Checkout block (Store API) and the classic [woocommerce_checkout] shortcode. The check runs on the server when the order is placed, so it cannot be skipped by disabling JavaScript or calling the API directly.
Can a customer be charged before verifying?
No. The order is not created until the billing email is verified, so payment is never requested for an unverified checkout. If a payment fails, the customer can retry payment for the same order and the same email without a new code.
What about express payment buttons (Apple Pay, Google Pay)?
Express buttons outside the checkout form skip the verification popup. While checkout verification is required, such orders are refused with the message “Please verify your email address to place your order.” and the customer can complete the purchase through the checkout form. Turn checkout verification off if you rely on express-only payments.
Can I customize the verification emails?
Yes. Each email has its own subject, preheader and HTML. Use placeholders such as {{otp_code}}, {{customer_name}}, {{site_name}}, {{expiry_minutes}} and {{support_email}}. Scripts, forms, iframes and unsafe links are removed when you save, and PHP is never executed.
How long is a code valid?
5 minutes by default, with 5 attempts. You can set expiry (1–30 minutes), resend delay and attempts separately for registration, password reset and checkout.
Is the customer logged in after resetting their password?
No. The customer returns to the sign-in form and signs in with the new password.
Does this plugin work with SMTP plugins?
Yes. Emails are sent with WordPress’s wp_mail(), so SMTP plugins that hook into wp_mail() (for example WP Mail SMTP, FluentSMTP or Post SMTP) handle delivery. The sender name and address you set apply only to this plugin’s emails.
Is there CAPTCHA?
No. Earlier versions could display reCAPTCHA or Turnstile without verifying it on the server, which gave no real protection, so it was removed in 2.1.2. The forms are protected by server-side rate limits and attempt limits.
Does it slow down the site?
No noticeable impact. The My Account scripts load only on the My Account page for visitors who are not logged in, the checkout script loads only on the checkout page when checkout verification is enabled, and admin assets load only on the plugin’s own admin pages.
My site is behind a proxy or CDN. Which IP address is used?
For rate limiting and activity logs the plugin uses REMOTE_ADDR and does not trust forwarded headers. If your server sits behind a trusted proxy, return the real client IP through the ceovw_client_ip filter.
What happens to my data if I delete the plugin?
Pending codes, reset authorizations and logs are always removed. Settings and email templates are kept unless you turn on “Delete all plugin data” under General Settings.
Screenshots












Changelog
2.1.2
Added:
* Optional checkout email verification (off by default) for the Checkout block and classic checkout, for guests and logged-in customers. Enforced on the server before the order is created; verification is single-use and bound to the browser session, the exact email and the checkout purpose.
* Accessible checkout verification popup with paste support, countdown, resend cooldown, change email and a mobile layout.
* The registration and password reset code popup now matches the checkout popup: dialog semantics, Escape to close, focus kept inside, paste and one-time-code autofill, arrow and Backspace keys, and inline messages instead of browser alerts.
* New “Naimur OTP” admin menu with Overview, Verification (Registration, Password Reset and Checkout tabs), Email Templates, Security, Activity & Diagnostics, General Settings and Help & Documentation.
* Overview page with real status for each verification, email delivery and security health, a setup checklist and quick actions.
* Plain-language settings with help text, unsaved-changes warning, Discard changes, inline validation, a settings finder and contextual links to the documentation.
* Three new responsive email templates (registration, password reset, checkout) using your store logo and brand colour.
* HTML email template editor with syntax highlighting, placeholders, sandboxed live preview (desktop and mobile), reset and test email.
* Per-flow settings for code expiry, resend delay and attempts; adjustable rate limits within safe ranges.
* Sender name and email for this plugin’s emails only, store logo, uninstall data retention option and activity log retention.
* Server-side resend cooldown for all flows.
* Declared compatibility with WooCommerce HPOS and the Cart and Checkout blocks.
Changed:
* Settings moved from WooCommerce → Email Verification to the new Naimur OTP menu. Existing settings are kept; old admin links redirect.
* Email HTML, security limits and general settings now require a site administrator (manage_options). Shop managers can still turn verification on or off and send test emails.
* A custom HTML template and custom subject from earlier versions are migrated to the registration and password reset templates. The bundled templates 1–3 are replaced by the new design.
* Password reset button now reads “Update Password” (the customer is not logged in automatically).
* When password reset or registration OTP is turned off, the standard WooCommerce links are shown instead.
Removed:
* reCAPTCHA and Cloudflare Turnstile widgets. They were never verified on the server. Saved keys are kept but unused, and no third-party scripts are loaded.
Security:
* All 2.1.1 protections retained: hashed codes, single-use reset authorization, atomic attempt counting, expiry, rate limits, cron cleanup, no automatic login after reset.
* Email HTML is filtered with a strict allowlist; placeholder values are escaped.
* Verification fails closed while a database upgrade is pending.
2.1.1
Security:
* Hardened password reset authorization.
* Added expiration and single-use reset authorization.
* Password reset no longer logs the customer in automatically; they sign in with the new password.
* Improved OTP storage and verification protections.
* Added expired-record cleanup and rate limiting.
* Forgot Password now returns a generic response.
* OTP codes, passwords and reset tokens are no longer stored or shown in plugin logs; emails in logs are masked.
* Registration data awaiting verification now stores a password hash instead of the password.
* The admin email template preview now accepts only the bundled templates (1, 2 and 3).
Changed:
* Client IP (used for rate limiting and activity logs) now comes from REMOTE_ADDR only. Forwarded headers, which the 2.1.0 “Real IP tracking” relied on, are no longer trusted. Behind Cloudflare or another proxy, configure the server to pass the real visitor IP or use the ceovw_client_ip filter.
* Database tables are upgraded automatically; no reactivation needed.
Documentation:
* Removed claims of Login and Checkout OTP, which the plugin does not provide.
* CAPTCHA is now described accurately: the widget can be displayed, but its response is not yet verified on the server.
2.1.0
- Added: Advanced Device & OS Detection (Mobile, PC, Mac) for activity logging.
- Added: Enterprise-grade Real IP tracking (works behind Cloudflare/Proxies).
- Added: Performance-optimized database cleanup via WP Cron to keep logs clean and fast.
- Added: Enhanced security with brute-force protection (IP-based rate limiting).
- Tweak: Completely revamped AJAX engine for zero-buffering, smooth OTP verification.
- Tweak: Strict DOM Isolation for CSS to prevent theme/page builder conflicts.
- Fix: Resolved “An error occurred” AJAX issue by ensuring clean JSON responses.
- Fix: Fixed timezone discrepancies for OTP expiry logic.
1.2.0
- Added: Full Name & Confirm Password fields to the registration form.
- Added: Cloudflare Turnstile Captcha support alongside Google reCAPTCHA.
- Added: Custom database table (
wp_ceovw_logs) for optimized activity tracking. - Added: Smart OTP Paste event in the frontend modal.
- Tweak: Fully responsive, 100% full-width modern CSS design for all devices.
- Security: Implemented absolute sanitization and strict nonces across all AJAX calls.
1.1.5
- Text domain aligned with slug
naimur-email-otp-for-woocommerce. - Added nonce checks, escaping, sanitization and translators comments.
- reCAPTCHA mobile token capture improvements and safe debug logging.
