Skip to the products
LCPanelLicence Center Panel

Payment Gateways

PayPal, Stripe, Coinbase Commerce, bKash, Nagad, SSLCommerz, Paddle and bank transfer for premium upgrades, with pending orders you approve. Free.

Plugins Updated 6 Nov 2026 23 / 50

The Payment Gateways plugin is how members pay for a premium package. It puts the payment methods on the /upgrade page, sends the member to the provider, listens for the provider's confirmation and lets the core upgrade the account the moment the money is confirmed. Fourteen ways to pay come with it: PayPal, Stripe, Coinbase Commerce (crypto), SSLCommerz, Paddle, Bank transfer / manual, and, since version 1.1.0, the Bangladeshi mobile wallets - bKash, Nagad, Rocket, Upay, SureCash, Tap, MCash and a generic Bank / other wallet - which work without any API keys: the member sends the money to your number and reports the transaction ID, and you approve it (see Mobile wallets below).

Without this plugin the upgrade page lists your packages but has no way to pay; the only way to premium is the admin logging a payment by hand under People → Payments → Manually Log Payment, or a voucher from the Voucher Reseller plugin.

Who it is for

Any site that sells premium accounts. The Bangladeshi gateways (the mobile wallets and SSLCommerz) charge in taka; the rest charge in the site currency set under Site Settings → Premium Pricing, or in the member's own currency when the Multi Currency plugin is on.

Switching it on

Payment Gateways is free and works with every licence; a fresh install switches it on. Otherwise open Admin → Extensions → Plugins (Manage Plugins) and switch it on. Two pages appear under Extensions:

  • Manage Gateways (/admin/plugin/payment-gateways) - switch gateways on, type their keys, choose test mode.
  • Pending Orders (/admin/plugin/payment-gateways/pending) - bank transfers, wallet payments and other orders waiting for you: approve, or reject with a note.

The two pages sit under one Payment Gateways entry of the menu, which opens when you are on either of them (The admin panel).

When first switched on, only Bank transfer / manual is enabled, so the upgrade page works before you have any keys.

Manage Gateways

Every gateway is a card with Enabled, Test / sandbox (not for the manual gateway) and Label shown to members (empty = the gateway's own name), then its keys:

GatewayWhat to typeWhere the confirmation comes from
PayPalPayPal e-mail (business) - the account that receives the moneyPayPal IPN to /plugins/payment-gateways/ipn/paypal
StripeSecret key (sk_live_… or sk_test_…), Webhook signing secret (whsec_…, optional)Webhook checkout.session.completed to /plugins/payment-gateways/ipn/stripe; without a webhook the return page asks Stripe about the session itself
Coinbase CommerceAPI key, Webhook shared secret/plugins/payment-gateways/ipn/coinbase
bKashHow members pay (below), then for the API way App key, App secret, Username, PasswordThe member comes back and the plugin executes the payment
NagadHow members pay, then for the API way Merchant ID, Merchant private key (PEM), Nagad public key (PEM)Nagad's callback
Rocket, Upay, SureCash, Tap, MCash, Bank / other walletNumber, account type, name, QR, instructions ... (below); no keysYou, on Pending Orders
SSLCommerzStore ID, Store password/plugins/payment-gateways/ipn/sslcommerz
PaddleVendor ID, Vendor auth code, Public key (PEM, checks the webhook)/plugins/payment-gateways/ipn/paddle
Bank transfer / manualInstructions - your bank details, shown to the memberYou, on Pending Orders

The page prints the webhook / IPN address pattern at the top: https://your-site/plugins/payment-gateways/ipn/<gateway>. Register it with each provider that uses one. A password field left empty keeps the saved secret. Save gateways keeps everything.

The plugin's own options:

  • Taka per unit of the site currency (120) - the wallets (all but Bank / other wallet) and SSLCommerz charge in BDT; when your site currency is USD or EUR the price is converted with this rate. A member who chose taka in the Multi Currency picker is charged the price shown instead.
  • Pending orders live (hours) (72) - an unpaid gateway order older than this is cancelled by the cron job Payments: expire old orders (payment_expire_orders, hourly). Bank-transfer orders, and wallet orders whose payer has reported a payment, wait for you.
  • Thank-you text - shown when a payment is confirmed.

Mobile wallets (bKash, Nagad, Rocket and the rest)

Eight cards - bKash, Nagad, Rocket, Upay, SureCash, Tap, MCash and Bank / other wallet - are mobile-wallet gateways. Besides Enabled and Label shown to members each carries these fields (stored as gw_<code>_<field>, for example gw_bkash_number):

Field (gw_<code>_…)What it does
Account type (type)Personal, Merchant or Agent (default Personal). Shown to the payer so they use the right menu: Send Money, Payment or Cash Out.
Wallet number / account (number)The number members pay to.
Account name (acc_name)Shown beside the number.
QR picture (qr)Optional. PNG, JPG, WebP or GIF, kept in uploads/wallets/; upload a new one to replace it, or tick the remove box.
Instructions for the payer (instructions)Free text with the placeholders {amount}, {number}, {name}, {type}, {wallet} and {order}. Empty uses a standard text: open the app, choose Send Money (or Payment for a Merchant number), send {amount} to {number}, then write the transaction ID and your own number in the form.
Transaction ID required (trx_required)On by default. Off lets a member submit without one.
Payment screenshot (screenshot)Not asked, Optional (default) or Required.
Payment link (optional) (pay_link)An http(s) address the Pay now button opens, for example a bKash payment link. Anything else is dropped.

{amount} is the price in taka for the wallets (converted with Taka per unit of the site currency) and in the order's own currency for Bank / other wallet; {order} is the order number, the first ten characters of the order hash.

bKash and Nagad also have How members pay (gw_bkash_mode, gw_nagad_mode): Automatic (the default: the API way when the App key, or the Merchant ID, is filled in, otherwise manual), Manual (number + transaction ID) or API (payment page). In manual mode the member sees your number and the keys are not used; in API mode they pay on bKash's or Nagad's own page, as before. The other wallets are always manual.

The member's side

Choosing a manual wallet on /upgrade sends the member to the wallet page (/plugins/payment-gateways/wallet?o=<order>), which shows the amount to send, the order number and the package, then Pay to with the number in large type, the account type and name, your instructions, a Pay now button when a link is set, and the QR picture with Scan to pay. Under it the I have paid form takes:

  • Your number - the wallet number the money came from (a plausible phone number; for Bank / other wallet, the account);
  • Transaction ID - four to sixty letters, digits and - _ . /; refused when another order on the same wallet already used it;
  • Screenshot of the payment - a picture of at most 4 MB, when you ask for one;
  • Note - optional, 300 characters.

Send payment details saves them and the page says Waiting for approval; until you act the member can open the page again and press Update details. Screenshots are kept in uploads/proofs/, which the web server refuses to serve; only the member and the administrators see one, through the Screenshot link.

Pending Orders: approve or reject

Each waiting order shows the date, member, order number, the gateway with your number, the amount and, for a wallet, Payment details: From the sender's number, the Trx ID, the screenshot and the note - or Nothing reported yet. The buttons:

  • Approve & upgrade - after you have seen the money arrive. The account is upgraded as for any confirmed payment; the member's transaction ID is kept as the payment's reference.
  • Reject with a reason typed in the box beside it - the order is cancelled, the member gets a notification and the e-mail template Payment not accepted (payment_rejected, editable under E-mail & Templates) with your reason, and can try again from /upgrade.
  • Cancel - drops an order without telling anyone.

Your payments

Under the packages on /upgrade a signed-in member sees Your payments: their own unfinished wallet and bank-transfer orders, and the ones you rejected in the last fourteen days, newest first (six at most), each with the package, the wallet, the order number, the amount and a state - Payment details needed (with an Open link back to the wallet page), Waiting for approval or Rejected with your note.

How a purchase runs

  1. The member picks a package and a period on /upgrade (pricing comes from Account packages), chooses a gateway from the radio list and presses the button. The form posts to /plugins/payment-gateways/checkout.
  2. An order row is made in bp_payments with an order hash, and the member is sent to the provider (or shown your bank details at /plugins/payment-gateways/manual?o=<order> for the manual gateway, or the wallet page above for a manual wallet).
  3. The provider confirms - by webhook/IPN, or when the member returns to /plugins/payment-gateways/return?o=<order>&s=return. The core's order_complete() upgrades the account, extends Paid Expiry Date, logs the payment under People → Payments and fires bp_order_completed, which the Rewards Program uses to credit the referrer.
  4. The member sees Payment received with your thank-you text, or Waiting for the payment to be confirmed (the page checks again every eight seconds) when the provider has not called back yet. s=cancel shows The payment was not completed.

Pending Orders

Every order that has started but is not confirmed, newest first: date, member, order number (the first ten characters of the hash, which the member quotes as the bank reference), gateway and amount, and for a wallet the payment details the member reported. Approve & upgrade completes a bank transfer or wallet payment once the money is in your account; Reject (with a note) turns it down and tells the member; Cancel drops a dead order. Gateway orders disappear by themselves after Pending orders live (hours); so does a wallet order whose payer never reported a payment. Bank-transfer orders, and wallet orders with a report waiting, stay until you decide (see Mobile wallets above).

Tips

  • For a wallet, check the sender number and transaction ID against your wallet's statement before Approve & upgrade; the plugin only refuses an ID that another order already used.
  • Put your QR picture and a short Instructions text on every wallet you enable, and keep Transaction ID required on: a report without an ID is the hardest to check.
  • Run each gateway in Test / sandbox first, buy the cheapest period yourself, then switch test off. The gateway's test keys go in the same fields.
  • Stripe with a webhook secret refuses any call without a valid Stripe-Signature; without a secret the return page does the confirming, which is fine for a small site.
  • Prices in Premium Pricing are in one currency; the taka rate covers the local gateways. Check it now and then.
  • A refunded or charged-back payment is handled from People → Payments; the Rewards plugin cancels the referrer's reward with it.
  • The site's e-mail must work for receipts: Configuration → E-mail & Templates → Sending has a test button, and the template premium_activated is what the member gets.
Was this helpful?
Share this chapter