The eClass LMS Payment Gateways Addon php-scripts extension is a paid add-on for the eClass Learning Management System that adds eleven regional and international payment gateways to the platform’s course checkout. It exists because the base LMS ships with a limited set of ways to take money, and this add-on fills the gaps for course sellers whose students pay through M-Pesa, bKash, eSewa, PayTabs, DPO or similar local rails. It is aimed at educators, training institutes and course businesses selling to learners in Africa, South Asia, Southeast Asia and the Middle East rather than to a purely US or European audience.
The item is sold on ThemeForest under the PHP scripts category at $35, published by the Mediacity developer account. Sales figures are not disclosed on the listing, so there is no meaningful purchase history to weigh. The review below works from the vendor’s feature list, changelog and stated requirements.
What the eClass LMS Payment Gateways Addon php-scripts extension actually adds
The core value is breadth of coverage in a single install. Rather than asking an eClass site owner to commission custom gateway work for each country they sell into, the add-on bundles eleven integrations behind one admin screen. The vendor lists M-Pesa (Kenya), eSewa (Nepal), Authorize.Net (US), PayTabs (Saudi Arabia), DPO Payments (Africa), SManager and bKash (Bangladesh), Square and Worldpay (US), Midtrans (Indonesia) and OnePay (Vietnam).
What that means in practice is that a course business can present a checkout page populated with the methods its students already recognise. A Kenyan learner can complete an enrolment with M-Pesa; a Bangladeshi learner can use bKash; an Indonesian learner can use Midtrans. Local payment familiarity is one of the more reliable levers on checkout completion in emerging markets, where card penetration is uneven and international card acceptance can be patchy.
Administration and configuration
Gateways are enabled and managed from inside the LMS admin rather than through a separate dashboard, which keeps credential management in one place. The vendor describes the setup as quick and the integration as native to eClass. Each gateway will still need its own merchant account and API credentials from the respective provider, so the add-on supplies the connection layer, not the merchant account itself.
Compatibility and maintenance history
The changelog is the most informative part of the listing. The add-on launched in May 2021 with M-Pesa alone, then added Authorize.Net, DPO, PayTabs and SManager in September 2021, followed by bKash, Worldpay, Midtrans and Square later that month. OnePay arrived in January 2023. The most recent release, version 1.9 in August 2025, adds support for a new layout, compatibility with eClass 6.9 and a move to PHP 8.2.14. That is a four-year update trail with a recent release, which is a reasonable signal that the add-on is still being maintained alongside the parent theme.
Stated security posture
The listing claims transactions are handled through reliable APIs with encryption. The vendor does not publish technical detail on tokenisation, PCI scope or how card data is handled in each integration, so buyers who need to document compliance should verify that directly with the developer before relying on the claim.
Where this add-on fits, and where it does not
The clearest fit is an eClass installation that already sells courses and has an audience concentrated in one or more of the eleven supported regions. A training institute in Dhaka selling to local professionals, a Kenyan educator running cohort courses paid by mobile money, or an Indonesian bootcamp taking Midtrans payments all get direct value from a single $35 purchase.
A second fit is the multi-country course business. An organisation selling the same catalogue into Africa, South Asia and the Middle East would otherwise need three or four separate gateway integrations. Bundling them reduces both development cost and the number of moving parts to maintain.
A third fit is agencies building eClass sites for education clients. The add-on shortens delivery on projects where the client’s payment requirements are already known and fall within the supported list.
It is the wrong purchase in several common situations. If the audience pays by Stripe, PayPal or a standard card processor, the add-on adds nothing, because none of those are in the list. If the site runs on WordPress with WooCommerce, Tutor LMS, LearnDash or a SaaS platform, the add-on is irrelevant since it depends entirely on eClass. And if the business sells to a region not represented among the eleven gateways, the purchase will not solve the actual problem.
Strengths and limitations of the eClass LMS Payment Gateways Addon
Strengths
- Unusually wide regional coverage for the price. Eleven gateways for $35 is inexpensive next to commissioning even one custom integration.
- Strong emerging-market representation. M-Pesa, bKash, eSewa, DPO, PayTabs, Midtrans and OnePay cover markets that mainstream LMS payment stacks routinely ignore.
- Recent, documented maintenance. Version 1.9 in August 2025 confirms active compatibility work with eClass 6.9 and PHP 8.2.14.
- Single admin surface. Managing every gateway from within the LMS reduces the operational overhead of juggling multiple plugins or custom code.
- Incremental growth. The changelog shows gateways added over time rather than a single launch, which suggests the developer responds to regional demand.
Limitations
- No Stripe or PayPal. The two most widely used global processors are absent. Sites that need them must source them elsewhere, which undercuts the “one addon” pitch.
- Hard version and PHP requirements. eClass 6.9 or above and PHP 8.2.14 are stated as mandatory. Sites on older eClass builds or PHP 8.1 will need to upgrade before installing, and that upgrade may be more disruptive than the add-on itself.
- No published sales or rating data. There is no purchase history or review score on the listing to use as a confidence signal, which matters for a payment-related component where reliability is critical.
- Merchant accounts are the buyer’s responsibility. Each gateway requires separate onboarding with the provider, and some regional providers have lengthy KYC processes that the add-on does nothing to shorten.
- Thin technical documentation on the listing. Security, refund handling and failure-mode behaviour are described in marketing terms rather than specifics, so due diligence requires contacting the developer.
- Preview media is not licensed. The vendor explicitly notes that images, icons and logos in the previews are excluded and require separate permission.
How the add-on compares with the wider payment-integration category
Payment options for an LMS generally fall into three buckets: gateways built into the core platform, third-party plugins that connect a processor, and custom development. The eClass LMS Payment Gateways Addon php-scripts product sits in the second bucket but behaves more like a curated bundle than a single-processor connector.
Against built-in gateways, the add-on wins on regional reach. Core LMS payment features tend to favour Stripe, PayPal and maybe one or two card processors, which is fine for Western audiences and inadequate for African or South Asian ones. Against single-processor plugins, the add-on wins on breadth but loses on depth: a dedicated Stripe or PayPal plugin will typically offer more configuration, stronger documentation and a longer support record than any one gateway inside this bundle.
Against custom development, the economics favour the add-on for any project that needs two or more of the supported gateways. A single custom integration can easily cost more in developer hours than the $35 price tag. Custom work becomes the better choice only when the required gateway is not in the list, or when the site needs behaviour the add-on does not expose.
The honest positioning is that this is a regional-coverage tool, not a universal payment solution. Buyers who expect it to replace a full payment stack will be disappointed; buyers who need M-Pesa plus bKash plus PayTabs in one install will find little else that does the job at this price.
Frequently Asked Questions
Does the eClass LMS Payment Gateways Addon work with Stripe or PayPal?
No. Neither Stripe nor PayPal appears among the eleven supported gateways. The add-on covers M-Pesa, eSewa, Authorize.Net, PayTabs, DPO Payments, SManager, bKash, Square, Worldpay, Midtrans and OnePay. Sites that need Stripe or PayPal must source those integrations separately, either through the base eClass platform or a dedicated plugin.
What version of eClass and PHP does the add-on require?
eClass 6.9 or above and PHP 8.2.14 are both stated as mandatory. The base LMS must already be installed on the server before the add-on will function. Older eClass builds and earlier PHP versions are not supported by the current release, so an upgrade may be required before installation.
Is the add-on a one-time purchase or a subscription?
The listing shows a one-time price of $35 with no subscription mentioned. ThemeForest items typically include support and updates for a defined period, after which renewal is optional. Buyers should confirm the current support terms on the item page, since the vendor does not spell them out in the description.
Can the add-on be used on a WordPress site with WooCommerce?
No. It is built specifically for the eClass Learning Management System, which is a standalone PHP application rather than a WordPress plugin. Sites running WooCommerce, Tutor LMS, LearnDash or any other WordPress-based LMS cannot use this add-on, regardless of which payment gateways they need.
Verdict on the eClass LMS Payment Gateways Addon php-scripts extension
Buy this if the site runs eClass 6.9 or later on PHP 8.2.14 and the student base pays through one or more of the eleven supported regional gateways. The price is low relative to the integration work it replaces, the changelog shows genuine maintenance, and the coverage of African and South Asian payment rails is difficult to match elsewhere.
Do not buy it if the audience pays by Stripe, PayPal or standard card processing, if the platform is anything other than eClass, or if the required gateway is not on the list. The absence of published sales and rating data also means buyers should test the demo admin credentials the vendor provides before committing, particularly the specific gateway they intend to use.




