| 开发者 |
laxmidigital
mozzenoplugin |
|---|---|
| 更新时间 | 2026年6月9日 23:19 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wc-api/mozzeno_webhook) to move orders through mozzeno-specific statusesassets.mozzeno.com)
This plugin loads JavaScript from assets.mozzeno.com to display the financing simulation widget on product, cart, and checkout pages, and to handle the payment redirect flow. The scripts receive the loan amount, branch identifier, language, and customer first name, last name, and email address — but only when the customer initiates the mozzeno checkout flow. No data is sent on page load for widget display alone.
Terms of service — Privacy policy
mozzeno API (api.mozzeno.com / api-dev.mozzeno.com)
Outbound webhooks are sent to the mozzeno API when the merchant updates key order states (delivery initiated, cancellation). The payload includes the order reference and event type. In sandbox mode, requests go to api-dev.mozzeno.com; in live mode, to api.mozzeno.com.
Terms of service — Privacy policy
Select2 for admin multi-select fields is bundled in the plugin and makes no external requests.
wp-content/plugins/./wc-api/mozzeno_webhook).api.mozzeno.com or api-dev.mozzeno.com).
mozzeno adds custom order statuses for the loan lifecycle. WooCommerce core statuses (for example Processing, Completed, Cancelled) still behave as usual.
In the gateway and advanced settings you can choose which WooCommerce status should notify mozzeno that delivery has started (order.delivery_initiated). Stock release strings for declined or cancelled loans are configurable in advanced options. Always test status changes in sandbox before going live.
Yes, as long as those plugins follow WooCommerce APIs. mozzeno registers its own statuses and maps mozzeno webhook events to them; it does not remove third-party statuses. If another plugin also forces status transitions on the same orders, coordinate rules so two automations do not conflict (for example, avoid duplicate stock changes by testing with your full stack).
Yes. The plugin declares compatibility with custom order tables.
Defaults are configurable in settings; the plugin ships with a broad range suitable for typical mozzeno flows. Adjust min and max to match your contract with mozzeno.
Custom database tables are created on activation (mozzeno_transaction, mozzeno_log, mozzeno_stock_reservation with your WordPress table prefix). Logs can be pruned by the plugin’s scheduled tasks according to your configuration.