Title: Moksa for WooCommerce
Author: Moksa
Published: 31 juli 2026
Last modified: 8 oktober 2026
---
Plugins zoeken
# Moksa for WooCommerce
Door [Moksa](https://profiles.wordpress.org/moksa0923/)
[Download](https://downloads.wordpress.org/plugin/moksa-for-woocommerce.1.12.0.zip)
* [Details](https://nl.wordpress.org/plugins/moksa-for-woocommerce/#description)
* [Beoordelingen](https://nl.wordpress.org/plugins/moksa-for-woocommerce/#reviews)
* [Installatie](https://nl.wordpress.org/plugins/moksa-for-woocommerce/#installation)
* [Ontwikkeling](https://nl.wordpress.org/plugins/moksa-for-woocommerce/#developers)
[Ondersteuning](https://wordpress.org/support/plugin/moksa-for-woocommerce/)
## Beschrijving
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](https://github.com/Moksa1123/moksa-for-woocommerce).
### External Services
This plugin is a toolkit of optional integrations. Each integration only loads and
only transmits data when you, the site administrator, explicitly enable that module
and a customer chooses the corresponding payment / shipping / invoice option. No
data is sent to any third party unless the relevant module is enabled and used.
The plugin never sends data to Moksa or any analytics/telemetry service.
For every integration below, requests are made server-to-server over HTTPS using
your own merchant credentials, and typically include the order number, order amount,
buyer name, e-mail, phone, shipping/billing address, item descriptions, and (for
e-invoices) the buyer tax ID or carrier number that the customer enters at checkout.
When a module is set to test/sandbox mode, requests go to the provider’s corresponding
staging hostname instead of the production one listed below (for example payment-
stage.ecpay.com.tw, logistics-stage.ecpay.com.tw, einvoice-stage.ecpay.com.tw, ccore.
newebpay.com, sandbox-api.payuni.com.tw, sandbox-api.pchomepay.com.tw, sandbox-api-
pay.line.me, sandbox.tappaysdk.com, api-sandbox.shoplinepayments.com, cinv.ezpay.
com.tw, test.paynow.com.tw, testinvoice.paynow.com.tw, ssl.smse.com.tw/api_test).
#### Payment gateways
These run when a customer selects the gateway at checkout (to create the payment)
and when you query, capture, refund or void the payment from the order screen.
* **ECPay (綠界科技)** — credit card, ATM, CVS, barcode, installments, wallets.
Endpoints: payment.ecpay.com.tw, ecpayment.ecpay.com.tw (test mode: payment-stage.
ecpay.com.tw, ecpayment-stage.ecpay.com.tw). Terms: https://support.ecpay.com.
tw/10075/ — Privacy: https://www.ecpay.com.tw/CreditCard/Privacy
* **NewebPay (藍新金流)** — credit card, ATM, CVS, barcode, wallets. Endpoints:
core.newebpay.com (test mode: ccore.newebpay.com). Terms: https://www.newebpay.
com/website/Page/content/new_service_policy — Privacy: https://www.newebpay.com/
website/Page/content/privacy
* **PAYUNi (統一金流)** — credit card, ATM, CVS, wallets. Endpoints: api.payuni.
com.tw (test mode: sandbox-api.payuni.com.tw). Terms: https://www.payuni.com.
tw/terms — Privacy: https://www.payuni.com.tw/privacy
* **SmilePay (速買配)** — credit card, ATM, CVS, barcode. Endpoints: ssl.smse.com.
tw (SmilePay’s own API hostname — smse.com.tw and smilepay.net are both operated
by the same company, 訊航科技 Shinhang Technology; its policies are published
on the smilepay.net brand site; test mode uses the /api_test path on the same
hostname). Terms: https://www.smilepay.net/em/servicepolicy.asp — Privacy: https://
www.smilepay.net/em/servicepolicy.asp (SmilePay publishes a single combined service&
personal-data-protection document, so both links point at that document)
* **PayNow (立吉富)** — credit card, ATM, CVS, installments. Endpoints: www.paynow.
com.tw (test mode: test.paynow.com.tw). Terms: https://www.paynow.com.tw/PayNowUserAgreement.
aspx — Privacy: https://www.paynow.com.tw/safepolicy.aspx
* **PChomePay (支付連)** — credit card, ATM, CVS, barcode. Endpoints: api.pchomepay.
com.tw (test mode: sandbox-api.pchomepay.com.tw). Terms: https://www.pchomepay.
com.tw/other/service_treaty — Privacy: https://web.pchomepay.com.tw/introduction/
privacy
* **LINE Pay** — LINE Pay wallet. Endpoints: api-pay.line.me (test mode: sandbox-
api-pay.line.me). Terms: https://terms2.line.me/linepay_TW_TermsofUse?lang=zh-
Hant — Privacy: https://terms2.line.me/linepay_TW_PP
* **TapPay** — credit card via the TapPay Fields SDK loaded in the browser (js.
tappaysdk.com). Card data is tokenised client-side; only the token reaches your
server. Endpoints: prod.tappaysdk.com, js.tappaysdk.com (test mode: sandbox.tappaysdk.
com). Terms: https://www.tappaysdk.com/taiwan-en/privacy-term — Privacy: https://
www.tappaysdk.com/taiwan-en/privacy-term (TapPay publishes a single combined
terms & privacy document, so both links point at that document)
* **Shopline Payments** — credit card, wallets. Endpoints: api.shoplinepayments.
com (test mode: api-sandbox.shoplinepayments.com). Terms: https://book.shoplineapp.
com/pages/shopline-payments-terms-and-conditions — Privacy: https://www.shopline.
com/shopline-payments-privacy
#### Shipping / logistics
These run when a customer opens the convenience-store map at checkout (the store-
selection map is hosted by the provider), when a shipment is created after an order
is placed, and when you print a label or query shipment status.
* **ECPay Logistics (綠界物流)** — 7-11 / FamilyMart / Hi-Life / OK / home delivery.
Endpoints: logistics.ecpay.com.tw (test mode: logistics-stage.ecpay.com.tw).
Terms: https://support.ecpay.com.tw/10075/ — Privacy: https://www.ecpay.com.tw/
CreditCard/Privacy
* **NewebPay Logistics (藍新物流)** — CVS / home delivery. Endpoints: core.newebpay.
com (test mode: ccore.newebpay.com). Terms: https://www.newebpay.com/website/
Page/content/new_service_policy — Privacy: https://www.newebpay.com/website/Page/
content/privacy
* **PAYUNi Logistics (統一物流)** — 7-11 / home delivery (incl. cold chain). Endpoints:
api.payuni.com.tw (test mode: sandbox-api.payuni.com.tw). Terms: https://www.
payuni.com.tw/terms — Privacy: https://www.payuni.com.tw/privacy
* **SmilePay Logistics (速買配物流)** — 7-11 / FamilyMart / home delivery. Endpoints:
ssl.smse.com.tw (SmilePay’s own API hostname; see the SmilePay entry above —
same operator as smilepay.net; test mode uses the /api_test path on the same
hostname). Terms: https://www.smilepay.net/em/servicepolicy.asp — Privacy: https://
www.smilepay.net/em/servicepolicy.asp (single combined service & personal-data-
protection document)
#### E-invoice (Taiwan electronic invoicing)
These run when an invoice is issued for an order (immediately on payment, on completion,
or manually, per your setting) and when you void / issue an allowance / query an
invoice. Data includes the order amount, item descriptions and the buyer’s carrier
number, donation code or company tax ID entered at checkout.
* **ECPay e-Invoice (綠界電子發票)** — Endpoints: einvoice.ecpay.com.tw (test mode:
einvoice-stage.ecpay.com.tw). Terms: https://support.ecpay.com.tw/10075/ — Privacy:
https://www.ecpay.com.tw/CreditCard/Privacy
* **ezPay e-Invoice (ezPay 電子發票)** — Endpoints: inv.ezpay.com.tw (test mode:
cinv.ezpay.com.tw). Terms: https://www.ezpay.com.tw/info/Site_description/service_page/
member — Privacy: https://www.ezpay.com.tw/info/Site_description/service_page/
member (ezPay publishes a single combined membership & data-protection terms
page, so both links point at that page)
* **SmilePay e-Invoice (速買配電子發票)** — Endpoints: ssl.smse.com.tw (SmilePay’s
own API hostname; see the SmilePay entry above — same operator as smilepay.net;
test mode uses the /api_test path on the same hostname). Terms: https://www.smilepay.
net/em/servicepolicy.asp — Privacy: https://www.smilepay.net/em/servicepolicy.
asp (single combined service & personal-data-protection document)
* **PayNow e-Invoice (立吉富電子發票)** — Endpoints: invoice.paynow.com.tw (test
mode: testinvoice.paynow.com.tw). Terms: https://www.paynow.com.tw/PayNowUserAgreement.
aspx — Privacy: https://www.paynow.com.tw/safepolicy.aspx
* **AMEGO e-Invoice (光貿電子發票)** — Endpoints: invoice-api.amego.tw. Terms:
https://invoice.amego.tw/term — Privacy: https://invoice.amego.tw/privacy
#### Carrier tracking links (hyperlinks only — the plugin itself never contacts these hosts)
When a shipment has a tracking number, the order screen renders a plain hyperlink
to the carrier’s own public parcel-tracking page. The plugin makes no HTTP request
to any of these hosts and transmits no data to them; the shipment number only leaves
your site if a person clicks the link, at which point the carrier’s own terms and
privacy policy apply in their browser:
* **T-Cat 黑貓宅配** (t-cat.com.tw, incl. the tracking link shown for PAYUNi home-
delivery shipments) — Privacy: https://www.t-cat.com.tw/member/privacy.aspx
* **7-ELEVEN** (eservice.7-11.com.tw) — Privacy: https://www.7-11.com.tw/privacy.
asp
* **7-ELEVEN pickup status via PAYUNi logistics** (tracking.shopmore.com.tw, operated
by the Uni-President group for PAYUNi shipments) — service info: https://help.
shopmore.com.tw/ ; the PAYUNi logistics policies above apply to the shipment
itself
* **FamilyMart 全家** (fmec.famiport.com.tw), **Hi-Life 萊爾富** (www.hilife.com.
tw), **OK Mart** (ecservice.okmart.com.tw) — public tracking pages of each chain;
their site policies are linked from those pages
* **Chunghwa Post 中華郵政** (postserv.post.gov.tw) — Privacy: https://www.post.
gov.tw/post/internet/Group/index.jsp?ID=156739569921
#### Moksa AI assistant (optional, admin-only)
When an administrator actively uses the in-admin Moksa AI assistant, the typed question
and the store/order data needed to answer it (for example an order number, status,
totals or invoice/shipping numbers) are sent to the AI provider you have connected
in WordPress under **Settings Connectors** — Anthropic, Google or OpenAI — through
the WordPress 7.0 AI Client. This never happens automatically and only for the administrator
using the assistant. The plugin does not store these conversations on any Moksa
server, sends nothing to Moksa, and never transmits your AI provider keys (WordPress
manages the connector credentials). The transmitted data is governed by the terms
and privacy policy of the provider you choose: Anthropic — Terms: https://www.anthropic.
com/legal/commercial-terms — Privacy: https://www.anthropic.com/legal/privacy ;
Google — Terms: https://ai.google.dev/gemini-api/terms — Privacy: https://policies.
google.com/privacy ; OpenAI — Terms: https://openai.com/policies/terms-of-use/ —
Privacy: https://openai.com/policies/privacy-policy/
#### MCP server (optional, off by default)
This plugin can optionally expose a standards-compliant, stateless MCP (Model Context
Protocol) endpoint on **your own site** at `/wp-json/moksa-for-woocommerce/v1/mcp`,
so a standard MCP client you control (for example mcp-remote or Claude) can look
up orders and reports through the WordPress REST API. This is **not a Moksa service
and is not a phone-home**: nothing is sent to Moksa, the endpoint only runs on your
server and only exposes the plugin’s own WordPress Abilities. It is **off by default**
and must be turned on under WooCommerce Moksa AI Settings. Access requires authentication
with a WordPress Application Password for a user that has the “edit orders” capability(
use a dedicated, limited account). By default only read-only tools are exposed;
order-changing tools stay hidden unless you also enable the separate “allow external
AI to make changes” option, and every request is permission-checked on your server.
## Schermafbeeldingen
[⌊Modules overview — enable only the payment, shipping and e-invoice integrations
you need, all from one settings page.⌉⌊Modules overview — enable only the payment,
shipping and e-invoice integrations you need, all from one settings page.⌉[
Modules overview — enable only the payment, shipping and e-invoice integrations
you need, all from one settings page.
[⌊Block-based Checkout rendering Taiwanese payment methods natively, alongside the
order summary.⌉⌊Block-based Checkout rendering Taiwanese payment methods natively,
alongside the order summary.⌉[
Block-based Checkout rendering Taiwanese payment methods natively, alongside the
order summary.
[⌊Order list with the plugin's own order statuses plus shipping-method and tracking-
number columns (HPOS-native).⌉⌊Order list with the plugin's own order statuses plus
shipping-method and tracking-number columns (HPOS-native).⌉[
Order list with the plugin’s own order statuses plus shipping-method and tracking-
number columns (HPOS-native).
[⌊Order edit screen with per-provider payment, shipping and e-invoice cards.⌉⌊Order
edit screen with per-provider payment, shipping and e-invoice cards.⌉[
Order edit screen with per-provider payment, shipping and e-invoice cards.
[⌊Issuing an e-invoice from the order screen, including carrier type and mobile
barcode entry.⌉⌊Issuing an e-invoice from the order screen, including carrier type
and mobile barcode entry.⌉[
Issuing an e-invoice from the order screen, including carrier type and mobile barcode
entry.
## Installatie
#### Minimum Requirements
* PHP 8.2+
* WordPress 7.0+
* WooCommerce 9.9+
#### Setup
1. Install and activate the plugin.
2. Go to **WooCommerce Settings Moksa for WooCommerce** to enable the modules you
need.
3. Configure the credentials for each enabled provider on its dedicated tab.
## FAQ
### 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 ` 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.
## Beoordelingen
### [推薦！](https://wordpress.org/support/topic/%e6%8e%a8%e8%96%a6%ef%bc%81/)
[fan wu](https://profiles.wordpress.org/bboyfan/) 5 augustus 2026
超級金物流、發票大禮包！推薦
[ Lees 1 beoordeling ](https://wordpress.org/support/plugin/moksa-for-woocommerce/reviews/)
## Bijdragers & ontwikkelaars
“Moksa for WooCommerce” is open source software. De volgende personen hebben bijgedragen
aan deze plugin.
Bijdragers
* [ Moksa ](https://profiles.wordpress.org/moksa0923/)
[Vertaal “Moksa for WooCommerce” in je eigen taal.](https://translate.wordpress.org/projects/wp-plugins/moksa-for-woocommerce)
### Interesse in ontwikkeling?
[Bekijk de code](https://plugins.trac.wordpress.org/browser/moksa-for-woocommerce/),
haal de [SVN repository](https://plugins.svn.wordpress.org/moksa-for-woocommerce/)
op, of abonneer je op het [ontwikkellog](https://plugins.trac.wordpress.org/log/moksa-for-woocommerce/)
via [RSS](https://plugins.trac.wordpress.org/log/moksa-for-woocommerce/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.12.0 – 2026-10-09
New
* An “Invoice number” column on the WooCommerce orders list, shown whenever
an e-invoice provider is enabled. It reads whichever provider actually issued the
invoice — ECPay, ezPay, Amego, PayNow, SmilePay, or PAYUNi’s built-in invoice —
and marks voided invoices. Like any column, it can be hidden from Screen Options.
Fixed
* The “Invoice number” personalization tag in the block email editor only
read ECPay invoices, so it came out empty for invoices issued by the other providers.
It now reads all of them, and leaves voided invoices out.
#### 1.11.4 – 2026-10-07
Fixed
* On the classic checkout, a half-width field could be pushed into the middle
of the row and its partner dropped to the next line when the two fields above it
differed in height by a few pixels (for example the country field being slightly
taller than the state field). Each pair of half-width fields now starts on a new
row.
#### 1.11.3 – 2026-10-07
Security
* SmilePay payment notices could be forged. The only secret in SmilePay’s
check value is a 4-digit merchant code, leaving under a hundred values to try. Every
new SmilePay order now carries its own signed key in the notification URL, failed
checks stop automatic confirmation for that order after three attempts, and the
check value is computed from the order total rather than the amount in the notice.
Orders placed before this update keep the previous check. * A late failure or payment-
code notice could switch an already paid ECPay, NewebPay or SmilePay order back
to failed or on hold, and overwrote the transaction number used for refunds. Such
notices are now only recorded as an order note. * An ECPay or NewebPay payment whose
amount does not match the order total (for example an old payment tab completed
after the cart changed) now puts the order on hold for review instead of marking
it paid.
Fixed
* ECPay shipping status follow-up checks and the order screen’s status lookup
never worked: ECPay’s successful reply was treated as an error. * PAYUNi store pickup
on the block checkout: a first-time customer could not place an order, because the
hidden address fields were still required. * ECPay paper invoices were issued to
the ECPay member carrier instead of being printed. * ECPay tax-ID and paper invoices
failed on store-pickup orders without a street address. The pickup store’s address
is now used. * PAYUNi “hide billing address for store pickup” on the classic checkout:
switching back to home delivery left the address fields marked optional. * The AI
assistant button appeared a second time inside the plugin-update screen.
Changed
* Shipping status follow-up checks no longer save the order on every check(
so no hourly order-updated webhooks), also compare the status description, rotate
through every eligible order, and no longer run 8 hours late. * The Taiwanese field
layout is now switched on only from its own section. If the old “reorder fields”
checkbox was off, the section starts off. * The Taiwanese mobile number check is
now its own setting and works without the Taiwan address tools.
#### 1.11.2 – 2026-09-11
Fixed
* Half-width fields on the classic checkout could end up stranded at half
width on their own — the phone field, for instance, whenever its neighbour had been
hidden by store-pickup billing hiding, the country-hiding option, or a WooCommerce
setting. Pairing was decided once on the server before any of that hiding happened.
It is now re-checked in the browser from the fields actually on screen, every time
the checkout refreshes, so a field whose partner disappears takes the full row. *
The email field could not usefully be set to 50% width: pairing reserved a slot
for it on the shipping address form, which has no email field, so its neighbour
there fell out of step. Pairing is now worked out per form from the fields it actually
contains. * NewebPay convenience-store pickup on the classic checkout never showed
the store picker. The picker was drawn 200 ms after choosing the method, and WooCommerce’s
own refresh then replaced that part of the page and wiped it. It is now redrawn
after every refresh, the same way the ECPay, PAYUNi and SmilePay pickers already
were.
Older entries are available in the plugin’s repository.
## Meta
* Versie **1.12.0**
* Laatst geüpdatet **1 dag geleden**
* Actieve installaties **10+**
* WordPress versie ** 7.0 of nieuwer **
* Getest t/m **7.1.3**
* PHP versie ** 8.2 of nieuwer **
* Taal
* [English (US)](https://wordpress.org/plugins/moksa-for-woocommerce/)
* Tags
* [invoice](https://nl.wordpress.org/plugins/tags/invoice/)[payment](https://nl.wordpress.org/plugins/tags/payment/)
[shipping](https://nl.wordpress.org/plugins/tags/shipping/)[taiwan](https://nl.wordpress.org/plugins/tags/taiwan/)
[woocommerce](https://nl.wordpress.org/plugins/tags/woocommerce/)
* [Geavanceerde weergave](https://nl.wordpress.org/plugins/moksa-for-woocommerce/advanced/)
## Waarderingen
5 van 5 sterren.
* [ 1 5 ster beoordeling ](https://wordpress.org/support/plugin/moksa-for-woocommerce/reviews/?filter=5)
* [ 0 4 sterren beoordelingen ](https://wordpress.org/support/plugin/moksa-for-woocommerce/reviews/?filter=4)
* [ 0 3 sterren beoordelingen ](https://wordpress.org/support/plugin/moksa-for-woocommerce/reviews/?filter=3)
* [ 0 2 sterren beoordelingen ](https://wordpress.org/support/plugin/moksa-for-woocommerce/reviews/?filter=2)
* [ 0 1 sterren beoordelingen ](https://wordpress.org/support/plugin/moksa-for-woocommerce/reviews/?filter=1)
[Je beoordeling](https://wordpress.org/support/plugin/moksa-for-woocommerce/reviews/#new-post)
[Bekijk alle beoordelingen](https://wordpress.org/support/plugin/moksa-for-woocommerce/reviews/)
## Bijdragers
* [ Moksa ](https://profiles.wordpress.org/moksa0923/)
## Ondersteuning
Opgeloste problemen in de laatste twee maanden:
0 van de 1
[Het supportforum bekijken](https://wordpress.org/support/plugin/moksa-for-woocommerce/)