WooCommerce
The WooCommerce plug-in does the server-side work of this reference inside WordPress: a button on the products you choose, the configurator opened with the right board, and one cart line at a price your server verified. It is in early access and not in the WordPress directory.
Early access: the merchant API is built and can be tried in a sandbox shop; plug-ins for shop platforms are still in development. CutOptim collects no payment: the cart, the checkout and the payment stay in your shop.
Paths, field names, error codes, header names and code samples stay in English: they are the contract.
What happens before a cart line exists
The shopper orders in the configurator; the browser sends the order to your WordPress site. The plug-in then checks, in this order:
- The order belongs to your shop, in your currency, and is priced.
- The quote hash recomputed from the quote the browser sent equals the one in the token; any changed line or total is refused before the service is asked.
- The token, checked with
POST /cfg/v1/quote/verifyand your secret key, is valid and already redeemed by a real order. - The order the browser names, looked up with
GET /cfg/v1/orders/{id}, has the same plan hash, quote hash and totals. - The token has not been used for a cart line before.
The cart line
Only then is one line added, with the verified price stored on the server side of the cart. Stock, tax, shipping and payment stay in WooCommerce.
The webhook
The plug-in also receives order.created and order.status_changed and verifies them as described in Webhooks.
More
The product page: WooCommerce plug-in. Setting it up in your shop: the WooCommerce help page.
There is no "try it" button here on purpose: the secret key belongs on your server, never in a browser. The demo shop shows the embed and the order hand-off working end to end.
LegalConfigurator terms ·Data processing agreement ·Shopper privacy notice ·Third-party licences