Multi Currency (plugin)
Prices in the visitor's own currency: a list of currencies with typed or daily online rates and a margin, the picker in the header and on the upgrade page, the currency each gateway charges in, and how an order is settled back into the site currency. Free.
Packages are priced in one currency, the site currency set under Site Settings → Premium Pricing (Currency symbol and Currency code). The Multi Currency plugin lets a visitor see every price in a currency of their own - taka, euro, rupee, pound - converted with a rate you set or fetch, and, where the payment method can take that currency, pays in it. A picker sits in the site header and on the upgrade page, the choice is remembered, and when the payment is confirmed the order is settled back into the site currency so your reports stay in one currency.
Who it is for
Sites whose visitors come from several countries and would rather read "৳ 1,200" than "$10", and sites that sell through a local gateway such as bKash or SSLCommerz next to PayPal and Stripe (Payment Gateways). A site with one audience and one currency has no use for it and can leave it off.
Switching it on
Multi Currency is free and works with every licence. A fresh install switches it on; on a site that was updated, switch it on at Admin → Extensions → Plugins (Manage Plugins) if it is off (Updating). Switching it on adds a column currency to the users table and the table bp_currency_orders. Its page appears under Extensions as Currencies (/admin/plugin/currency), with a Settings tab beside it.
Until at least one currency is switched on with a rate, the plugin does nothing: no picker, no change to any price.
The currencies
The Currencies page begins with the site currency and the rate source, then lists your currencies, one row each:
| Field | What it means |
|---|---|
| Code | Three to five letters, such as BDT. The site currency itself cannot be added (its rate is 1). |
| Name | Shown in the picker beside the code. |
| Symbol | Up to eight characters: ৳, €, Rs. |
| Rate (1 <site currency> =) | How many units of this currency one unit of the site currency buys; 120 for BDT when the site currency is USD. |
| Decimals | 0 to 4 digits after the point; 0 for a currency you show in whole units. |
| Position | The symbol Before the number or After the number. |
| Auto rate | Fetched rates replace this row's rate. Leave it off for a rate you want to keep as typed. |
| On | Offered in the picker. A currency without a rate cannot be switched on; the page says so when you save. |
| Remove | Deletes the row when you save. |
Fill the empty last row to add a currency. Add popular currencies adds fourteen ready rows (BDT, EUR, GBP, INR, USD, AED, SAR, MYR, PKR, JPY, CAD, AUD, TRY, RUB) with their symbols and decimals, switched off and without a rate: type or fetch the rates, then switch on the ones you want. Save currencies keeps the table.
Rates: by hand or online
Under Settings → Rates:
- Rate source - Manual (typed by hand) or Online (fetched).
- Rate address (
fetch_url) - where online rates come from;{BASE}becomes the site currency code. The default ishttps://open.er-api.com/v6/latest/{BASE}, which needs no key. Answers in therates,conversion_ratesand exchangerate.hostquotesshapes are understood. - Margin on fetched rates (%) (
rate_margin) - added on top of every fetched rate, for the bank's spread; 0 adds nothing. - Fetch rates every day (
auto_fetch) - lets the cron job do the fetching.
Fetch rates now on the Currencies page reads the address at once and updates every row marked Auto rate; a line under Rate source says how many rates changed, from which host, and when - or why it failed. The cron job Currency: fetch exchange rates (currency_rates, once a day) does the same by itself, but only while the source is Online and Fetch rates every day is on; otherwise it reports Rates are set by hand (nothing fetched) (Scheduled jobs).
What members see
Under Settings → Showing:
- Currency picker in the site header (
show_selector, on) - a small list of the site currency and your currencies. The upgrade page always carries one, under the packages, whatever this says. - "Prices shown in X, charged in Y" note on the upgrade page (
show_note, on) - says which currency the member will really pay in, one line per payment method when they differ, and the rate used. - Currency for new visitors (
default_code) - a code from your list, such asBDT. Empty keeps the site currency until the visitor chooses.
The choice is kept in the cookie bp_cur for a year and, for a signed-in member, in their account (bp_users.currency), so it follows them to another browser. A visitor without a choice gets the member's saved currency, then Currency for new visitors, then the site currency. Every price the site draws - the packages, the upgrade page, the download and file pages, the home page - is converted and rounded to the currency's decimals. The admin panel is never converted: you always see the site currency there.
Which gateway charges in which currency
A payment method takes only the currencies it declares: PayPal and Paddle a list of about twenty-five, Stripe, Coinbase Commerce, bank transfer and the generic bank / other wallet any, and bKash, Nagad, SSLCommerz, Rocket, Upay, SureCash, Tap and MCash taka only. Under Settings → Gateways every payment method that is switched on has a box <name> charges in (the setting map_<gateway>, for example map_paypal):
- empty - what the gateway declares, printed under the box;
- a list of codes separated by commas, such as
USD, EUR; *- any currency;-- never; always the site currency.
When a member chooses a currency and presses Pay, the plugin checks the gateway:
- It takes that currency. The order is re-priced: the amount becomes the converted price and the order's currency becomes the member's. The provider sees, say, 1,200 BDT.
- It does not. The order stays in the site currency and the upgrade page said so beforehand (charged in USD). A taka gateway still converts to taka by itself with its own Taka per unit of the site currency (Payment Gateways).
What the order stores, and how it settles
At checkout a row in bp_currency_orders records the order, the gateway, the currency the member saw, the currency and amount charged, the site currency and amount, and the rate. The order in the payments table carries the charged currency while it waits.
When the order is confirmed - by the provider, or by you on Pending Orders - the plugin puts the site-currency amount and code back on the order and marks the row settled just before the account is upgraded. People → Payments, the revenue chart and the Rewards Program therefore count the site currency, never a mix; the amount the provider really took stays in bp_currency_orders (charged_amount, charged_code, rate).
Tips
- Set the rates by hand first, look at the upgrade page in a private window, then switch on the daily fetch.
- Keep a small Margin on fetched rates when your gateway or bank takes a spread, so you are not paid less than the package price.
- A currency that is not on the gateway's list is simply charged in the site currency; you need not hide it. Narrow a gateway with the charges in box if you only want certain currencies there.
- Make one small purchase per currency with each gateway in its test mode before you rely on it: the plugin sends the amount, and each gateway's own rules for decimals apply.
- A rate that was never set cannot be switched on, and a switched-off currency never shows in the picker.