Published 2026-09-09 by Ripplarity Inc, a Delaware corporation, doing business as Trilatic. It is preparing an application for certification as a Federal Independent Dispute Resolution (IDR) entity under 45 CFR 149.510; on certification it will decide out-of-network payment disputes as described below. This policy governs a separate class of dispute: disagreements that arise after an AI agent has completed a purchase on a person's behalf. No statute or network rule yet defines who resolves such disputes when they are not fraud. This document states the rules under which this entity resolves them, so that a merchant, an agent platform and a payer can agree in advance to be bound by them.
Canonical URL: https://trilatic.com/atdrp/v0.1. Machine-readable schemas and a reference implementation are proposed to the Agentic Commerce Protocol as the `dispute_resolution` extension. Questions: compliance@trilatic.com.
An agent-initiated transaction is a payment executed by a software agent under a signed authorization from a person: in AP2 terms, a Checkout Mandate and a Payment Mandate, closed by Checkout and Payment Receipts; in ACP terms, a completed checkout session and its Order.
This policy covers disputes inside an intact authorization chain:
A claim that no valid authorization exists -- the person never authorized the agent, or the mandate is forged or replayed -- is a fraud question. It is outside this policy and is directed to the card network or payment service provider. The neutral checks the chain before anything else and returns `authorization_chain_broken` if it does not bind.
A provider applying this policy must not be, and must not be controlled by, a party to the dispute, a payment network, a payment service provider settling the disputed payment, or the agent platform that executed the mandate. Revenue from any single class of party above a published threshold must be disclosed. This is the condition that lets merchants, platforms and issuers accept one another's chosen providers.
The neutral decides on the record the protocols already produce. No party is asked for anything the transaction did not generate:
| Artifact | Fields used |
|---|---|
| Checkout Mandate | `checkout_hash`, `iat`, `exp`, presence of the merchant-signed checkout |
| Payment Mandate | `transaction_id` (must equal `checkout_hash`), `payee.id`, `payment_amount`, `iat`, `exp`, `execution_date`, `risk_data` |
| Checkout Receipt | `status`, `reference` (must equal `checkout_hash`), `order_id` |
| Payment Receipt | `status`, `reference`, `payment_id`, processor and network confirmation ids, `iat` |
| Order | `status`, per-line ordered / current / fulfilled quantities, fulfilments, adjustments, estimated delivery |
| Instruction and confirmed cart | only if the agent platform retained them; never published |
The neutral will not weigh, and screens every submission for: the size or reputation of any party; dispute or chargeback history outside this record; and any reference to network monitoring programs or ratios. Every determination states that these were screened and excluded.
Applied per line, in this order; the first decisive finding controls and the rest are still recorded:
The rule is deterministic. Two providers given the same record reach the same outcome, and the reference implementation is published so that this can be checked.
Calendar days. A dispute may be opened within 120 days of the payment receipt. The neutral confirms the authorization chain, the window and the receipt status within 2 days; each party may submit within 5 days; a signed written determination issues within 10 days of eligibility.
The non-prevailing party pays the neutral's published per-resolution fee. Both parties pre-fund the fee through the agent platform or payment service provider; the prevailing party's fee is returned. The schedule is set by the provider and published in advance; it is not set by any regulator. No schedule is set under this policy.
Every determination names the parties and their roles, the checkout hash and payment id, the authorization-chain finding, the outcome and amount per line, the five considerations and how each weighed, the statement that prohibited considerations were excluded, the human signer of record and their credential, whether AI assistance was used in drafting, and a verification path. Determinations are sealed on an append-only hash chain and are verifiable by anyone at `/verify/` without an account, for as long as the entity exists.
A determination under this policy is signed by a named natural person holding a credential the entity publishes. Software may draft; a person decides and signs, and the record says which.
The entity publishes, at a minimum group size of eleven: dispute volume, median days to determination, uphold and overturn rates by ground, and its fee schedule.
This policy is versioned. A dispute is decided under the version in force when it was opened. Changes are announced on this page with their effective date.