ardenti payby Ardenti Labs Connector marketplace

Self-hosted commerce

WooCommerce orders, translated from each store’s own environment.

Connect an HTTPS-enabled WooCommerce store using merchant-issued REST credentials and normalize orders, customers, line items, taxes, discounts, shipping totals, refunds, and status changes.

Normalized contract

What Ardenti Pay records

Provider-specific fields are translated into predictable commerce and payment objects without erasing their original source context.

Legal and operational boundaries

Responsibility stays where it belongs.

  • The store owner remains responsible for the WordPress installation, hosting, patches, plugins, backups and security of its own environment.
  • WooCommerce records commerce activity, but the configured payment gateway—not Ardenti Pay—processes and settles the underlying payment.
  • The merchant remains responsible for product claims, sales taxes, consumer disclosures, refund policies, privacy notices and data-retention decisions.
  • Consumer credentials must be rotated after suspected disclosure and revoked when the connection is no longer authorized.
  • Refund and order states are normalized from the store response and do not independently prove bank settlement.

Terminology

Terms used in this integration

Consumer Key
The public identifier for a WooCommerce REST API credential pair.
Consumer Secret
The confidential credential used with the Consumer Key to authenticate API requests.
Store administrator
The person or entity authorized to create API credentials and configure the WooCommerce installation.
Payment gateway
The separate service selected by the merchant to authorize, process and settle customer payments.

Ardenti Pay + WooCommerce

Every payment. One connection.

Bring provider activity into one governed integration layer while keeping the original merchant and transaction context intact.

Return to connector marketplace