About this plugin
Three manual payment gateways built for the Bangladeshi market, verified by you from the order screen:
- AAM 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.
- BD Manual Bank Transfer — the customer transfers the full order total to one of your bank accounts and submits their account details for verification.
They share the same payment page, verification workflow, and settings — enable any of them 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 the payment details (a QR code and copyable number for mobile payment, or your bank account details for bank transfer) and a form.
- They pay via bKash/Nagad/Rocket or bank transfer, then submit their sender number or account details (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
- Three gateways: partial advance (delivery charge), full mobile payment, and manual bank transfer.
- bKash, Nagad, and Rocket — each with Merchant and Personal accounts, each with its own number, QR image, and instructions, independently switched on/off.
- Multiple bank accounts — add several bank accounts (name, number, branch, routing, phone) for the bank-transfer gateway, each 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.