Payment rail

Cardano

On Cardano, a CIP-20 message holds the ATR hash, committed by the signed body. 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 a CIP-20 message.

What a payment on this rail proves

Of these 1 pairings, 1 have the buyer’s signature cover the ATR hash, 1 leave a public proof of it, and 1 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/cardanoNative FieldBuyer signs H: yesH on chain: yesPublic proof: yesRecoverable from chain: yes
Pattern: Native Field (LCP §8.3.1)⁠ (opens in a new tab)
Where the ATR hash rides: A CIP-20 message (metadata label 674) holding H’s LCP string as two strings, lcp:sha256:0x and the 64 lowercase hex digits, which the signed body commits to through auxiliary_data_hash.
What a payment through it proves: The payer signed a Cardano transaction whose body commits, through its auxiliary_data_hash, to a CIP-20 message (label 674) carrying this ATR's hash. The ledger included the transaction as valid, at the stated depth; the rail allows a rollback of fewer than k blocks. The hash is in the transaction's metadata on chain. This does not show that amount, payee, asset or timing match the ATR's content.
LCP profile: x402/exact/cardano⁠ (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)