@agent-score/commerce 1.8.1 → 2.0.0

package/dist/{signer-CFVQsWjL.d.mts → signer-3FAit11j.d.mts}

@@ -32,10 +32,36 @@ interface PaymentSigner {
  *   Extracted separately because some frameworks (Express) don't expose a web `Request` object.
  */
 declare function extractPaymentSigner(request: Request, x402PaymentHeader?: string): Promise<PaymentSigner | null>;
+/**
+ * Headers-only variant for adapters that don't natively expose a Web Fetch `Request`
+ * (Express, Fastify, ASGI-bridged frameworks). Constructs a synthetic Request carrying
+ * only the `authorization` header and delegates to {@link extractPaymentSigner}. Works
+ * because the MPP and x402 paths only read `request.headers.get('authorization')` and
+ * the explicit `x402PaymentHeader` arg — no body, query, or method semantics needed.
+ */
+declare function extractPaymentSignerFromAuth(authHeader: string | null | undefined, x402PaymentHeader?: string): Promise<PaymentSigner | null>;
 /**
  * Read the x402 payment header from a `Request`, matching the alternate names merchants might
  * use. Falls back to reading either header directly.
  */
 declare function readX402PaymentHeader(request: Request): string | undefined;
+/**
+ * One-call signer extraction across both supported credential formats.
+ *
+ * Tries the x402 `payment-signature` / `x-payment` header first (EIP-3009
+ * `payload.authorization.from`), then falls back to the MPP
+ * `Authorization: Payment` header DID. Returns the first one that resolves,
+ * or `null`.
+ *
+ * Use this for wallet-cap prechecks and other "did the agent claim to sign as
+ * X?" checks where you need the signer BEFORE invoking Checkout. Checkout's
+ * own settle path runs verification separately and surfaces the verified
+ * signer on `SettleOutcome.signerAddress`.
+ *
+ * Accepts a plain headers dict so it works regardless of which framework the
+ * merchant uses (the gate adapters all serialize headers down to a dict by
+ * the time they reach the merchant's hooks).
+ */
+declare function extractSignerForPrecheck(headers: Record<string, string>): Promise<PaymentSigner | null>;
 
-export { type PaymentSigner as P, type SignerNetwork as S, extractPaymentSigner as e, readX402PaymentHeader as r };
+export { type PaymentSigner as P, type SignerNetwork as S, extractPaymentSignerFromAuth as a, extractSignerForPrecheck as b, extractPaymentSigner as e, readX402PaymentHeader as r };

package/dist/{signer-CFVQsWjL.d.ts → signer-3FAit11j.d.ts}

@@ -32,10 +32,36 @@ interface PaymentSigner {
  *   Extracted separately because some frameworks (Express) don't expose a web `Request` object.
  */
 declare function extractPaymentSigner(request: Request, x402PaymentHeader?: string): Promise<PaymentSigner | null>;
+/**
+ * Headers-only variant for adapters that don't natively expose a Web Fetch `Request`
+ * (Express, Fastify, ASGI-bridged frameworks). Constructs a synthetic Request carrying
+ * only the `authorization` header and delegates to {@link extractPaymentSigner}. Works
+ * because the MPP and x402 paths only read `request.headers.get('authorization')` and
+ * the explicit `x402PaymentHeader` arg — no body, query, or method semantics needed.
+ */
+declare function extractPaymentSignerFromAuth(authHeader: string | null | undefined, x402PaymentHeader?: string): Promise<PaymentSigner | null>;
 /**
  * Read the x402 payment header from a `Request`, matching the alternate names merchants might
  * use. Falls back to reading either header directly.
  */
 declare function readX402PaymentHeader(request: Request): string | undefined;
+/**
+ * One-call signer extraction across both supported credential formats.
+ *
+ * Tries the x402 `payment-signature` / `x-payment` header first (EIP-3009
+ * `payload.authorization.from`), then falls back to the MPP
+ * `Authorization: Payment` header DID. Returns the first one that resolves,
+ * or `null`.
+ *
+ * Use this for wallet-cap prechecks and other "did the agent claim to sign as
+ * X?" checks where you need the signer BEFORE invoking Checkout. Checkout's
+ * own settle path runs verification separately and surfaces the verified
+ * signer on `SettleOutcome.signerAddress`.
+ *
+ * Accepts a plain headers dict so it works regardless of which framework the
+ * merchant uses (the gate adapters all serialize headers down to a dict by
+ * the time they reach the merchant's hooks).
+ */
+declare function extractSignerForPrecheck(headers: Record<string, string>): Promise<PaymentSigner | null>;
 
-export { type PaymentSigner as P, type SignerNetwork as S, extractPaymentSigner as e, readX402PaymentHeader as r };
+export { type PaymentSigner as P, type SignerNetwork as S, extractPaymentSignerFromAuth as a, extractSignerForPrecheck as b, extractPaymentSigner as e, readX402PaymentHeader as r };

package/dist/solana-Cds87OTu.d.mts

@@ -0,0 +1,67 @@
+/**
+ * USD ↔ atomic-unit conversion for token amounts.
+ *
+ * `usdToAtomic(usd, { decimals: 6 })` returns the bigint atomic value of a USD
+ * amount for a token with `decimals` places of precision (USDC is 6). String
+ * parsing + bigint arithmetic so the result is exact; ROUND_HALF_UP at the
+ * rounding boundary matches the cross-language Python sibling.
+ *
+ * Rejects negative, NaN, infinite, and unparseable inputs. Fixed-notation only;
+ * scientific notation (e.g. `"1e6"`) is not parsed (mirrors the locked cross-
+ * language fixture corpus, which uses fixed notation exclusively).
+ */
+/**
+ * Convert a USD amount to atomic units for a token with `decimals` places.
+ *
+ * @param usd USD amount. Strings (`"1.23"`) and `number`s (`1.23`) are accepted.
+ *   `number` is converted via `String(usd)` before parsing, so JS float precision
+ *   limits apply when the float can't represent the value exactly.
+ * @param opts.decimals Number of decimal places in the atomic unit (6 for USDC,
+ *   18 for ETH, etc.). Must be a non-negative integer.
+ *
+ * @returns Integer atomic units as a `bigint`. `"1.23"` with `decimals: 6`
+ *   returns `1_230_000n`.
+ *
+ * @throws RangeError when `usd` is negative, NaN, infinite, or `decimals` is
+ *   not a non-negative integer.
+ * @throws SyntaxError when `usd` cannot be parsed as a fixed-notation decimal.
+ */
+declare function usdToAtomic(usd: string | number, opts: {
+    decimals: number;
+}): bigint;
+/**
+ * Format an integer cent amount as a fixed-2-decimal USD string.
+ *
+ * `formatUsdCents(500)` returns `"5.00"`. Negative values are formatted with a
+ * leading minus. Use everywhere a merchant emits `(cents / 100).toFixed(2)`;
+ * consistent formatting across catalog rows, order responses, and 402 bodies
+ * prevents agent-side string-comparison flakiness.
+ */
+declare function formatUsdCents(cents: number): string;
+
+/**
+ * Solana MPP fee-payer signer loader.
+ *
+ * Buyers paying via Solana MPP USDC don't typically carry SOL for transaction
+ * fees, so merchants commonly co-sign the buyer's `solana/charge` tx as the
+ * fee payer (~5000 lamports per tx; negligible vs the USDC value moved).
+ *
+ * `loadSolanaFeePayer({ privateKey })` accepts a Solana keypair in any of the
+ * three forms agents commonly export it as:
+ *
+ *   - **base58** (Phantom export format) — 64-byte secret+public, or 32-byte
+ *     secret-only
+ *   - **hex** — 128-char string (64 bytes hex: 32-byte secret + 32-byte public)
+ *
+ * Returns a `KeyPairSigner` from `@solana/kit` ready to pass as the `signer`
+ * field on a `SolanaMppRailSpec`. Returns `undefined` when `privateKey` is
+ * empty / absent (so consumers can use `process.env.X` directly without
+ * null-checks).
+ *
+ * Requires the `@solana/kit` peer dependency.
+ */
+declare function loadSolanaFeePayer(opts: {
+    privateKey: string | undefined;
+}): Promise<unknown | undefined>;
+
+export { formatUsdCents as f, loadSolanaFeePayer as l, usdToAtomic as u };

package/dist/solana-Cds87OTu.d.ts

@@ -0,0 +1,67 @@
+/**
+ * USD ↔ atomic-unit conversion for token amounts.
+ *
+ * `usdToAtomic(usd, { decimals: 6 })` returns the bigint atomic value of a USD
+ * amount for a token with `decimals` places of precision (USDC is 6). String
+ * parsing + bigint arithmetic so the result is exact; ROUND_HALF_UP at the
+ * rounding boundary matches the cross-language Python sibling.
+ *
+ * Rejects negative, NaN, infinite, and unparseable inputs. Fixed-notation only;
+ * scientific notation (e.g. `"1e6"`) is not parsed (mirrors the locked cross-
+ * language fixture corpus, which uses fixed notation exclusively).
+ */
+/**
+ * Convert a USD amount to atomic units for a token with `decimals` places.
+ *
+ * @param usd USD amount. Strings (`"1.23"`) and `number`s (`1.23`) are accepted.
+ *   `number` is converted via `String(usd)` before parsing, so JS float precision
+ *   limits apply when the float can't represent the value exactly.
+ * @param opts.decimals Number of decimal places in the atomic unit (6 for USDC,
+ *   18 for ETH, etc.). Must be a non-negative integer.
+ *
+ * @returns Integer atomic units as a `bigint`. `"1.23"` with `decimals: 6`
+ *   returns `1_230_000n`.
+ *
+ * @throws RangeError when `usd` is negative, NaN, infinite, or `decimals` is
+ *   not a non-negative integer.
+ * @throws SyntaxError when `usd` cannot be parsed as a fixed-notation decimal.
+ */
+declare function usdToAtomic(usd: string | number, opts: {
+    decimals: number;
+}): bigint;
+/**
+ * Format an integer cent amount as a fixed-2-decimal USD string.
+ *
+ * `formatUsdCents(500)` returns `"5.00"`. Negative values are formatted with a
+ * leading minus. Use everywhere a merchant emits `(cents / 100).toFixed(2)`;
+ * consistent formatting across catalog rows, order responses, and 402 bodies
+ * prevents agent-side string-comparison flakiness.
+ */
+declare function formatUsdCents(cents: number): string;
+
+/**
+ * Solana MPP fee-payer signer loader.
+ *
+ * Buyers paying via Solana MPP USDC don't typically carry SOL for transaction
+ * fees, so merchants commonly co-sign the buyer's `solana/charge` tx as the
+ * fee payer (~5000 lamports per tx; negligible vs the USDC value moved).
+ *
+ * `loadSolanaFeePayer({ privateKey })` accepts a Solana keypair in any of the
+ * three forms agents commonly export it as:
+ *
+ *   - **base58** (Phantom export format) — 64-byte secret+public, or 32-byte
+ *     secret-only
+ *   - **hex** — 128-char string (64 bytes hex: 32-byte secret + 32-byte public)
+ *
+ * Returns a `KeyPairSigner` from `@solana/kit` ready to pass as the `signer`
+ * field on a `SolanaMppRailSpec`. Returns `undefined` when `privateKey` is
+ * empty / absent (so consumers can use `process.env.X` directly without
+ * null-checks).
+ *
+ * Requires the `@solana/kit` peer dependency.
+ */
+declare function loadSolanaFeePayer(opts: {
+    privateKey: string | undefined;
+}): Promise<unknown | undefined>;
+
+export { formatUsdCents as f, loadSolanaFeePayer as l, usdToAtomic as u };

package/dist/stripe-multichain/index.d.mts

@@ -21,20 +21,6 @@ interface StripePaymentIntent {
     } | null;
     [key: string]: unknown;
 }
-interface CreateMultichainPaymentIntentInput {
-    /** A configured Stripe SDK instance. */
-    stripe: StripeClientLike;
-    /** Amount in cents (Stripe convention — $1.00 = 100). */
-    amount: number;
-    /** Currency code. Default 'usd'. */
-    currency?: string;
-    /** Networks to advertise to Stripe deposit_options. Default ['tempo', 'base', 'solana']. */
-    networks?: string[];
-    /** Metadata to attach to the PI (visible in Stripe dashboard). */
-    metadata?: Record<string, string>;
-    /** Idempotency key — agent retries of the same purchase won't create duplicate PIs. */
-    idempotencyKey?: string;
-}
 interface MultichainPaymentIntentResult {
     /** Stripe PaymentIntent ID. */
     paymentIntentId: string;
@@ -51,13 +37,20 @@ interface MultichainPaymentIntentResult {
  * Distinct from the Stripe SPT (Shared Payment Token) flow, which is handled via
  * `createMppxStripe` + the agent's own Stripe account or `link-cli`.
  */
-declare function createMultichainPaymentIntent(input: CreateMultichainPaymentIntentInput): Promise<MultichainPaymentIntentResult>;
-/**
- * Convenience accessor: get the deposit address for a specific network from a
- * createMultichainPaymentIntent result. Returns undefined if Stripe didn't issue
- * an address for that network.
- */
-declare function getDepositAddress(result: MultichainPaymentIntentResult, network: string): string | undefined;
+declare function createMultichainPaymentIntent({ stripe, amount, currency, networks, metadata, idempotencyKey, }: {
+    /** A configured Stripe SDK instance. */
+    stripe: StripeClientLike;
+    /** Amount in cents (Stripe convention — $1.00 = 100). */
+    amount: number;
+    /** Currency code. Default 'usd'. */
+    currency?: string;
+    /** Networks to advertise to Stripe deposit_options. Default ['tempo', 'base', 'solana']. */
+    networks?: string[];
+    /** Metadata to attach to the PI (visible in Stripe dashboard). */
+    metadata?: Record<string, string>;
+    /** Idempotency key — agent retries of the same purchase won't create duplicate PIs. */
+    idempotencyKey?: string;
+}): Promise<MultichainPaymentIntentResult>;
 
 /**
  * Stripe's documented magic test_helpers transaction hash that resolves the
@@ -73,7 +66,14 @@ declare const STRIPE_TEST_TX_HASH_SUCCESS = "0x000000000000000000000000000000000
  * (PaymentIntent returns to `requires_payment_method` within 15 seconds).
  */
 declare const STRIPE_TEST_TX_HASH_FAILED = "0x000000000000000000000000000000000000000000000000000000testfailed";
-interface SimulateCryptoDepositInput {
+/**
+ * Call Stripe's `test_helpers/payment_intents/{id}/simulate_crypto_deposit` endpoint. Used
+ * in testnet/dev to simulate a deposit landing on a PaymentIntent so the integration
+ * end-to-end can be exercised without on-chain transfers.
+ *
+ * Throws on non-2xx responses (returns Stripe's error body in the message).
+ */
+declare function simulateCryptoDeposit({ paymentIntentId, network, buyerWallet, tokenCurrency, transactionHash, stripeSecretKey, stripeVersion, stripeApiBase, extra, }: {
     /** Stripe PaymentIntent id to simulate a deposit on. */
     paymentIntentId: string;
     /** Network the simulated deposit lands on. */
@@ -92,16 +92,23 @@ interface SimulateCryptoDepositInput {
     stripeApiBase?: string;
     /** Arbitrary additional form params to merge into the request body. */
     extra?: Record<string, string>;
-}
+}): Promise<void>;
 /**
- * Call Stripe's `test_helpers/payment_intents/{id}/simulate_crypto_deposit` endpoint. Used
- * in testnet/dev to simulate a deposit landing on a PaymentIntent so the integration
- * end-to-end can be exercised without on-chain transfers.
+ * Higher-level wrapper around {@link simulateCryptoDeposit} for the testnet/dev path.
+ * Bundles the three steps every Stripe-multichain merchant repeats:
  *
- * Throws on non-2xx responses (returns Stripe's error body in the message).
+ *   1. Gate on `sk_test_` key prefix — production keys reject the test_helpers endpoint
+ *      with 400; live deposits reach Stripe's real crypto-deposit watcher instead.
+ *   2. Resolve the PaymentIntent id from the deposit address (cache lookup).
+ *   3. Call `simulate_crypto_deposit` with Stripe's documented success magic hash.
+ *
+ * Logs `[stripe] ✓ Simulated <network> deposit for PI <id>` on success and
+ * `[stripe] ✗ Failed to simulate <network> deposit for PI <id>: <err>` on failure.
+ * Errors are caught + logged (never thrown) so a sim hiccup doesn't fail the order.
+ *
+ * Use case is exclusively dev/testnet end-to-end — production servers (sk_live_) no-op.
  */
-declare function simulateCryptoDeposit(input: SimulateCryptoDepositInput): Promise<void>;
-interface SimulateDepositIfTestModeInput {
+declare function simulateDepositIfTestMode({ getPaymentIntentId, depositAddress, network, buyerWallet, tokenCurrency, stripeSecretKey, stripeVersion, }: {
     /** Stripe PaymentIntent id resolver — given a deposit address, return the PI id (or undefined
      *  if the cache TTL expired between 402 emit and settlement). Typically `cache.getPaymentIntentId`. */
     getPaymentIntentId: (depositAddress: string) => string | undefined;
@@ -117,32 +124,8 @@ interface SimulateDepositIfTestModeInput {
     stripeSecretKey: string;
     /** Stripe API version (e.g. `'2026-03-04.preview'` for the deposit-mode preview). */
     stripeVersion?: string;
-}
-/**
- * Higher-level wrapper around {@link simulateCryptoDeposit} for the testnet/dev path.
- * Bundles the three steps every Stripe-multichain merchant repeats:
- *
- *   1. Gate on `sk_test_` key prefix — production keys reject the test_helpers endpoint
- *      with 400; live deposits reach Stripe's real crypto-deposit watcher instead.
- *   2. Resolve the PaymentIntent id from the deposit address (cache lookup).
- *   3. Call `simulate_crypto_deposit` with Stripe's documented success magic hash.
- *
- * Logs `[stripe] ✓ Simulated <network> deposit for PI <id>` on success and
- * `[stripe] ✗ Failed to simulate <network> deposit for PI <id>: <err>` on failure.
- * Errors are caught + logged (never thrown) so a sim hiccup doesn't fail the order.
- *
- * Use case is exclusively dev/testnet end-to-end — production servers (sk_live_) no-op.
- */
-declare function simulateDepositIfTestMode(input: SimulateDepositIfTestModeInput): Promise<void>;
+}): Promise<void>;
 
-interface CreateMppxStripeInput {
-    /** Stripe profile_id / network_id (the value advertised in your `stripe/charge` accepted_methods entry). */
-    profileId: string;
-    /** Stripe secret key — mppx uses it to validate inbound SharedPaymentTokens. */
-    secretKey: string;
-    /** Payment method types this stripe rail accepts. Default ['card', 'link']. */
-    paymentMethodTypes?: string[];
-}
 /**
  * Wraps the `mppStripe.charge(...)` boilerplate from `mppx/server`. Returns the value
  * vendors pass into `Mppx.create({ methods: [...] })`. mppx is an OPTIONAL peer dependency —
@@ -165,7 +148,14 @@ interface CreateMppxStripeInput {
  *
  * Throws if mppx is not installed.
  */
-declare function createMppxStripe(input: CreateMppxStripeInput): Promise<unknown>;
+declare function createMppxStripe({ profileId, secretKey, paymentMethodTypes, }: {
+    /** Stripe profile_id / network_id (the value advertised in your `stripe/charge` accepted_methods entry). */
+    profileId: string;
+    /** Stripe secret key — mppx uses it to validate inbound SharedPaymentTokens. */
+    secretKey: string;
+    /** Payment method types this stripe rail accepts. Default ['card', 'link']. */
+    paymentMethodTypes?: string[];
+}): Promise<unknown>;
 
 /**
  * Stripe PaymentIntent + deposit-address cache.
@@ -191,15 +181,6 @@ declare function createMppxStripe(input: CreateMppxStripeInput): Promise<unknown
  * multi-instance deployments need a shared cache (Redis) so a deposit lands on
  * whichever instance settles it.
  */
-interface PiCacheOptions {
-    /** Redis connection URL (e.g. `rediss://…cache.amazonaws.com:6379`). When omitted,
-     *  the cache falls back to in-process Maps with the same API. */
-    redisUrl?: string;
-    /** TTL for cached entries in seconds. Default 300. */
-    ttlSeconds?: number;
-    /** Prefix for Redis keys. Default `'payto:'`. */
-    keyPrefix?: string;
-}
 interface PiCache {
     /** Mark an on-chain address as one this merchant minted. Idempotent + TTL-bounded. */
     cacheAddress(address: string): Promise<void>;
@@ -216,6 +197,14 @@ interface PiCache {
     /** Stop the background TTL-eviction loop. Call from server shutdown handlers. */
     stop(): void;
 }
-declare function createPiCache(opts?: PiCacheOptions): PiCache;
+declare function createPiCache({ redisUrl, ttlSeconds, keyPrefix, }?: {
+    /** Redis connection URL (e.g. `rediss://…cache.amazonaws.com:6379`). When omitted,
+     *  the cache falls back to in-process Maps with the same API. */
+    redisUrl?: string;
+    /** TTL for cached entries in seconds. Default 300. */
+    ttlSeconds?: number;
+    /** Prefix for Redis keys. Default `'payto:'`. */
+    keyPrefix?: string;
+}): PiCache;
 
-export { type CreateMppxStripeInput, type CreateMultichainPaymentIntentInput, type MultichainPaymentIntentResult, type PiCache, type PiCacheOptions, STRIPE_TEST_TX_HASH_FAILED, STRIPE_TEST_TX_HASH_SUCCESS, type SimulateCryptoDepositInput, type SimulateDepositIfTestModeInput, type StripeClientLike, type StripePaymentIntent, createMppxStripe, createMultichainPaymentIntent, createPiCache, getDepositAddress, simulateCryptoDeposit, simulateDepositIfTestMode };
+export { type MultichainPaymentIntentResult, type PiCache, STRIPE_TEST_TX_HASH_FAILED, STRIPE_TEST_TX_HASH_SUCCESS, type StripeClientLike, type StripePaymentIntent, createMppxStripe, createMultichainPaymentIntent, createPiCache, simulateCryptoDeposit, simulateDepositIfTestMode };

package/dist/stripe-multichain/index.d.ts

@@ -21,20 +21,6 @@ interface StripePaymentIntent {
     } | null;
     [key: string]: unknown;
 }
-interface CreateMultichainPaymentIntentInput {
-    /** A configured Stripe SDK instance. */
-    stripe: StripeClientLike;
-    /** Amount in cents (Stripe convention — $1.00 = 100). */
-    amount: number;
-    /** Currency code. Default 'usd'. */
-    currency?: string;
-    /** Networks to advertise to Stripe deposit_options. Default ['tempo', 'base', 'solana']. */
-    networks?: string[];
-    /** Metadata to attach to the PI (visible in Stripe dashboard). */
-    metadata?: Record<string, string>;
-    /** Idempotency key — agent retries of the same purchase won't create duplicate PIs. */
-    idempotencyKey?: string;
-}
 interface MultichainPaymentIntentResult {
     /** Stripe PaymentIntent ID. */
     paymentIntentId: string;
@@ -51,13 +37,20 @@ interface MultichainPaymentIntentResult {
  * Distinct from the Stripe SPT (Shared Payment Token) flow, which is handled via
  * `createMppxStripe` + the agent's own Stripe account or `link-cli`.
  */
-declare function createMultichainPaymentIntent(input: CreateMultichainPaymentIntentInput): Promise<MultichainPaymentIntentResult>;
-/**
- * Convenience accessor: get the deposit address for a specific network from a
- * createMultichainPaymentIntent result. Returns undefined if Stripe didn't issue
- * an address for that network.
- */
-declare function getDepositAddress(result: MultichainPaymentIntentResult, network: string): string | undefined;
+declare function createMultichainPaymentIntent({ stripe, amount, currency, networks, metadata, idempotencyKey, }: {
+    /** A configured Stripe SDK instance. */
+    stripe: StripeClientLike;
+    /** Amount in cents (Stripe convention — $1.00 = 100). */
+    amount: number;
+    /** Currency code. Default 'usd'. */
+    currency?: string;
+    /** Networks to advertise to Stripe deposit_options. Default ['tempo', 'base', 'solana']. */
+    networks?: string[];
+    /** Metadata to attach to the PI (visible in Stripe dashboard). */
+    metadata?: Record<string, string>;
+    /** Idempotency key — agent retries of the same purchase won't create duplicate PIs. */
+    idempotencyKey?: string;
+}): Promise<MultichainPaymentIntentResult>;
 
 /**
  * Stripe's documented magic test_helpers transaction hash that resolves the
@@ -73,7 +66,14 @@ declare const STRIPE_TEST_TX_HASH_SUCCESS = "0x000000000000000000000000000000000
  * (PaymentIntent returns to `requires_payment_method` within 15 seconds).
  */
 declare const STRIPE_TEST_TX_HASH_FAILED = "0x000000000000000000000000000000000000000000000000000000testfailed";
-interface SimulateCryptoDepositInput {
+/**
+ * Call Stripe's `test_helpers/payment_intents/{id}/simulate_crypto_deposit` endpoint. Used
+ * in testnet/dev to simulate a deposit landing on a PaymentIntent so the integration
+ * end-to-end can be exercised without on-chain transfers.
+ *
+ * Throws on non-2xx responses (returns Stripe's error body in the message).
+ */
+declare function simulateCryptoDeposit({ paymentIntentId, network, buyerWallet, tokenCurrency, transactionHash, stripeSecretKey, stripeVersion, stripeApiBase, extra, }: {
     /** Stripe PaymentIntent id to simulate a deposit on. */
     paymentIntentId: string;
     /** Network the simulated deposit lands on. */
@@ -92,16 +92,23 @@ interface SimulateCryptoDepositInput {
     stripeApiBase?: string;
     /** Arbitrary additional form params to merge into the request body. */
     extra?: Record<string, string>;
-}
+}): Promise<void>;
 /**
- * Call Stripe's `test_helpers/payment_intents/{id}/simulate_crypto_deposit` endpoint. Used
- * in testnet/dev to simulate a deposit landing on a PaymentIntent so the integration
- * end-to-end can be exercised without on-chain transfers.
+ * Higher-level wrapper around {@link simulateCryptoDeposit} for the testnet/dev path.
+ * Bundles the three steps every Stripe-multichain merchant repeats:
  *
- * Throws on non-2xx responses (returns Stripe's error body in the message).
+ *   1. Gate on `sk_test_` key prefix — production keys reject the test_helpers endpoint
+ *      with 400; live deposits reach Stripe's real crypto-deposit watcher instead.
+ *   2. Resolve the PaymentIntent id from the deposit address (cache lookup).
+ *   3. Call `simulate_crypto_deposit` with Stripe's documented success magic hash.
+ *
+ * Logs `[stripe] ✓ Simulated <network> deposit for PI <id>` on success and
+ * `[stripe] ✗ Failed to simulate <network> deposit for PI <id>: <err>` on failure.
+ * Errors are caught + logged (never thrown) so a sim hiccup doesn't fail the order.
+ *
+ * Use case is exclusively dev/testnet end-to-end — production servers (sk_live_) no-op.
  */
-declare function simulateCryptoDeposit(input: SimulateCryptoDepositInput): Promise<void>;
-interface SimulateDepositIfTestModeInput {
+declare function simulateDepositIfTestMode({ getPaymentIntentId, depositAddress, network, buyerWallet, tokenCurrency, stripeSecretKey, stripeVersion, }: {
     /** Stripe PaymentIntent id resolver — given a deposit address, return the PI id (or undefined
      *  if the cache TTL expired between 402 emit and settlement). Typically `cache.getPaymentIntentId`. */
     getPaymentIntentId: (depositAddress: string) => string | undefined;
@@ -117,32 +124,8 @@ interface SimulateDepositIfTestModeInput {
     stripeSecretKey: string;
     /** Stripe API version (e.g. `'2026-03-04.preview'` for the deposit-mode preview). */
     stripeVersion?: string;
-}
-/**
- * Higher-level wrapper around {@link simulateCryptoDeposit} for the testnet/dev path.
- * Bundles the three steps every Stripe-multichain merchant repeats:
- *
- *   1. Gate on `sk_test_` key prefix — production keys reject the test_helpers endpoint
- *      with 400; live deposits reach Stripe's real crypto-deposit watcher instead.
- *   2. Resolve the PaymentIntent id from the deposit address (cache lookup).
- *   3. Call `simulate_crypto_deposit` with Stripe's documented success magic hash.
- *
- * Logs `[stripe] ✓ Simulated <network> deposit for PI <id>` on success and
- * `[stripe] ✗ Failed to simulate <network> deposit for PI <id>: <err>` on failure.
- * Errors are caught + logged (never thrown) so a sim hiccup doesn't fail the order.
- *
- * Use case is exclusively dev/testnet end-to-end — production servers (sk_live_) no-op.
- */
-declare function simulateDepositIfTestMode(input: SimulateDepositIfTestModeInput): Promise<void>;
+}): Promise<void>;
 
-interface CreateMppxStripeInput {
-    /** Stripe profile_id / network_id (the value advertised in your `stripe/charge` accepted_methods entry). */
-    profileId: string;
-    /** Stripe secret key — mppx uses it to validate inbound SharedPaymentTokens. */
-    secretKey: string;
-    /** Payment method types this stripe rail accepts. Default ['card', 'link']. */
-    paymentMethodTypes?: string[];
-}
 /**
  * Wraps the `mppStripe.charge(...)` boilerplate from `mppx/server`. Returns the value
  * vendors pass into `Mppx.create({ methods: [...] })`. mppx is an OPTIONAL peer dependency —
@@ -165,7 +148,14 @@ interface CreateMppxStripeInput {
  *
  * Throws if mppx is not installed.
  */
-declare function createMppxStripe(input: CreateMppxStripeInput): Promise<unknown>;
+declare function createMppxStripe({ profileId, secretKey, paymentMethodTypes, }: {
+    /** Stripe profile_id / network_id (the value advertised in your `stripe/charge` accepted_methods entry). */
+    profileId: string;
+    /** Stripe secret key — mppx uses it to validate inbound SharedPaymentTokens. */
+    secretKey: string;
+    /** Payment method types this stripe rail accepts. Default ['card', 'link']. */
+    paymentMethodTypes?: string[];
+}): Promise<unknown>;
 
 /**
  * Stripe PaymentIntent + deposit-address cache.
@@ -191,15 +181,6 @@ declare function createMppxStripe(input: CreateMppxStripeInput): Promise<unknown
  * multi-instance deployments need a shared cache (Redis) so a deposit lands on
  * whichever instance settles it.
  */
-interface PiCacheOptions {
-    /** Redis connection URL (e.g. `rediss://…cache.amazonaws.com:6379`). When omitted,
-     *  the cache falls back to in-process Maps with the same API. */
-    redisUrl?: string;
-    /** TTL for cached entries in seconds. Default 300. */
-    ttlSeconds?: number;
-    /** Prefix for Redis keys. Default `'payto:'`. */
-    keyPrefix?: string;
-}
 interface PiCache {
     /** Mark an on-chain address as one this merchant minted. Idempotent + TTL-bounded. */
     cacheAddress(address: string): Promise<void>;
@@ -216,6 +197,14 @@ interface PiCache {
     /** Stop the background TTL-eviction loop. Call from server shutdown handlers. */
     stop(): void;
 }
-declare function createPiCache(opts?: PiCacheOptions): PiCache;
+declare function createPiCache({ redisUrl, ttlSeconds, keyPrefix, }?: {
+    /** Redis connection URL (e.g. `rediss://…cache.amazonaws.com:6379`). When omitted,
+     *  the cache falls back to in-process Maps with the same API. */
+    redisUrl?: string;
+    /** TTL for cached entries in seconds. Default 300. */
+    ttlSeconds?: number;
+    /** Prefix for Redis keys. Default `'payto:'`. */
+    keyPrefix?: string;
+}): PiCache;
 
-export { type CreateMppxStripeInput, type CreateMultichainPaymentIntentInput, type MultichainPaymentIntentResult, type PiCache, type PiCacheOptions, STRIPE_TEST_TX_HASH_FAILED, STRIPE_TEST_TX_HASH_SUCCESS, type SimulateCryptoDepositInput, type SimulateDepositIfTestModeInput, type StripeClientLike, type StripePaymentIntent, createMppxStripe, createMultichainPaymentIntent, createPiCache, getDepositAddress, simulateCryptoDeposit, simulateDepositIfTestMode };
+export { type MultichainPaymentIntentResult, type PiCache, STRIPE_TEST_TX_HASH_FAILED, STRIPE_TEST_TX_HASH_SUCCESS, type StripeClientLike, type StripePaymentIntent, createMppxStripe, createMultichainPaymentIntent, createPiCache, simulateCryptoDeposit, simulateDepositIfTestMode };