內容簡介
Bikram COD Order Verification for WooCommerce 為您的 WooCommerce 商店的貨到付款流程新增了一個簡單且免費的驗證步驟，要求客戶在下單前確認一次性密碼（OTP），以減少假訂單和退回損失。
【主要功能】
• 支援經典和現代 WooCommerce 結帳方式
• 透過電子郵件或 SMS 進行驗證
• 可自訂 OTP 長度和有效時間
• 可自訂電子郵件主旨和內容模板
• 伺服器端強制執行驗證
• 防暴力破解：OTP 猜測次數限制
外掛標籤
開發者團隊
② 後台搜尋「Bikram COD Order Verification for WooCommerce」→ 直接安裝（推薦）
原文外掛簡介
Bikram COD Order Verification for WooCommerce adds a simple, no-cost verification step to your store’s Cash on Delivery (COD) checkout flow. Before a customer can place a COD order, they must confirm a one-time password (OTP) sent to their email or phone number. This helps reduce fake orders, prank orders, and Return to Origin (RTO) losses that are especially common with COD in emerging markets.
Key Features
Works with both the Classic (shortcode) checkout and the modern WooCommerce Blocks checkout.
Verification by Email (via the site’s own wp_mail()) or SMS (via Twilio or your own custom HTTP API).
Customizable OTP length (4-6 digits) and expiry time.
Customizable email subject/message templates.
Server-side enforcement – verification cannot be bypassed by disabling JavaScript or editing hidden form fields.
Brute-force protection: OTP guesses are capped, and codes are single-use.
Lightweight dashboard widget showing OTPs sent, verified, and orders blocked.
Full HPOS (High-Performance Order Storage) compatibility.
No bloat: verification only appears when Cash on Delivery is the selected payment method.
How it works
The customer fills in their details and selects Cash on Delivery at checkout.
A small verification box appears, asking for their email or phone number.
The customer requests a code and enters it to confirm their identity.
Only once verified can they successfully place the order – this is enforced on the server, not just in the browser.
External services
This plugin can, depending on how you configure it, send data to external services in order to deliver the OTP code to your customers:
Email delivery uses your WordPress installation’s own wp_mail() function to send the OTP. No third-party service is contacted for this by default; delivery depends on your site’s own mail configuration (e.g. an SMTP plugin, if you use one).
SMS delivery (optional, only if you choose SMS as the verification method):
Twilio – if you select Twilio as your SMS gateway and enter your Twilio credentials, the OTP code and the customer’s phone number are sent to Twilio’s API (https://api.twilio.com) in order to deliver the SMS. This is only used when you have explicitly configured Twilio credentials in the plugin’s settings. See Twilio’s Terms of Service and Privacy Policy.
Custom API – if you select “Custom API” and provide your own SMS provider’s endpoint URL, the OTP code and the customer’s phone number are sent to the URL you configure. No default third-party endpoint is used – this only happens if you actively configure it.
No data is sent to any external service unless you actively choose and configure SMS as your verification method. If you use Email verification (the default), no third-party service is contacted by this plugin.
