@devlab.group/agent-commerce 1.4.1 → 1.5.0

package/README.md

@@ -1,7 +1,7 @@
 <h1 align="center">Agent Commerce Gateway</h1>
 
 <p align="center">
-  <strong>One backend. Agent-commerce protocols on the front. No proprietary middleman.</strong>
+  <strong>One backend. Multiple agent-commerce protocols. Self-hosted and non-custodial.</strong>
 </p>
 
 <p align="center">
@@ -10,6 +10,7 @@
   <img alt="TypeScript" src="https://img.shields.io/badge/TypeScript-strict-3178c6">
   <img alt="MCP" src="https://img.shields.io/badge/MCP-supported-6b4fbb">
   <img alt="x402" src="https://img.shields.io/badge/x402-supported-0052ff">
+  <img alt="MPP" src="https://img.shields.io/badge/MPP-experimental-f0a30a">
   <img alt="A2A" src="https://img.shields.io/badge/A2A-experimental-f0a30a">
   <img alt="ACP" src="https://img.shields.io/badge/ACP-experimental-f0a30a">
   <img alt="AP2" src="https://img.shields.io/badge/AP2-experimental-f0a30a">
@@ -17,21 +18,19 @@
 
 ## What it is, in ten seconds
 
-You already have an HTTP API. AI agents want to **discover** it, **call** it and
-**pay** for it - over protocols you did not write and do not want to maintain.
+You already have an HTTP API. Agent Commerce Gateway lets AI agents discover,
+call and pay for it without adding those protocols to your backend.
 
-Agent Commerce Gateway sits in front of your existing API, in **your**
-infrastructure, and does that for you. You describe an endpoint in a YAML file -
-or generate that description from an OpenAPI document you already have - and
-agents get an MCP tool and an x402 paywall. Switch on the experimental adapters
-and the same resource is also an A2A skill, or an ACP checkout session. Switch
-on AP2 and a paid resource can also demand a signed mandate: proof the human
-behind the agent approved that exact purchase. The money goes straight to your
-wallet - the gateway never holds it, and never holds your keys.
+Run the gateway in your infrastructure and describe each endpoint in YAML, or
+generate draft resource definitions from OpenAPI. Resources can be exposed over
+HTTP, MCP or experimental A2A; dedicated resources can implement experimental
+ACP checkout operations. Paid resources use x402 or experimental MPP and can
+also require an AP2 mandate proving that the buyer approved the purchase. Funds
+go directly to the merchant wallet; the gateway never holds them or your keys.
 
 ```text
 Your existing API → Agent Commerce Gateway → AI Agent
-      MCP · A2A · ACP · x402 · AP2 · receipts · doctor
+    MCP · A2A · ACP · x402 · MPP · AP2 · receipts · doctor
 ```
 
 ## Demo
@@ -68,21 +67,18 @@ npm install -g @devlab.group/agent-commerce # or install the `agent-commerce` bi
 agent-commerce doctor
 ```
 
-Requires **Node >= 22**. One package ships two things: the `agent-commerce`
-CLI (`init`, `validate`, `doctor`, `demo`) and a library for embedding the
-gateway in your own process. A default install is ~65 MB and pulls no
-blockchain or wallet dependencies at all - ~17 MB of that is the OpenAPI
-parser behind `import openapi`, which is a normal dependency because
-onboarding an existing API is the CLI's main job.
+Requires **Node >= 22**. The package includes the `agent-commerce` CLI
+(`init`, `validate`, `doctor`, `demo`) and a library for embedding the gateway.
+The default install excludes optional protocol, payment and authorization
+peers. The OpenAPI parser is a regular dependency because import is part of the
+CLI.
 
 ```ts
 import { createGateway, loadConfig, receipts } from '@devlab.group/agent-commerce';
 
 const config = await loadConfig({ path: 'config.yaml' });
 const store = receipts({ path: './receipts.sqlite' });
-// Every ReceiptStore must be initialised before anything else touches it -
-// for the SQLite one this is where a schema written by a newer version is
-// caught, at boot rather than at the first query
+// Initialize before use so an incompatible SQLite schema fails at startup
 await store.init();
 
 const gateway = await createGateway({
@@ -94,21 +90,23 @@ const gateway = await createGateway({
 const { url } = await gateway.listen();
 ```
 
-### Optional peers - install only the rails you use
+### Optional peers
 
-The MCP adapter, the x402 provider and AP2 verification live on their own
-subpaths, because each needs a dependency the rest of the package does not -
-the x402 rail brings the whole EVM signing and RPC stack, which a gateway
-serving a free HTTP resource has no business installing.
+Components with extra dependencies use separate subpaths, so a gateway serving
+free HTTP resources does not install MCP, EVM, JOSE or SD-JWT packages.
 
 | You want                                | Install                            | Import                                     |
 | --------------------------------------- | ---------------------------------- | ------------------------------------------ |
 | gateway, config, receipts, CLI          | `@devlab.group/agent-commerce`     | `from '@devlab.group/agent-commerce'`      |
 | expose resources as MCP tools           | `+ @modelcontextprotocol/sdk`      | `from '@devlab.group/agent-commerce/mcp'`  |
 | accept x402 payments                    | `+ @x402/core @x402/evm viem`      | `from '@devlab.group/agent-commerce/x402'` |
+| accept MPP payments                     | `+ mppx viem @x402/core @x402/evm` | `from '@devlab.group/agent-commerce/mpp'`  |
 | verify AP2 mandates, sign checkout JWTs | `+ jose @sd-jwt/core canonicalize` | `from '@devlab.group/agent-commerce/ap2'`  |
 | authenticate to a CDP facilitator       | `+ @coinbase/x402`                 | (no import - loaded on demand)             |
 
+MPP settles through an x402 facilitator, so its entry also needs the x402
+peers.
+
 ```bash
 npm install @devlab.group/agent-commerce @modelcontextprotocol/sdk @x402/core @x402/evm viem
 ```
@@ -119,23 +117,17 @@ import { x402 } from '@devlab.group/agent-commerce/x402';
 import { ap2 } from '@devlab.group/agent-commerce/ap2';
 ```
 
-The AP2 three are small - about 1.3 MB installed between them, against roughly
-63 MB for the x402 stack - but they stay optional on the same principle: a
-deployment that gates nothing on a mandate should not carry a JOSE stack and an
-SD-JWT parser to serve a resource.
+AP2 peers remain optional because a deployment without mandate-gated resources
+does not need JOSE or SD-JWT support.
 
 Peers are pinned exactly: x402's schemas and EIP-712 domains cross this
 boundary, so a version skew is a correctness problem rather than a convenience
-one. Import a subpath without its
-peer installed and Node fails at load naming the missing package - deliberately,
-rather than starting a gateway that silently serves nothing.
+one. Importing a subpath without its peer fails at load time and names the
+missing package.
 
-`@coinbase/x402` is the odd one out: it has no import of its own and is loaded
-dynamically, only when `facilitator.auth.type: cdp` is configured. It is worth
-avoiding if you can - it brings `@coinbase/cdp-sdk` and `axios`, which carry
-high-severity advisories, while the package itself and the other three peers
-audit clean. `auth.type: bearer` covers any facilitator with a static token and
-installs nothing.
+`@coinbase/x402` has no subpath import. It is loaded dynamically only for
+`facilitator.auth.type: cdp` and brings the larger CDP dependency tree. A
+facilitator with a static token can use `auth.type: bearer` without it.
 
 ## Quickstart
 
@@ -155,15 +147,13 @@ npm run agent-commerce -- doctor --config config-demo.yaml # verify the whole st
 npm run demo:agent # watch an agent buy something
 ```
 
-<sub><b>Linux only</b>, and only if your user is not UID/GID 1000 (check with
-<code>id -u && id -g</code>): export <code>DOCKER_UID=$(id -u) DOCKER_GID=$(id -g)</code>
-before <code>docker compose up</code>. The chain-deploy step runs as that user so the
-deployment manifest it writes stays host-writable rather than root-owned. Docker
-Desktop on macOS and Windows translates permissions through its VM and does not
-need this.</sub>
+<sub><b>Linux:</b> if your UID/GID is not 1000, export
+<code>DOCKER_UID=$(id -u) DOCKER_GID=$(id -g)</code> before
+<code>docker compose up</code>. This keeps the generated deployment manifest
+host-writable. Docker Desktop does not need this.</sub>
 
-That is the whole thing. The stack is a private Anvil chain, a mock USDC token,
-a demo merchant API, the gateway and a dashboard - all local and disposable.
+The disposable local stack includes Anvil, MockUSDC, a demo merchant API, the
+gateway and a dashboard.
 
 To stop and wipe state: `docker compose down -v`.
 
@@ -174,7 +164,7 @@ To stop and wipe state: `docker compose down -v`.
 │                                   AI Agent                                   │
 └───────────────────────────────────────┬──────────────────────────────────────┘
                                         │  MCP · A2A · ACP · HTTP
-                                        │  PAYMENT-SIGNATURE
+                                        │  payment proof
                                         │  Agent-Authorization
 ┌───────────────────────────────────────▼──────────────────────────────────────┐
 │                        Agent Commerce Gateway (yours)                        │
@@ -184,7 +174,7 @@ To stop and wipe state: `docker compose down -v`.
 │             ┌────────────────────┬──────────────┴──┬────────────────┐        │
 │             ▼                    ▼                 ▼                ▼        │
 │   AuthorizationProvider   PaymentProvider   BackendExecutor   ReceiptStore   │
-│           (ap2)               (x402)        (bounded HTTP)      (SQLite)     │
+│           (ap2)             (x402, mpp)     (bounded HTTP)      (SQLite)     │
 └───────────────────────────────────────┬──────────────────────────────────────┘
                                         │
                              ┌──────────▼─────────┐
@@ -192,11 +182,10 @@ To stop and wipe state: `docker compose down -v`.
                              └────────────────────┘
 ```
 
-Every protocol adapter converges on **one execution pipeline**. That is what
-makes payment enforcement a property of the system rather than something each
-adapter has to remember. Money never passes through the box: the buyer pays the
-merchant directly on chain, and the gateway holds neither the funds nor a key.
-Full detail in [docs/architecture.md](docs/architecture.md).
+Every protocol adapter uses one execution pipeline, so payment enforcement does
+not depend on the adapter. The buyer pays the merchant directly on-chain; the
+gateway holds neither the funds nor a buyer or merchant key. See
+[Architecture](docs/architecture.md).
 
 ## Configure a resource
 
@@ -231,57 +220,56 @@ Already have an OpenAPI description? Generate the resources from it
 agent-commerce import openapi ./openapi.yaml
 ```
 
-It writes a reviewable `resources:` fragment - path, query and JSON body
-mapped, schemas converted to what the gateway actually enforces - and
-deliberately leaves `pricing` and `expose` out, because an OpenAPI document has
-no opinion on what an operation costs or who may see it. Credentials are never
-imported. See [OpenAPI import](docs/openapi-import.md) for the exact supported subset.
+It writes a reviewable `resources:` fragment with path, query and JSON body
+bindings and supported schemas. It omits `pricing`, `expose` and credentials;
+the source document cannot decide price or exposure. See
+[OpenAPI import](docs/openapi-import.md) for the supported subset.
 
 See [docs/configuration.md](docs/configuration.md).
 
 ## Protocol support
 
-| Protocol  | Status       | Pinned revision                                          |
-| --------- | ------------ | -------------------------------------------------------- |
-| **MCP**   | Supported    | `@modelcontextprotocol/sdk@1.30.0`                       |
-| **x402**  | Supported    | x402 v2 (`@x402/core`, `@x402/evm`), scheme `exact`, EVM |
-| **HTTP**  | Supported    | native routes                                            |
-| **A2A**   | Experimental | A2A v1.0.0, binding `JSONRPC`, method `SendMessage`      |
-| **ACP**   | Experimental | ACP `2026-04-17`, REST checkout + discovery              |
-| **AP2**   | Experimental | AP2 `v0.2.0`, Direct Checkout Mandate verification       |
-| UCP · MPP | Planned      | -                                                        |
-
-[AP2](docs/ap2.md) is in that table because people look there, but it is an **authorization**
-method rather than a transport: it gates settlement on a resource that still
-takes a real payment, and it is the verifying half only - the gateway holds no
-signing key and issues no Checkout Receipt.
-
-"Planned" means **no code ships for it**. "Experimental" means the code ships,
-is tested against the protocol's own official artifacts, and serves a narrow
-named subset: [A2A](docs/protocols.md#a2a) and [ACP](docs/protocols.md#acp) are
-both off by default and documented in full there, as are
-[MCP](docs/protocols.md#mcp) and [x402](docs/protocols.md#x402). ACP serves the
-five stable checkout operations and advertises `services: ["checkout"]` and
-nothing more; its `payment_data` stays with the merchant's own checkout and is
-never turned into an x402 payment.
-
-Each adapter reports its own `supportedSpec`, `capabilities` and `unsupported`
-list at runtime through `GET /.well-known/agent-commerce` and
-`agent-commerce doctor`, so the claim is checkable rather than marketing.
+| Protocol | Status       | Pinned revision                                                           |
+| -------- | ------------ | ------------------------------------------------------------------------- |
+| **HTTP** | Supported    | native routes                                                             |
+| **MCP**  | Supported    | `@modelcontextprotocol/sdk@1.30.0`                                        |
+| **x402** | Supported    | x402 v2 (`@x402/core`, `@x402/evm`), scheme `exact`, EVM                  |
+| **MPP**  | Experimental | `mppx@0.10.1`, `charge` + `evm` + EIP-3009, USDC on Base Sepolia and Base |
+| **A2A**  | Experimental | A2A v1.0.0, binding `JSONRPC`, method `SendMessage`                       |
+| **ACP**  | Experimental | ACP `2026-04-17`, REST checkout + discovery                               |
+| **AP2**  | Experimental | AP2 `v0.2.0`, Direct Checkout Mandate verification                        |
+| UCP      | Planned      | no implementation                                                         |
+
+[AP2](docs/ap2.md) is an authorization method, not a transport. It verifies a
+mandate before a paid resource settles; the gateway does not issue the mandate
+or its Checkout Receipt.
+
+The experimental entries above ship off by default with documented subsets:
+[A2A](docs/protocols.md#a2a), [ACP](docs/protocols.md#acp),
+[AP2](docs/ap2.md#not-implemented) and [MPP](docs/protocols.md#mpp). Supported
+[MCP](docs/protocols.md#mcp) and [x402](docs/protocols.md#x402) are also scoped.
+ACP exposes only its five checkout operations; merchant `payment_data` is never
+converted into a gateway payment proof.
+
+`GET /.well-known/agent-commerce` reports `supportedSpec`, `capabilities` and
+`unsupported` for registered adapters and providers. `agent-commerce doctor`
+prints the `unsupported` lists for A2A, ACP and AP2.
 
 ## Payment model
 
 - **Non-custodial.** The gateway never holds funds, and never asks for a
   merchant or buyer private key. `payTo` is your address.
 - **Fail closed.** Missing, malformed, expired, replayed, wrong-amount,
-  wrong-recipient, wrong-network and wrong-asset payments all fail - each with a
-  test.
+  wrong-recipient, wrong-network and wrong-asset payments are rejected.
 - **Replay-safe twice over.** EIP-3009 stops a double spend on-chain; the
   gateway additionally reserves a `replayKey` derived from the authorisation
   before it settles anything.
-- **Real settlement in CI.** The end-to-end test asserts the buyer's balance
+- **On-chain settlement in CI.** The end-to-end test asserts the buyer's balance
   falls and the merchant's rises by exactly the price, with a real transaction
   hash in the receipt. A log line saying "payment successful" would not count.
+- **One selected rail per resource.** A resource can name several rails, such as
+  `payments: [x402, mpp]`; the first enabled one serves it, and nothing selects
+  or falls back between rails per request.
 - **Authorization is separate from payment.** A resource can also require an
   AP2 mandate, verified before settlement and spendable exactly once. It never
   moves money and never unlocks a resource on its own - the payment still has
@@ -294,19 +282,20 @@ not this process. No code changes, and no "live mode" to switch on.
 
 ### It has actually settled
 
-Not a roadmap entry. Both of these moved 0.01 USDC from a buyer to a merchant
-through a remote facilitator:
+These transactions each moved 0.01 USDC from a buyer to a merchant through a
+remote facilitator:
 
-| Network      | Transaction                                                                                                           |
-| ------------ | --------------------------------------------------------------------------------------------------------------------- |
-| Base Sepolia | [`0xea41b234c4…`](https://sepolia.basescan.org/tx/0xea41b234c4645a4d335589ec9753646aa7cccd1b97e9e15823b88bff7b54a247) |
-| Base         | [`0x57ec81c2a3…`](https://basescan.org/tx/0x57ec81c2a360d14d59a43cf4e24be09a6bd75cbe6185016372895bda73e42763)         |
+| Rail | Network      | Transaction                                                                                                           |
+| ---- | ------------ | --------------------------------------------------------------------------------------------------------------------- |
+| x402 | Base Sepolia | [`0xea41b234c4…`](https://sepolia.basescan.org/tx/0xea41b234c4645a4d335589ec9753646aa7cccd1b97e9e15823b88bff7b54a247) |
+| x402 | Base         | [`0x57ec81c2a3…`](https://basescan.org/tx/0x57ec81c2a360d14d59a43cf4e24be09a6bd75cbe6185016372895bda73e42763)         |
+| MPP  | Base Sepolia | [`0x5d9fcd111b…`](https://sepolia.basescan.org/tx/0x5d9fcd111b615bb8fc9e56d55096f119fc81c3c72c334f813cfaecee402d0ac3) |
+| MPP  | Base         | [`0xf4255bd7ec…`](https://basescan.org/tx/0xf4255bd7ec46ed06505dedfb5f9537924bd2633816e7952ec6f2b468395b1087)         |
 
-In both, the gateway held no key, signed nothing and paid no gas - the buyer
-signed an EIP-3009 authorisation offline holding no ETH, and the facilitator
-broadcast it. Each run reads the buyer and merchant balances and the
-transaction receipt back off the chain afterwards; the gateway's own report of
-success is not the proof.
+The buyer signed each EIP-3009 authorisation without ETH; the remote facilitator
+paid gas and broadcast it. The gateway path received no buyer or merchant key.
+The public-network smoke suites verify balance changes and fetch the transaction
+receipt from the chain instead of trusting the gateway's response.
 
 Reproduce with `npm run test:testnet` / `npm run test:mainnet` - both spend
 real funds, skip themselves without credentials, and never run in CI.
@@ -322,17 +311,14 @@ gateway on a public network.
 | `local`            | this process, with an Anvil dev key | the local dev chain only |
 | `remote`           | an HTTP facilitator you point at    | anywhere                 |
 
-With `remote`, the gateway holds **no signing key at all**. The buyer signs an
-EIP-3009 authorisation offline - no ETH required - and the facilitator pays the
-gas. A facilitator cannot redirect your money: the authorisation names its
-recipient, amount and chain, so it can broadcast exactly that transfer or
-nothing. What it can do is see every authorisation you handle, and stop
-answering.
+With `remote`, the gateway holds no facilitator signing key. The buyer signs an
+EIP-3009 authorisation without ETH, and the facilitator pays gas. Because the
+authorisation fixes the recipient, amount and chain, the facilitator cannot
+redirect the transfer. It can see authorisations and refuse service.
 
-Three auth types: `none`, `bearer` (a static token, installs nothing) and `cdp`
-(Coinbase Developer Platform, which signs a fresh JWT per request). Anything
-else is refused at config load rather than sent nothing. You can also run your
-own - `remote` does not care who operates the endpoint.
+Remote facilitator auth supports `none`, `bearer` and `cdp`. CDP signs a fresh
+JWT per request and conditionally loads `@coinbase/x402`; bearer auth needs no
+extra peer. Other types are rejected at config load.
 
 ### Base Sepolia
 
@@ -366,8 +352,7 @@ together, and reported by `doctor`, `health()` and `/.well-known`.
 
 ### Base mainnet
 
-Real funds, so nothing is defaulted. Every one of these is checked at config
-load, and the gateway will not start without them:
+Mainnet moves real funds. Config validation requires:
 
 | Required                                        |                                                                                                                |
 | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
@@ -375,13 +360,13 @@ load, and the gateway will not start without them:
 | `facilitator.mode: remote`                      | `local` needs a funded gas key inside this process                                                             |
 | an HTTPS `facilitator.url`                      |                                                                                                                |
 | `allowUnauthenticatedFacilitator: true`         | only if that facilitator takes no credential                                                                   |
-| a non-development `payTo`                       |                                                                                                                |
-| `asset` = USDC on Base, `assetName: "USD Coin"` | **not** `"USDC"` - that deployment predates the rename, and the buyer signs the name into their EIP-712 domain |
+| a non-development destination (`payTo` or `recipient`) |                                                                                                         |
+| Base USDC with `assetName: "USD Coin"` and `assetVersion: "2"` | the buyer signs this EIP-712 domain; `"USDC"` is wrong on Base |
 
 Full config in [`examples/base-mainnet/`](examples/base-mainnet/), and
 [`examples/base-mainnet-payai/`](examples/base-mainnet-payai/) for an
-unauthenticated facilitator. `npm run test:mainnet` proves it end to end and
-spends real USDC on every run.
+unauthenticated facilitator. The mainnet smoke suites cover x402 and MPP and
+spend real USDC when their opt-ins and credentials are present.
 
 `agent-commerce validate` reports any of the above before anything starts, and
 `doctor` prints `LIVE MAINNET MODE - REAL FUNDS`.
@@ -404,17 +389,15 @@ INFO  A2A                  disabled
 INFO  ACP                  disabled
 INFO  AP2                  disabled
 PASS  Payments             x402 v2 (scheme=exact) enabled - LOCAL dev chain (eip155:84532, chain id shared with Base Sepolia), destination=0x7099…79C8, facilitator=local
-INFO  Payments (MPP)       planned - not implemented in this release
+INFO  Payments (MPP)       MPP not configured
 PASS  Storage              sqlite schema v1 writable; receipts=2
 PASS  Protocol versions    reported by gateway /.well-known/agent-commerce
 
 Score: 7/7 checks passed
 ```
 
-That is real output, not an illustration. `doctor` also cross-checks the
-gateway's *live* settlement configuration against what your local config
-resolves to, and fails if they disagree - a diagnostic that passes while the
-system is misconfigured is worse than none.
+`doctor` cross-checks the gateway's live settlement configuration against the
+resolved local config and fails if they differ.
 
 Exits non-zero if anything fails. `--json` for machines.
 
@@ -452,12 +435,12 @@ See [CONTRIBUTING.md](CONTRIBUTING.md).
 **Now** - MCP, x402 v2, settlement on the local chain, Base Sepolia and Base
 mainnet, receipts, doctor, deterministic demo, experimental A2A v1.0.0 and ACP
 `2026-04-17` checkout adapters, experimental AP2 v0.2.0 mandate verification,
-and experimental OpenAPI import.
+experimental MPP `charge` payments, and experimental OpenAPI import.
 
-**Next** - a `doctor` GitHub Action · UCP · MPP · autonomous-mode AP2 (open
-mandates, agent key binding, constraint evaluation) · more of ACP (carts, feed,
-delegated payment) · Shopify and WooCommerce examples · PostgreSQL · richer
-observability · multi-file and remote OpenAPI sources.
+**Next** - a `doctor` GitHub Action · UCP ·
+autonomous-mode AP2 (open mandates, agent key binding, constraint evaluation) ·
+more of ACP (carts, feed, delegated payment) · Shopify and WooCommerce examples ·
+PostgreSQL · richer observability · multi-file and remote OpenAPI sources.
 
 New protocols land only after the adapter model survives real use. Scope
 discipline is a release requirement, not a mood.
@@ -467,8 +450,8 @@ discipline is a release requirement, not a mood.
 |                                                |                                             |
 | ---------------------------------------------- | ------------------------------------------- |
 | [Architecture](docs/architecture.md)           | how the pieces fit                          |
-| [Payment flow](docs/payment-flow.md)           | the paid round trip, and every way it fails |
-| [Protocols](docs/protocols.md)                 | exactly what is and is not supported        |
+| [Payment flow](docs/payment-flow.md)           | the paid round trip and failure paths       |
+| [Protocols](docs/protocols.md)                 | supported and unsupported protocol features |
 | [AP2](docs/ap2.md)                             | mandate verification and the trust model    |
 | [Configuration](docs/configuration.md)         | `config.yaml` reference                     |
 | [OpenAPI import](docs/openapi-import.md)       | generate resources from an existing API     |

package/dist/ap2.d.ts

@@ -1,7 +1,7 @@
 import { E as EnabledAp2Config } from './types-CJtwLu1c.js';
 export { A as AP2_CHECKOUT_MANDATE_VCT, a as AP2_CHECKOUT_PROFILE, b as AP2_DEFAULT_CLOCK_SKEW_SECONDS, c as AP2_MAX_CLOCK_SKEW_SECONDS, d as AP2_SIGNING_ALGORITHM, e as AP2_SPEC_VERSION, f as Ap2AuthorizationConfig, g as Ap2Mode, h as Ap2TrustedIssuer, i as Ap2TrustedKey } from './types-CJtwLu1c.js';
-import { A as AuthorizationProvider } from './authorization-CPDcpJVa.js';
-import { C as Clock, L as Logger } from './runtime-CKq3d_3K.js';
+import { A as AuthorizationProvider } from './authorization-DA7mjy_O.js';
+import { C as Clock, L as Logger } from './runtime-DC5XQ9Cc.js';
 
 /**
  * A private ES256 key: either a private JWK (the pair of the public one in the
@@ -139,8 +139,8 @@ interface Ap2ReplayStore {
  * The AP2 authorization provider: the seam between core's generic contract and
  * the mandate machinery.
  *
- * Owns the replay database, so the gateway owns this object's lifetime and
- * closes it on shutdown.
+ * The provider owns its replay store. The caller that creates the provider must
+ * call `close()`; `createGateway` does not close authorization providers.
  */
 
 interface Ap2AuthorizationProviderOptions {
@@ -151,7 +151,7 @@ interface Ap2AuthorizationProviderOptions {
     readonly replayStore?: Ap2ReplayStore;
 }
 interface Ap2AuthorizationProvider extends AuthorizationProvider {
-    /** Closes the replay database */
+    /** Closes the replay store */
     close(): void;
 }
 /**

package/dist/ap2.js

@@ -1,6 +1,6 @@
-import { AP2_CHECKOUT_MANDATE_VCT, AP2_SIGNING_ALGORITHM, AP2_DIGEST_ALGORITHM, AP2_CHECKOUT_PROFILE, AP2_SPEC_VERSION, AP2_KEY_TYPE, AP2_JWK_CURVE, openSqliteDatabase } from './chunk-GF6KHHKL.js';
-export { AP2_CHECKOUT_MANDATE_VCT, AP2_CHECKOUT_PROFILE, AP2_DEFAULT_CLOCK_SKEW_SECONDS, AP2_MAX_CLOCK_SKEW_SECONDS, AP2_SIGNING_ALGORITHM, AP2_SPEC_VERSION } from './chunk-GF6KHHKL.js';
-import { systemClock, NOOP_LOGGER, CommerceError, PACKAGE_VERSION } from './chunk-ZEGFLRGV.js';
+import { AP2_CHECKOUT_MANDATE_VCT, AP2_SIGNING_ALGORITHM, AP2_DIGEST_ALGORITHM, AP2_CHECKOUT_PROFILE, AP2_SPEC_VERSION, AP2_KEY_TYPE, AP2_JWK_CURVE, openSqliteDatabase } from './chunk-US622BKF.js';
+export { AP2_CHECKOUT_MANDATE_VCT, AP2_CHECKOUT_PROFILE, AP2_DEFAULT_CLOCK_SKEW_SECONDS, AP2_MAX_CLOCK_SKEW_SECONDS, AP2_SIGNING_ALGORITHM, AP2_SPEC_VERSION } from './chunk-US622BKF.js';
+import { systemClock, NOOP_LOGGER, CommerceError, PACKAGE_VERSION } from './chunk-5GEWKNIH.js';
 import { SignJWT, importPKCS8, importJWK, jwtVerify } from 'jose';
 import canonicalize from 'canonicalize';
 import { decodeSdJwt, splitSdJwt, getClaims } from '@sd-jwt/core';
@@ -81,6 +81,15 @@ async function computeInputHash(input) {
   const digest = await crypto.subtle.digest("SHA-256", new TextEncoder().encode(canonical));
   return Buffer.from(digest).toString("base64url");
 }
+var EVM_ADDRESS = /^0x[0-9a-f]{40}$/i;
+function sameCoordinate(declared, expected) {
+  if (typeof declared === "string" && expected !== void 0) {
+    if (EVM_ADDRESS.test(declared) && EVM_ADDRESS.test(expected)) {
+      return declared.toLowerCase() === expected.toLowerCase();
+    }
+  }
+  return declared === expected;
+}
 function asRecord(value) {
   return typeof value === "object" && value !== null && !Array.isArray(value) ? value : void 0;
 }
@@ -115,7 +124,7 @@ async function bindMandateToPurchase(mandate, context, errorContext) {
   ]) {
     const declared = profile[claim];
     if (declared === void 0 && expected === void 0) continue;
-    if (declared !== expected) throw ap2Rejected("purchase_mismatch", errorContext);
+    if (!sameCoordinate(declared, expected)) throw ap2Rejected("purchase_mismatch", errorContext);
   }
   return {
     resourceId: profile["resource_id"],
@@ -226,7 +235,6 @@ var AP2_UNSUPPORTED = [
   "digest algorithms other than sha-256",
   // Roles this gateway does not play
   "mandate issuance",
-  "merchant checkout JWT issuance",
   "AP2 over the ACP checkout adapter"
 ];
 function buildAp2Descriptor(implementationVersion) {
@@ -277,17 +285,17 @@ function createAp2ReplayStore(options) {
   const reserveTx = db.transaction((request) => {
     const at = new Date(now()).toISOString();
     const existing = selectByReference.get(request.reference);
-    if (existing !== void 0) {
-      if (existing.state !== "released") {
-        return { kind: "replayed", state: existing.state };
-      }
-      reReserve.run({ reference: request.reference, request_id: request.requestId, at });
-      return { kind: "reserved" };
+    if (existing !== void 0 && existing.state !== "released") {
+      return { kind: "replayed", state: existing.state };
     }
     const sameCheckout = selectLiveByJti.get(request.checkoutJti, request.reference);
     if (sameCheckout !== void 0) {
       return { kind: "replayed", state: sameCheckout.state };
     }
+    if (existing !== void 0) {
+      reReserve.run({ reference: request.reference, request_id: request.requestId, at });
+      return { kind: "reserved" };
+    }
     insert.run({
       reference: request.reference,
       checkout_jti: request.checkoutJti,