uniple checkout for WooCommerce

Description

uniple checkout for WooCommerce lets merchants accept JPYC, a Japanese yen stablecoin / electronic payment instrument (電子決済手段), through uniple’s hosted checkout.

Shoppers choose the uniple payment method in WooCommerce and are redirected to the uniple checkout page. uniple handles wallet connection and settlement, then returns the shopper to the WooCommerce order-received page. Payment confirmation is applied through a signed webhook, with a server-side session lookup fallback when the return page is reached before the webhook arrives.

Features:

• Redirect-only WooCommerce payment gateway.
• Classic checkout and Cart / Checkout Blocks support.
• High-Performance Order Storage (HPOS) compatibility.
• HMAC-SHA256 signed webhook verification.
• Atomic webhook idempotency lock and event history.
• Return URL order key verification and live lookup fallback.
• Masked API key and webhook secret fields in the WooCommerce admin.
• x402 / AI purchase product sync with per-product AI purchase target settings.
• Signed, read-only catalog endpoint with five-minute central synchronization.

This plugin is built for WooCommerce stores. It is not developed by, affiliated with, or endorsed by WooCommerce or Automattic.

How to obtain an API key

uniple checkout requires a merchant account with uniple. Apply for an account at:

https://forms.gle/b8kwVZeynA1ffV8j6

After your application is approved, uniple will issue your API key and webhook secret, which you enter in the plugin settings (WooCommerce → Settings → Payments → uniple checkout (JPYC)).

External services

This plugin connects to the uniple hosted checkout API. The default service endpoint is https://uniple.io; the settings screen also permits https://dev.uniple.io for test use.

The plugin exchanges data with uniple for checkout processing and
merchant-triggered product catalog synchronization:

• When a shopper places an order with the uniple payment method, the plugin sends POST /api/merchant/checkout/sessions to the configured uniple API base URL.
• The session creation request includes the order total as amountJpyc, the WooCommerce order ID as clientReferenceId, the order description / order number, the configured merchant label, a one-line item summary, the success URL, the cancel URL, and the webhook URL.
• The session creation request also includes the merchant API key in the Authorization header and a plugin User-Agent containing the plugin version, WordPress version, and WooCommerce version.
• When the shopper returns from hosted checkout before the webhook has completed the order, the plugin may send GET /api/merchant/checkout/sessions/{sessionId} to verify the session status. This request includes the uniple session ID, the merchant API key, and the same plugin User-Agent.
• When a merchant runs x402 product sync, manually or through a server-side schedule, the plugin sends PUT /api/merchant/products. It sends product or variation IDs, names, descriptions, image and product-page URLs, JPYC prices, tax labels, ordering, and active flags. It does not send customer or order data in this request.
• After a successful product push, the plugin sends PUT /api/merchant/catalog-sync to register the store’s signed catalog URL, platform, plugin version, five-minute interval, and a purpose-derived pull secret. The raw API key is not used as the stored pull credential.
• The settings screen may send GET /api/merchant/catalog-sync to show registration and last-run status. An authenticated rollback may send DELETE /api/merchant/catalog-sync.
• The product and catalog API requests include the merchant API key in the Authorization header and the same plugin User-Agent described above.
• Once registered, uniple periodically sends a signed GET request to /wp-json/uniple/v1/catalog. The plugin verifies the request locally and returns the same product fields as a complete catalog snapshot. Unsigned requests are rejected, and customer/order data is not returned.
• uniple sends payment webhooks back to the store at /wp-json/uniple/v1/webhook. The plugin verifies the webhook signature locally with the configured webhook secret.

The plugin does not send full billing addresses, shipping addresses, customer account details, card details, wallet private keys, or browser cookies to uniple.

Service documentation and legal terms:

• uniple: https://uniple.io/
• Terms of Service: https://uniple.io/terms/
• Privacy Policy: https://uniple.io/privacy/