Integra Lens Merch Shop: terms of sale

Version 1.2. Last updated: October 4, 2026. Effective October 4, 2026.

These terms of sale apply to every order placed at integralens.store. The seller is Integra Ledger, Inc. ("Integra",

"we"). By placing an order you agree to them. Each order records the SHA-256 of the version of these terms the buyer

accepted, so buyer and seller can both check what was agreed.

1. The goods

Every item is made to order and printed and shipped by our print-on-demand partner when the order is placed. We hold

no stock.

Colours on screen are close to, but not exactly, the printed result. Sizes follow the size chart on each product page.

Prices are in US dollars and do not include sales tax. Tax where it applies is shown at checkout before you pay.
Delivery is to addresses in the United States only, at a flat $4.99 per order.
A price shown on a product page holds until the date given with it, and in any case for the order you place.
Most orders are printed within 2 to 5 business days and then shipped; the delivery estimate is given at checkout.
Payment is taken at checkout, by the method shown there. Checkout is not open yet: until it opens, nothing can be

bought.

The LCP mark and the Integra Lens mark printed on an item are licensed only as part of that item: to wear, use,

display and give away the item itself.

Buying an item grants no right to reproduce, alter or resell the artwork apart from the item, and no right to use the

marks to suggest that Integra endorses any person, product or service.

A misprinted, damaged or lost item is replaced or refunded if reported within 30 days of delivery, with a photo where

the item arrived.

Because each item is made for the order, items are not returnable for a change of mind or of size.
Refunds go back to the original payment method within 10 business days of approval.

Our liability for an order is limited to the amount paid for it. Nothing in these terms limits a right you have by

law as a consumer.

We may change these terms for future orders. Each change takes a new version number and date, and an order is always

governed by the version it records.

SHA-256 of terms.md: 0x9e3a5c3e85095e32957b2215dc226f87b422ce3f929370564562a67d9deb6b03

1 · Discoverable	R1.2 product data in the served HTML · R3.2 admit self-identified agents
2 · Agreeable	R4.2–R4.5 terms · R7.2 legal name · R8.2 product identifier · R9.2–R9.4 price, tax basis, total. Needs Discoverable.
3 · Transactable	R2.2–R2.3 a checkout an agent completes without a browser. Needs Discoverable.
4 · Provable	R10.2–R10.3 an agreement record (ATR) per sale · R6.2 the buyer's payment signature covers its hash. Needs Agreeable and Transactable.

By hand	Stages 1 and 2 are static files and page markup. This shop does both; copy from the tabs.
Integra's appliance	Stage 4 for your own checkout: it issues the ATR and checks the payment (tab 4). Your checkout still needs an agent protocol for stage 3 (tab 3).
Integra Demo Studio	All four at once, on test networks: describe a shop and it is generated with every check in place. Use it to see a passing reference before you build.

R1.2	Can an agent read a product and its price without a browser? Fix: JSON-LD `Product` with an `Offer` on every product page, in the HTML as served, not injected by script.
R3.2	Does the site answer an agent that says what it is? Fix: serve clients that identify themselves in `User-Agent`; rate-limit them rather than challenge them with a CAPTCHA.

R4.2	Terms found and readable without a browser. Fix: serve them in the delivered HTML or as a file.
R4.3	The terms state their effective or last-changed date.
R4.4	Each version has an identifier and a stable URL.
R4.5	Byte-identical across fetches. Fix: a static file, no per-request content.
R7.2	The seller's legal entity, machine-readable. Fix: `Organization` with `legalName`.
R8.2	Each product carries an identifier an agreement can name: `sku`, or better a `gtin`.
R9.2–R9.4	`price` and `priceCurrency` on every offer; `priceSpecification.valueAddedTaxIncluded`; delivery cost in `shippingDetails`.

R2.2	Can an agent start a purchase without a browser? Cart links count, but an agent protocol (R2.3) is the real fix.
R2.3	Can it complete one? Fix: publish the UCP checkout capability, or ACP's discovery document.
R2.4	Next rung: accept a payment built for agents: x402, MPP or L402, or AP2 mandates through UCP.

UCP	checkout over REST (`/checkout-sessions`) and over MCP (`create_checkout` … `complete_checkout`)
x402	`/buy/<offer>` answers `402` with a payment challenge
A2A	an agent card at `/.well-known/agent-card.json`
MPP, AP2	the same checkout, paid with MPP's credential or AP2's mandates

R10.2	Each sale offers one agreement record (ATR) whose bytes hash to the value advertised with the payment request.
R10.3	The ATR contains the published terms' digest.
R6.2	The buyer's payment signature covers the ATR's hash. On x402 `exact` with EIP-3009, the hash is the authorization's `nonce`.

`POST /claim`	with the buyer's payment: checks it carries the hash of a record you issued
`POST /report`	paid or declined, with the transaction reference
`GET /status/<hash>`	the record's state, and what it proves