By payment rail
The agreement rides in the rail’s own field.
For each rail the published package supports, the field the ATR hash rides in, in the form that field can hold, with no new contract on any of them. Where a rail has no field for it, its page says what carries it instead. Source: lcp docs: rails (opens in a new tab) · Source: lcp docs: binding (opens in a new tab)
Chains
Settlement on a public ledger, read through a reader you supply.
- EVM chainsthe signed authorization’s nonce15 pairings
- TempoMPP’s attribution memo4 pairings
- Solanaone Memo instruction6 pairings
- Stellarthe seller’s muxed address2 pairings
- XRP Ledgerthe Payment’s InvoiceID3 pairings
- Hederathe signed transaction body’s memo4 pairings
- Algorandthe asset transfer’s note1 pairings
- Aptosthe challenge only1 pairings
- Cardanoa CIP-20 message1 pairings
- Casperthe CEP-3009 authorization’s nonce1 pairings
- Concordiumthe transfer’s memo1 pairings
- NEARthe NEP-141 transfer’s memo2 pairings
- Polkadot Asset Huba remark batched with the transfer1 pairings
- Starknetthe outside execution’s nonce1 pairings
- Suian unused Pure input1 pairings
- Tronthe TRC-20 transfer’s memo1 pairings
- TONthe Jetton transfer’s text comment1 pairings
- Stacksthe SIP-010 transfer’s memo1 pairings
- Lightningthe BOLT11 invoice4 pairings
Card networks and processors
Settlement off chain, through the network or the provider.
Every payment type in the package: where the ATR hash rides, and what each proves