Moksa for WooCommerce
| 开发者 | moksa0923 |
|---|---|
| 更新时间 | 2026年8月1日 23:45 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
详情介绍:
A Taiwan-focused WooCommerce extension. Toggleable modules cover ECPay (綠界), NewebPay (藍新), SmilePay (速買配), LINE Pay, PAYUNi (統一金流), PayNow (立即富), PChomePay (支付連), TapPay and Shopline Payments for payments; ECPay, NewebPay, SmilePay, PAYUNi and PayNow for convenience-store + home-delivery shipping; ezPay, ECPay, SmilePay, PayNow and AMEGO for Taiwan e-invoicing.
Enable only the providers you need from a single settings page — payment, shipping and invoice modules are fully independent and can be mixed in any combination.
HPOS-native, Block Checkout-native, PHP 8.2+ strict-typed, GPLv3, no premium gating.
Moksa AI assistant (new in 1.3.0)
Built on the WordPress 7.0 AI Client, Moksa AI is an optional in-admin chat assistant that lets you run common store tasks in natural language: find orders by invoice / shipping / payment number, look up order details and counts, change order status (single or batch), add order notes, issue / void / allowance e-invoices, create and print shipping labels, and enable or disable modules, individual payment methods and invoice issuing methods. Every action that changes data first shows a summary and waits for your explicit confirmation before it runs. The assistant uses whichever AI provider you connect under Settings → Connectors — the plugin never handles your AI keys, refunds, or credentials.
Source
Source code and issue tracker: github.com/Moksa1123/moksa-for-woocommerce.
安装:
Minimum Requirements
- PHP 8.2+
- WordPress 7.0+
- WooCommerce 9.9+
- Install and activate the plugin.
- Go to WooCommerce → Settings → Moksa for WooCommerce to enable the modules you need.
- Configure the credentials for each enabled provider on its dedicated tab.
屏幕截图:
常见问题:
Does it work with the Block-based Checkout?
Yes. Every payment method ships an AbstractPaymentMethodType + React component, and the convenience-store picker / invoice fields render inside the Checkout block.
Is it HPOS-compatible?
Yes. All order meta uses $order->update_meta_data() / $order->save(), never update_post_meta().
Can I mix providers?
Yes. Payment, shipping and invoice modules are fully independent — any combination works.
What is the Moksa AI assistant and what does it need?
It is an optional in-admin chat assistant for managing orders, e-invoices, shipping labels and module settings in natural language. It requires WordPress 7.0 (for the built-in AI Client) and an AI provider connected under Settings → Connectors; enable it under the plugin's Advanced settings. Every action that changes data first asks for your confirmation, and the assistant can never read or change your provider credentials, switch sandbox/live mode, or issue refunds.
Can external AI tools connect to my store over MCP?
Yes, optional and off by default. Turn it on under WooCommerce → Moksa AI → Settings → "Enable external MCP server". The plugin then serves a standards-compliant, stateless MCP (Model Context Protocol) endpoint at /wp-json/moksa-for-woocommerce/v1/mcp that any standard MCP client (for example mcp-remote or Claude) can connect to directly — no bridge required.
Authentication uses a WordPress Application Password for a user that has the "edit orders" capability; use a dedicated, limited account rather than an administrator. Connect your client to the endpoint with an Authorization: Basic <base64 of username:application-password> header. By default only read-only tools (look up orders, reports, settings overview) are exposed; order-changing tools stay hidden unless you also enable the "allow external AI to make changes" option, and destructive actions still require in-store confirmation. Every request is permission-checked on the server.
更新日志:
1.5.4 - 2026-08-01
- Fix: saving the module list switched off any module whose card is not on that screen. Order number lookup is configured on the Advanced tab, so every save silently turned it off — and because it is what registers the assistant's tools, the AI assistant was left with nothing to work with.
- Fix: enabling only the AI assistant gave it no tools at all, so the chat window never appeared and nothing seemed to happen. It now registers the order abilities it needs on its own.
- Fix: opening the Moksa AI screen while both modules were off showed "you do not have permission to access this page", which is what WordPress says about a page that is not registered — it was never a permissions problem. The screen now explains the situation and links to the module list.
- Fix: the checkout field order list was missing the email field.
- Fix: 1.5.2 could show a floating assistant button on every admin screen even when nothing was available to run, opening an empty panel. It now appears only when there is something to show.
- Fix: the assistant button used an emoji, which WordPress replaces with an image hosted on s.w.org; on sites that cannot reach that host it rendered as a broken image. It is now drawn as an inline icon and loads nothing external.
- Fix: the fallback panel shown when no AI provider is configured was untranslated. Its labels now follow the site language.
- The Moksa AI chat window is now a shared component. When several Moksa plugins are installed alongside each other they no longer each draw their own floating window; one window serves them all and can reach every plugin's abilities. Installed on its own, this plugin behaves exactly as before.
- Fix: the assistant advertised its 28 abilities to the AI model even when the module that actually registers them was switched off. A model given a tool name that does not exist does not report an error — it invents an answer that looks plausible. Only abilities that are genuinely registered are offered now.
- Fix: the "About Moksa AI" status badge used emoji, which WordPress replaces with an image hosted on s.w.org. On sites where that host is unreachable the badge rendered as a broken image. It is now drawn in CSS and loads nothing external.
- Fix: the Moksa AI submenu appeared under WooCommerce whether or not the assistant was in use. It now appears only once the Moksa AI or Storefront support module is enabled.
- Fix: those two modules had no card on the module overview, so there was no way to enable them from the settings tab at all. They now appear under Tools alongside every other module.
- Fix: both modules were behind two separate switches — the module card and a second master switch inside the Moksa AI screen — so enabling one alone did nothing. The module card is now the only switch. Sites that had the old master switch off keep both modules off.
- The Moksa AI screen now uses the same collapsible section cards as the rest of the settings tab.
- i18n: every translatable string is now written in English in the source, and Traditional Chinese ships as a real translation. Previously the source strings were Chinese, which meant the plugin could never be translated into any other language and WordPress.org reported it as having no Traditional Chinese localisation at all. 2,442 strings are covered, so Chinese stores see exactly the same wording as before.
- i18n: Taiwanese cities and districts now use a translator context (
_x), so the districts that share a name across cities — Zhongzheng in both Taipei and Keelung, for example — are no longer collapsed into one entry that translators cannot tell apart. - Fix: invoice line-item units sent to the e-invoice services were wrapped in a translation call, so on a non-Chinese site they would have been submitted in the site language instead of the value the tax authority expects. They are now sent as fixed data.
- Fix: the order-status labels shown as post-status counts in the admin order list are now translatable in their own right rather than reusing an unrelated shipment-tracking string.
- Dev: the translation catalogue is generated from a single English-to-Chinese map and the build fails if any string is missing a translation, so a new string can no longer ship untranslated.
- Security: two SmilePay logistics endpoints (T-cat tracking-number retrieval and C2B label data) were still declared with plain http://; both now use https:// (verified reachable), so every request the plugin makes is TLS-encrypted as the readme states.
- Security: the module on/off save handler and the order-status colour save handler verified neither a nonce nor a capability inside the method, relying on the WooCommerce settings page upstream. Both now verify the WooCommerce settings nonce and the manage_woocommerce capability inline, in the same form WooCommerce core uses.
- Security: the quick-edit and bulk-edit handlers for the product temperature-zone field verified a nonce name that WooCommerce never issues for those forms, so the check always failed and the field silently stopped saving from quick/bulk edit. They now verify the same woocommerce_quick_edit_nonce that WooCommerce core verifies, restoring the feature.
- Security: the classic-checkout store validation and the PAYUNi store-restore handler now verify their nonces first, in straight-line form, before touching any request field.
- readme: every provider entry now lists its test/sandbox hostname inline and carries an explicit Terms link and an explicit Privacy link (providers publishing a single combined document have both links pointing at it, with a note); the AMEGO terms link points at the actual terms page; added the previously undocumented ecpayment-stage.ecpay.com.tw test hostname.
- i18n: the text domain is now
moksa-for-woocommerce, matching the assigned plugin slug (all 4,000+ gettext calls, the plugin header, the block-checkout scripts and the bundled zh_TW translation files were updated; the main plugin file was renamed accordingly). - Security: the PChomePay webhook no longer trusts its payload at all. On top of the source-IP allowlist, every notification now triggers a server-to-server query back to PChomePay (
GET /v1/payment/{id}) and the authoritative API response gates the order transition:order_confirmrequires API status S with a matching amount, and expiry/failure notifications are rejected for orders the API reports as paid. The allowlisted IPs are now filterable viamoksafowo_pchomepay_notify_ips. - Security: the product temperature quick-edit / bulk-edit / product-save / variation-save handlers now re-verify the WooCommerce nonce and check
edit_productcapability in-place (fail-closed) instead of relying on the upstream caller having done so. - readme: each SmilePay integration now explains that ssl.smse.com.tw is SmilePay's own API hostname (smse.com.tw and smilepay.net are operated by the same company, 訊航科技); OpenAI policy links point at the individual terms and privacy pages.
- Naming: the PHP namespace root was changed from
MoksaWeb\Mowc\toMoksafowo\, so every global identifier the plugin declares (namespaces, constants, options, hooks, AJAX actions, database tables) now shares the singlemoksafowoprefix. - Naming: six filters were still published under WooCommerce-prefixed hook names (
woocommerce_get_sections_*,woocommerce_get_settings_*,woocommerce_shipping_*_is_available) even though the methods that fire them fully override WooCommerce and never call the parent implementation. They are nowmoksafowo_*. - Naming: the checkout field namespace and admin CSS class prefix were unified under
moksafowo; the unused legacyMOWP_VAULT_KEYconstant fallback was removed. - Database: every table name now goes through
$wpdb->prepare()using the%iidentifier placeholder, and everyLIKEpattern through%s. No table name or search term is interpolated into SQL anywhere in the plugin, includinguninstall.php. - Fix:
Aes::decrypt_cbc_hex()validated its input only after callinghex2bin(), which emitted a PHP warning on malformed input before the exception was thrown. It now validates first. - Admin: order detail notes no longer expose the internal plugin codename.
- Security fix: the NewebPay logistics store-map callback verified its signature only when a HashData value was actually supplied, so an attacker could omit it to skip verification. Now rejected (fail-closed) whenever HashData is missing.
- Security fix: PayNow's secondary PassCode2 check (barcode/e-wallet payments) was skipped when the field was empty instead of being required; now fail-closed.
- Settings: corrected the SmilePay "Mid" field description, which still described the old skip-if-empty behaviour after the fail-closed fix.
- readme: OpenAI's Terms/Privacy links replaced with OpenAI's policy hub, which several individual policy sub-pages intermittently blocked as bot traffic.
- Added explicit references to the exact WooCommerce core methods (
WC_Settings_Page,WC_Shipping_Method::is_available()) that mandate thewoocommerce_*-prefixed filter tag names flagged by the automated prefix scan — these are WooCommerce's own extension-point names, not ones this plugin defines.
- Security hardening: the SmilePay payment callback now rejects requests when the merchant verification code (參數碼) is not configured (fail-closed) and only accepts callbacks for orders actually paid via SmilePay.
- The LINE Pay admin confirm action now uses the standard check_ajax_referer() flow.
- Readme: clarified SmilePay/ezPay combined terms & privacy documents and documented carrier tracking links (pure hyperlinks — the plugin never contacts those hosts) with verified policy links.
- Removed a non-functional leftover PAYUNi credentials migrator (its map used identical source and target option names, so it did nothing).
- The e-invoice donation-organization option is now written under a statically-prefixed, allow-listed option name.
- Reworked the PAYUNi store-selection restore so the nonce verification is inline and explicit.
- Completed the "External services" documentation in the readme to list every payment, shipping and e-invoice endpoint the plugin can contact, including the credit-card query endpoint and all sandbox/test hostnames.
- Minor security hardening of the PAYUNi store-selection AJAX handler: the request nonce is now verified before any other processing.
- Improved the AI assistant's handling of multi-part questions (e.g. asking for revenue and pending-shipment counts in one message) so they are answered reliably in a single reply.
- Further hardened output escaping on the admin order payment panel and the customer payment-information notice and email (allow-listed HTML at the point of output).
- E-invoice fields on the block checkout now show, hide and validate through WooCommerce's native conditional field logic (JSON Schema) instead of custom scripting, for reliable behaviour across WooCommerce updates.
- The mobile-barcode and personal-certificate carrier inputs are now separate fields, each with its own format validation.
- Raised the minimum WooCommerce version to 9.9, required by the native conditional checkout fields.
- Internal consolidation of the e-invoice checkout-field code, plus further hardening of asset loading and input handling.
- New Moksa AI in-admin assistant (requires WordPress 7.0 AI Client and a configured AI connector): query and manage orders, e-invoices, shipping labels and module settings in natural language, with a human confirmation step before any change is applied.
- Order tools via the WordPress Abilities API: find order by number, order details, order counts, status changes (single and batch), order notes, and an advanced order list.
- Taiwan e-invoice actions: issue, void and allowance, plus per-channel issuing-method toggles.
- Shipping: create a logistics booking and print labels (single and batch).
- Manage settings by natural language: enable or disable provider modules, individual payment methods and invoice issuing methods — each behind a confirmation step. Credentials and sandbox/live switches are never exposed.
- Raised the minimum WordPress version to 7.0, required by the AI assistant and the Abilities API. Core payment, shipping and invoice features are unchanged.
- Removed the unused SMS module.
- All global identifiers renamed to the unique
moksafowoprefix (options, hooks, AJAX actions, gateway IDs, script handles, order meta, custom order statuses) per WordPress.org review. - Hardened all payment / logistics webhook handlers: signature verification before any use, full per-field input sanitization, no raw request logging.
- Store-selection restore at checkout now requires a nonce.
- All inline
<script>/<style>output replaced withwp_enqueue_*,wp_add_inline_*andwp_print_inline_script_tag(). - All dynamic admin card / tracking-link HTML now escaped through explicit
wp_ksesallowlists at output time.
- Initial public release on the WordPress.org Plugin Directory.