Payment rail

Lightning

On Lightning, the invoice the seller’s node signs carries the ATR hash, or the ATR names the invoice. Source: lcp docs: rails⁠ (opens in a new tab) The Agentic Transaction Record (ATR) is one record of exactly what was agreed, for one transaction. Its ATR hash, the ATR’s fingerprint, is the proof bound to the transaction: change one byte of the ATR and it no longer matches. Source: lcp docs: the ATR⁠ (opens in a new tab) · Source: lcp docs: the ATR hash⁠ (opens in a new tab)

lcp docs: rails⁠ (opens in a new tab) · lcp docs: the ATR⁠ (opens in a new tab) · lcp docs: the ATR hash⁠ (opens in a new tab)

Lightning

Example

Field: the BOLT11 invoice

0x8448dc1b716a5103287cb8f35e36b614ffd91e630ab8b7911833c54748ad5ca6

The ATR hash itself, all 32 bytes.

This example’s ATR hash, as it rides

Where the ATR hash rides

On this rail, the ATR hash rides in the BOLT11 invoice.

Exhibit Each field, and the pairings that use it

The package

Lightning has no public settlement to read: the invoice and its preimage, which the parties hold, show that the invoice was paid, not who paid it, and no public ledger shows the payment. Source: lcp docs: rails⁠ (opens in a new tab)

The BOLT11 invoice’s m field, which the seller’s node signs. Source: lcp docs: rails⁠ (opens in a new tab)
x402/exact/lnbtc
Nothing in the invoice: the ATR’s x402 slot names the invoice instead. Source: lcp docs: rails⁠ (opens in a new tab)
x402/exact/lnbtc/invoice-named
The BOLT11 invoice’s description hash h, which the seller’s node signs. Source: lcp docs: rails⁠ (opens in a new tab)
mpp/charge/lightningmpp/session/lightning

Entry points: @integraledger/lcp/lightning

The data

Read from the published packages when the site was built; nothing here is typed by hand.

The ATR hash of the site’s example ATR, as this rail carries it

H’s 32 bytes, in the invoice the seller’s node signs

0x8448dc1b716a5103287cb8f35e36b614ffd91e630ab8b7911833c54748ad5ca6

Computed from the site’s example ATR by this rail’s own helper in the package, when the site was built.

What a payment on this rail proves

Of these 4 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.

lcp docs: pairings reference⁠ (opens in a new tab)

Exhibit Each pairing’s record

The package

Pattern: native-field, the package’s name for it
Where the ATR hash rides: The BOLT11 invoice’s m field, which the seller’s node signs.
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 seller's node's BOLT11 invoice has this ATR's hash as its payment metadata and x402's request hash as its description hash. Its signature is not verified here, and the payer signed nothing that carries the hash. Settlement is the seller's report; the invoice and its preimage, which the parties hold, show that the invoice was paid; they do not show who paid it, and no public ledger shows the payment. This does not show that amount, payee or timing match the ATR's content.
LCP profile: x402/exact/lnbtc⁠ (opens in a new tab)
Pattern: HTTP-layer advisory (LCP §8.3.7)⁠ (opens in a new tab)
Where the ATR hash rides: Nothing in the invoice: the ATR’s x402 slot names the invoice instead.
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 names this payment: its binding slot holds the payment option as issued, including the seller node's signed BOLT11 invoice, whose description hash is x402's request hash. The invoice does not carry this ATR's hash, and the payer signed nothing that does. Settlement is the seller's report; the invoice and its preimage, which the parties hold, show that the invoice was paid; they do not show who paid it, and no public ledger shows the payment. This does not show that amount, payee or timing match the ATR's content.
Pattern: native-field, the package’s name for it
Where the ATR hash rides: The BOLT11 invoice’s description hash h, which the seller’s node signs.
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 seller's node's BOLT11 invoice's description hash is this ATR's hash, and the ATR commits its payment hash. Its signature is not verified here, and the payer signed nothing that carries the hash. Settlement is the seller's report; the invoice and its preimage, which the parties hold, show that the invoice was paid; they do not show who paid it, and no public ledger shows the payment. This does not show that amount, payee or timing match the ATR's content.
LCP profile: mpp/charge⁠ (opens in a new tab)
Pattern: native-field, the package’s name for it
Where the ATR hash rides: The BOLT11 invoice’s description hash h, which the seller’s node signs.
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 seller's node's BOLT11 invoice's description hash is this ATR's hash, and the ATR commits its payment hash. Its signature is not verified here, and the payer signed nothing that carries the hash. Settlement is the seller's report; the invoice and its preimage, which the parties hold, show that the invoice was paid; they do not show who paid it, and no public ledger shows the payment. This does not show that amount, payee or timing match the ATR's content. The close is the seller's report.
LCP profile: mpp/charge⁠ (opens in a new tab)

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

This rail has no public settlement for the package to read.

The protocols that pay on it

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

Ready to see your own agreements proved?

Tell us what you sell, buy or carry, and we will show you where the agreement rides in it.

Integra Binder, hosted by Integra, does the seller’s side of each agreement and is free on test networks, with test-network USDC.

Talk to us