Payment rail

Aptos

On Aptos, the challenge carries the ATR hash; a standard transfer has no field for it. Source: lcp docs: rails⁠ (opens in a new tab)

Sources (1)

lcp docs: rails⁠ (opens in a new tab)

Where the ATR hash rides

On this rail, the ATR hash rides in the challenge only.

What a payment on this rail proves

Of these 1 pairings, 0 have the buyer’s signature cover the ATR hash, 0 leave a public proof of it, and 0 let anyone read it back from the chain alone. Source: lcp docs: pairings reference⁠ (opens in a new tab)

Switch to Technical to see each pairing, and the sentence its record states about what a payment through it proves.

The standard

x402/exact/aptosHTTP-layer advisoryBuyer signs H: noH on chain: noPublic proof: noRecoverable from chain: no
Pattern: HTTP-layer advisory (LCP §8.3.7)⁠ (opens in a new tab)
Where the ATR hash rides: The challenge only. No field of a standard Aptos transfer carries H; the seller ties the payment to H when it claims it for the request.
What a payment through it proves: Before this payment, the buyer signed and paid an agreement transaction carrying this ATR's hash on <network>, recorded in <transaction>. The ATR was assembled and written to the seller's storage before the challenge went out, and the challenge advertised its hash and link. The payer's signed Aptos transaction does not carry the hash. The seller tied the hash to this payment when it claimed it for this request, and identified the settlement as the payer's committed transaction by sender, sequence number and a digest of its transfer. This does not show that the buyer's approval carried the hash, or that amount, payee, asset or timing match the ATR's content.

Where a sentence names <network> and <transaction>, the pairing’s record fills them in: they name the agreement payment the buyer made first. Source: lcp docs: pairings reference⁠ (opens in a new tab) · Source: lcp docs: the agreement URL⁠ (opens in a new tab)

Reading the settlement

The package reads a payment’s settlement through a reader you supply: the endpoint, the credentials, the timeouts and the retries are yours. A reader that fails never makes a payment read as failed. Source: lcp docs: reading settlement⁠ (opens in a new tab)

Sources (1)

lcp docs: reading settlement⁠ (opens in a new tab)

The protocols that pay on it

x402

lcp docs: rails⁠ (opens in a new tab)