@zkp2p/zkp2p-attestation 1.1.0 → 1.3.0

package/CHANGELOG.md

@@ -1,7 +1,31 @@
 # Changelog
 
+## 1.3.0
+
+- BREAKING: Buyer TEE verify request body field renamed from `metadata` to `params`. The server Zod schema rejects the legacy `metadata` field. All `*BuyerTeeMetadata` types in `@zkp2p/zkp2p-attestation` are renamed to `*BuyerTeeParams`, and `BuyerTeeMetadataByPlatform` is now `BuyerTeeParamsByPlatform`.
+- BREAKING: Buyer TEE `params` shape no longer accepts duplicate provider-row fields. `N26BuyerTeeParams` is `{}`. `RevolutBuyerTeeParams`, `CitiBuyerTeeParams`, and `BankOfAmericaBuyerTeeParams` are `{ index }` only — `paymentId`, `transactionId`, and `confirmationNumber` are derived from the selected response row.
+- BREAKING: Drop `jweId` from the buyer TEE session-material plaintext and from `EncryptBuyerTeeSessionMaterialBaseParams`. The server enforces a strict plaintext schema and rejects envelopes that still carry `jweId`. Seller credential upload still uses `jweId`.
+- BREAKING: Drop `issuedAtMs` and `now` from `EncryptBuyerTeeSessionMaterialBaseParams` and from the buyer TEE plaintext schema. The server no longer enforces a 5-minute capture-age window on buyer envelopes; encrypted session material is valid for the lifetime of the upstream session (cookies/PAT). Seller credential upload still carries `issuedAtMs` and is unchanged.
+- Migration: regenerate buyer TEE envelopes after upgrading; do not retry an envelope produced by `<1.3.0`. Update buyer TEE call sites to rename `metadata` to `params` and drop the removed per-platform fields (Revolut `paymentId`, Citi `transactionId`, BoA `confirmationNumber`, N26 `paymentId`).
+- Operational note: a leaked encrypted JWE is now valid for the upstream session lifetime — treat any disclosure as equivalent to leaking the underlying upstream credential and rotate the upstream session.
+
+## 1.2.0
+
+- Expand buyer TEE SDK types from Venmo-only to all 15 server-registered platforms.
+- Tie each buyer TEE platform to its valid `actionType`, metadata shape, and named session-material header map.
+- Require documented buyer TEE session-material headers in the per-platform TypeScript types (e.g. Wise `Cookie` or `X-Access-Token`, Revolut `Cookie` and `x-device-id`). A payload missing the required headers is a type error at the call site.
+- Export `AttestationOutput`, `BuyerTeeVerifier`, `/buyer/supported`, and service response types for callers.
+- Add `verifyBuyerTeePayment()` and `uploadSellerCredential()` one-shot helpers that chain attest → encrypt → POST → unwrap and return a typed result.
+- Enforce `timeoutMs` across buyer TEE verify and seller credential upload POST requests, including through response body reads so stalled streams abort.
+- Preserve structured unsuccessful ServiceResponse details on SDK errors via a new `SERVICE_RESPONSE_ERROR` code carrying `details.responseObject` — enables UIs to consume Wise multi-profile `WISE_PROFILE_SELECTION_REQUIRED` payloads and any future business-logic 4xx.
+- Reject successful ServiceResponse envelopes that omit a `responseObject` (defends against bad-deploy / proxy-rewrite cases that would otherwise resolve helpers with `undefined`).
+- Add buyer TEE discriminated-union type tests for Wise metadata/action narrowing and Revolut header enforcement.
+- Drop the deprecated `verifyingContract` from the new buyer TEE verify helper parameters; the server resolves it from `DEPLOYMENT_ENV`.
+- Keep the internal service-response envelope out of the public SDK type exports.
+
 ## 1.1.0
 
+- Add buyer TEE session-material encryption helpers.
 - Add platform-aware seller credential upload encryption.
 - Support Wise seller credential uploads with `platform: "wise"` and no top-level `payeeId`.
 - Preserve the existing payee-based upload shape for Venmo, Cash App, and PayPal.

package/README.md

@@ -1,6 +1,6 @@
 # @zkp2p/zkp2p-attestation
 
-Client-side verifier and encryptor for ZKP2P Nitro seller credential uploads.
+Client-side verifier and encryptor for ZKP2P Nitro seller credential uploads and buyer TEE session-material requests.
 
 The package runs in Chrome MV3 service workers, browser DOM contexts, React Native with a Web Crypto polyfill, and Node >= 20. Library entrypoints use `fetch`, `SubtleCrypto`, `crypto.getRandomValues`, and `Uint8Array`; they do not import `node:*` modules or use `Buffer`.
 
@@ -57,6 +57,17 @@ await fetch(`${attestationServiceUrl}/seller/credentials/wise`, {
 
 This fetches `GET /attestation?nonce=...`, verifies the Nitro document to the pinned AWS root and PCR8, extracts the attested seller-upload RSA SPKI, and returns a compact JWE for `POST /seller/credentials/:platform`.
 
+For the same flow without hand-rolling the POST:
+
+```ts
+const credentialBundle = await nitro.uploadSellerCredential({
+  platform: "wise",
+  sessionMaterial: {
+    apiToken: "<wise-api-token>",
+  },
+});
+```
+
 Venmo, Cash App, and PayPal still require a top-level `payeeId`; existing callers can keep using the same call shape:
 
 ```ts
@@ -66,6 +77,73 @@ const encryptedUpload = await nitro.createEncryptedSellerCredentialUpload({
 });
 ```
 
+Buyer TEE requests use the same attested upload key and compact JWE envelope. The typed helper encrypts the captured
+session material, posts `{ encryptedSessionMaterial, params, chainId, intent }` to
+`POST /buyer/verify/:platform/:actionType`, unwraps the service envelope, and returns a typed `AttestationOutput`.
+The service does not enforce capture-age or one-use replay limits for buyer TEE session material; verification depends
+on the upstream session still being active. A leaked encrypted JWE is therefore valid for the upstream session
+lifetime — treat any accidental disclosure as equivalent to leaking the underlying upstream credential (cookies, PAT,
+etc.) and rotate the upstream session.
+
+```ts
+const attestation = await nitro.verifyBuyerTeePayment({
+  platform: "venmo",
+  actionType: "transfer_venmo",
+  sessionMaterial: {
+    Cookie: "<captured-cookie-header>",
+    "User-Agent": "<captured-user-agent>",
+  },
+  params: { senderId: "<venmo-account-id>", index: 0 },
+  chainId,
+  intent,
+});
+```
+
+The helper is a thin wrapper over the existing wire format; callers can still hand-roll the final POST:
+
+```ts
+const encryptedSessionMaterial = await nitro.createEncryptedBuyerTeeSessionMaterial({
+  platform: "wise",
+  actionType: "transfer_wise",
+  sessionMaterial: { "X-Access-Token": "<captured-token>" },
+});
+
+await fetch(`${attestationServiceUrl}/buyer/verify/wise/transfer_wise`, {
+  method: "POST",
+  headers: { "content-type": "application/json" },
+  body: JSON.stringify({
+    encryptedSessionMaterial,
+    params: { profileId: "41246868", transactionId: "123456789" },
+    chainId,
+    intent,
+  }),
+});
+```
+
+Buyer TEE platform matrix:
+
+| Platform | `actionType` | Required encrypted session material | Public params fields |
+|---|---|---|---|
+| `venmo` | `transfer_venmo` | `Cookie` | `senderId`, `index` |
+| `cashapp` | `transfer_cashapp` | `Cookie`, `x-csrf-token`, `x-device-name`, `x-request-signature`, `x-request-uuid`, `cash-web-request`, `x-web-device-info`, `x-web-context`, `x-bt-id` | `senderId`, `index` |
+| `luxon` | `transfer_luxon` | `X-Auth-Token` | `transferId` |
+| `monzo` | `transfer_monzo` | `Authorization` | `txId` |
+| `n26` | `transfer_n26` | `Cookie`, `csrf-token`, `body` | `{}` |
+| `wise` | `transfer_wise` | `Cookie` or `X-Access-Token` | `profileId`, `transactionId` |
+| `revolut` | `transfer_revolut` | `Cookie`, `x-device-id` | `index` |
+| `idfc` | `transfer_idfc` | `Cookie` | `senderId`, `index` |
+| `citi` | `transfer_zelle` | `Cookie` | `index` |
+| `chime` | `transfer_chime` | `Cookie`, `body` | `{}` |
+| `chase` | `transfer_zelle` | `Cookie`, `x-jpmc-channel`, `x-jpmc-csrf-token`, `Referer`, `Origin` | `index` |
+| `bankofamerica` | `transfer_zelle` | `Cookie` | `index` |
+| `mercadopago` | `transfer_mercadopago` | `Cookie` | `paymentId`, `urlParamsFrom` |
+| `paypal` | `transfer_paypal` | `Cookie` | `index` |
+| `alipay` | `transfer_alipay` | `Cookie` | `tradeNo` |
+
+Per-platform session-material types require these headers using the canonical names shown above while still allowing
+additional captured headers. Captured request bodies are session material because they can contain sensitive data and
+are encrypted before being sent to the service.
+
 ## Cache-Friendly Path
 
 ```ts
@@ -80,6 +158,19 @@ const encryptedUpload = await nitro.encryptSellerCredentialUpload({
 });
 ```
 
+For buyer TEE flows with a cached attestation:
+
+```ts
+const encryptedSessionMaterial = await nitro.encryptBuyerTeeSessionMaterial({
+  key: verified.attestedSellerUploadKey,
+  platform: "venmo",
+  actionType: "transfer_venmo",
+  sessionMaterial: {
+    Cookie: "<captured-cookie-header>",
+  },
+});
+```
+
 The attested SPKI is stable within one enclave process. If the enclave restarts, cached keys become stale and upload decrypt will fail; fetch a fresh attestation for a new session.
 
 ## React Native Wiring
@@ -101,9 +192,13 @@ Any conforming `SubtleCrypto` works. The package does not require `Buffer`.
 
 ```ts
 import {
+  createEncryptedBuyerTeeSessionMaterial,
   createEncryptedSellerCredentialUpload,
+  encryptBuyerTeeSessionMaterial,
   encryptSellerCredentialUpload,
   fetchAndVerifyAttestation,
+  uploadSellerCredential,
+  verifyBuyerTeePayment,
 } from "@zkp2p/zkp2p-attestation";
 ```
 

package/dist/cli/verify.js

@@ -4470,6 +4470,9 @@ function requireArray(value, label) {
   fail("PAYLOAD_FIELD_MISSING", `Attestation payload field ${label} must be an array`);
 }
 
+// src/timeout.ts
+var DEFAULT_TIMEOUT_MS = 1e4;
+
 // src/trust/pins.ts
 var STAGING_PCR8 = "5636e3bd96f847cf12cfd9de7faa8cad0e6fa00962ce16ba185f8e5ea57105abb3cc9cc34f1e1e4de3444ceabcca7485";
 var PRODUCTION_PCR8 = "41a4ae0b9b96752cab5addb7d22689b3070e564e29f90a54316fa33fa38ea51387a6e887ea4f5a4b0cc34f69cea3f40e";
@@ -4518,7 +4521,6 @@ function findHostPin(hostPins, hostname) {
 }
 
 // src/fetchAndVerifyAttestation.ts
-var DEFAULT_TIMEOUT_MS = 1e4;
 var DEFAULT_FRESHNESS_WINDOW_MS = 5 * 60 * 1e3;
 async function fetchAndVerifyAttestation(params) {
   const fetcher = resolveFetch(params.fetch);