A governed webhook contract for payment systems beyond native connectors.

Accept normalized payment and refund events from an authorized sender using signed requests, idempotency controls, replay protection, and a documented data contract.

Open product preview Compare connectors

Normalized contract

What Ardenti Pay records

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

Event identityUnique external event ID, event type, connection, received time and processing status

TransactionExternal transaction and parent IDs, charge or refund kind, status, amount and currency

Business contextCustomer reference, invoice number, description and account reference when lawfully supplied

Payment methodMethod type and last four digits only; raw payment credentials are prohibited

Integrity evidencePayload hash, signature verification result, idempotency state and processing error when applicable

Legal and operational boundaries

Responsibility stays where it belongs.

The sender represents that it is authorized to transmit the event and has a lawful basis for every personal-data field included.
The sender must not transmit full card numbers, security codes, passwords, authentication secrets, bank credentials or unnecessary sensitive data.
The originating processor or merchant system remains authoritative for authorization, settlement, refunds, disputes and chargebacks.
Delivery acknowledgement does not prove that funds settled or that an event was legally valid; downstream reconciliation remains required.
Secrets must be rotated after suspected compromise, and timestamp or replay controls should be enforced for every production sender.

Terminology

Terms used in this integration

HMAC signature: A keyed cryptographic digest used to verify that the request came from a holder of the connection secret and was not altered in transit.
Idempotency: Processing the same external event more than once without creating duplicate financial records.
Replay protection: Rejecting a validly signed request when it is stale or has already been processed.
Authoritative system: The processor or merchant platform whose records control the actual payment and settlement state.

Merchant compliance notice

Ardenti Pay provides integration infrastructure, not legal, tax, accounting, banking, or payment-network advice. Merchants and platform operators remain responsible for their agreements, disclosures, taxes, refund obligations, privacy duties, reconciliation, and compliance with laws and provider rules applicable to their business.

The Universal Webhook connector is an Ardenti Labs product and does not imply affiliation with any payment provider represented in a customer-supplied event.

Ardenti Pay + Universal Webhook

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