| 开发者 | rescindly |
|---|---|
| 更新时间 | 2026年4月1日 03:07 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
rescindly-for-woocommerce folder to /wp-content/plugins/.m_ and can be found in your Rescindly dashboard.Yes. This plugin requires an active Rescindly account and a valid Merchant ID.
You can find your Merchant ID in your Rescindly dashboard after creating an account.
Your Rescindly widget is likely set to floating mode while the plugin is set to Order triggers mode. In that setup, the floating widget can render its own button while the plugin also renders order-page triggers. Fix: either switch the plugin to Footer only mode, or change your widget to inline mode in the Rescindly dashboard.
When prefill is enabled, the plugin passes the order number, customer name, and billing email to the widget through HTML data attributes. This data is used only to prefill the form on the page. It is not submitted to the Rescindly service until the customer confirms and submits the workflow.
No server-side API calls are made by the plugin from WordPress. The plugin loads a JavaScript file from the Rescindly CDN and renders the necessary integration points in WooCommerce.
No. This plugin is an integration layer for WooCommerce and depends on the external Rescindly service for the core withdrawal workflow.
Deactivation stops the widget from loading. Deletion through the Plugins page removes the plugin's Rescindly settings from your database.
No. The Hide trigger after N days setting is a convenience visibility limit only. It controls when the order-specific trigger is shown, not whether a customer may have statutory rights or contact the merchant through other channels.
The plugin is designed as a lightweight wrapper and loads the Rescindly widget from the official CDN. As with any storefront script, merchants should test their own theme and store environment before going live.