- 2026-07-06
- by LethaldiranMX
- Trends
- 0 Comments
LethaldiranMX Insight
This plugin addresses a critical pain point in the Bangladeshi e-commerce ecosystem by mitigating the high return rates associated with standard Cash-on-Delivery (COD) transactions. By facilitating a structured, manual workflow for collecting partial advance payments (such as delivery charges) or full payments via bKash, Nagad, and Rocket, it establishes a secure commitment from the buyer without requiring complex API integrations. The inclusion of a dedicated payment page, copyable numbers, and QR codes significantly improves the user experience over standard manual payment instructions. From an operational standpoint, it brings order and traceability to manual mobile financial service (MFS) transactions directly within the WooCommerce admin panel.
Best Fit & Operational Role: This solution is ideal for small-to-medium WooCommerce stores operating in Bangladesh that want to reduce fake or non-serious orders without the administrative hurdle of acquiring official MFS merchant API keys. It serves as a risk-management gatekeeper at checkout, allowing merchants to validate customer intent before committing inventory or shipping fees. Operationally, it integrates directly into the WooCommerce order management screen with a dedicated metabox, making it a natural fit for teams that handle order fulfillment and payment verification manually.
Potential Limitations & Pitfalls: The primary operational bottleneck is the manual verification requirement; because there are no API integrations to automatically reconcile payments, store administrators must manually cross-reference transaction IDs or sender numbers against their MFS account statements. Consequently, this workflow may scale poorly for high-volume stores experiencing hundreds of orders per day. No technical performance overhead or security vulnerabilities were identified based on available information, as the plugin operates locally, supports High-Performance Order Storage (HPOS), and avoids third-party telemetry or external API dependencies.
Collect a partial advance (delivery charge) or the full order total via bKash/Nagad/Rocket to confirm orders. No API keys required.
Two manual mobile-payment gateways built for the Bangladeshi market, verified by you from the order screen:
- BD Partial COD — the customer pays a small advance equal to the delivery charge via bKash/Nagad/Rocket to confirm a Cash-on-Delivery order. The rest is collected as cash on delivery.
- BD Manual Mobile Payment (full) — the customer pays the full order total via bKash/Nagad/Rocket up front.
Both share the same payment page, verification workflow, and settings — enable one or both at checkout.
Customer flow
- At checkout the customer sees a notice (e.g. “You must pay ৳X (delivery charge) now to confirm this order.”).
- After placing the order they land on a standalone payment page showing a QR code, a copyable number, and a form.
- They pay via bKash/Nagad/Rocket, then submit their sender number (and optionally the Transaction ID).
- The order is held until you verify the payment.
Admin flow
- Open the order — the metabox shows the method, sender number, Transaction ID, amount due, and remaining COD.
- Click Verify payment to confirm the order (status Processing), or Reject to send it back.
Features
- Two modes: partial advance (delivery charge) and full payment.
- bKash, Nagad, and Rocket — each with Merchant and Personal accounts, each with its own number, QR image, and instructions, independently switched on/off.
- Editable texts — customise every customer-facing string (checkout notice, payment page title/labels/button/footer, status messages) per gateway, in any language. Every field is pre-filled with the default, ready to edit.
- Transaction ID (TrxID) — ask for it Off / Optional / Required.
- Flexible sender number — require a full 11-digit number, or let the customer confirm with just the last few digits.
- Gateway icon — choose the icon shown beside the method at checkout and in the payment page header.
- Reuse numbers — the full gateway can use its own numbers, copy the partial gateway’s numbers once on save, or always mirror them live.
- Copy-to-clipboard number and QR display.
- Manual admin verification — no API keys required.
- High-Performance Order Storage (HPOS) compatible.
- Theme-overridable payment template and i18n-ready strings.
Editorial note: This overview combines WordPress.org official plugin metadata with an AI-assisted LethaldiranMX editorial review. Plugin data should be verified on the official WordPress.org listing before installation.
