ardenti payby Ardenti Labs Connector marketplace

Merchant point of sale

Clover merchant activity, normalized across orders and tenders.

Connect an authorized Clover merchant and unify POS locations, orders, line items, tenders, payments, refunds, timestamps, and transaction references.

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 Clover merchant remains responsible for goods and services, pricing, taxes, receipts, refunds, employees and customer-facing policies.
  • Clover and the merchant’s acquiring relationship remain responsible for payment authorization, settlement, disputes and chargebacks.
  • Ardenti Pay requests only the merchant permissions needed for the disclosed integration functions.
  • Merchant and customer information must be collected, used and shared consistently with Ardenti Labs’ privacy disclosures and the merchant’s own notices.
  • Clover App Market distribution may require functional review, a privacy policy, terms of service and provider approval before production sale.

Terminology

Terms used in this integration

Merchant ID
The Clover identifier for the business whose resources are being accessed.
Tender
The provider object describing how an order or payment was satisfied.
App permission
A Clover configuration authorizing access to a category of merchant data or functionality.
Merchant-scoped token
An access credential limited to the Clover merchant that granted authorization.

Ardenti Pay + Clover

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