Wallet, Payments & Pro
One balance per member: PayPal, Stripe, bKash, Nagad, SSLCommerz, Razorpay or a bank transfer you approve, Pro packages, and the filters other plugins charge through.
The Wallet plugin gives every member a balance in your site's currency, lets them add money through PayPal, Stripe, bKash, Nagad, SSLCommerz, Razorpay or a bank / mobile-money transfer you approve by hand, and sells Pro packages: a badge beside the name, a place at the front of "People you may know", no ads and boost credits. Other plugins (gifts, tips, marketplace, jobs, funding) charge and credit wallets through this plugin, so there is one balance and one history for everything a member pays for.
What members get
- The Wallet page at
/wallet(also in the side menu): the balance in big type, what came in and went out this month, Add money, Send money and Go Pro. Under it the transaction history: what each row was (added money through Stripe, sent to Karim, Pro membership, a refund), when, its state (pending, paid, failed, rejected, refunded), the signed amount and the balance after it. The list can be filtered by kind and state. - Add money at
/wallet/add: an amount (with quick chips and the limits you set) and the payment method. The member is sent to the gateway's own page and comes back to a result page: Payment received, Waiting for confirmation or The payment did not go through. Money is counted only when the gateway's API confirms the amount; nothing the browser sends is trusted. - Manual transfer: the member sees your instructions (bank account, bKash or Nagad personal number, whatever you wrote), the amount and a code (
MMB-123) to put on the transfer, then submits the transaction ID and, if you require it, a screenshot. The money arrives in the wallet when you approve it; the member is told either way, and the screenshot is deleted after the decision. - Send money to another member by username, with a note. The site may keep a commission (a percent you set); the receiver gets a notification.
- Go Pro at
/pro: the packages as cards (colour, price, length, features), Buy with wallet or Pay directly through a gateway (the money goes into the wallet and the package is bought from it at once). A Pro member sees their package, the end date and the boost credits left; buying the same package again adds its length to the end. - The badge (PRO, VIP, or the text you choose, in the package's colour) beside the member's name in post headers, comments, member tiles and the profile header.
- Settings → Wallet & Pro: balance, Pro status, the last five transactions.
- Notifications: money added, payment approved or rejected, money received, Pro bought, Pro ending in three days, Pro ended. E-mails for money added and for the three-day warning (editable on Admin → E-mail templates).
Amounts are kept in the site currency with two decimals (DECIMAL columns, never floating point); a charge can never take a balance under zero.
Settings
Admin → Plugin pages → Wallet & Pro → Settings.
| Setting | What it does |
|---|---|
| Site currency | One currency for every wallet, price and package (USD by default; pick BDT for taka). The symbol, its position and the decimals follow the currency; you can override each. bKash and Nagad need BDT; Razorpay works best with INR. |
| Smallest / largest amount | The limits of a top-up. A Pro package dearer than the largest amount can still be paid for directly. |
| Members can send money to each other | The Send money button and the member-to-member path other plugins use. |
| Site commission (%) | Kept by the site on member-to-member money; the receiver gets the rest. |
| Manual transfer | On/off, the instructions the member sees, and whether a screenshot is required. Without instructions the method stays hidden. |
| Pro packages are on | Off hides /pro, the menu row and the badges; nobody loses a membership. |
| Badge text | The site-wide badge word (PRO); a package may carry its own. |
| Mock gateway server | Developers only: a local address every gateway talks to instead of the real service. Leave it empty on a live site; the Overview tab warns while it is set. |
The other tabs: Overview (money in today, this month and all time, pending payments, a 30-day chart, the state of every gateway, the last transactions), Transactions (every row with filters by member, kind, state, gateway and dates; add or take money by hand with a note; refund a paid charge), Pending payments (manual transfers to approve or reject, with the transaction ID and screenshot; and payments members started but did not finish), Packages and Gateways. Everything you do by hand is written to Admin → Logs.
Gateways
Admin → Plugin pages → Wallet & Pro → Gateways. Each gateway has its own card: Members can pay with it, Test mode where the gateway has a sandbox, its keys, and the addresses to register in the gateway's dashboard. Secrets are stored encrypted and never shown again: a saved secret reads as dots, an empty box keeps it, a single - clears it. A gateway is shown to members only when it is on, complete and takes your site currency.
Replace https://your-site.com with your address.
PayPal
Keys from the PayPal developer dashboard: Client ID and Secret of a REST app (sandbox keys with Test mode on, live keys with it off). The plugin uses the Orders v2 API: it creates an order, sends the member to PayPal, and captures the order when they come back.
- Return URL:
https://your-site.com/wallet/return/paypal(PayPal sends members back here by itself; nothing to register) - Webhook URL (optional):
https://your-site.com/api/wallet/webhook/paypal, eventsCHECKOUT.ORDER.APPROVEDandPAYMENT.CAPTURE.COMPLETED. Paste the Webhook ID PayPal shows after you add it, so every call is verified with PayPal. The webhook captures an approved order even when the member closes the browser before returning.
Stripe
Keys from Stripe → Developers → API keys: Publishable key and Secret key. Test or live follows the key (sk_test_… / sk_live_…). The plugin opens a Stripe Checkout session and reads it back from Stripe when the member returns.
- Return URL:
https://your-site.com/wallet/return/stripe(set automatically on each session) - Webhook URL (optional):
https://your-site.com/api/wallet/webhook/stripe, eventcheckout.session.completed; paste the signing secret (whsec_…) so the plugin checks theStripe-Signatureheader.
bKash (Bangladesh, BDT)
From your bKash merchant / developer account (developer.bka.sh): Username, Password, App key and App secret of the tokenized checkout. Test mode uses the sandbox address. The flow is grant token → create payment → the member pays on bKash's page → execute on the callback (with a status query when execute times out).
- Callback URL:
https://your-site.com/wallet/return/bkash(sent with every payment; whitelist your domain in the bKash portal)
Nagad (Bangladesh, BDT)
From Nagad: Merchant ID, Merchant mobile number, your Merchant private key (the RSA key you generated and whose public half you gave Nagad; PEM or the bare base64 body) and Nagad's public key. Test mode uses the sandbox address. Every request is RSA-signed and the sensitive data RSA-encrypted the way Nagad's checkout wants; the payment is verified through Nagad's verify API before money is counted.
- Callback URL:
https://your-site.com/wallet/return/nagad(tell Nagad this address and your domain)
SSLCommerz (Bangladesh)
From the SSLCommerz merchant panel: Store ID and Store password (sandbox ones with Test mode on). The member pays on the SSLCommerz page; the result is validated with the validation API before anything is credited.
- Success / fail / cancel URL:
https://your-site.com/api/wallet/return/sslcommerz(sent with every session) - IPN URL:
https://your-site.com/api/wallet/webhook/sslcommerz(register it in the panel too; itsverify_signis checked)
Razorpay (India)
From Razorpay → Settings → API keys: Key ID and Key secret (rzp_test_… for test). The plugin creates an order, opens Razorpay's checkout in the member's browser, checks the returned signature and then reads the payment from Razorpay's API.
- Webhook URL (optional):
https://your-site.com/api/wallet/webhook/razorpay, eventpayment.captured; paste the Webhook secret so theX-Razorpay-Signatureheader is checked.
Manual bank / mobile-money transfer
No keys. Switch it on and write the instructions on the Settings tab: your bank account, your bKash or Nagad personal number, and "write the code shown on the page as the reference". Each submission lands on Pending payments, where you approve it (the money is credited, the member is told) or reject it with a note. Payments the member never finished are marked failed after seven days (two days for gateway payments).
Bangladesh mobile wallets (1.2.0)
Below the gateways sits Bangladesh mobile wallets: bKash, Nagad, Rocket (DBBL), Upay, Tap (Trust Axiata Pay), mCash (IBBL), SureCash, OK Wallet, Cellfin (IBBL), Meghna Pay and an Other mobile wallet you name yourself. They are manual gateways ("send the money, then give the transaction ID") and are separate from the bKash and Nagad API gateways above, which keep working as before. Open a wallet and set:
- On / off and the numbers: add, edit and remove rows; each number is tagged Personal, Merchant or Agent, with an optional label. The member is told what to tap in the app for each one: Personal → Send Money, Merchant → Payment, Agent → Cash In. A wallet cannot be switched on without a number.
- Logo: a plain coloured badge with the wallet's initials is used (no company logo is shipped); upload the wallet's real logo if you have the right to use it.
- Currency it takes (BDT by default), an optional fee % added on top, the smallest / largest payment in that currency, an optional reference text, and whether the sender number and a screenshot are not asked, optional or required.
- Instructions in English and Bengali; empty means the default text.
{wallet},{action},{amount}and{reference}are filled in.
On /wallet/add the member picks the wallet, sees each number with a Copy button and the exact amount to send in the wallet's currency ("৳1,190 = $10.00 at today's rate"), sends the money and submits only the transaction ID (plus the sender number or screenshot when you ask for them). The payment waits on Pending payments with the wallet, the number used and its type, the sender number, the TrxID and the amount sent; approve or reject it with a note. A TrxID that is waiting or was paid is refused a second time, for every member. Updating from 1.1: a bKash, Nagad or Rocket number written in the old manual-transfer instructions becomes that wallet's number automatically.
Currencies (1.2.0)
Every gateway says which currency it charges in: the site currency by default, or one the gateway supports that you pick (for example bKash in BDT on a USD site). When it differs from the site currency, the amount is converted through the Multi Currency plugin (currency_convert filter); without that plugin, or without its rate, the gateway's own manual rate (1 site unit = ? of that currency) is used, and with neither the gateway is simply not offered. The transaction keeps the amount, currency and rate the member was charged, and the wallet is credited in its own (site) currency with that stored rate, even when the rate changes before you approve a manual payment.
Promoting Pro (1.2.0)
Settings → Promote Pro switches each place on or off:
- the profile menu: a highlighted Go Pro row above Settings & privacy ("Your Pro: Gold until 12 Nov 2026" for members who have a package);
- an Upgrade to Pro card in the left side column and a card in the home feed after the sixth post, for members without a package only, with three or four features of your best package and the starting price; the member can hide them (the feed card comes back after 1 day, 3 days, a week or 30 days, as you set);
- a Go Pro badge link beside the name on a member's own profile;
- upgrade messages: where a feature is missing, the message names the package that unlocks it and the link opens /pro?feature=… with that package marked;
- house ads: every package with a price is offered to the Ads plugin as a ready-made "Go Pro" ad (a picture drawn in the package colour, its features and price, linking /pro). It runs in the feed, side column and player spots beside the faruk.bd product ads, and Pro members never see it.
Pro packages
Admin → Plugin pages → Wallet & Pro → Packages. A package has a name, a colour, a price, how long it lasts (days; 0 = lifetime), and its features: the badge beside the name (with its own text, say VIP), a place at the front of "People you may know", no ads (the Ads plugin hides ads from Pro members when its own "Ad-free for Pro members" is on), boost credits, an upload-limit line, and any extra lines. Switch a package off to stop selling it without touching the members who have it; a package with members cannot be deleted.
A membership sets the core Pro fields of the member (the same ones you can set by hand on Admin → Members), so everything in MyMeetBook that asks "is this member Pro?" gets the same answer. The cron job Wallet: end Pro that ran out ends memberships at their end date, clears the flag, tells the member, and three days before sends a notification and an e-mail.
Packages and features
Since Wallet 1.1.0 every package also decides what a member may use. The package form (Packages → Edit) lists every feature the site has, grouped (Posts, Stories, Profile, Advertising, Blog, Marketplace, Jobs, Offers, Funding, Groups, Pages, Events, Messenger and those of any other plugin): a switch for things a member may or may not do (upload videos, schedule posts, post anonymously, post stories, ask for the verified badge, create ad campaigns, write blog articles, sell on the marketplace, post jobs and offers, start fundraisers, create groups / pages / events, audio / video / group calls, meetings, recording) and a number for limits (posts a day, largest upload in MB, free post boosts a day, listings at a time, people in a group call, longest recording in minutes). A switch that is off, or an empty number, means "same as free members", so a package never takes away what everybody has.
Free members (the card under the list) sets what members without a package get. Out of the box everything stays allowed and every limit is the site's own, so upgrading never locks anybody out; switch off what should need a package, or press Use the suggested free plan: video calls, group calls, meetings, recording and ad campaigns then need a package, everything else stays as it is. Admins pass every gate.
What a member gets is answered in this order: their active package, then the Free members set, then the site's own setting. A member who opens something their package does not include sees a friendly card ("Your package does not include this. Upgrade to use it.") with a button to /pro; the app and the JSON API get the error with upgrade: true and the link.
Free boosts a day: a package with, say, 3 free post boosts a day lets the member boost three posts every day without a budget (the boost window says how many are left). The count starts again at midnight (UTC). Largest upload raises (or lowers) the video and file limit of the member; pictures keep the site's own limit.
/pro shows each package with what it includes (✓, numbers, and ✗ for what neither the package nor free members have) and a Compare the packages table: Free and every package side by side, row by row. On a phone the table keeps the feature names in the first column.
Four ready packages are added once when none of them exists (your own packages stay): Basic (2.99 a month: video uploads, scheduled posts, stories, audio calls, 1 free boost a day), Plus (6.99: + no ads, anonymous posts, verified-badge requests, video calls, blog, marketplace with 20 listings, 3 boosts a day, 100 MB uploads), Pro (14.99, badge + featured: + group calls with 8 people, meetings, 30 minutes of recording, jobs, offers, fundraisers, 50 listings, 5 boosts a day, 500 MB) and Business (29.99, badge + featured: + group calls with 16 people, 120 minutes of recording, events, pages, groups, ad campaigns, unlimited listings, 15 boosts a day, 2 GB). A BDT site gets ৳299 / 699 / 1,499 / 2,999. On a site that already sells packages the four wait switched off.
Registering features (plugin authors)
A plugin adds its own features through the feature_list filter and asks before it does the thing; it never calls a Wallet function:
add_filter('feature_list', static fn (array $l) => $l + [
'recipes.publish' => ['label' => __('Publish recipes'), 'group' => __('Recipes'), 'type' => 'bool', 'default' => true],
'recipes.max' => ['label' => __('Recipes at a time'), 'group' => __('Recipes'), 'type' => 'int', 'default' => 0, 'help' => __('0 = no limit')],
]);
// where the member publishes:
if (function_exists('feature_allowed') && !feature_allowed('recipes.publish')) {
feature_refuse(); // the upgrade card on a page, the "upgrade" JSON error in an API call
}
$max = function_exists('feature_limit') ? feature_limit('recipes.max', user_id(), 20) : 20;
The features show up in every package form and on /pro at once. With no plugin answering the filters everything is allowed, so the same code works on a site without Wallet.
Migrating from WoWonder
The migration adds a Wallet & Pro step after Members: the four WoWonder Pro types (Wo_Manage_Pro) become packages with their prices, lengths, colours and features; Pro members get a membership with their end date; the wallet history (Wo_Payment_Transactions, Wo_Payments) comes across; bank receipts still waiting for approval appear on Pending payments. Balances were already copied with the members. A site without those tables is skipped quietly.
For plugin authors
Never call a function of this plugin; use the filters, and treat a null answer as "the wallet plugin is off".
$balance = apply_filters('wallet_balance', null, $userId); // float, or null when the plugin is off
$r = apply_filters('wallet_charge', null, $userId, 4.50, [
'reason' => 'Gift: a rose', // shown in the history
'ref' => 'gifts:12', // your own reference
'kind' => 'gift', // topup|purchase|pro|gift|refund|admin|transfer
'to' => $receiverId, // optional: the receiver is credited in the same transaction, minus the site commission
]);
// $r = ['ok' => bool, 'error' => string, 'balance' => float, 'txn' => int]
$r = apply_filters('wallet_credit', null, $userId, 2.00, ['reason' => 'Refund: a rose', 'ref' => 'gifts:12', 'kind' => 'refund']);
echo apply_filters('wallet_money', '', 12.5); // "$12.50" / "৳12.50", as the admin set it
$c = apply_filters('wallet_currency', []); // ['code' => 'USD', 'symbol' => '$', 'decimals' => 2, 'position' => 'before']
$url = apply_filters('wallet_topup_url', '', $userId); // the add-money page, to send a member who is short
$isPro = apply_filters('user_is_pro', false, $userId);
echo apply_filters('pro_badge_html', '', $userId); // the badge markup, or ''
$n = apply_filters('pro_boost_credits', 0, $userId); // free boosts left
$used = apply_filters('pro_boost_use', false, $userId); // true when one credit was taken
A charge that fails (not enough money, unknown member, bad amount) returns ok => false and changes nothing. Money arithmetic is done on DECIMAL columns inside a row lock, so two charges at once cannot overdraw a wallet.