Payment rail

Stripe

Through Stripe, MPP’s challenge carries the ATR hash into the PaymentIntent’s metadata. Source: lcp docs: MPP⁠ (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: MPP⁠ (opens in a new tab) · lcp docs: the ATR⁠ (opens in a new tab) · lcp docs: the ATR hash⁠ (opens in a new tab)

Stripe

Example

Field: the PaymentIntent’s metadata

What the payer signs carries none of the ATR hash; where it rides instead is below.

This example’s ATR hash, as it rides

Where the ATR hash rides

On this rail, the ATR hash rides in the PaymentIntent’s metadata.

Exhibit Each field, and the pairings that use it

What a payment on this rail proves

Of these 2 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: Opaque Challenge (LCP §8.3.4)⁠ (opens in a new tab)
Where the ATR hash rides: The MPP request’s methodDetails.metadata.legal_context, which Stripe copies into the PaymentIntent. The buyer’s token signs nothing that carries H.
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 MPP challenge carried this ATR's hash in its id and its opaque reference, bound to the challenge by the seller's own server, and the buyer's credential echoed that challenge. The seller also placed the hash in the method's reference field (externalId for card; the PaymentIntent's metadata for Stripe). Nothing the buyer or its card or Stripe token signed carries the hash, and nothing the buyer signed was checked. Settlement is the seller's report. This record does not show that the buyer's approval carried the hash.
Pattern: Opaque Challenge (LCP §8.3.4)⁠ (opens in a new tab)
Where the ATR hash rides: The MPP request’s methodDetails.metadata.legal_context, which Stripe copies into the PaymentIntent. The buyer’s token signs nothing that carries H.
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 MPP challenge carried this ATR's hash in its id and its opaque reference, bound to the challenge by the seller's own server, and the buyer's credential echoed that challenge. The seller also placed the hash in the method's reference field (externalId for card; the PaymentIntent's metadata for Stripe). Nothing the buyer or its card or Stripe token signed carries the hash, and nothing the buyer signed was checked. Settlement is the seller's report. This record does not show that the buyer's approval carried the hash. The close is the seller's report.

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: MPP⁠ (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