tersign 0.4.11 → 0.6.0

package/README.md

@@ -17,17 +17,26 @@
 
 ## Verify a Real Entry — Right Now
 
-No account. No API key. This is the genesis receipt, `seq 1` on the production chain:
+No account. No API key. This is the genesis receipt, `seq 1` on the production chain. It is a self-signed demo: Tersign signed it as seller and named its own key as payer, so its EIP-712 payload signature (domain `{name: "x402 receipt", version: "1", chainId: 1}`, per the x402 offer-and-receipt extension) recovers to the payload's own payer, `0x36f82906859E5B0bd076069f8cdfAea355358b14`. [`/v1/genesis`](https://tersign.ai/v1/genesis) serves the record with the recipe for each of its signatures.
 
 ```sh
 npx tersign verify 0xe5874f1ffe87f0a6dd9eb157730f67b86ee4538b125fe30fcc4e165213dd3fc4
 ```
 
 ```text
-ledger: counter-signed OK (seller tersign-first, seq 1 …) VALID
+ledger:    https://tersign.ai
+           reports: found, counter-signed chain intact (seller tersign-first, seq 1, …) — not checked locally
+VALID (ledger-reported) — https://tersign.ai reports the record and its counter-signed chain; nothing was verified locally
 ```
 
-`npx tersign verify <receipt.json | 0xdigest> [--ledger url]` recovers the EIP-712 signature **locally**. A bare digest is then checked against the Tersign ledger unless `--ledger` names another; a receipt file verifies offline and touches no chain at all. The ledger consulted is always printed. Prefer raw HTTP? The same proof, no CLI:
+`npx tersign verify <receipt.json | 0xdigest> [--signer 0xaddr] [--ledger url]` takes a receipt file or a digest.
+
+- A **receipt file** is checked locally and touches no network unless you add `--ledger`. The EIP-712 signature is recovered, and `--signer` compares it with the issuer's address, which you take from the issuer through a channel you trust, never from the receipt. Without `--signer` the signer is reported `UNAUTHENTICATED` and the verdict reads `VALID (signer UNAUTHENTICATED)`: recovery yields an address for any payload, so an edited receipt reaches that same line with a different address.
+- A receipt signed with a **published test key** (the 20 Hardhat/Anvil default dev-mnemonic accounts, or private key 1, 2 or 3) is flagged `published test key` either way: anyone can produce that signature. Fields in the file that the signature does not cover are listed by name, and a signed field in another JSON type (`"version": "1"`) is refused. The signature must be the one canonical encoding (`0x` + 130 lower-case hex digits, v 27/28, low-s): a re-encoding of a genuine signature (v 0/1, upper-case hex, the high-s twin) also recovers the issuer, under a different digest, so it is refused.
+- The file is a receipt, `{receipt, record}`, or an evidence-bundle record file (`records/NNNNNN.json`, verdict qualified `record artifact only`: its chain fields are not checked here). Anything else that nests a receipt — a second receipt at the top level, or any other field beside it — is refused, because a reader would take those fields for the receipt that was checked. Duplicate keys and non-integer numbers are refused too.
+- A **digest** is looked up on the Tersign ledger unless `--ledger` names another; the answer is that ledger's own counter-signed chain check, nothing in it is re-verified locally, and the verdict says so (`VALID (ledger-reported)`). The ledger consulted is always printed. The local check is the receipt file with `--signer`.
+
+Exit status: `0` valid (read the last line — for a file, a bare `VALID` means a bound, non-test-key signer on a receipt or `{receipt, record}`; a digest is always `VALID (ledger-reported)`), `1` invalid, `2` usage (an unknown or valueless flag, `--signer` with a digest, a missing or non-JSON file). Prefer raw HTTP? The same proof, no CLI:
 
 ```sh
 curl https://tersign.ai/v1/receipts/0xe5874f1ffe87f0a6dd9eb157730f67b86ee4538b125fe30fcc4e165213dd3fc4/verify
@@ -41,7 +50,7 @@ Counter-signed evidence that your agent presented a disclosure — one command,
 npx tersign disclose "You are chatting with an AI assistant." --medium chat --agent-id my-agent
 ```
 
-The text is digested **locally** (only the digest travels — data-minimization by construction). Your key signs the record; the ledger counter-signs it into a per-signer hash chain whose head is submitted for Bitcoin anchoring on a six-hourly cron. First call self-provisions a free signer-keyed account bound set-once to your key (key resolution: `TERSIGN_SELLER_KEY` env → macOS keychain `tersign-signer` → `~/.tersign/signer.key`, created on first use). Free tier is quota- and rate-limited — [limits](https://tersign.ai/pricing). What this is: independently verifiable evidence the disclosure was attested at that time. What it is not: a compliance certification.
+The text is digested **locally** (only the digest travels — data-minimization by construction). Your key signs the record; the ledger counter-signs it into a per-signer hash chain whose head is submitted for Bitcoin anchoring on a six-hourly cron. The first call self-provisions a free signer-keyed account bound set-once to your key, unless that key is already registered to an API-key ledger account (409: submit through that account) or the day's provisioning caps are reached (429). Key resolution: `TERSIGN_SELLER_KEY` env → macOS keychain `tersign-signer` → `~/.tersign/signer.key`, created on first use. Free tier is quota- and rate-limited — [limits](https://tersign.ai/pricing). What this is: independently verifiable evidence the disclosure was attested at that time. What it is not: a compliance certification.
 
 ## Chain of Custody
 
@@ -60,7 +69,7 @@ graph LR
 
 <sub>Diagram renders on GitHub. On npm, the paragraph above IS the diagram.</sub>
 
-Refunds chain back to the original receipt via `refundOf`. Disputes attach to the digest with objective reason codes. Party statements are structurally segregated behind an `UNVERIFIED` marker — the evidence stays prompt-injection-hardened.
+A refund record references the record it corrects by digest (`refundOf`). Disputes attach to the digest with objective reason codes. Party statements are structurally segregated behind an `UNVERIFIED` marker — the evidence stays prompt-injection-hardened.
 
 ## Enter the Record
 
@@ -68,15 +77,28 @@ Refunds chain back to the original receipt via `refundOf`. Disputes attach to th
 npm i tersign
 ```
 
-`withAssure()` wraps your x402 fetch handler so every paid call issues a signed, chained receipt. The full register:
+`withAssure()` wraps your x402 fetch handler. On a settled call it signs a receipt and a compliance-fields record with your key and merges both into the `PAYMENT-RESPONSE` header, the base64 JSON settlement response x402 wallets already read; the response body is left alone. When it cannot issue them (a settlement network that is neither CAIP-2 nor a v1 name in its table, such as `"bsc"`, or a ledger error), the paid response goes out exactly as your handler returned it, with no receipt, and the error goes to `onError` (default: `console.error`); with idempotency on, a retry with the same payment id replays that response. On a 402 it adds `compliance-fields` to the `PAYMENT-REQUIRED` header. When the `Assure` is built with a ledger, the ledger counter-signs the receipt into your chain; the compliance-fields record is not counter-signed, and is bound to its receipt only by your own signature, which covers the receipt's digest. Without a ledger, both carry your signature alone.
+
+```ts
+import { privateKeyToAccount } from 'viem/accounts';
+import { Assure, withAssure } from 'tersign';
+
+const signer = privateKeyToAccount(process.env.TERSIGN_SELLER_KEY as `0x${string}`);
+const assure = new Assure({ signer, issuer: { name: 'Example API Ltd', jurisdiction: 'HK' } });
+export default { fetch: withAssure(app.fetch, { assure }) }; // app: your x402-protected Hono app
+```
+
+A wallet finds the receipt at `extensions["offer-receipt"].info.receipt` and the record at `extensions["compliance-fields"].info.record` of the decoded `PAYMENT-RESPONSE` (`X-PAYMENT-RESPONSE` on x402 v1). Sellers whose readers still parse the JSON body can pass `legacyBodyPlacement: true` for one more minor release.
+
+The full register:
 
 | Capability | In the record |
 |---|---|
 | Receipts | Seller-signed EIP-712 (x402 offer-receipt extension), keccak256 canonical digests |
-| `withAssure()` | x402 fetch-handler adapter — a receipt per paid call |
-| Compliance exports | EU Art-226b minimal tier · EN 16931 full tier · HK IRO s.51C retention |
+| `withAssure()` | x402 fetch-handler adapter — receipt + compliance-fields record in `PAYMENT-RESPONSE` on each paid call it can issue for, the paid response passed through unchanged when it cannot; `compliance-fields` advertised on 402 |
+| Compliance-fields records | MINIMAL tier (Art 226b simplified-invoice content) via `buildMinimalRecord` · ledger exports `format=art226b` · `format=s51c` — mappings, not certifications |
 | Action records | `ActionRecordV1` — GDPR-minimized; captures the content of an Art-50 disclosure so the disclosure itself is independently attested, not self-reported |
-| Refunds | Chained to the original receipt via `refundOf` |
+| Refunds | A refund record carries `refundOf`, the digest of the record it corrects · `record_refund` logs a pending refund entry on the ledger (not counter-signed) |
 | Disputes v0 | Objective reason codes, evidence submission, adjudication |
 | Venue envelopes | Internet Court (5,000-char slot) · Kleros ERC-1497 · UMA · generic |
 | Evidence packs | `format=art50` · `format=safr` (beta) |
@@ -112,25 +134,27 @@ when that stabilizes. It makes no conformance claim to that draft.
   "mcpServers": {
     "tersign": {
       "command": "npx",
-      "args": ["tersign"],
-      "env": { "TERSIGN_SELLER_KEY": "0x<your-seller-key>" }
+      "args": ["tersign"]
     }
   }
 }
 ```
 
+No configuration is needed. With `TERSIGN_SELLER_KEY` unset or empty, the server signs with the key in the macOS keychain (`tersign-signer`) or `~/.tersign/signer.key`, and generates one there on first run; the key never leaves your machine. Set `TERSIGN_SELLER_KEY` only to bring your own.
+
 **Tools** — `issue_receipt` · `verify_receipt` · `verify_compliance_record` · `record_disclosure` · `record_refund` · `open_dispute` · `submit_dispute_evidence` · `adjudicate_dispute` · `get_dispute`
 
 | Env var | Required | Purpose |
 |---|---|---|
-| `TERSIGN_SELLER_KEY` | yes | 0x-prefixed private key that signs your receipts and records |
-| `TERSIGN_LEDGER_URL` | no | hosted ledger for counter-signing + chain checks |
-| `TERSIGN_LEDGER_API_KEY` | no | your seller API key on that ledger |
-| `TERSIGN_LEDGER_SELLER_ID` | no | your seller id on that ledger |
+| `TERSIGN_SELLER_KEY` | no | your own 0x-prefixed signing key; unset or empty, the keychain or keyfile key is used (generated on first run). If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key |
+| `TERSIGN_LEDGER_URL` | no | ledger for counter-signing + chain checks; needed by the dispute tools; `record_disclosure` defaults to `https://tersign.ai` |
+| `TERSIGN_LEDGER_API_KEY` | no | your seller API key on that ledger; with the seller id, enables `record_refund` and chained `issue_receipt`; also authenticates respondent dispute evidence |
+| `TERSIGN_LEDGER_SELLER_ID` | no | your seller id on that ledger; with the API key, enables `record_refund` and chained `issue_receipt` |
 | `TERSIGN_ISSUER_NAME` | no | issuer name stamped on action records |
 | `TERSIGN_ISSUER_JURISDICTION` | no | issuer jurisdiction stamped on action records |
+| `TERSIGN_ISSUER_TAX_ID` | no | issuer tax / business-registration id stamped on action records |
 
-Cold to counter-signed in one session: call `issue_receipt`, then check the issued receipt's digest with `npx tersign verify <digest> --ledger <url>`.
+Cold to counter-signed in one session, with no configuration: call `record_disclosure`, then check the `digest` it returns with `npx tersign verify <digest>` (a bare digest checks against https://tersign.ai). `issue_receipt` counter-signs as well once `TERSIGN_LEDGER_URL`, `TERSIGN_LEDGER_API_KEY` and `TERSIGN_LEDGER_SELLER_ID` are set; without them it returns a locally signed, unchained receipt.
 
 The agent skill `tersign-evidence` ships at [tersignhq/skills](https://github.com/tersignhq/skills).
 
@@ -148,7 +172,7 @@ Full URLs, readable without auth. If you are an agent, start here.
 | Surface | Address |
 |---|---|
 | npm package | `tersign` — https://www.npmjs.com/package/tersign |
-| MCP registry | `io.github.tersignhq/evidence` — `npx tersign` needs no configuration; the first call self-provisions a signer-keyed account |
+| MCP registry | `io.github.tersignhq/evidence` — `npx tersign` needs no configuration; `record_disclosure`'s first call self-provisions a signer-keyed account, unless the key is registered to an API-key account (409) or the daily provisioning caps are reached (429) |
 | ARD catalog (Agentic Resource Discovery) | https://tersign.ai/.well-known/ai-catalog.json |
 | Verify API | `GET https://tersign.ai/v1/receipts/{digest}/verify` |
 | Envelope API | `GET https://tersign.ai/v1/receipts/{digest}/envelope?venue={internet-court\|kleros\|uma\|generic}` |
@@ -156,8 +180,8 @@ Full URLs, readable without auth. If you are an agent, start here.
 | Ledger signer | `GET https://tersign.ai/v1/ledger` |
 | Bundle verifier, out-of-band | https://tersign.ai/verify/v1/ — `verify_bundle.py` · `keccak.py` · `secp256k1.py` · `SHA256SUMS`. A bundle ships its own checker; for evidence from an interested party fetch this copy and diff the two. |
 | llms.txt | https://raw.githubusercontent.com/tersignhq/tersign-js/main/llms.txt |
-| Conformance vectors (RFC 8785 + keccak256) | https://github.com/tersignhq/tersign-js/blob/main/test/fixtures/canonical-vectors.json |
-| Sample action record + digests | https://github.com/tersignhq/tersign-js/blob/main/test/fixtures/compliance-record.json |
+| Conformance vectors (RFC 8785 + keccak256, two-sided) | https://github.com/tersignhq/evidence-record-conformance |
+| Sample compliance-fields record + digests | https://github.com/tersignhq/tersign-js/blob/main/test/fixtures/compliance-record.json |
 | Genesis verify | `npx tersign verify 0xe5874f1ffe87f0a6dd9eb157730f67b86ee4538b125fe30fcc4e165213dd3fc4` |
 
 ---
@@ -189,7 +213,7 @@ If a maintainer ever asks you to reopen work elsewhere because of this, that is
   <img src="https://raw.githubusercontent.com/tersignhq/.github/main/assets/seal.svg" alt="Tersign seal" width="72">
 </p>
 
-<p align="center"><sub>MIT · built and published from <a href="https://github.com/tersignhq/tersign-js">tersignhq/tersign-js</a> via trusted-publishing CI, provenance attested · <code>tersign</code> reserved on PyPI</sub></p>
+<p align="center"><sub>MIT · built and published from <a href="https://github.com/tersignhq/tersign-js">tersignhq/tersign-js</a> via trusted-publishing CI, provenance attested · Python verifier: <code>pip install tersign</code></sub></p>
 
 <p align="center"><sub><b>Venues rotate. The transcript endures.</b></sub></p>
 

package/dist/adapter/x402.d.ts

@@ -6,8 +6,42 @@ export interface SettlementInfo {
     network?: string | undefined;
     payer?: string | undefined;
 }
+/** Encode a JSON value the way an x402 HTTP header carries it (base64 over UTF-8 JSON). */
+export declare function encodeX402Header(value: unknown): string;
+/** Decode an x402 HTTP header value; `undefined` when it is not base64 over UTF-8 JSON. */
+export declare function decodeX402Header(value: string): unknown;
 export declare function extractPaymentPayload(headers: Headers): unknown;
 export declare function extractSettlement(headers: Headers): SettlementInfo | undefined;
+/** What a 402 advertises under `extensions["compliance-fields"].info`. Each member is a claim
+ * about the records this server emits, so set one only when it is true of every record:
+ * `tiers: ['minimal']` needs every record to carry each MINIMAL member, including `tax.amount`
+ * whenever `tax.scheme` is not `none`. The default advertises the extension with no tier or
+ * jurisdiction claim. */
+export interface ComplianceAdvertisement {
+    tiers?: ReadonlyArray<'minimal' | 'full'>;
+    jurisdictions?: ReadonlyArray<string>;
+}
+/** JSON Schema for the advertised `info` (the core v2 spec makes `schema` a required member of
+ * every PaymentRequired extension entry). */
+export declare const COMPLIANCE_FIELDS_ADVERTISEMENT_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly type: "object";
+    readonly properties: {
+        readonly tiers: {
+            readonly type: "array";
+            readonly items: {
+                readonly type: "string";
+                readonly enum: readonly ["minimal", "full"];
+            };
+        };
+        readonly jurisdictions: {
+            readonly type: "array";
+            readonly items: {
+                readonly type: "string";
+            };
+        };
+    };
+};
 export interface WithAssureConfig {
     assure: Assure;
     /** describe the supply for the receipt; defaults to the request path */
@@ -20,10 +54,32 @@ export interface WithAssureConfig {
         required: boolean;
         scope: string;
     };
+    /** Advertise `compliance-fields` in a 402's `PAYMENT-REQUIRED` header (x402 v2). Default: on,
+     * with an empty claim set. `false` leaves 402 responses untouched. An entry the handler
+     * already put there is kept as it is. */
+    advertise?: false | ComplianceAdvertisement;
+    /** @deprecated Also decorate a JSON response BODY with the receipt and record (the ≤0.5
+     * placement). The `PAYMENT-RESPONSE` header carries them either way. Scheduled for removal in
+     * the next minor release after the one that introduced header placement. A body that does not
+     * parse as a JSON object is left as it is. */
+    legacyBodyPlacement?: boolean;
+    /** Called when a settled call's receipt cannot be issued: a settlement network that is neither
+     * CAIP-2 nor in the v1 table (`toCaip2Network`), a ledger error, a throwing `toSettlementContext`
+     * or `describeSupply`. The paid response then goes out exactly as the handler returned it, with
+     * no receipt or record in it. Default: one `console.error` line per failure. An error thrown by
+     * this callback, or a rejection of a promise it returns, is ignored. */
+    onError?: (err: unknown) => void;
 }
 type FetchHandler = (req: Request) => Response | Promise<Response>;
-/** Wrap an x402-protected handler: enforce idempotency on the way in, issue the signed
- * receipt + compliance record on the way out (only when the settlement header reports
- * success and the response body is JSON). */
+/** Wrap an x402-protected handler: enforce idempotency on the way in; on the way out, advertise
+ * `compliance-fields` on a 402, and — when the settlement header reports success — issue the
+ * signed receipt + compliance-fields record and merge both into that same settlement header
+ * (`PAYMENT-RESPONSE`, or `X-PAYMENT-RESPONSE` for v1), where x402 wallets read them. The
+ * response body is left untouched unless `legacyBodyPlacement` is set.
+ *
+ * Once the settlement header reports success the buyer has paid, so a failure to issue does not
+ * throw: the response goes out exactly as the handler returned it, the error goes to `onError`,
+ * and with idempotency on the payment id is completed with that delivered response, so a retry
+ * replays it instead of finding the id stuck in flight. */
 export declare function withAssure(handler: FetchHandler, cfg: WithAssureConfig): FetchHandler;
 export {};

package/dist/adapter/x402.js

@@ -1,22 +1,57 @@
-import { attachToExtensions } from '../assure.js';
+import { attachToExtensions, attachToSettlementResponse } from '../assure.js';
 import { checkIdempotency, extractPaymentId, fingerprint, REPLAY_HEADER, } from '../idempotency/middleware.js';
 /** Adapter for x402-protected fetch-style handlers ((Request) => Response) — this is the
  * shape of a Hono app (`app.fetch`), a Workers export, and Next.js route handlers, so one
  * wrapper covers the common seller stacks. An adapter pinned to the official x402 SDK's
  * middleware internals is deliberately deferred until we integrate against a pinned
  * version (its surface is still churning); this wrapper only touches the WIRE contract:
- * the payment payload request header and the settlement response header. */
-/** x402 v2 header names, with v1 fallbacks. Re-verify at integration (CLAUDE.md rule 1). */
+ * the payment payload request header, the payment-required header and the settlement
+ * response header. */
+/** x402 HTTP transport headers, v2 names first with v1 fallbacks. Verified 2026-09-29 against
+ * x402-foundation/x402 specs/transports-v2/http.md (main 5eee1e3c35): `PAYMENT-REQUIRED`
+ * (server → client, PaymentRequired), `PAYMENT-SIGNATURE` (client → server, PaymentPayload),
+ * `PAYMENT-RESPONSE` (server → client, SettlementResponse), each base64 over UTF-8 JSON; "All
+ * x402 protocol information is communicated through headers". Re-verify at integration
+ * (CLAUDE.md rule 1). */
 const PAYMENT_PAYLOAD_HEADERS = ['payment-signature', 'x-payment'];
 const SETTLEMENT_HEADERS = ['payment-response', 'x-payment-response'];
+const PAYMENT_REQUIRED_HEADER = 'payment-required';
+/** base64 → UTF-8 text, as the upstream reference decodes (`safeBase64Decode`), so a record
+ * carrying a non-ASCII issuer name or supply description survives the header round trip. Unlike
+ * the reference, invalid UTF-8 is refused rather than replaced with U+FFFD: a header this
+ * wrapper rewrites must decode exactly, or it is left alone. */
+function b64decodeUtf8(value) {
+    const binary = atob(value);
+    const bytes = new Uint8Array(binary.length);
+    for (let i = 0; i < binary.length; i++)
+        bytes[i] = binary.charCodeAt(i);
+    return new TextDecoder('utf-8', { fatal: true }).decode(bytes);
+}
+/** UTF-8 text → base64, as the upstream reference encodes (`safeBase64Encode`). Plain `btoa`
+ * throws on any character above U+00FF. */
+function b64encodeUtf8(text) {
+    const bytes = new TextEncoder().encode(text);
+    let binary = '';
+    for (const b of bytes)
+        binary += String.fromCharCode(b);
+    return btoa(binary);
+}
 function b64json(value) {
     try {
-        return JSON.parse(atob(value));
+        return JSON.parse(b64decodeUtf8(value));
     }
     catch {
         return undefined;
     }
 }
+/** Encode a JSON value the way an x402 HTTP header carries it (base64 over UTF-8 JSON). */
+export function encodeX402Header(value) {
+    return b64encodeUtf8(JSON.stringify(value));
+}
+/** Decode an x402 HTTP header value; `undefined` when it is not base64 over UTF-8 JSON. */
+export function decodeX402Header(value) {
+    return b64json(value);
+}
 export function extractPaymentPayload(headers) {
     for (const name of PAYMENT_PAYLOAD_HEADERS) {
         const raw = headers.get(name);
@@ -25,29 +60,105 @@ export function extractPaymentPayload(headers) {
     }
     return undefined;
 }
-export function extractSettlement(headers) {
+function findSettlement(headers) {
     for (const name of SETTLEMENT_HEADERS) {
         const raw = headers.get(name);
         if (!raw)
             continue;
         const parsed = b64json(raw);
-        if (!parsed || typeof parsed !== 'object')
+        if (!isPlainRecord(parsed))
             continue;
-        return {
-            success: parsed.success === true,
-            transaction: str(parsed.transaction) ?? str(parsed.txHash),
-            network: str(parsed.network) ?? str(parsed.networkId),
-            payer: str(parsed.payer) ?? str(parsed.from),
-        };
+        return { name, response: parsed };
     }
     return undefined;
 }
+export function extractSettlement(headers) {
+    const found = findSettlement(headers);
+    return found ? settlementInfo(found.response) : undefined;
+}
+function settlementInfo(parsed) {
+    return {
+        success: parsed.success === true,
+        transaction: str(parsed.transaction) ?? str(parsed.txHash),
+        network: str(parsed.network) ?? str(parsed.networkId),
+        payer: str(parsed.payer) ?? str(parsed.from),
+    };
+}
 function str(v) {
     return typeof v === 'string' && v.length > 0 ? v : undefined;
 }
-/** Wrap an x402-protected handler: enforce idempotency on the way in, issue the signed
- * receipt + compliance record on the way out (only when the settlement header reports
- * success and the response body is JSON). */
+function isPlainRecord(v) {
+    return typeof v === 'object' && v !== null && !Array.isArray(v);
+}
+/** JSON Schema for the advertised `info` (the core v2 spec makes `schema` a required member of
+ * every PaymentRequired extension entry). */
+export const COMPLIANCE_FIELDS_ADVERTISEMENT_SCHEMA = {
+    $schema: 'https://json-schema.org/draft/2020-12/schema',
+    type: 'object',
+    properties: {
+        tiers: { type: 'array', items: { type: 'string', enum: ['minimal', 'full'] } },
+        jurisdictions: { type: 'array', items: { type: 'string' } },
+    },
+};
+function reportIssueError(err) {
+    let message;
+    try {
+        message = String(err instanceof Error ? err.message : err);
+    }
+    catch {
+        message = 'unprintable error';
+    }
+    console.error(`tersign withAssure: receipt not issued, response delivered unchanged: ${message.replace(/\s+/g, ' ')}`);
+}
+/** The legacy body placement reads a clone, so a body that is not a JSON object stays readable
+ * and goes out as it came. */
+async function jsonObjectBody(res) {
+    try {
+        const parsed = await res.clone().json();
+        return isPlainRecord(parsed) ? parsed : undefined;
+    }
+    catch {
+        return undefined;
+    }
+}
+function withHeaders(res, headers, body = res.body) {
+    return new Response(body, { status: res.status, statusText: res.statusText, headers });
+}
+function advertiseCompliance(res, adv) {
+    if (res.status !== 402)
+        return res;
+    const raw = res.headers.get(PAYMENT_REQUIRED_HEADER);
+    if (!raw)
+        return res;
+    const required = b64json(raw);
+    if (!isPlainRecord(required))
+        return res;
+    const prior = isPlainRecord(required.extensions) ? required.extensions : {};
+    if (prior['compliance-fields'] !== undefined)
+        return res;
+    const info = {};
+    if (adv.tiers !== undefined)
+        info.tiers = [...adv.tiers];
+    if (adv.jurisdictions !== undefined)
+        info.jurisdictions = [...adv.jurisdictions];
+    const decorated = {
+        ...required,
+        extensions: { ...prior, 'compliance-fields': { info, schema: COMPLIANCE_FIELDS_ADVERTISEMENT_SCHEMA } },
+    };
+    const headers = new Headers(res.headers);
+    headers.set(PAYMENT_REQUIRED_HEADER, encodeX402Header(decorated));
+    return withHeaders(res, headers);
+}
+/** Wrap an x402-protected handler: enforce idempotency on the way in; on the way out, advertise
+ * `compliance-fields` on a 402, and — when the settlement header reports success — issue the
+ * signed receipt + compliance-fields record and merge both into that same settlement header
+ * (`PAYMENT-RESPONSE`, or `X-PAYMENT-RESPONSE` for v1), where x402 wallets read them. The
+ * response body is left untouched unless `legacyBodyPlacement` is set.
+ *
+ * Once the settlement header reports success the buyer has paid, so a failure to issue does not
+ * throw: the response goes out exactly as the handler returned it, the error goes to `onError`,
+ * and with idempotency on the payment id is completed with that delivered response, so a retry
+ * replays it instead of finding the id stuck in flight. */
 export function withAssure(handler, cfg) {
     const now = cfg.clock ?? (() => Math.floor(Date.now() / 1000));
     return async (req) => {
@@ -74,25 +185,48 @@ export function withAssure(handler, cfg) {
             }
         }
         let res = await handler(req);
-        const settlement = extractSettlement(res.headers);
-        if (settlement?.success && (res.headers.get('content-type') ?? '').includes('application/json')) {
-            const url = new URL(req.url);
-            const overrides = cfg.toSettlementContext?.(req, settlement) ?? {};
-            const ctx = {
-                network: settlement.network ?? 'eip155:8453',
-                resourceUrl: url.origin + url.pathname,
-                payer: settlement.payer ?? 'unknown',
-                settledAt: now(),
-                supplyDescription: cfg.describeSupply?.(req) ?? url.pathname,
-                ...(settlement.transaction !== undefined ? { txHash: settlement.transaction } : {}),
-                ...overrides,
-            };
-            const issued = await cfg.assure.issueFor(ctx);
-            const body = (await res.json());
-            const decorated = attachToExtensions(body, issued);
-            const headers = new Headers(res.headers);
-            headers.delete('content-length');
-            res = new Response(JSON.stringify(decorated), { status: res.status, headers });
+        if (cfg.advertise !== false)
+            res = advertiseCompliance(res, cfg.advertise ?? {});
+        const found = findSettlement(res.headers);
+        const settlement = found ? settlementInfo(found.response) : undefined;
+        if (found && settlement?.success) {
+            // Paid: nothing from here may cost the buyer the response. On any failure `res` stays the
+            // handler's own, and the idempotency entry below is completed with it.
+            try {
+                const url = new URL(req.url);
+                const overrides = cfg.toSettlementContext?.(req, settlement) ?? {};
+                const ctx = {
+                    network: settlement.network ?? 'eip155:8453',
+                    resourceUrl: url.origin + url.pathname,
+                    payer: settlement.payer ?? 'unknown',
+                    settledAt: now(),
+                    supplyDescription: cfg.describeSupply?.(req) ?? url.pathname,
+                    ...(settlement.transaction !== undefined ? { txHash: settlement.transaction } : {}),
+                    ...overrides,
+                };
+                const issued = await cfg.assure.issueFor(ctx);
+                const headers = new Headers(res.headers);
+                headers.set(found.name, encodeX402Header(attachToSettlementResponse(found.response, issued)));
+                const body = cfg.legacyBodyPlacement && (res.headers.get('content-type') ?? '').includes('application/json')
+                    ? await jsonObjectBody(res)
+                    : undefined;
+                if (body) {
+                    headers.delete('content-length');
+                    res = withHeaders(res, headers, JSON.stringify(attachToExtensions(body, issued)));
+                }
+                else {
+                    res = withHeaders(res, headers);
+                }
+            }
+            catch (err) {
+                try {
+                    // An async reporter's rejection is caught too: left unhandled it would end the process.
+                    void Promise.resolve((cfg.onError ?? reportIssueError)(err)).catch(() => { });
+                }
+                catch {
+                    // a throwing reporter must not cost the paid response either
+                }
+            }
         }
         if (onComplete) {
             const body = await res.clone().text();

package/dist/assure.d.ts

@@ -9,7 +9,8 @@ export interface AssureConfig {
     ledger?: LedgerConfig;
 }
 export interface SettlementContext {
-    /** CAIP-2 */
+    /** CAIP-2 (`"eip155:8453"`), or an x402 v1 name (`"base"`), which the receipt payload carries as
+     * CAIP-2; an unknown name throws. */
     network: string;
     resourceUrl: string;
     payer: string;
@@ -30,18 +31,79 @@ export interface IssuedReceipt {
     compliance: SignedComplianceRecord;
     ledger?: CountersignResult;
 }
-/** The core primitive: after a settled x402 payment, issue the signed base receipt
- * (merged offer-receipt extension, EIP-712) plus the Tersign compliance record bound to it,
- * and counter-sign into the hosted ledger when configured. Attach the result to the
- * SettlementResponse via `attachToExtensions`. */
+/** The core primitive: after a settled x402 payment, issue the seller-signed receipt
+ * (offer-receipt extension, EIP-712) and the Tersign compliance record. With a ledger configured,
+ * the ledger counter-signs the receipt into the seller's hash chain; the compliance-fields record is not
+ * counter-signed, and is bound to its receipt only by the seller's own signature, which covers the
+ * receipt's digest. Merge the result into the x402 SettlementResponse (the `PAYMENT-RESPONSE`
+ * header) with `attachToSettlementResponse`; `withAssure` does this for you. */
 export declare class Assure {
     private cfg;
     private ledger?;
     constructor(cfg: AssureConfig);
     issueFor(ctx: SettlementContext): Promise<IssuedReceipt>;
 }
-/** Decorate an x402 SettlementResponse body with the receipt at the spec-defined placement
- * (`extensions["offer-receipt"].info.receipt`) and the Tersign record alongside it. */
+/** JSON Schema for `extensions["offer-receipt"]` on a SettlementResponse — the same shape the
+ * upstream reference server attaches (x402-foundation/x402 typescript/packages/extensions/src/
+ * offer-receipt/server.ts RECEIPT_SCHEMA, main 5eee1e3c35, read 2026-09-29). */
+export declare const OFFER_RECEIPT_RESPONSE_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly type: "object";
+    readonly properties: {
+        readonly receipt: {
+            readonly type: "object";
+            readonly properties: {
+                readonly format: {
+                    readonly type: "string";
+                };
+                readonly payload: {
+                    readonly type: "object";
+                    readonly properties: {
+                        readonly version: {
+                            readonly type: "integer";
+                        };
+                        readonly network: {
+                            readonly type: "string";
+                        };
+                        readonly resourceUrl: {
+                            readonly type: "string";
+                        };
+                        readonly payer: {
+                            readonly type: "string";
+                        };
+                        readonly issuedAt: {
+                            readonly type: "integer";
+                        };
+                        readonly transaction: {
+                            readonly type: "string";
+                        };
+                    };
+                    readonly required: readonly ["version", "network", "resourceUrl", "payer", "issuedAt"];
+                };
+                readonly signature: {
+                    readonly type: "string";
+                };
+            };
+            readonly required: readonly ["format", "signature"];
+        };
+    };
+    readonly required: readonly ["receipt"];
+};
+/** Merge the receipt and the compliance record into an x402 `SettlementResponse` — the object
+ * the HTTP transport carries, base64-encoded, in the `PAYMENT-RESPONSE` header. The receipt goes
+ * to `extensions["offer-receipt"].info.receipt` (offer-receipt spec §5.1, same for v1 and v2)
+ * with its schema; the record and its attestation to `extensions["compliance-fields"].info`
+ * (placement proposed in x402-foundation/x402#2853, open). Every other member of the settlement
+ * response, and every other extension, is kept; an `offer-receipt` entry already present is
+ * replaced, because the record binds to THIS receipt's digest. */
+export declare function attachToSettlementResponse<T extends Record<string, unknown>>(settlement: T, issued: IssuedReceipt): T & {
+    extensions: Record<string, unknown>;
+};
+/** LEGACY: decorate the resource's JSON response BODY with the same extension entries. The x402
+ * v2 HTTP transport carries protocol data in headers only ("Response bodies are a server
+ * implementation concern"), so a wallet reading `PAYMENT-RESPONSE` never sees a body placement.
+ * Kept for readers built against tersign ≤0.5; `withAssure` uses it only with
+ * `legacyBodyPlacement: true`. */
 export declare function attachToExtensions<T extends Record<string, unknown>>(responseBody: T, issued: IssuedReceipt): T & {
     extensions: Record<string, unknown>;
 };