@atumlabs/payment-gateway-client 3.0.0 → 4.0.0

package/dist/index.d.ts

@@ -1,4 +1,6 @@
 import { AxiosRequestConfig, AxiosResponse } from 'axios';
+import { h as AuthorizePaymentData, i as AuthorizePaymentResponse, G as GetDefaultsData, j as GetDefaultsResponse, H as HealthCheckResponse, k as SubmitPaymentData, l as SubmitPaymentResponse, m as GetPaymentStatusData, n as GetPaymentStatusResponse2, R as ResolvePaymentData, o as ResolvePaymentResponse2, p as GetPaymentTimelineData, q as GetPaymentTimelineResponse, r as PreparePaymentData, s as PreparePaymentResponse2, t as CreateQuoteRequestData, u as CreateQuoteRequestResponse, w as GetQuoteRequestStatusData, x as GetQuoteRequestStatusResponse, y as AwardQuoteData, z as AwardQuoteResponse, B as SignedMessage, E as ErrorResponse, P as PaymentRequest, D as CreateQuoteRequest } from './sender-auth-verify-CEf7FN6s.js';
+export { $ as $OpenApiTs, A as AuthTerms, F as AuthorizationResult, I as AwardAccepted, J as AwardRequest, K as AwardResponse, L as AwardedPayment, M as AwardedQuote, N as BidAward, O as ChainDefaultsByChain, Q as ChainDefaultsWire, C as CommitmentOutcome, a as CommitmentResult, T as DataIntegrityProof, U as DeclineReason, W as DeclineSummaryEntry, X as FulfillmentAuthorization, Y as FulfillmentConfirmation, Z as GetDefaultsResult, _ as GetPaymentStatusResponse, a0 as OwnedAsset, b as ParsedPermit, a1 as PaymentBlockchainContext, a2 as PaymentFailure, a3 as PaymentResponse, a4 as PaymentStatus, a5 as PaymentSummary, a6 as PaymentTimelineResponse, a7 as PaymentTransaction, a8 as PaymentTransactions, a9 as PreparePaymentRequest, aa as PreparePaymentResponse, ab as Quote, ac as QuoteRequestAccepted, ad as QuoteRequestResponse, ae as QuoteRequestStatusResponse, af as RefundSignature, ag as ResolvePaymentResponse, ah as SenderAuth, ai as SenderAuthMessageScheme, S as SolanaDomain, aj as TimelineStep, ak as VerifiableCredential, al as VerifiableCredentialAuth, V as VerifiedSenderAuth, c as VerifyPaymentRequestExpectations, d as VerifyResult, am as deposit, an as domain, ao as error_code, ap as fulfill, aq as reserve, ar as scheme, as as status, at as status2, au as status3, av as status4, aw as status5, ax as status6, ay as status7 } from './sender-auth-verify-CEf7FN6s.js';
 import { Signer } from 'ethers';
 
 type ApiRequestOptions = {
@@ -73,1916 +75,6 @@ declare abstract class BaseHttpRequest {
     abstract request<T>(options: ApiRequestOptions): CancelablePromise<T>;
 }
 
-/**
- * The result of a counterparty authorization request. Contains either
- * the PSP's authorization decision (authorized/declined with proof) or
- * an error indicating why authorization could not be completed.
- *
- */
-type AuthorizationResult = {
-    /**
-     * Correlation key for this authorization
-     */
-    payment_id: string;
-    /**
-     * The beneficiary PSP's DID
-     */
-    counterparty_did: string;
-    /**
-     * Authorization outcome. "authorized" or "declined" when the PSP responded.
-     * "error" or "timeout" when the authorization could not be completed.
-     *
-     */
-    status: 'authorized' | 'declined' | 'error' | 'timeout';
-    /**
-     * The PSP's raw authorization response (present when status is authorized or declined)
-     */
-    authorization_response?: {
-        [key: string]: unknown;
-    };
-    /**
-     * Machine-readable error code (present when status is error or timeout).
-     * Counterparty-sourced codes are derived from the error code the
-     * Counterparty Gateway publishes. GATEWAY_TIMEOUT, PROOF_INVALID, and
-     * PROOF_STALE are raised by this gateway itself (no counterparty envelope corresponds).
-     *
-     */
-    error_code?: 'COUNTERPARTY_NOT_FOUND' | 'COUNTERPARTY_TIMEOUT' | 'WEBHOOK_ERROR' | 'WEBHOOK_CONNECTION_ERROR' | 'INTERNAL_ERROR' | 'GATEWAY_TIMEOUT' | 'PROOF_INVALID' | 'PROOF_STALE';
-    /**
-     * Human-readable error description
-     */
-    error_message?: string;
-    /**
-     * HTTP status code from the PSP webhook (only for WEBHOOK_ERROR)
-     */
-    webhook_http_status?: number;
-};
-/**
- * Authorization outcome. "authorized" or "declined" when the PSP responded.
- * "error" or "timeout" when the authorization could not be completed.
- *
- */
-type status = 'authorized' | 'declined' | 'error' | 'timeout';
-/**
- * Machine-readable error code (present when status is error or timeout).
- * Counterparty-sourced codes are derived from the error code the
- * Counterparty Gateway publishes. GATEWAY_TIMEOUT, PROOF_INVALID, and
- * PROOF_STALE are raised by this gateway itself (no counterparty envelope corresponds).
- *
- */
-type error_code = 'COUNTERPARTY_NOT_FOUND' | 'COUNTERPARTY_TIMEOUT' | 'WEBHOOK_ERROR' | 'WEBHOOK_CONNECTION_ERROR' | 'INTERNAL_ERROR' | 'GATEWAY_TIMEOUT' | 'PROOF_INVALID' | 'PROOF_STALE';
-/**
- * Structured payment request with sender authorization and optional W3C Verifiable Credentials
- */
-type PaymentRequest = {
-    /**
-     * Semver-shaped declaration version (MAJOR.MINOR). The major component is locked to this schema's parent directory (v1 → major must be 1). Producers MUST emit the canonical value exported by the bindings' Version constant; the canonical bumps on each additive minor evolution.
-     */
-    version: string;
-    /**
-     * Unique identifier for this payment request (used for idempotency)
-     */
-    request_id: string;
-    source: OwnedAsset;
-    /**
-     * Array of destination assets for the settlement agent to choose from (at least one required, at most 16).
-     * The ceiling bounds the fan-out one request can buy: every consumer iterates this list.
-     */
-    destination: Array<OwnedAsset>;
-    /**
-     * The exact amount to be received at the destination (in the smallest unit, e.g., wei for ETH, cents for USD).
-     */
-    fulfillment_amount: string;
-    /**
-     * The maximum amount willing to be spent from the source (in the smallest unit).
-     */
-    max_source_amount?: string;
-    /**
-     * Required. The deadline for receiving price quotes from settlement providers. After this
-     * point no new quotes are accepted. The gateway injects no default and validates the value
-     * is in the future. The originator must supply it, and a request that omits it or supplies
-     * a past value is rejected with 400.
-     */
-    quote_deadline: string;
-    /**
-     * Required. The final deadline for completing the payment. If not completed by this time the
-     * payment is cancelled and eligible for a refund. The gateway injects no default and validates
-     * the value is in the future. The originator must supply it, and a request that omits it or
-     * supplies a past value is rejected with 400.
-     */
-    fulfillment_deadline: string;
-    /**
-     * Policy requirements for settler authentication. Keys are policy names, values indicate if the policy is required.
-     */
-    settler_auth_required?: {
-        [key: string]: (boolean);
-    };
-    sender_auth: SenderAuth;
-    originator_auth?: VerifiableCredentialAuth;
-    /**
-     * Wallet address or public key of a trusted service that will automatically select
-     * the best exchange rate for your payment. Leave empty to use the default selector.
-     */
-    quote_selector?: string;
-    /**
-     * Third-party service that will independently verify your payment was delivered.
-     * Leave empty to use the default verifier.
-     */
-    fulfillment_verifier?: {
-        /**
-         * The wallet address or public key of the verification service
-         */
-        account: string;
-        /**
-         * Origin of the fulfillment verifier service, with no path — the caller
-         * appends the verifier's own API paths. The gateway's `/v1/defaults` response
-         * supplies the default fulfillment verifier for each chain.
-         */
-        endpoint: string;
-    };
-    /**
-     * Escrow contract address, used to protect source funds until proof of fulfillment has been verified. Leave empty to use the default.
-     */
-    escrow_contract_address?: string;
-    /**
-     * Fulfillment Proxy contract address, used to emit proof of fulfillment on the destination chain. Leave empty to use the default.
-     */
-    fulfillment_proxy?: string;
-    /**
-     * Optional settler filtering requirements. If whitelist is present, only whitelisted settlers may win. If blacklist is present, blacklisted settlers are excluded. Both can be specified; blacklist takes precedence (a settler in both lists is rejected).
-     */
-    settler_requirements?: {
-        /**
-         * List of settler DIDs permitted to fulfill this request. If present and non-empty, only these settlers may win. Use W3C DID format (e.g., did:pkh:eip155:1:0xABC...).
-         */
-        whitelist?: Array<(string)>;
-        /**
-         * List of settler DIDs excluded from fulfilling this request. If present and non-empty, these settlers are rejected. Use W3C DID format (e.g., did:pkh:eip155:1:0xABC...).
-         */
-        blacklist?: Array<(string)>;
-    };
-};
-/**
- * Confirmation details after a payment has been successfully delivered.
- * Contains proof of delivery and transaction details for both source and destination chains.
- *
- */
-type FulfillmentConfirmation = {
-    /**
-     * Unique identifier for this payment transaction.
-     * Use this to track the payment across all systems.
-     *
-     */
-    payment_id: string;
-    /**
-     * Your original request ID that was provided when creating the payment.
-     * Helps match confirmations to your internal systems.
-     *
-     */
-    request_id: string;
-    /**
-     * Timestamp when the fulfillment was completed
-     */
-    fulfillment_timestamp: string;
-    /**
-     * The blockchain where funds were locked in escrow, using CAIP-2 format.
-     * CAIP-2 is a standard way to identify blockchains: {namespace}:{reference}
-     * Examples:
-     * - "eip155:1" for Ethereum mainnet
-     * - "eip155:42161" for Arbitrum
-     * - "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp" for Solana
-     * - "tron:mainnet" for Tron
-     *
-     */
-    source_chain_id: string;
-    /**
-     * The blockchain where the payment was delivered, using CAIP-2 format.
-     * CAIP-2 is a standard way to identify blockchains: {namespace}:{reference}
-     * Examples:
-     * - "eip155:1" for Ethereum mainnet
-     * - "eip155:42161" for Arbitrum
-     * - "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp" for Solana
-     * - "tron:mainnet" for Tron
-     *
-     */
-    destination_chain_id: string;
-    /**
-     * Transaction hash of the escrow reservation on the source chain
-     */
-    source_tx_hash?: string;
-    /**
-     * Transaction hash of the fulfillment on the destination chain
-     */
-    destination_tx_hash?: string;
-    /**
-     * Block number where the source transaction was confirmed
-     */
-    source_block_number?: number;
-    /**
-     * Block number where the destination transaction was confirmed
-     */
-    destination_block_number?: number;
-};
-/**
- * Represents a cryptocurrency or token in a specific wallet. This tells the system what asset you're sending/receiving and which wallet to use.
- */
-type OwnedAsset = {
-    /**
-     * A unique identifier for the asset using CAIP-19 format.
-     * CAIP-19 is a standard way to identify blockchain assets: {chain_id}/{asset_namespace}:{asset_reference}
-     * Examples:
-     * - Ethereum USDC: "eip155:1/erc20:0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
-     * - Arbitrum USDC: "eip155:42161/erc20:0xaf88d065e77c8cC2239327C5EDb3A432268e5831"
-     * - Solana USDC: "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp/token:EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"
-     * - Tron USDT: "tron:mainnet/trc20:TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"
-     */
-    asset_identifier: string;
-    /**
-     * The wallet address that owns this asset.
-     * Format depends on the blockchain:
-     * - Ethereum/EVM: 0x-prefixed hex address (42 characters)
-     * - Solana: Base58 encoded address
-     * - Tron: T-prefixed Base58 address
-     *
-     * A destination account is checked at ingress and must be payable on the chain named by
-     * its `asset_identifier`: it parses for that chain, carries a valid EIP-55 checksum when
-     * mixed-case, has no surrounding whitespace, and is not the zero address. A receiver that
-     * fails any of these is refused with `INVALID_DESTINATION_ACCOUNT`, before any funds move.
-     */
-    account: string;
-};
-/**
- * Authorization from the asset owner to execute the payment. The exact format depends on the source blockchain's authorization mechanism.
- */
-type SenderAuth = {
-    /**
-     * DEPRECATED: inner-document credential carrier. Credentials MUST ride ONLY in the holder-signed PaymentRequestEnvelope (PRE); the inner PaymentRequest carries no credential and its Data Integrity signature EXCLUDES this field (stripped before canonicalization on both producer and verifier). Populated only for one back-compat rollout cycle, then removed.
-     * @deprecated
-     */
-    verifiable_credential?: VerifiableCredentialAuth;
-    message_scheme: SenderAuthMessageScheme;
-    /**
-     * Array of signed messages (at least one required)
-     */
-    signed_messages: Array<SignedMessage>;
-};
-/**
- * The signature method used for authorizing this payment:
- * - `EVM_PERMIT2`: Gasless token approvals for Ethereum/EVM chains
- * - `EVM_PERMIT2_ESCROW`: Gasless approvals with escrow support
- * - `SOLANA`: Standard Solana transaction signatures
- * - `TRON`: Tron transaction signatures
- */
-type SenderAuthMessageScheme = 'EVM_PERMIT2' | 'EVM_PERMIT2_ESCROW' | 'SOLANA' | 'TRON';
-/**
- * A message that has been cryptographically signed to prove authorization. The signature proves you control the wallet that's sending funds.
- */
-type SignedMessage = {
-    /**
-     * The data that was signed. Format depends on the blockchain:
-     * - EVM: Hex-encoded message hash (with 0x prefix)
-     * - Solana: Hex-encoded message hash (with 0x prefix)
-     * - Tron: Hex-encoded message hash (possibly without 0x prefix)
-     */
-    message: string;
-    /**
-     * Optional: If 'message' contains a hash, this field contains the original data before it was hashed. Useful for verification and debugging.
-     */
-    message_prehash?: string;
-    /**
-     * The cryptographic signature proving you authorized this message. Hex-encoded with a 0x prefix on every supported chain. The signer's own public key is base58 on Solana, but the signature itself is not.
-     */
-    signature: string;
-    /**
-     * Optional chain-specific payload containing additional signing context (e.g., delegate_signer for Solana). Preserved through the pipeline for downstream consumers.
-     */
-    payload?: {
-        [key: string]: unknown;
-    };
-};
-/**
- * Optional identity verification using cryptographic credentials.
- *
- * DEPRECATED. Credentials are moving to a holder-signed W3C VerifiablePresentation that
- * travels alongside a request rather than inside it. That envelope is not part of this
- * HTTP contract, so there is nothing here to move them to yet: treat this as a legacy
- * carrier, and do not build a new integration on it.
- */
-type VerifiableCredentialAuth = {
-    verifiable_credential: VerifiableCredential;
-    /**
-     * Reference to verification method from the DID Document
-     */
-    verification_method_id: string;
-    /**
-     * Cryptographic signature matching the verification method type
-     */
-    signature: string;
-};
-/**
- * W3C Verifiable Credential structure conforming to the W3C Verifiable Credentials Data Model v1.1
- */
-type VerifiableCredential = {
-    /**
-     * JSON-LD context array, must include 'https://www.w3.org/2018/credentials/v1'
-     */
-    '@context': Array<(string)>;
-    /**
-     * Unique identifier for this credential
-     */
-    id: string;
-    /**
-     * Credential types, must include 'VerifiableCredential'
-     */
-    type: Array<(string)>;
-    /**
-     * DID or issuer object of the credential issuer
-     */
-    issuer: string | {
-        [key: string]: unknown;
-    };
-    /**
-     * When the credential was issued
-     */
-    issuanceDate: string;
-    /**
-     * When the credential expires
-     */
-    expirationDate?: string;
-    /**
-     * Claims about the credential subject (structure varies by issuer)
-     */
-    credentialSubject: {
-        [key: string]: unknown;
-    };
-    /**
-     * Information for credential revocation checking. Not consulted by the verifier today.
-     */
-    credentialStatus?: {
-        [key: string]: unknown;
-    };
-    /**
-     * Cryptographic proof of credential integrity
-     */
-    proof: {
-        [key: string]: unknown;
-    };
-};
-/**
- * Response from submitting a payment request. If settlement completes inside the
- * gateway's synchronous window, the response includes a fulfillment_confirmation with
- * full settlement details. Otherwise you receive a payment_id plus the payment's
- * current `status`, and can poll /v1/payments/{paymentId}/status for updates.
- *
- * Read `status` before deciding what to do next: a `pending` payment is in flight and
- * must NOT be re-submitted under a new request_id (that would be a second payment),
- * whereas a `failed` or `cancelled` one is terminal — re-submitting it under the SAME
- * request_id resolves to the same terminal payment, so a genuine re-attempt needs a
- * new request_id.
- *
- * **A synchronously-completed payment carries proof of QUOTE as well as of delivery.** When
- * settlement lands inside the window you get `status: completed`, a full
- * `fulfillment_confirmation`, and — since a quote necessarily was awarded to get there —
- * `quote_id` and `fulfillment_quote`. The fast path therefore needs no follow-up call to
- * verify: recompute `quote_hash` over the returned quote and compare it against the on-chain
- * commitment from this response alone.
- *
- */
-type PaymentResponse = {
-    /**
-     * Unique ID for tracking this payment. Save this to check status later.
-     *
-     */
-    payment_id: string;
-    /**
-     * Current status of the payment, with the same meaning as on
-     * /v1/payments/{paymentId}/status:
-     * - `pending`: accepted and being processed
-     * - `completed`: successfully delivered
-     * - `failed`: failed (funds returned if escrowed)
-     * - `cancelled`: cancelled before completion
-     *
-     * Present on every response. `completed` is always accompanied by
-     * fulfillment_confirmation; `failed` is accompanied by `error` where a reason has
-     * been recorded.
-     *
-     */
-    status: 'pending' | 'completed' | 'failed' | 'cancelled';
-    /**
-     * Whether this response describes a payment that already existed, rather than one
-     * created by this request. `true` means the request_id had been used before and you
-     * are being handed the ORIGINAL payment — no second payment was created and nothing
-     * additional was charged.
-     *
-     * **Re-attempting a payment.** Re-submit the same request and you get the same payment
-     * back. You may re-send the original bytes unchanged: the deadlines will have expired by
-     * then — `quote_deadline` bounds the auction and is short, while this endpoint may hold a
-     * submission for up to 30 seconds — and an expired deadline on a re-submission is not an
-     * error, because the request is resolved onto the payment that already exists rather than
-     * used to create one.
-     *
-     * Re-signing with fresh deadlines is equally fine and returns the same payment. What you
-     * must NOT change is the request_id, and what you must not change under it is the
-     * payment's economics — source, destination, fulfillment_amount, max_source_amount — which
-     * are rejected with 409 IDEMPOTENCY_TERMS_MISMATCH. Deadlines and the signature are
-     * exempt precisely so that a re-attempt is possible.
-     *
-     * A genuinely new payment needs a NEW request_id. In particular a `failed` payment is
-     * terminal: re-submitting its request_id keeps returning that dead payment, so recovering
-     * means starting a new one under a new key.
-     *
-     * Present on every response, `false` for a newly created payment. A response without
-     * the field is from a gateway predating it, not a newly created payment.
-     *
-     * This is the field to read when reconciling a suspected double charge: two
-     * submissions where the second reports `true` are one payment, whereas two both
-     * reporting `false` are two. It says nothing about how far the payment has got —
-     * read `status` for that.
-     *
-     */
-    idempotent_replay: boolean;
-    /**
-     * The winning quote's ID. Present when `status` is `completed` — a payment cannot settle
-     * without an award — and absent on a `pending` response, where no quote has been selected
-     * yet. Same value and meaning as on GET /v1/payments/{paymentId}/status.
-     *
-     */
-    quote_id?: string;
-    /**
-     * The settler-signed FulfillmentQuote for the winning quote, returned verbatim as an
-     * opaque signed document — the PREIMAGE of the `quote_hash` committed on-chain. Same
-     * value, semantics and canonicalization caveats as on
-     * GET /v1/payments/{paymentId}/status; see that field for how to verify it.
-     *
-     * Present when `status` is `completed`. It may be absent even then, if the stored quote
-     * is unreadable: the award is reported through `quote_id` regardless, so a present
-     * `quote_id` with no `fulfillment_quote` means "verification preimage unavailable" and
-     * never "no quote was awarded". A consumer that requires the preimage should fall back to
-     * the status endpoint rather than treat the payment as unverified.
-     *
-     */
-    fulfillment_quote?: {
-        [key: string]: unknown;
-    };
-    fulfillment_confirmation?: FulfillmentConfirmation;
-    error?: PaymentError;
-};
-/**
- * Current status of the payment, with the same meaning as on
- * /v1/payments/{paymentId}/status:
- * - `pending`: accepted and being processed
- * - `completed`: successfully delivered
- * - `failed`: failed (funds returned if escrowed)
- * - `cancelled`: cancelled before completion
- *
- * Present on every response. `completed` is always accompanied by
- * fulfillment_confirmation; `failed` is accompanied by `error` where a reason has
- * been recorded.
- *
- */
-type status2 = 'pending' | 'completed' | 'failed' | 'cancelled';
-type GetPaymentStatusResponse = {
-    /**
-     * The payment ID you're checking status for.
-     *
-     */
-    payment_id?: string;
-    /**
-     * Current status of your payment:
-     * - `pending`: Payment is being processed
-     * - `completed`: Payment successfully delivered
-     * - `failed`: Payment failed (funds returned if escrowed)
-     * - `cancelled`: Payment was cancelled before completion
-     *
-     */
-    status?: 'pending' | 'completed' | 'failed' | 'cancelled';
-    /**
-     * When the status was last updated
-     */
-    updated_at?: string;
-    /**
-     * The winning quote's ID. Present once a quote has been awarded for this payment;
-     * absent while the payment is still collecting or awarding. Cross-references the
-     * `quote_id` returned by GET /v1/payments/quote-requests/{quoteRequestId}.
-     *
-     */
-    quote_id?: string;
-    /**
-     * The settler-signed FulfillmentQuote for the winning quote, returned verbatim as an
-     * opaque signed document (structurally the canonical FulfillmentQuote/v1 declaration at
-     * https://schemas.atum.xyz/declarations/FulfillmentQuote/v1). Present once a quote has
-     * been awarded — including after the payment completes and `fulfillment_confirmation` is
-     * populated, since that is precisely when a consumer verifies.
-     *
-     * This is the PREIMAGE of the `quote_hash` committed on-chain in the escrow deposit and
-     * reserve witnesses. On-chain we commit only the hash, so a quote-selector consumer
-     * recomputes quote_hash over these bytes and compares it against the on-chain commitment
-     * to confirm the payment settled against the quote it selected ("trust but verify"), and
-     * verifies the settler signature over the same bytes.
-     *
-     * quote_hash is canonicalization-based (URDNA2015), so it is stable across JSON
-     * key-order/whitespace normalization and across JSON string-escaping differences. The
-     * returned bytes are hash-equivalent to, but not necessarily byte-identical with, what
-     * the settler emitted (quotes are stored as JSONB, which normalizes on write). The
-     * gateway still never re-serializes the quote through a typed struct (that renormalizes
-     * timestamp values and WOULD change quote_hash), so the Go binding exposes it as a raw
-     * JSON passthrough.
-     *
-     */
-    fulfillment_quote?: {
-        [key: string]: unknown;
-    };
-    fulfillment_confirmation?: FulfillmentConfirmation;
-    error?: PaymentError;
-    /**
-     * How many settler agents this payment's auction was broadcast to. Absent means
-     * unknown, never zero.
-     *
-     */
-    requested_count?: number;
-    /**
-     * Why the payment drew few or no quotes. Read from the same settler reports as the
-     * quote-request endpoints, keyed by this payment, so a payment that failed on an expired
-     * quote deadline can say WHY nobody funded it instead of only that nobody did.
-     *
-     * Every declining agent is counted exactly once under its most recent reason. Empty means
-     * no agent declined against this payment, absent means the breakdown could not be read. A
-     * payment awarded out of a quote-request batch was bid on at quote time, so its declines
-     * are keyed to that batch and are read from the batch's status endpoint rather than here.
-     * As on the quote-request endpoints, the free-form decline detail is never relayed.
-     *
-     */
-    decline_summary?: Array<DeclineSummaryEntry>;
-};
-/**
- * Error details when payment status is "failed".
- * Only present when the payment has failed. Contains a machine-readable
- * code for programmatic handling and a human-readable message for debugging.
- *
- */
-type PaymentError = {
-    /**
-     * Public error category in SCREAMING_SNAKE_CASE.
-     * Common codes:
-     * - `SETTLEMENT_FAILED`: The settlement could not be completed
-     * - `NO_QUOTES_RECEIVED`: No quotes arrived within the auction window
-     * - `INTERNAL_ERROR`: An unexpected error occurred
-     *
-     */
-    code: string;
-    /**
-     * Human-readable error description with additional context.
-     *
-     */
-    message: string;
-    /**
-     * Service domain where the error originated.
-     *
-     */
-    domain?: 'PAYMENT_GATEWAY' | 'SETTLER_GATEWAY' | 'SETTLER_AGENT' | 'WALLET_ORCHESTRATION' | 'VERIFICATION_SERVICE' | 'BLOCKCHAIN' | 'EXTERNAL_SERVICE';
-    blockchain_context?: PaymentBlockchainContext;
-};
-/**
- * Service domain where the error originated.
- *
- */
-type domain = 'PAYMENT_GATEWAY' | 'SETTLER_GATEWAY' | 'SETTLER_AGENT' | 'WALLET_ORCHESTRATION' | 'VERIFICATION_SERVICE' | 'BLOCKCHAIN' | 'EXTERNAL_SERVICE';
-/**
- * Blockchain-specific error context. Only present when the error
- * originated from an on-chain operation (e.g., escrow revert,
- * fulfillment failure).
- *
- */
-type PaymentBlockchainContext = {
-    /**
-     * CAIP-2 chain identifier
-     */
-    chain_id?: string;
-    /**
-     * Failed transaction hash
-     */
-    tx_hash?: string;
-    /**
-     * Block number where error occurred
-     */
-    block_number?: number;
-    /**
-     * Contract address involved in the error
-     */
-    contract_address?: string;
-    /**
-     * Smart contract revert reason
-     */
-    revert_reason?: string;
-    /**
-     * Gas consumed before failure
-     */
-    gas_used?: string;
-    /**
-     * Estimated gas needed for success
-     */
-    estimated_gas_needed?: string;
-};
-/**
- * Human-readable payment request parameters for generating an unsigned PaymentRequest.
- * Asset identifiers use a CAIP-19-like format with "/" separator and support friendly names.
- *
- */
-type PreparePaymentRequest = {
-    /**
-     * Unique identifier for tracking this payment request.
-     * Used for idempotency and matching responses to requests.
-     *
-     */
-    request_id: string;
-    /**
-     * Source asset in human-readable CAIP-19-like format: {chain}/{asset}
-     * Supports both friendly names and full CAIP-19 identifiers:
-     * - "ethereum/usdc" (friendly names)
-     * - "eip155:1/erc20:0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48" (full CAIP-19)
-     *
-     */
-    source_asset: string;
-    /**
-     * Wallet address that will send the payment
-     */
-    source_account: string;
-    /**
-     * Destination asset in human-readable CAIP-19-like format: {chain}/{asset}
-     * Supports both friendly names and full CAIP-19 identifiers:
-     * - "arbitrum/usdc"
-     * - "eip155:42161/erc20:0xaf88d065e77c8cC2239327C5EDb3A432268e5831"
-     *
-     */
-    destination_asset: string;
-    /**
-     * Wallet address that will receive the payment
-     */
-    destination_account: string;
-    /**
-     * Simple amount specification in decimal format (e.g., "1.50" for $1.50 USDC).
-     * Use this OR specify both max_source_amount and fulfillment_amount.
-     * Cannot be used together with max_source_amount/fulfillment_amount.
-     *
-     */
-    amount?: string;
-    /**
-     * Maximum amount willing to spend from source (in decimal format).
-     * Must be specified together with fulfillment_amount.
-     * Cannot be used together with amount field.
-     *
-     */
-    max_source_amount?: string;
-    /**
-     * Exact amount to be fulfilled at destination (in decimal format).
-     * Must be specified together with max_source_amount.
-     * Cannot be used together with amount field.
-     *
-     */
-    fulfillment_amount?: string;
-    /**
-     * Seconds until quote deadline (from now).
-     * How long to wait for settlement provider quotes.
-     *
-     */
-    quote_deadline_seconds?: number;
-    /**
-     * Seconds until fulfillment deadline (from now).
-     * Final deadline for completing the payment.
-     *
-     */
-    fulfillment_deadline_seconds?: number;
-};
-/**
- * Complete unsigned PaymentRequest ready for signing.
- * Contains all resolved technical details and typed data ready for signing.
- *
- */
-type PreparePaymentResponse = {
-    /**
-     * Complete PaymentRequest with signature field set to null.
-     * Client should fill in the signature field(s) in
-     * sender_auth.signed_messages, either by signing the message_hash
-     * field in signed_messages or by using typed data signing on the
-     * message_prehash field in signed messages, and then submit the full
-     * object to POST /v1/payments.
-     *
-     */
-    payment_request: PaymentRequest;
-};
-type ResolvePaymentResponse = {
-    /**
-     * The payment ID that corresponds to the given request ID
-     */
-    payment_id: string;
-};
-/**
- * Step-by-step view of a payment's settlement lifecycle. Includes a route
- * summary, a list of steps with timings, and if the payment failed, a
- * structured error describing where and why.
- *
- */
-type PaymentTimelineResponse = {
-    payment_id: string;
-    /**
-     * High-level status:
-     * - `pending`: Bidding, awarded, or early in settlement
-     * - `settling`: Settlement in progress (on-chain steps executing)
-     * - `completed`: Payment successfully delivered
-     * - `failed`: Payment failed
-     * - `cancelled`: Payment was cancelled
-     *
-     */
-    status: 'pending' | 'settling' | 'completed' | 'failed' | 'cancelled';
-    created_at: string;
-    updated_at: string;
-    /**
-     * Total time from first step to last completed step (only set for terminal states)
-     */
-    total_duration_ms?: number;
-    summary?: PaymentSummary;
-    error?: TimelineError;
-    steps: Array<TimelineStep>;
-};
-/**
- * High-level status:
- * - `pending`: Bidding, awarded, or early in settlement
- * - `settling`: Settlement in progress (on-chain steps executing)
- * - `completed`: Payment successfully delivered
- * - `failed`: Payment failed
- * - `cancelled`: Payment was cancelled
- *
- */
-type status3 = 'pending' | 'settling' | 'completed' | 'failed' | 'cancelled';
-/**
- * Top-level context about the payment (parties, assets, amounts)
- */
-type PaymentSummary = {
-    /**
-     * CAIP-19 identifier of the source asset
-     */
-    source_asset?: string;
-    source_account?: string;
-    dest_asset?: string;
-    dest_account?: string;
-    /**
-     * Raw fulfillment amount in smallest token units
-     */
-    fulfillment_amount?: string;
-    /**
-     * Human-readable formatted amount with symbol, e.g. "1.00 USDC".
-     * Only set when the source asset's decimals are known via the token registry.
-     *
-     */
-    display_amount?: string;
-    /**
-     * Raw max source amount in smallest token units
-     */
-    max_source_amount?: string;
-    request_id?: string;
-};
-/**
- * Structured error details when a payment has failed
- */
-type TimelineError = {
-    /**
-     * Machine-readable error code
-     */
-    code: string;
-    /**
-     * Human-readable error description
-     */
-    message: string;
-    /**
-     * Which component reported the error
-     */
-    domain?: string;
-    /**
-     * CAIP-2 chain where the error occurred (if on-chain)
-     */
-    chain_id?: string;
-    /**
-     * Transaction hash of the failed on-chain attempt (if applicable)
-     */
-    tx_hash?: string;
-    /**
-     * Smart-contract revert reason (if the error was an on-chain revert)
-     */
-    revert_reason?: string;
-};
-type TimelineStep = {
-    /**
-     * Internal name of the step (matches settlement event type)
-     */
-    name: string;
-    /**
-     * Human-readable label
-     */
-    label: string;
-    /**
-     * Current status of this step:
-     * - `completed`: Step finished successfully
-     * - `in_progress`: Step currently executing
-     * - `pending`: Step hasn't started yet
-     * - `failed`: Step errored out
-     * - `skipped`: Step will never execute because an earlier step failed
-     *
-     */
-    status: 'completed' | 'in_progress' | 'pending' | 'failed' | 'skipped';
-    /**
-     * When the step completed (if it has)
-     */
-    timestamp?: string;
-    /**
-     * Time this step took, measured from the previous step
-     */
-    duration_ms?: number;
-    /**
-     * CAIP-2 chain this step happened on (if on-chain)
-     */
-    chain_id?: string;
-    /**
-     * Transaction hash associated with this step (if on-chain)
-     */
-    tx_hash?: string;
-    /**
-     * Additional step-specific data (e.g. block_number, settler, reason)
-     */
-    details?: {
-        [key: string]: unknown;
-    };
-};
-/**
- * Current status of this step:
- * - `completed`: Step finished successfully
- * - `in_progress`: Step currently executing
- * - `pending`: Step hasn't started yet
- * - `failed`: Step errored out
- * - `skipped`: Step will never execute because an earlier step failed
- *
- */
-type status4 = 'completed' | 'in_progress' | 'pending' | 'failed' | 'skipped';
-/**
- * Safe, outward-facing error. Derived from an internal error through the shared error catalog. The public code identifies the category and the message is a curated, safe description.
- *
- * A panic is caught by shared middleware that responds `{"error": "Internal server error occurred"}` instead, so a 500 is not guaranteed to carry this shape.
- */
-type ErrorResponse = {
-    /**
-     * Public, machine-readable error category in SCREAMING_SNAKE_CASE.
-     */
-    code: string;
-    /**
-     * Curated, safe, human-readable message.
-     */
-    message: string;
-    /**
-     * Correlation id to quote to support to locate the internal error record.
-     */
-    request_id?: string;
-    /**
-     * The payment this error was raised against. Absent when the error is not about a specific payment.
-     */
-    payment_id?: string;
-    /**
-     * Link to the documentation page for this public code.
-     */
-    docs_url?: string;
-    /**
-     * Originating service domain.
-     */
-    domain?: string;
-    /**
-     * What the caller should do next. Absent means the condition has not been classified, which is not the same as safe to retry.
-     * Re-sending the same `request_id` is an idempotent replay and always safe. This value is about submitting a new one, which starts a new operation. See https://docs.atum.xyz/errors for the value set.
-     */
-    retry_classification?: string;
-};
-/**
- * Request body for opening a quote-request batch. Structurally the existing PaymentRequest
- * with `sender_auth` omitted (the spend authorization is deferred to the award call); see
- * schemas/declarations/PaymentRequest/v1/schema.json.
- *
- */
-type CreateQuoteRequest = {
-    /**
-     * Semver-shaped declaration version (MAJOR.MINOR), locked to major 1 for v1. Producers emit
-     * the canonical value exported by the bindings' Version constant.
-     *
-     */
-    version: string;
-    /**
-     * Client-supplied idempotency key for this quote-request. The same request_id from the
-     * same originator returns the same quote_request_id. Independent of the award-call request_id.
-     *
-     */
-    request_id: string;
-    source: OwnedAsset;
-    /**
-     * Array of destination assets for the settlement agent to choose from (at least one required, at most 16).
-     * The ceiling bounds the fan-out one request can buy: every consumer iterates this list.
-     *
-     */
-    destination: Array<OwnedAsset>;
-    /**
-     * The exact amount to be received at the destination (smallest unit, e.g. wei or cents).
-     */
-    fulfillment_amount: string;
-    /**
-     * Optional cap on what the originator is willing to spend from source (smallest unit).
-     * Quotes with source_amount above this are filtered. No cap applied if omitted.
-     *
-     */
-    max_source_amount?: string;
-    /**
-     * Required. End of the collection window. After this point no new quotes are accepted.
-     * The gateway injects no default and never mutates the originator-supplied body, so the
-     * value is carried through verbatim to the award call. It must be supplied and must be in
-     * the future. Must be strictly earlier than fulfillment_deadline.
-     *
-     */
-    quote_deadline: string;
-    /**
-     * Required. Final deadline for completing the payment. Past it the payment is cancelled and
-     * eligible for refund. The gateway injects no default and never mutates the
-     * originator-supplied body, so the value is carried through verbatim to the award call. It
-     * must be supplied and must be in the future. Must be strictly later than quote_deadline.
-     *
-     */
-    fulfillment_deadline: string;
-    /**
-     * Policy requirements for settler authentication. Keys are policy names, values indicate if required.
-     */
-    settler_auth_required?: {
-        [key: string]: (boolean);
-    };
-    originator_auth?: VerifiableCredentialAuth;
-    /**
-     * Wallet address or public key of a trusted service that auto-selects the best rate.
-     * Leave empty to use the default selector.
-     *
-     */
-    quote_selector?: string;
-    /**
-     * Optional third-party service that independently verifies delivery. Leave empty for the default verifier.
-     */
-    fulfillment_verifier?: {
-        /**
-         * The wallet address or public key of the verification service
-         */
-        account: string;
-        /**
-         * Origin of the fulfillment verifier service, with no path — the caller
-         * appends the verifier's own API paths. The gateway's `/v1/defaults` response
-         * supplies the default fulfillment verifier for each chain.
-         *
-         */
-        endpoint: string;
-    };
-    /**
-     * Optional escrow contract address. Leave empty to use the default.
-     */
-    escrow_contract_address?: string;
-    /**
-     * Optional fulfillment-proxy contract address on the destination chain. Leave empty to use the default.
-     */
-    fulfillment_proxy?: string;
-    /**
-     * Optional settler filtering. If whitelist is present, only whitelisted settlers may win.
-     * If blacklist is present, blacklisted settlers are excluded. Both can be specified;
-     * blacklist takes precedence (a settler in both is rejected).
-     *
-     */
-    settler_requirements?: {
-        /**
-         * Settler DIDs permitted to fulfill this request (W3C DID format). If present, only these may win.
-         */
-        whitelist?: Array<(string)>;
-        /**
-         * Settler DIDs excluded from fulfilling this request (W3C DID format).
-         */
-        blacklist?: Array<(string)>;
-    };
-    /**
-     * Optional JSON-LD context URLs — present when the originator wraps the request in a W3C
-     * Data Integrity envelope so a downstream verifier can recover the signer identity.
-     *
-     */
-    '@context'?: Array<(string)>;
-    proof?: DataIntegrityProof;
-    /**
-     * Optional document-level W3C Verifiable Credentials (e.g. KnownToAtum about the request producer).
-     */
-    verifiableCredential?: Array<VerifiableCredential>;
-};
-/**
- * W3C Data Integrity proof conforming to the Data Integrity 1.0 specification. Which of jws or proofValue is required depends on the cryptosuite named in type, and that pairing is checked where the proof is verified rather than by this schema, so a document can satisfy the schema and still be refused at verification.
- */
-type DataIntegrityProof = {
-    /**
-     * Proof type identifier. ECDSA-secp256k1 (recoverable, EVM-compatible) for did:pkh:eip155:* signers; Ed25519 for did:pkh:solana:* signers.
-     */
-    type: string;
-    /**
-     * ISO 8601 timestamp when the proof was created. Canonicalize the value exactly as it appears in the raw JSON: parsing it into a date-time and re-serializing can change the spelling (Z versus +00:00), and a different spelling canonicalizes to different bytes, so the signature no longer verifies.
-     */
-    created: string;
-    /**
-     * DID URL identifying the verification method, e.g., 'did:pkh:eip155:1:0x...#blockchainAccountId' for ECDSA or 'did:pkh:solana:<chain>:<addr>#SolanaMethod2021' for Ed25519.
-     */
-    verificationMethod: string;
-    /**
-     * Purpose of the proof (e.g., assertionMethod, authentication).
-     */
-    proofPurpose: string;
-    /**
-     * Detached JWS signature in <base64url(header)>..<base64url(sig)> form, header {alg:ES256K-R, b64:false, crit:[b64]}. Required at runtime for EcdsaSecp256k1RecoverySignature2020.
-     */
-    jws?: string;
-    /**
-     * Multibase-encoded raw signature bytes. Required at runtime for Ed25519Signature2020; mutually exclusive with jws in practice.
-     */
-    proofValue?: string;
-};
-/**
- * One collected quote — the content-hash identifier plus the verbatim settler-signed FulfillmentQuote.
- */
-type Quote = {
-    /**
-     * Canonical content-hash of the signed quote bytes; identifies the quote server-side at
-     * award time. Provided as a convenience — the gateway re-derives it from
-     * bid_award.fulfillment_quote_json.
-     *
-     */
-    quote_id: string;
-    /**
-     * The settler-signed FulfillmentQuote (structurally the canonical FulfillmentQuote/v1
-     * declaration at https://schemas.atum.xyz/declarations/FulfillmentQuote/v1), returned
-     * verbatim as an opaque signed document. A client recomputes quote_hash over the returned
-     * bytes and verifies the settler signature, then re-embeds them into
-     * bid_award.fulfillment_quote_json at award. quote_hash is canonicalization-based
-     * (URDNA2015), so it is stable across JSON key-order/whitespace normalization. The
-     * returned bytes are hash-equivalent to, but not necessarily byte-identical with, what the
-     * settler emitted (quotes are stored as JSONB, which normalizes on write). The gateway
-     * still never re-serializes the quote through a typed struct (that renormalizes timestamp
-     * values and WOULD change quote_hash), so the Go binding exposes it as a raw JSON passthrough.
-     *
-     */
-    fulfillment_quote: {
-        [key: string]: unknown;
-    };
-};
-/**
- * A collected quote in the status response, annotated with its award linkage.
- */
-type AwardedQuote = {
-    quote_id: string;
-    /**
-     * The settler-signed FulfillmentQuote (structurally the canonical FulfillmentQuote/v1
-     * declaration at https://schemas.atum.xyz/declarations/FulfillmentQuote/v1), returned
-     * verbatim as an opaque signed document. A client recomputes quote_hash over the returned
-     * bytes and verifies the settler signature, then re-embeds them into
-     * bid_award.fulfillment_quote_json at award. quote_hash is canonicalization-based
-     * (URDNA2015), so it is stable across JSON key-order/whitespace normalization. The
-     * returned bytes are hash-equivalent to, but not necessarily byte-identical with, what the
-     * settler emitted (quotes are stored as JSONB, which normalizes on write). The gateway
-     * still never re-serializes the quote through a typed struct (that renormalizes timestamp
-     * values and WOULD change quote_hash), so the Go binding exposes it as a raw JSON passthrough.
-     *
-     */
-    fulfillment_quote: {
-        [key: string]: unknown;
-    };
-    /**
-     * payment_id if this quote was awarded; null otherwise. Under MVP single-award, at most
-     * one quote per batch carries a non-null value.
-     *
-     */
-    awarded_payment_id?: string | null;
-};
-/**
- * A (quote_id, payment_id) pair for an awarded quote in a batch.
- */
-type AwardedPayment = {
-    quote_id: string;
-    payment_id: string;
-};
-/**
- * Synchronous response to POST /v1/payments/quote-requests. Self-contained — the corridor
- * fields are echoed at the response root so a drop-recovery client can build the award call
- * without retaining the original request body.
- *
- * The corridor echoed here describes the batch you actually receive. On an idempotent
- * replay that is the ORIGINAL batch's corridor and window, which may differ from what you
- * just sent in the ways a retry is allowed to differ (the deadlines, and address casing).
- *
- */
-type QuoteRequestResponse = {
-    /**
-     * Gateway-generated resource ID for the batch, used in subsequent status reads and awards.
-     */
-    quote_request_id: string;
-    /**
-     * Collection-phase outcome of the create call:
-     * - `ready` — collection complete; `quotes` populated. If no settler bid, this is still
-     * `ready` with an empty `quotes` array (a successful "no quotes available" result —
-     * distinct from `expired`, which only applies to collected quotes that later lapse).
-     * - `collecting` — the sync wait cap fired before the quote deadline; poll the status endpoint for quotes.
-     * The `awarded` and `expired` lifecycle states are observed only via the status endpoint, not here.
-     *
-     */
-    status: 'collecting' | 'ready';
-    /**
-     * Whether this response describes a batch that already existed, rather than one opened
-     * by this request. `true` means the `request_id` had been used before and you are being
-     * handed the ORIGINAL batch — no second batch was opened and no second broadcast went
-     * out to settlement agents.
-     *
-     * **Re-attempting a quote-request.** Re-submit the same request and you get the same
-     * batch back. You may re-send the original bytes unchanged: `quote_deadline` bounds the
-     * collection window and is short, so it will usually have expired by the time you
-     * retry, and an expired deadline on a re-submission is not an error — the request is
-     * resolved onto the batch that already exists rather than used to open one.
-     * Re-signing with fresh deadlines is equally fine and returns the same batch.
-     *
-     * The window is NOT extended either way: it belongs to the batch, and `quote_deadline`
-     * in this response is the batch's own. Read `status` to see whether collection is
-     * still running.
-     *
-     * What you must not change under one `request_id` is the corridor's economics —
-     * accounts, assets, or amounts — which are rejected with 409
-     * IDEMPOTENCY_TERMS_MISMATCH rather than resolved onto the first batch. A genuinely
-     * different corridor needs a new `request_id`.
-     *
-     * Present on every response, `false` for a newly opened batch. A response without the
-     * field is from a gateway predating it, not a newly opened batch.
-     *
-     */
-    idempotent_replay: boolean;
-    source?: OwnedAsset;
-    destination?: Array<OwnedAsset>;
-    fulfillment_amount?: string;
-    max_source_amount?: string;
-    fulfillment_deadline?: string;
-    quote_deadline?: string;
-    /**
-     * Collected quotes. Present when status is `ready` — an empty array if no settler bid.
-     */
-    quotes?: Array<Quote>;
-    /**
-     * How many agents the request was broadcast to, so silence is distinguishable from a
-     * decline without a second call. Same meaning and same absence rule as on the status
-     * endpoint: absent means unknown, never zero.
-     *
-     */
-    requested_count?: number;
-    /**
-     * Why the request drew few or no quotes, carried here so that a `ready` response with an
-     * empty `quotes` array explains itself rather than requiring a follow-up read.
-     *
-     * Same counting rules as the status endpoint: every declining agent counted exactly once
-     * under its most recent reason, empty when nobody declined, absent when the detail could not
-     * be read. Provisional while `status` is `collecting`, because agents are still responding.
-     *
-     */
-    decline_summary?: Array<DeclineSummaryEntry>;
-};
-/**
- * Collection-phase outcome of the create call:
- * - `ready` — collection complete; `quotes` populated. If no settler bid, this is still
- * `ready` with an empty `quotes` array (a successful "no quotes available" result —
- * distinct from `expired`, which only applies to collected quotes that later lapse).
- * - `collecting` — the sync wait cap fired before the quote deadline; poll the status endpoint for quotes.
- * The `awarded` and `expired` lifecycle states are observed only via the status endpoint, not here.
- *
- */
-type status5 = 'collecting' | 'ready';
-/**
- * Asynchronous (202) response to POST /v1/payments/quote-requests. Returns the batch handle
- * plus the echoed corridor; quotes are retrieved via the status endpoint.
- *
- * The corridor echoed here describes the batch you actually receive. On an idempotent
- * replay that is the ORIGINAL batch's corridor and window, which may differ from what you
- * just sent in the ways a retry is allowed to differ (the deadlines, and address casing).
- *
- */
-type QuoteRequestAccepted = {
-    quote_request_id: string;
-    /**
-     * Always `collecting` — a constant on this response, not a report of the batch's state.
-     * On an idempotent replay the batch's window may already have closed; read
-     * GET /v1/payments/quote-requests/{quoteRequestId} for its actual state.
-     *
-     */
-    status: 'collecting';
-    /**
-     * Whether this response describes a batch that already existed, rather than one opened
-     * by this request. `true` means the `request_id` had been used before and you are being
-     * handed the ORIGINAL batch — no second batch was opened and no second broadcast went
-     * out to settlement agents.
-     *
-     * The idempotency contract is the same as on the synchronous (200) response: a
-     * re-submission may carry expired deadlines and is resolved onto the existing batch
-     * rather than rejected, the collection window is the batch's own and is not extended,
-     * and differing economics are rejected with 409 IDEMPOTENCY_TERMS_MISMATCH rather than
-     * collapsed onto the first batch.
-     *
-     * Present on every response, `false` for a newly opened batch. A response without the
-     * field is from a gateway predating it, not a newly opened batch.
-     *
-     */
-    idempotent_replay: boolean;
-    source?: OwnedAsset;
-    destination?: Array<OwnedAsset>;
-    fulfillment_amount?: string;
-    max_source_amount?: string;
-    fulfillment_deadline?: string;
-    quote_deadline?: string;
-};
-/**
- * Always `collecting` — a constant on this response, not a report of the batch's state.
- * On an idempotent replay the batch's window may already have closed; read
- * GET /v1/payments/quote-requests/{quoteRequestId} for its actual state.
- *
- */
-type status6 = 'collecting';
-/**
- * Response to GET /v1/payments/quote-requests/{quoteRequestId}. The `status` enum describes
- * the quote-request batch lifecycle and is disjoint from the payment-status enum.
- *
- */
-type QuoteRequestStatusResponse = {
-    quote_request_id: string;
-    /**
-     * Derived batch lifecycle, computed at read time (not a stored state machine). Disjoint
-     * from the payment-status enum returned by the award and payment-status endpoints.
-     * - `collecting` — collection window still open; `quotes` lists those collected so far
-     * (a quote is awardable from arrival, by its own `award_deadline`; more may arrive until
-     * `collection_close`).
-     * - `ready` — collection complete; none awarded yet; either at least one quote is still
-     * within its `award_deadline`, or no settler bid (empty `quotes` array — the successful
-     * "no quotes available" result).
-     * - `awarded` — a quote produced a payment row; no further awards accepted (MVP).
-     * - `expired` — collection closed, nothing awarded, and every collected quote is now past
-     * its `award_deadline` ("quotes lapsed"). An empty batch is `ready`, not `expired` — the
-     * two are deliberately distinct ("no quotes available" vs "quotes lapsed").
-     *
-     */
-    status: 'collecting' | 'ready' | 'awarded' | 'expired';
-    /**
-     * Collected quotes with award linkage — those collected so far while `collecting`, the full set once the window closes.
-     */
-    quotes?: Array<AwardedQuote>;
-    /**
-     * Flat list of awarded (quote_id, payment_id) pairs. At most one entry under MVP single-award.
-     */
-    payments?: Array<AwardedPayment>;
-    /**
-     * How many agents the request was broadcast to. The only auction count that is not
-     * derivable from the rest of this response:
-     *
-     * - quoted = `quotes` length
-     * - declined = sum of `decline_summary[].count`
-     * - participated = quoted + declined
-     * - silent = `requested_count` - participated
-     *
-     * Silence and a decline are different signals, which is why the denominator is surfaced
-     * rather than left implicit.
-     *
-     * ABSENT when the number is unknown, which happens when the broadcast count was never
-     * recorded or when the auction detail could not be read. Absence means unknown, never zero,
-     * so `silent` is derivable only when this field is present.
-     *
-     */
-    requested_count?: number;
-    /**
-     * Why the request drew few or no quotes, so a caller can tell "nobody can fund this right
-     * now" from "my request was malformed".
-     *
-     * EXHAUSTIVE over agents: every agent that declined is counted exactly once, under its most
-     * recent reason, so the counts sum to the number of agents that declined. An agent that
-     * declined more than once with different reasons is counted once, not once per reason.
-     *
-     * Empty means nobody declined. ABSENT means the auction detail could not be read, so the
-     * breakdown is unknown. While `status` is `collecting` it is provisional, because agents are
-     * still responding.
-     *
-     * The free-form decline detail is never relayed, because that detail carries an agent's
-     * balances and would let a caller map inventory by polling cheap quote-requests across
-     * corridors.
-     *
-     */
-    decline_summary?: Array<DeclineSummaryEntry>;
-};
-/**
- * Derived batch lifecycle, computed at read time (not a stored state machine). Disjoint
- * from the payment-status enum returned by the award and payment-status endpoints.
- * - `collecting` — collection window still open; `quotes` lists those collected so far
- * (a quote is awardable from arrival, by its own `award_deadline`; more may arrive until
- * `collection_close`).
- * - `ready` — collection complete; none awarded yet; either at least one quote is still
- * within its `award_deadline`, or no settler bid (empty `quotes` array — the successful
- * "no quotes available" result).
- * - `awarded` — a quote produced a payment row; no further awards accepted (MVP).
- * - `expired` — collection closed, nothing awarded, and every collected quote is now past
- * its `award_deadline` ("quotes lapsed"). An empty batch is `ready`, not `expired` — the
- * two are deliberately distinct ("no quotes available" vs "quotes lapsed").
- *
- */
-type status7 = 'collecting' | 'ready' | 'awarded' | 'expired';
-type DeclineSummaryEntry = {
-    reason: DeclineReason;
-    /**
-     * Agents whose most recent decline reason was this one. Counts agents, never rows, and an
-     * agent appears under one reason only.
-     *
-     */
-    count: number;
-    /**
-     * What would have to change for a settler giving this reason to bid, drawn from the same
-     * closed set as the `retry_classification` on an error response so a caller reads one
-     * vocabulary.
-     *
-     * It describes the decline only. The authoritative instruction for the payment is the
-     * `retry_classification` on its own error response: a payment can fail for a reason no
-     * settler named, and it can succeed while some settlers declined.
-     *
-     * Optional, and a pattern-constrained string for the same reason `DeclineReason` is.
-     *
-     */
-    retry_classification?: string;
-};
-/**
- * A settler's reason for not bidding, projected from its internal reason code through
- * the shared decline catalog (`apis/decline/v1/catalog.json`), which is the single
- * source of truth for the reason set. Several internal codes may map to one public
- * reason.
- *
- * Deliberately a pattern-constrained string rather than a closed enum. The set grows
- * whenever a settler gains a cause worth naming, and a consumer whose generated client
- * closes the set rejects the whole response on a value it has not seen. Treat an
- * unrecognised value as `OTHER`.
- *
- * `OTHER` covers a reason whose detail is settler-authored free text, and any reason
- * this gateway does not recognise. Both are counted so the summary stays exhaustive,
- * without relaying text we neither author nor validate.
- *
- */
-type DeclineReason = string;
-/**
- * Request body for POST /v1/payments/awards. Carries the two originator-signed artifacts:
- * `sender_auth` (Permit2 deposit authorization) and a fully-formed `bid_award` declaration.
- * The awarded quote is derived server-side from bid_award.fulfillment_quote_json — no
- * explicit quote_id on the wire.
- *
- */
-type AwardRequest = {
-    /**
-     * Client-supplied idempotency key for this award call. Independent of the quote-request's request_id.
-     */
-    request_id: string;
-    sender_auth: SenderAuth;
-    bid_award: BidAward;
-};
-/**
- * Fully-formed, originator-signed bid award. Mirrors schemas/declarations/BidAward/v1/schema.json.
- * `authorization` carries the Escrow reserve-witness signature naming the chosen settler;
- * `fulfillment_quote_json` is the verbatim settler-signed quote string received in the quote
- * response (carrying the settler's proof).
- *
- */
-type BidAward = {
-    /**
-     * Semver-shaped declaration version (MAJOR.MINOR), locked to major 1 for v1. Producers emit
-     * the canonical value exported by the bindings' Version constant.
-     *
-     */
-    version: string;
-    authorization: SignedMessage;
-    /**
-     * The settler-signed FulfillmentQuote received in the quote response, forwarded verbatim.
-     * Verification is canonicalization-based — the settler's W3C Data Integrity proof is checked
-     * over the canonicalized form, and `quote_id` is derived as the canonical content-hash — so a
-     * JSON decode/re-encode that only changes key order or whitespace does not invalidate it.
-     * Clients SHOULD still forward the received bytes as-is rather than rebuild the object; the
-     * SDK helpers do this and also expose settler-proof verification.
-     *
-     */
-    fulfillment_quote_json: string;
-    /**
-     * Optional JSON-LD context URLs when the award is wrapped in a W3C Data Integrity envelope.
-     */
-    '@context'?: Array<(string)>;
-    proof?: DataIntegrityProof;
-    /**
-     * Optional W3C Verifiable Credentials attesting the award producer.
-     */
-    verifiableCredential?: Array<VerifiableCredential>;
-};
-/**
- * Synchronous response to POST /v1/payments/awards. The `status` field describes the payment
- * lifecycle. Note there are two distinct status surfaces for a Quote-API payment, with
- * different vocabularies: (1) this award response (`awarding`/`completed`/…), and
- * (2) the separate GET /v1/payments/{paymentId}/status endpoint you poll afterward, which
- * reports the same payment under its own values (an in-progress payment reads as `pending`
- * there). Both are disjoint from the quote-request batch status on the quote-request endpoints.
- *
- */
-type AwardResponse = {
-    payment_id: string;
-    /**
-     * Payment lifecycle status on the award response:
-     * - `completed` — settlement finished within the sync wait (includes fulfillment_confirmation).
-     * - `awarding` — settlement still in progress when the sync cap fired (or on wait=false);
-     * poll GET /v1/payments/{paymentId}/status.
-     * - `failed` — settlement reached a terminal failure (e.g. the settler could not fulfill, or
-     * an on-chain step was rejected).
-     * - `cancelled` — the payment was terminated before settlement completed and will not proceed.
-     * `failed` and `cancelled` are terminal states surfaced here only when they occur within the
-     * sync wait; otherwise the response is `awarding` and the terminal state is read from the
-     * payment-status endpoint.
-     *
-     */
-    status: 'awarding' | 'completed' | 'failed' | 'cancelled';
-    fulfillment_confirmation?: FulfillmentConfirmation;
-};
-/**
- * Payment lifecycle status on the award response:
- * - `completed` — settlement finished within the sync wait (includes fulfillment_confirmation).
- * - `awarding` — settlement still in progress when the sync cap fired (or on wait=false);
- * poll GET /v1/payments/{paymentId}/status.
- * - `failed` — settlement reached a terminal failure (e.g. the settler could not fulfill, or
- * an on-chain step was rejected).
- * - `cancelled` — the payment was terminated before settlement completed and will not proceed.
- * `failed` and `cancelled` are terminal states surfaced here only when they occur within the
- * sync wait; otherwise the response is `awarding` and the terminal state is read from the
- * payment-status endpoint.
- *
- */
-type status8 = 'awarding' | 'completed' | 'failed' | 'cancelled';
-/**
- * Asynchronous (202) response to POST /v1/payments/awards — just the payment handle.
- */
-type AwardAccepted = {
-    payment_id: string;
-    /**
-     * Always `awarding` — settlement is in progress server-side.
-     */
-    status: 'awarding';
-};
-/**
- * Always `awarding` — settlement is in progress server-side.
- */
-type status9 = 'awarding';
-/**
- * The addresses for one chain. Optional fields appear only where they apply to that
- * chain; an absent optional field is not an error.
- *
- */
-type ChainDefaults$1 = {
-    /**
-     * CAIP-2 identifier of the chain these defaults describe, normalised to lower case.
-     */
-    chain_id: string;
-    /**
-     * The account named as the reserver in the deposit authorization. Sign against this exact value; a deposit reserved by anyone else is rejected.
-     */
-    quote_selector: string;
-    /**
-     * The escrow the deposit is made into, and the spender of the token approval. Empty when the chain is not fully configured.
-     */
-    escrow_contract: string;
-    /**
-     * The contract that pays the receiver. Read this from the DESTINATION chain's defaults, not the source chain's. Empty when the chain is not fully configured.
-     */
-    fulfillment_proxy: string;
-    /**
-     * The service that attests settlement, and the account it signs with.
-     */
-    fulfillment_verifier: {
-        /**
-         * The account named as the releaser in the deposit authorization. Sign against this exact value.
-         */
-        account: string;
-        /**
-         * Base URL of the fulfillment verifier serving this chain.
-         */
-        endpoint: string;
-    };
-    /**
-     * The Permit2 this chain's escrow verifies against, sent only when it is not the canonical deployment. When absent, use the canonical Permit2 address for the chain. EVM and Tron only.
-     */
-    permit2_contract?: string;
-    /**
-     * Which deposit witness this chain's escrow expects. `4` and above select the four-member witness, `3` the two-member one; absent means four. EVM and Tron only - on Solana this is carried by `svm_signature_domain_version`.
-     */
-    deposit_witness_version?: number;
-    /**
-     * Tokens this chain's escrow accepts for deposit. Absent when the gateway has no listing for the chain, which does not mean no token is accepted.
-     */
-    tokens?: Array<{
-        symbol: string;
-        /**
-         * Token contract address, in the chain's native address format.
-         */
-        address: string;
-        /**
-         * Decimal places, for converting a human amount to base units.
-         */
-        decimals: number;
-    }>;
-    /**
-     * Solana only. The cluster the escrow's signing domain is bound to, needed to build the deposit hash. Absent for EVM and Tron.
-     */
-    svm_signature_cluster_id?: string;
-    /**
-     * Solana only. Version of the escrow's signing domain. Absent for EVM and Tron.
-     */
-    svm_signature_domain_version?: number;
-};
-/**
- * Either one chain's defaults or every chain keyed by CAIP-2 chain id, depending on whether `chain_id` was supplied. A top-level `chain_id` identifies the first.
- */
-type GetDefaultsResult = ChainDefaults$1 | ChainDefaultsByChain;
-/**
- * Defaults for every chain the gateway serves, keyed by CAIP-2 chain id. Each key repeats the `chain_id` of the value it maps to.
- */
-type ChainDefaultsByChain = {
-    [key: string]: ChainDefaults$1;
-};
-type SubmitPaymentData = {
-    requestBody: PaymentRequest;
-};
-type SubmitPaymentResponse = PaymentResponse;
-type GetPaymentStatusData = {
-    /**
-     * The ID of the payment to query
-     */
-    paymentId: string;
-};
-type GetPaymentStatusResponse2 = GetPaymentStatusResponse;
-type ResolvePaymentData = {
-    /**
-     * The client-supplied request ID embedded in the payment request
-     */
-    requestId: string;
-};
-type ResolvePaymentResponse2 = ResolvePaymentResponse;
-type GetPaymentTimelineData = {
-    /**
-     * The ID of the payment to query
-     */
-    paymentId: string;
-};
-type GetPaymentTimelineResponse = PaymentTimelineResponse;
-type PreparePaymentData = {
-    requestBody: PreparePaymentRequest;
-};
-type PreparePaymentResponse2 = PreparePaymentResponse;
-type AuthorizePaymentData = {
-    requestBody: PaymentRequest;
-};
-type AuthorizePaymentResponse = AuthorizationResult;
-type CreateQuoteRequestData = {
-    requestBody: CreateQuoteRequest;
-    /**
-     * Return a handle immediately (`false`, default) or hold the connection for collected quotes (`true`).
-     */
-    wait?: boolean;
-};
-type CreateQuoteRequestResponse = QuoteRequestResponse | QuoteRequestAccepted;
-type GetQuoteRequestStatusData = {
-    /**
-     * The ID of the quote-request batch to query
-     */
-    quoteRequestId: string;
-};
-type GetQuoteRequestStatusResponse = QuoteRequestStatusResponse;
-type AwardQuoteData = {
-    requestBody: AwardRequest;
-    /**
-     * Return a handle immediately (`false`, default) or hold the connection for the payment result (`true`).
-     */
-    wait?: boolean;
-};
-type AwardQuoteResponse = AwardResponse | AwardAccepted;
-type GetDefaultsData = {
-    /**
-     * CAIP-2 chain identifier. Omit it, or send it empty, to receive every chain the gateway serves, keyed by chain id.
-     */
-    chainId?: string;
-};
-type GetDefaultsResponse = GetDefaultsResult;
-type HealthCheckResponse = {
-    status?: string;
-};
-type $OpenApiTs = {
-    '/v1/payments': {
-        post: {
-            req: SubmitPaymentData;
-            res: {
-                /**
-                 * Payment request submitted successfully
-                 */
-                200: PaymentResponse;
-                /**
-                 * Invalid request
-                 */
-                400: ErrorResponse;
-                /**
-                 * Signature or sender authorization could not be verified
-                 */
-                401: ErrorResponse;
-                /**
-                 * Payment declined during counterparty authorization
-                 */
-                403: ErrorResponse;
-                /**
-                 * The `request_id` has already been used for a payment with different economics
-                 * (`IDEMPOTENCY_TERMS_MISMATCH`). Re-submitting one `request_id` is how a retry is
-                 * made safe, so it must identify one payment; use a distinct `request_id` per
-                 * payment.
-                 *
-                 */
-                409: ErrorResponse;
-                /**
-                 * Payment request too large to process
-                 */
-                413: ErrorResponse;
-                /**
-                 * Internal server error
-                 */
-                500: ErrorResponse;
-                /**
-                 * The request was not accepted: a dependency is temporarily unavailable, or this operation is paused (`SERVICE_PAUSED`). Nothing was submitted, so the request is safe to retry.
-                 */
-                503: ErrorResponse;
-            };
-        };
-    };
-    '/v1/payments/{paymentId}/status': {
-        get: {
-            req: GetPaymentStatusData;
-            res: {
-                /**
-                 * Payment status retrieved successfully
-                 */
-                200: GetPaymentStatusResponse;
-                /**
-                 * Payment not found
-                 */
-                404: ErrorResponse;
-                /**
-                 * Internal server error
-                 */
-                500: ErrorResponse;
-            };
-        };
-    };
-    '/v1/payments/resolve': {
-        get: {
-            req: ResolvePaymentData;
-            res: {
-                /**
-                 * Payment found
-                 */
-                200: ResolvePaymentResponse;
-                /**
-                 * Missing request_id parameter
-                 */
-                400: ErrorResponse;
-                /**
-                 * No payment found for the given request ID
-                 */
-                404: ErrorResponse;
-                /**
-                 * Internal server error
-                 */
-                500: ErrorResponse;
-            };
-        };
-    };
-    '/v1/payments/{paymentId}/timeline': {
-        get: {
-            req: GetPaymentTimelineData;
-            res: {
-                /**
-                 * Timeline retrieved successfully
-                 */
-                200: PaymentTimelineResponse;
-                /**
-                 * Payment not found
-                 */
-                404: ErrorResponse;
-                /**
-                 * Internal server error
-                 */
-                500: ErrorResponse;
-            };
-        };
-    };
-    '/v1/payments/prepare': {
-        post: {
-            req: PreparePaymentData;
-            res: {
-                /**
-                 * Payment request prepared successfully
-                 */
-                200: PreparePaymentResponse;
-                /**
-                 * Invalid request parameters
-                 */
-                400: ErrorResponse;
-                /**
-                 * Endpoint not yet implemented
-                 */
-                501: ErrorResponse;
-            };
-        };
-    };
-    '/v1/payments/authorizations': {
-        post: {
-            req: AuthorizePaymentData;
-            res: {
-                /**
-                 * Authorization decision received (authorized or declined)
-                 */
-                200: AuthorizationResult;
-                /**
-                 * The request was rejected before authorization was attempted, so no
-                 * authorization outcome exists.
-                 *
-                 */
-                400: ErrorResponse;
-                /**
-                 * The counterparty's proof was rejected (`PROOF_INVALID` or `PROOF_STALE`).
-                 * This is an authorization outcome, so the body is an `AuthorizationResult`
-                 * with `status: error`.
-                 *
-                 */
-                401: AuthorizationResult;
-                /**
-                 * Counterparty not found (no registration for the resolved DID). An
-                 * authorization outcome, so the body is an `AuthorizationResult` with
-                 * `status: error` and `error_code: COUNTERPARTY_NOT_FOUND`.
-                 *
-                 */
-                404: AuthorizationResult;
-                /**
-                 * Either shape, depending on where the failure happened. A failure before
-                 * authorization was attempted returns `ErrorResponse`. A failure carrying an
-                 * authorization outcome returns `AuthorizationResult` with `status: error`.
-                 *
-                 */
-                500: ErrorResponse | AuthorizationResult;
-                /**
-                 * Counterparty webhook error (HTTP error or connection failure). An
-                 * authorization outcome, so the body is an `AuthorizationResult` with
-                 * `status: error` and `error_code: WEBHOOK_ERROR` or
-                 * `WEBHOOK_CONNECTION_ERROR`.
-                 *
-                 */
-                502: AuthorizationResult;
-                /**
-                 * Authorization timed out (the counterparty did not respond). An
-                 * authorization outcome, so the body is an `AuthorizationResult` with
-                 * `status: timeout`.
-                 *
-                 */
-                504: AuthorizationResult;
-            };
-        };
-    };
-    '/v1/payments/quote-requests': {
-        post: {
-            req: CreateQuoteRequestData;
-            res: {
-                /**
-                 * Quote-request resolved synchronously. `status` is `ready` when quotes were collected,
-                 * or `collecting` when the sync wait cap fired before the quote deadline.
-                 *
-                 */
-                200: QuoteRequestResponse;
-                /**
-                 * Quote-request accepted; collection continues asynchronously.
-                 */
-                202: QuoteRequestAccepted;
-                /**
-                 * Invalid request. `QUOTE_DEADLINE_NOT_FUTURE` is the one worth planning for: a NEW
-                 * quote-request whose `quote_deadline` has already passed is refused, because there is
-                 * no window left to collect quotes in. It does not apply to a re-submission — an
-                 * already-used `request_id` resolves onto the batch that exists and its expired
-                 * deadline is ignored, which is what makes a retry recoverable.
-                 *
-                 */
-                400: ErrorResponse;
-                /**
-                 * The `request_id` has already been used for a quote-request with different
-                 * economics (`IDEMPOTENCY_TERMS_MISMATCH`). Re-submitting one `request_id` is how a
-                 * retry is made safe, so it must identify one batch; use a distinct `request_id`
-                 * per quote-request.
-                 *
-                 */
-                409: ErrorResponse;
-                /**
-                 * Internal server error
-                 */
-                500: ErrorResponse;
-                /**
-                 * The request was not accepted: a dependency is temporarily unavailable, or this operation is paused (`SERVICE_PAUSED`). Nothing was submitted, so the request is safe to retry.
-                 */
-                503: ErrorResponse;
-            };
-        };
-    };
-    '/v1/payments/quote-requests/{quoteRequestId}': {
-        get: {
-            req: GetQuoteRequestStatusData;
-            res: {
-                /**
-                 * Quote-request status retrieved successfully
-                 */
-                200: QuoteRequestStatusResponse;
-                /**
-                 * Quote-request not found, or not owned by the caller.
-                 */
-                404: ErrorResponse;
-                /**
-                 * Internal server error
-                 */
-                500: ErrorResponse;
-            };
-        };
-    };
-    '/v1/payments/awards': {
-        post: {
-            req: AwardQuoteData;
-            res: {
-                /**
-                 * Award resolved synchronously. `status` is `completed` with a fulfillment_confirmation
-                 * when settlement finished within the sync wait, or a non-terminal payment status
-                 * (e.g. `awarding`) if the cap fired first.
-                 *
-                 */
-                200: AwardResponse;
-                /**
-                 * Award accepted; settlement continues asynchronously.
-                 */
-                202: AwardAccepted;
-                /**
-                 * Invalid request (bad signatures, expired quote, or ownership mismatch)
-                 */
-                400: ErrorResponse;
-                /**
-                 * The quote, or another quote in the same batch, has already been awarded
-                 * (single-award-per-batch, FR-09).
-                 *
-                 */
-                409: ErrorResponse;
-                /**
-                 * Internal server error
-                 */
-                500: ErrorResponse;
-            };
-        };
-    };
-    '/v1/defaults': {
-        get: {
-            req: GetDefaultsData;
-            res: {
-                /**
-                 * Chain defaults. A single object when `chain_id` was supplied, otherwise an object keyed by CAIP-2 chain id.
-                 */
-                200: GetDefaultsResult;
-                /**
-                 * The `chain_id` is not a valid CAIP-2 chain identifier
-                 */
-                400: ErrorResponse;
-                /**
-                 * The requested chain is not served by this gateway, or - when `chain_id` was omitted - no chain could be resolved at all
-                 */
-                404: ErrorResponse;
-                /**
-                 * A dependency is temporarily unavailable
-                 */
-                503: ErrorResponse;
-            };
-        };
-    };
-    '/health': {
-        get: {
-            res: {
-                /**
-                 * Service is healthy
-                 */
-                200: {
-                    status?: string;
-                };
-            };
-        };
-    };
-};
-
 declare class PaymentsService {
     readonly httpRequest: BaseHttpRequest;
     constructor(httpRequest: BaseHttpRequest);
@@ -2284,25 +376,17 @@ interface ChainDefaults {
     fulfillmentProxy: string;
     permit2Contract?: string;
     /**
-     * Which deposit witness the escrow deployed on this chain pins, surfaced by payment-gw
-     * `/v1/defaults` as `deposit_witness_version` (CORE-2033). EVM/Tron only — Solana carries the
-     * same fact in `svmSignatureDomainVersion` below.
-     *
-     * `4` and above select the CORE-2120 four-member witness
-     * (`depositRequestHash`, `destination`, `reserver`, `releaser`); `3` selects the two-member
-     * witness a not-yet-redeployed escrow pins. ABSENT means four — see the sender-auth package's
-     * `ChainDefaults.depositWitnessVersion` for why absence is the permissive default.
-     *
-     * Passed through to the sender_auth adapter verbatim; this type only has to carry it.
-     */
-    depositWitnessVersion?: number;
-    /**
-     * V3 Solana escrow domain-separation fields, surfaced by payment-gw
-     * `/v1/defaults` for Solana source chains. Used to build the EscrowDomain that the
-     * V3 deposit hash binds to. Absent for EVM/Tron.
+     * Solana escrow domain-separation fields, used to build the EscrowDomain the deposit hash
+     * binds to. Absent for EVM/Tron.
      */
     svmSignatureClusterId?: string;
     svmSignatureDomainVersion?: number;
+    /**
+     * The depositRequestHash version to sign for a deposit from this chain: 1, keccak256 of the
+     * request_id, or 2, the hash of the request's terms. `preparePaymentRequest` signs v2 only for 2;
+     * absent, 1 or a version this build does not know signs v1.
+     */
+    depositRequestHashVersion?: number;
 }
 
 interface Logger {
@@ -2434,6 +518,8 @@ declare function createSenderSigner(sourceChainId: string, opts: SenderSignerOpt
  */
 declare function resolveTurnkeyAddresses(cfg: Omit<TurnkeyConfig, 'pinnedAddress'>): Promise<Record<string, string>>;
 
+declare const VERSION = "1.3";
+
 /**
  * CAIP-19 asset identifier parsing, backing the caller-facing entry points.
  *
@@ -2496,6 +582,20 @@ declare function parseAssetIdentifier(value: unknown): ParsedAssetIdentifier;
  */
 declare function assetChainId(value: unknown): string;
 
+/**
+ * Derive a `max_source_amount` from a settler's quoted `source_amount` plus a slippage
+ * tolerance in basis points.
+ *
+ * Input and output are both in the SOURCE token's smallest units: the exchange rate is already
+ * inside the quote, so no decimals or price are needed and none are guessed. The result rounds
+ * up, because a cap one unit below quote-plus-tolerance would refuse the fill the caller agreed to.
+ *
+ * @param sourceAmount The quoted `source_amount`, a positive integer in source smallest units.
+ * @param slippageBps Headroom above the quote, whole basis points in [0, 10000].
+ * @returns The cap as a canonical base-10 integer string.
+ */
+declare function capFromQuote(sourceAmount: string | bigint, slippageBps: number): string;
+
 /**
  * The frozen rejection taxonomy. These strings are part of the cross-language contract: Go must
  * reject the same input with the same reason.
@@ -2560,7 +660,7 @@ declare const $AuthorizationResult: {
 declare const $PaymentRequest: {
     readonly description: "Structured payment request with sender authorization and optional W3C Verifiable Credentials";
     readonly type: "object";
-    readonly required: readonly ["version", "request_id", "source", "destination", "fulfillment_amount", "sender_auth", "quote_deadline", "fulfillment_deadline"];
+    readonly required: readonly ["version", "request_id", "source", "destination", "fulfillment_amount", "sender_auth", "quote_deadline", "fulfillment_deadline", "fulfillment_verifier", "escrow_contract_address"];
     readonly properties: {
         readonly version: {
             readonly type: "string";
@@ -2598,15 +698,40 @@ declare const $PaymentRequest: {
         readonly quote_deadline: {
             readonly type: "string";
             readonly format: "date-time";
-            readonly description: "Required. The deadline for receiving price quotes from settlement providers. After this\npoint no new quotes are accepted. The gateway injects no default and validates the value\nis in the future. The originator must supply it, and a request that omits it or supplies\na past value is rejected with 400.";
+            readonly description: "Required. The deadline for receiving price quotes from settlement providers. After this\npoint no new quotes are accepted. The gateway injects no default and validates the value\nis in the future. The originator must supply it, and a request that omits it or supplies\na past value is rejected with 400.\n\nKeep this window short. A settler holds its quoted price for a limited period of its\nown choosing, and the gateway selects only once the window has closed, so a deadline\nset beyond that hold leaves no quote still awardable and the request is declined with\nQUOTE_WINDOW_TOO_LONG. That hold is set by each settler and is not part of this\ncontract, so treat 60 seconds as a practical upper bound and prefer a shorter window\nwhere your integration allows.";
             readonly example: "2024-12-25T10:30:00Z";
         };
         readonly fulfillment_deadline: {
             readonly type: "string";
             readonly format: "date-time";
-            readonly description: "Required. The final deadline for completing the payment. If not completed by this time the\npayment is cancelled and eligible for a refund. The gateway injects no default and validates\nthe value is in the future. The originator must supply it, and a request that omits it or\nsupplies a past value is rejected with 400.";
+            readonly description: "Required. The final deadline for completing the payment. If not completed by this time the\npayment fails and is eligible for a refund. The gateway injects no default and validates\nthe value is in the future. The originator must supply it, and a request that omits it or\nsupplies a past value is rejected with 400.";
             readonly example: "2024-12-25T11:00:00Z";
         };
+        readonly executor: {
+            readonly description: "Who performs each leg of the payment. Omitted on the wire means settler for every leg. The split object keeps deposit, reserve, and fulfill as separate keys.";
+            readonly oneOf: readonly [{
+                readonly type: "string";
+                readonly enum: readonly ["settler", "originator"];
+            }, {
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["deposit", "reserve", "fulfill"];
+                readonly properties: {
+                    readonly deposit: {
+                        readonly type: "string";
+                        readonly enum: readonly ["settler", "originator"];
+                    };
+                    readonly reserve: {
+                        readonly type: "string";
+                        readonly enum: readonly ["settler", "originator"];
+                    };
+                    readonly fulfill: {
+                        readonly type: "string";
+                        readonly enum: readonly ["settler", "originator"];
+                    };
+                };
+            }];
+        };
         readonly settler_auth_required: {
             readonly type: "object";
             readonly description: "Policy requirements for settler authentication. Keys are policy names, values indicate if the policy is required.";
@@ -2627,7 +752,7 @@ declare const $PaymentRequest: {
         };
         readonly fulfillment_verifier: {
             readonly type: "object";
-            readonly description: "Third-party service that will independently verify your payment was delivered.\nLeave empty to use the default verifier.";
+            readonly description: "The verification service that confirms the payment was delivered before the escrow\nreleases the source funds, and the account it signs with. Required on every chain:\nthe gateway's `/v1/defaults` response supplies it for each chain.";
             readonly required: readonly ["account", "endpoint"];
             readonly properties: {
                 readonly account: {
@@ -2645,7 +770,7 @@ declare const $PaymentRequest: {
         };
         readonly escrow_contract_address: {
             readonly type: "string";
-            readonly description: "Escrow contract address, used to protect source funds until proof of fulfillment has been verified. Leave empty to use the default.";
+            readonly description: "Escrow contract on the source chain that holds the source funds until proof of fulfillment has been verified. Required on every chain. Take the value for the source chain from the payment gateway's GET /v1/defaults (`escrow_contract`).";
             readonly example: "0x742D35cC6634c0532925a3b844Bc9e7595F41360";
         };
         readonly fulfillment_proxy: {
@@ -2685,10 +810,54 @@ declare const $PaymentRequest: {
         };
     };
 };
+declare const $FulfillmentAuthorization: {
+    readonly description: "Authorization for an originator to fulfill a payment request. The settler produces this declaration after authorizeFulfillment when the payment request's fulfill executor is \"originator\". A settler fulfill does not produce it.\n\nCanonical JSON Schema: schemas/declarations/FulfillmentAuthorization/v1/schema.json\nPublished at https://schemas.atum.xyz/declarations/FulfillmentAuthorization/v1";
+    readonly type: "object";
+    readonly additionalProperties: false;
+    readonly required: readonly ["version", "scheme", "authorization", "fulfillment_quote_json", "evidence"];
+    readonly properties: {
+        readonly version: {
+            readonly type: "string";
+            readonly description: "Semver-shaped declaration version (MAJOR.MINOR). The major component is locked to this schema's parent directory (v1 → major must be 1).";
+            readonly pattern: "^1\\.[0-9]+$";
+            readonly example: "1.0";
+        };
+        readonly scheme: {
+            readonly type: "string";
+            readonly description: "Authorization scheme.";
+            readonly enum: readonly ["EIP-3009"];
+        };
+        readonly authorization: {
+            readonly description: "Signed authorization. For scheme EIP-3009, message_prehash is the EIP-712 TransferWithAuthorization typed data as a JSON string ({domain, types, primaryType, message}, with uint256 values as decimal strings), message is its EIP-712 digest, signature is the settler's 65-byte signature over that digest, and payload is absent. message.validBefore is the payment request's fulfillment_deadline in whole unix seconds, and message.nonce is the fulfillment quote hash.";
+            readonly $ref: "#/components/schemas/SignedMessage";
+        };
+        readonly fulfillment_quote_json: {
+            readonly type: "string";
+            readonly description: "Raw JSON of the fulfillment quote (schemas/declarations/FulfillmentQuote/v1/schema.json), including proof metadata so its canonical quote hash can be computed.";
+        };
+        readonly evidence: {
+            readonly type: "object";
+            readonly description: "Pointer to the on-chain evidence of the fulfillment authorization.";
+            readonly additionalProperties: false;
+            readonly required: readonly ["transaction_id", "log_index"];
+            readonly properties: {
+                readonly transaction_id: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Chain transaction identifier. EVM transactions are 0x-prefixed hex, Tron transactions are hex without that prefix, and Solana transactions are base58.";
+                };
+                readonly log_index: {
+                    readonly type: "integer";
+                    readonly minimum: 0;
+                };
+            };
+        };
+    };
+};
 declare const $FulfillmentConfirmation: {
     readonly type: "object";
     readonly description: "Confirmation details after a payment has been successfully delivered.\nContains proof of delivery and transaction details for both source and destination chains.\n";
-    readonly required: readonly ["payment_id", "request_id", "fulfillment_timestamp", "source_chain_id", "destination_chain_id"];
+    readonly required: readonly ["payment_id", "request_id", "source_chain_id", "destination_chain_id", "source_tx_hash", "destination_tx_hash"];
     readonly properties: {
         readonly payment_id: {
             readonly type: "string";
@@ -2795,12 +964,12 @@ declare const $SignedMessage: {
     readonly properties: {
         readonly message: {
             readonly type: "string";
-            readonly description: "The data that was signed. Format depends on the blockchain:\n- EVM: Hex-encoded message hash (with 0x prefix)\n- Solana: Hex-encoded message hash (with 0x prefix)\n- Tron: Hex-encoded message hash (possibly without 0x prefix)";
+            readonly description: "The data that was signed, hex-encoded with a 0x prefix on every supported chain. For the deposit (signed_messages[0]) it is the 32-byte hash of message_prehash.";
             readonly example: "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef";
         };
         readonly message_prehash: {
             readonly type: "string";
-            readonly description: "Optional: If 'message' contains a hash, this field contains the original data before it was hashed. Useful for verification and debugging.";
+            readonly description: "The original data that `message` is the hash of. Required on every entry of a payment\nrequest's `sender_auth.signed_messages`: the gateway reads the signed terms from it.";
             readonly example: "{\"permit\":{\"token\":\"0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48\",\"amount\":\"1000000\"}}";
         };
         readonly signature: {
@@ -2896,9 +1065,82 @@ declare const $VerifiableCredential: {
         };
     };
 };
+declare const $PaymentStatus: {
+    readonly type: "string";
+    readonly description: "Where your payment is in its lifecycle. One payment reads the same however you ask\nabout it.\n\n- `pending`: accepted and in progress. Nothing has reached the recipient yet.\n- `finalizing`: the transaction paying your recipient is on chain and is accruing\n  the confirmations its chain requires. NOT FINAL, see below.\n- `completed`: delivered, with the required confirmations behind it.\n- `failed`: did not complete. Any funds held in escrow are returned, and `error`\n  describes what went wrong.\n- `refunding`: the settler will not deliver this payment and your funds are being\n  returned from escrow. NOT FINAL: it becomes `refund_available` or `refunded`, and it\n  can still become `completed` or `failed`.\n- `refund_available`: the settler did not deliver and the refund is authorized for you\n  to submit. GET /v1/payments/{paymentId}/status returns `refund_signature`, which you\n  submit to the source escrow to return your funds. The other responses report this\n  status without the signature. NOT FINAL: the funds are still in escrow, so it becomes\n  `refunded` once the refund lands, or `completed` if the settler delivers late and is\n  paid first. Do not pay again while it is `refund_available`.\n- `refunded`: your funds were returned from the source escrow. `transactions.refund` is\n  the refund transaction, when it is known.\n\n`completed`, `failed` and `refunded` are final and will not change afterwards.\n`pending`, `finalizing`, `refunding` and `refund_available` will.\n\n**Do not treat `finalizing` as delivered.** It says the payment has been made on\nchain but is not yet irreversible, much as a card authorization is not yet a\nsettlement. It normally becomes `completed`, and it can still become `failed` if\nthe transaction never reaches the confirmation depth its chain requires. Acting on\n`finalizing` — releasing goods, crediting an account — means accepting that risk\ndeliberately, at whatever threshold suits you rather than the one we wait for.\n\n`finalizing` is about paying the recipient. While your own funds are still being\ncommitted on the source chain the payment is `pending`, because nothing has reached\nthe recipient yet.\n";
+    readonly enum: readonly ["pending", "finalizing", "completed", "failed", "refunding", "refund_available", "refunded"];
+    readonly example: "pending";
+};
+declare const $PaymentTransaction: {
+    readonly type: "object";
+    readonly description: "One on-chain transaction belonging to a payment: which chain, which transaction, and\nwhich block it landed in.\n\nWhether the payment has actually happened is answered by `status`, not here. Read this\nto look the transaction up on chain and to verify it yourself.\n";
+    readonly required: readonly ["transaction_hash", "chain_id"];
+    readonly properties: {
+        readonly transaction_hash: {
+            readonly type: "string";
+            readonly description: "The transaction's hash on its chain. Hex hashes carry the `0x` prefix, including on\nTron, whose own tooling omits it.\n";
+            readonly pattern: "^(0x[a-fA-F0-9]{64}|[1-9A-HJ-NP-Za-km-z]{32,88})$";
+            readonly example: "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef";
+        };
+        readonly chain_id: {
+            readonly type: "string";
+            readonly description: "CAIP-2 identifier of the chain the transaction is on.";
+            readonly pattern: "^[a-z0-9]+:[a-zA-Z0-9_-]+$";
+            readonly example: "eip155:42161";
+        };
+        readonly block_number: {
+            readonly type: "integer";
+            readonly description: "The block the transaction landed in. Absent until it has been mined.\n\nProvisional while `status` is `finalizing`: on a chain that settles against another,\na reorganization there can move the transaction to a different block. Settled once\n`status` is `completed` — keep it as a final record only from then.\n";
+            readonly example: 61234567;
+        };
+    };
+};
+declare const $PaymentTransactions: {
+    readonly type: "object";
+    readonly description: "The transactions a payment has produced, one entry per stage, added as each becomes\nknown. A stage absent here has produced no transaction yet.\n\nThese are the movements that decide whether your payment happened: your funds being\ncommitted, your recipient being paid, and your funds being returned when the payment\nis refunded. Present on every outcome, so a payment that did not complete can still be\ntraced on chain.\n`fulfillment_confirmation` is not a substitute: it is written only once a payment\ncompletes, and describes the finished delivery rather than progress towards it.\n\nWhere a stage is attempted more than once, the entry describes the attempt that\ncounts — the one that succeeded, or the last one if none did.\n";
+    readonly properties: {
+        readonly deposit: {
+            readonly allOf: readonly [{
+                readonly $ref: "#/components/schemas/PaymentTransaction";
+            }];
+            readonly description: "Committing your funds on the source chain.";
+        };
+        readonly fulfillment: {
+            readonly allOf: readonly [{
+                readonly $ref: "#/components/schemas/PaymentTransaction";
+            }];
+            readonly description: "Paying your recipient on the destination chain.";
+        };
+        readonly refund: {
+            readonly allOf: readonly [{
+                readonly $ref: "#/components/schemas/PaymentTransaction";
+            }];
+            readonly description: "Returning your funds from the escrow on the source chain. Can be absent on a\n`refunded` payment when the refund transaction is not known.\n";
+        };
+    };
+};
+declare const $RefundSignature: {
+    readonly type: "object";
+    readonly description: "The refund authorization for a `refund_available` payment, as the verifier signed it.\nSubmit it to the source chain's escrow `refund` to return your funds yourself.\n\nAnyone holding it can submit the refund, but the escrow only ever pays the depositor. If\nthe settler delivers late and is paid first, the refund no longer goes through.\nOn Solana the submitter also receives the rent of the deposit account the refund closes.\n";
+    readonly required: readonly ["signature", "message_hash", "message_prehash"];
+    readonly properties: {
+        readonly signature: {
+            readonly type: "string";
+            readonly description: "The verifier's signature over `message_hash`. Hex with the `0x` prefix on EVM and\nTron chains, hex without it on Solana.\n";
+        };
+        readonly message_hash: {
+            readonly type: "string";
+            readonly description: "The signed digest, hex without the `0x` prefix.";
+        };
+        readonly message_prehash: {
+            readonly type: "string";
+            readonly description: "The signed message as JSON. On EVM and Tron chains it carries the RefundWitness the\nescrow's `refund` takes.\n";
+        };
+    };
+};
 declare const $PaymentResponse: {
     readonly type: "object";
-    readonly description: "Response from submitting a payment request. If settlement completes inside the\ngateway's synchronous window, the response includes a fulfillment_confirmation with\nfull settlement details. Otherwise you receive a payment_id plus the payment's\ncurrent `status`, and can poll /v1/payments/{paymentId}/status for updates.\n\nRead `status` before deciding what to do next: a `pending` payment is in flight and\nmust NOT be re-submitted under a new request_id (that would be a second payment),\nwhereas a `failed` or `cancelled` one is terminal — re-submitting it under the SAME\nrequest_id resolves to the same terminal payment, so a genuine re-attempt needs a\nnew request_id.\n\n**A synchronously-completed payment carries proof of QUOTE as well as of delivery.** When\nsettlement lands inside the window you get `status: completed`, a full\n`fulfillment_confirmation`, and — since a quote necessarily was awarded to get there —\n`quote_id` and `fulfillment_quote`. The fast path therefore needs no follow-up call to\nverify: recompute `quote_hash` over the returned quote and compare it against the on-chain\ncommitment from this response alone.\n";
+    readonly description: "Response from submitting a payment request. If settlement completes inside the\ngateway's synchronous window, the response includes a fulfillment_confirmation with\nfull settlement details. Otherwise you receive a payment_id plus the payment's\ncurrent `status`, and can poll /v1/payments/{paymentId}/status for updates.\n\nRead `status` before deciding what to do next: a `pending` or `finalizing` payment is\nin flight and must NOT be re-submitted under a new request_id (that would be a second\npayment), whereas a `failed` one is terminal — re-submitting it under the SAME\nrequest_id resolves to the same terminal payment, so a genuine re-attempt needs a\nnew request_id.\n\n**A synchronously-completed payment carries proof of QUOTE as well as of delivery.** When\nsettlement lands inside the window you get `status: completed`, a full\n`fulfillment_confirmation`, and — since a quote necessarily was awarded to get there —\n`quote_id` and `fulfillment_quote`. The fast path therefore needs no follow-up call to\nverify: recompute `quote_hash` over the returned quote and compare it against the on-chain\ncommitment from this response alone.\n\n`status` is present on every response. `completed` is always accompanied by\nfulfillment_confirmation; `failed` is accompanied by `error` where a reason has been\nrecorded.\n";
     readonly required: readonly ["payment_id", "status", "idempotent_replay"];
     readonly properties: {
         readonly payment_id: {
@@ -2907,9 +1149,10 @@ declare const $PaymentResponse: {
             readonly example: "0x761989729fefb4b0cb8b3e6f787301a3878c91e8fba35ed362a079292879f34f";
         };
         readonly status: {
-            readonly type: "string";
-            readonly enum: readonly ["pending", "completed", "failed", "cancelled"];
-            readonly description: "Current status of the payment, with the same meaning as on\n/v1/payments/{paymentId}/status:\n- `pending`: accepted and being processed\n- `completed`: successfully delivered\n- `failed`: failed (funds returned if escrowed)\n- `cancelled`: cancelled before completion\n\nPresent on every response. `completed` is always accompanied by\nfulfillment_confirmation; `failed` is accompanied by `error` where a reason has\nbeen recorded.\n";
+            readonly $ref: "#/components/schemas/PaymentStatus";
+        };
+        readonly transactions: {
+            readonly $ref: "#/components/schemas/PaymentTransactions";
         };
         readonly idempotent_replay: {
             readonly type: "boolean";
@@ -2929,8 +1172,31 @@ declare const $PaymentResponse: {
         readonly fulfillment_confirmation: {
             readonly $ref: "#/components/schemas/FulfillmentConfirmation";
         };
+        readonly fulfillment_authorization: {
+            readonly type: "object";
+            readonly description: "The settler-signed FulfillmentAuthorization for this payment, returned verbatim as an\nopaque signed document (structurally the canonical FulfillmentAuthorization/v1 declaration at\nhttps://schemas.atum.xyz/declarations/FulfillmentAuthorization/v1; see also\n`#/components/schemas/FulfillmentAuthorization`). The inner declaration requires\n`version`, `scheme`, `authorization` (the signed EIP-3009 transfer, in `authorization.message_prehash`), `fulfillment_quote_json`,\nand `evidence` (the on-chain authorizeFulfillment transaction). On the wire the settler\ntypically wraps that declaration in JSON-LD with `@context`, `type`, and `proof` — those\nenvelope fields ride alongside the declaration and MUST be preserved byte-for-byte.\n\nPresent when the settler authorized an originator fulfill. Mutually exclusive with\n`fulfillment_confirmation` until the originator fulfills: when this field is populated,\n`fulfillment_confirmation` is absent.\n\nThe service returns these bytes verbatim and does not re-serialize through a typed\nrepresentation (which would normalize timestamps and reorder JSON-LD envelope fields).\n";
+            readonly 'x-go-type': "json.RawMessage";
+        };
         readonly error: {
-            readonly $ref: "#/components/schemas/PaymentError";
+            readonly $ref: "#/components/schemas/PaymentFailure";
+        };
+        readonly refund_reason: {
+            readonly allOf: readonly [{
+                readonly $ref: "#/components/schemas/PaymentFailure";
+            }];
+            readonly description: "Why the settler did not deliver, as it reported when it gave up. Present only when\n`status` is `refunding`, `refund_available` or `refunded`, and absent when the refund\nstarted without a reason from the settler. `status` decides what to do next: its\n`retry_classification` and `request_id_reusable` describe the settler's error, not\nthis payment, and never mean paying again while it is `refunding` or `refund_available`.\n";
+        };
+        readonly requested_count: {
+            readonly type: "integer";
+            readonly description: "How many settler agents this payment's auction was broadcast to. Accompanies\n`decline_summary` and is present under the same condition. Same meaning and same\nabsence rule as on GET /v1/payments/{paymentId}/status: absent means unknown, never\nzero.\n";
+            readonly example: 8;
+        };
+        readonly decline_summary: {
+            readonly type: "array";
+            readonly description: "Why the payment drew few or no quotes, carried on the submission response so that a\n`failed` payment explains itself here rather than requiring a follow-up read. A\npayment that ran out its quote deadline reports `NO_QUOTES_RECEIVED` on `error`;\nthis is what the settlers actually said.\n\nPresent when `status` is `failed`, alongside `error`. A submission rejected before\nits auction opened is answered as an error response rather than this type and carries\nno breakdown, and GET /v1/payments/{paymentId}/status reports the breakdown in every\nstate.\n\nSame counting rules as GET /v1/payments/{paymentId}/status: every declining agent is\ncounted exactly once under its most recent reason, empty means no agent declined,\nabsent means the breakdown could not be read. The free-form decline detail is never\nrelayed.\n";
+            readonly items: {
+                readonly $ref: "#/components/schemas/DeclineSummaryEntry";
+            };
         };
     };
 };
@@ -2943,9 +1209,10 @@ declare const $GetPaymentStatusResponse: {
             readonly example: "0x761989729fefb4b0cb8b3e6f787301a3878c91e8fba35ed362a079292879f34f";
         };
         readonly status: {
-            readonly type: "string";
-            readonly enum: readonly ["pending", "completed", "failed", "cancelled"];
-            readonly description: "Current status of your payment:\n- `pending`: Payment is being processed\n- `completed`: Payment successfully delivered\n- `failed`: Payment failed (funds returned if escrowed)\n- `cancelled`: Payment was cancelled before completion\n";
+            readonly $ref: "#/components/schemas/PaymentStatus";
+        };
+        readonly transactions: {
+            readonly $ref: "#/components/schemas/PaymentTransactions";
         };
         readonly updated_at: {
             readonly type: "string";
@@ -2965,8 +1232,25 @@ declare const $GetPaymentStatusResponse: {
         readonly fulfillment_confirmation: {
             readonly $ref: "#/components/schemas/FulfillmentConfirmation";
         };
+        readonly fulfillment_authorization: {
+            readonly type: "object";
+            readonly description: "The settler-signed FulfillmentAuthorization for this payment, returned verbatim as an\nopaque signed document (structurally the canonical FulfillmentAuthorization/v1 declaration at\nhttps://schemas.atum.xyz/declarations/FulfillmentAuthorization/v1; see also\n`#/components/schemas/FulfillmentAuthorization`). The inner declaration requires\n`version`, `scheme`, `authorization` (the signed EIP-3009 transfer, in `authorization.message_prehash`), `fulfillment_quote_json`,\nand `evidence` (the on-chain authorizeFulfillment transaction). On the wire the settler\ntypically wraps that declaration in JSON-LD with `@context`, `type`, and `proof` — those\nenvelope fields ride alongside the declaration and MUST be preserved byte-for-byte.\n\nPresent when the settler authorized an originator fulfill. Mutually exclusive with\n`fulfillment_confirmation` until the originator fulfills: when this field is populated,\n`fulfillment_confirmation` is absent.\n\nThe service returns these bytes verbatim and does not re-serialize through a typed\nrepresentation (which would normalize timestamps and reorder JSON-LD envelope fields).\n";
+            readonly 'x-go-type': "json.RawMessage";
+        };
         readonly error: {
-            readonly $ref: "#/components/schemas/PaymentError";
+            readonly $ref: "#/components/schemas/PaymentFailure";
+        };
+        readonly refund_reason: {
+            readonly allOf: readonly [{
+                readonly $ref: "#/components/schemas/PaymentFailure";
+            }];
+            readonly description: "Why the settler did not deliver, as it reported when it gave up. Present only when\n`status` is `refunding`, `refund_available` or `refunded`, and absent when the refund\nstarted without a reason from the settler. `status` decides what to do next: its\n`retry_classification` and `request_id_reusable` describe the settler's error, not\nthis payment, and never mean paying again while it is `refunding` or `refund_available`.\n";
+        };
+        readonly refund_signature: {
+            readonly allOf: readonly [{
+                readonly $ref: "#/components/schemas/RefundSignature";
+            }];
+            readonly description: "Present only when `status` is `refund_available`.";
         };
         readonly requested_count: {
             readonly type: "integer";
@@ -2982,27 +1266,42 @@ declare const $GetPaymentStatusResponse: {
         };
     };
 };
-declare const $PaymentError: {
+declare const $PaymentFailure: {
     readonly type: "object";
-    readonly description: "Error details when payment status is \"failed\".\nOnly present when the payment has failed. Contains a machine-readable\ncode for programmatic handling and a human-readable message for debugging.\n";
+    readonly description: "Why a payment failed, or why its settler gave up. As `error` it is present only when\n`status` is `failed`, as `refund_reason` only on the refund statuses, and it is identical\nhowever you ask about the payment.\n\n`code` is the stable, machine-readable identity of the failure — branch on it\nrather than on `message`, which is written for a person and may be reworded.\n`docs_url` points at the page describing that code.\n";
     readonly required: readonly ["code", "message"];
     readonly properties: {
         readonly code: {
             readonly type: "string";
-            readonly description: "Public error category in SCREAMING_SNAKE_CASE.\nCommon codes:\n- `SETTLEMENT_FAILED`: The settlement could not be completed\n- `NO_QUOTES_RECEIVED`: No quotes arrived within the auction window\n- `INTERNAL_ERROR`: An unexpected error occurred\n";
+            readonly description: "Public error category in SCREAMING_SNAKE_CASE. Common codes:\n- `SETTLEMENT_FAILED`: the settlement could not be completed\n- `NO_QUOTES_RECEIVED`: no quotes arrived within the auction window\n- `INTERNAL_ERROR`: an unexpected error occurred\n";
             readonly example: "SETTLEMENT_FAILED";
         };
         readonly message: {
             readonly type: "string";
-            readonly description: "Human-readable error description with additional context.\n";
+            readonly description: "Human-readable description of the failure, for a person reading it. Do not\nbranch on this text.\n";
             readonly example: "No quotes received within the auction window";
         };
         readonly domain: {
             readonly type: "string";
-            readonly description: "Service domain where the error originated.\n";
+            readonly description: "Which part of the system reported the failure.\n";
             readonly enum: readonly ["PAYMENT_GATEWAY", "SETTLER_GATEWAY", "SETTLER_AGENT", "WALLET_ORCHESTRATION", "VERIFICATION_SERVICE", "BLOCKCHAIN", "EXTERNAL_SERVICE"];
             readonly example: "PAYMENT_GATEWAY";
         };
+        readonly docs_url: {
+            readonly type: "string";
+            readonly format: "uri";
+            readonly description: "Link to the documentation page for this public code.";
+        };
+        readonly retry_classification: {
+            readonly type: "string";
+            readonly description: "What the caller should do next. Absent means the condition has not been classified, which is not the same as safe to retry.\nRe-sending the same `request_id` is an idempotent replay and always safe. This value is about submitting a new one, which starts a new payment. See https://docs.atum.xyz/errors for the value set.";
+            readonly example: "RECONCILE_THEN_DECIDE";
+        };
+        readonly request_id_reusable: {
+            readonly type: "boolean";
+            readonly description: "Whether the caller may re-send the `request_id` this payment was created under. On this shape it is almost always false, because a payment exists by definition, but it is carried rather than assumed so a caller reads the same field here as on a synchronous error. Absent means undetermined, which a caller should read as false.";
+            readonly example: false;
+        };
         readonly blockchain_context: {
             readonly $ref: "#/components/schemas/PaymentBlockchainContext";
         };
@@ -3010,44 +1309,45 @@ declare const $PaymentError: {
 };
 declare const $PaymentBlockchainContext: {
     readonly type: "object";
-    readonly description: "Blockchain-specific error context. Only present when the error\noriginated from an on-chain operation (e.g., escrow revert,\nfulfillment failure).\n";
+    readonly description: "Where on chain a failed payment failed. Present only when the failure happened\non chain — an escrow revert, or a fulfillment that could not be delivered — so a\npayment that failed before any transaction was sent carries no context here.";
     readonly properties: {
         readonly chain_id: {
             readonly type: "string";
             readonly description: "CAIP-2 chain identifier";
-            readonly example: "eip155:42161";
+            readonly pattern: "^[a-z0-9]+:[a-zA-Z0-9_-]+$";
         };
-        readonly tx_hash: {
+        readonly transaction_hash: {
             readonly type: "string";
             readonly description: "Failed transaction hash";
-            readonly example: "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef";
+            readonly pattern: "^(0x[a-fA-F0-9]{64}|[1-9A-HJ-NP-Za-km-z]{32,88})$";
         };
         readonly block_number: {
             readonly type: "integer";
             readonly description: "Block number where error occurred";
-            readonly example: 12345678;
         };
         readonly contract_address: {
             readonly type: "string";
-            readonly description: "Contract address involved in the error";
-            readonly example: "0x1234567890abcdef1234567890abcdef12345678";
+            readonly description: "Contract that caused the error";
+            readonly pattern: "^(0x[a-fA-F0-9]{40}|[1-9A-HJ-NP-Za-km-z]{32,44})$";
         };
         readonly revert_reason: {
             readonly type: "string";
             readonly description: "Smart contract revert reason";
-            readonly example: "Insufficient balance";
         };
         readonly gas_used: {
             readonly type: "string";
             readonly description: "Gas consumed before failure";
-            readonly example: "21000";
         };
         readonly estimated_gas_needed: {
             readonly type: "string";
             readonly description: "Estimated gas needed for success";
-            readonly example: "50000";
         };
     };
+    readonly 'x-go-type': "atumerror.BlockchainContext";
+    readonly 'x-go-type-import': {
+        readonly name: "atumerror";
+        readonly path: "github.com/atum-labs/protocol/schemas/apis/error/v1/bindings/go";
+    };
 };
 declare const $PreparePaymentRequest: {
     readonly type: "object";
@@ -3097,8 +1397,8 @@ declare const $PreparePaymentRequest: {
         readonly quote_deadline_seconds: {
             readonly type: "integer";
             readonly description: "Seconds until quote deadline (from now).\nHow long to wait for settlement provider quotes.\n";
-            readonly default: 10;
-            readonly example: 10;
+            readonly default: 3;
+            readonly example: 3;
         };
         readonly fulfillment_deadline_seconds: {
             readonly type: "integer";
@@ -3140,9 +1440,10 @@ declare const $PaymentTimelineResponse: {
             readonly example: "0x8b73c3c69bb8fe3d512ecc4cf759cc79239f7b179b0ffacaa9a75d522b39400f";
         };
         readonly status: {
-            readonly type: "string";
-            readonly enum: readonly ["pending", "settling", "completed", "failed", "cancelled"];
-            readonly description: "High-level status:\n- `pending`: Bidding, awarded, or early in settlement\n- `settling`: Settlement in progress (on-chain steps executing)\n- `completed`: Payment successfully delivered\n- `failed`: Payment failed\n- `cancelled`: Payment was cancelled\n";
+            readonly $ref: "#/components/schemas/PaymentStatus";
+        };
+        readonly transactions: {
+            readonly $ref: "#/components/schemas/PaymentTransactions";
         };
         readonly created_at: {
             readonly type: "string";
@@ -3161,7 +1462,13 @@ declare const $PaymentTimelineResponse: {
             readonly $ref: "#/components/schemas/PaymentSummary";
         };
         readonly error: {
-            readonly $ref: "#/components/schemas/TimelineError";
+            readonly $ref: "#/components/schemas/PaymentFailure";
+        };
+        readonly refund_reason: {
+            readonly allOf: readonly [{
+                readonly $ref: "#/components/schemas/PaymentFailure";
+            }];
+            readonly description: "Why the settler did not deliver, as it reported when it gave up. Present only when\n`status` is `refunding`, `refund_available` or `refunded`, and absent when the refund\nstarted without a reason from the settler. `status` decides what to do next: its\n`retry_classification` and `request_id_reusable` describe the settler's error, not\nthis payment, and never mean paying again while it is `refunding` or `refund_available`.\n";
         };
         readonly steps: {
             readonly type: "array";
@@ -3213,40 +1520,6 @@ declare const $PaymentSummary: {
         };
     };
 };
-declare const $TimelineError: {
-    readonly type: "object";
-    readonly description: "Structured error details when a payment has failed";
-    readonly required: readonly ["code", "message"];
-    readonly properties: {
-        readonly code: {
-            readonly type: "string";
-            readonly description: "Machine-readable error code";
-            readonly example: "ESCROW_DEPOSIT_FAILED";
-        };
-        readonly message: {
-            readonly type: "string";
-            readonly description: "Human-readable error description";
-        };
-        readonly domain: {
-            readonly type: "string";
-            readonly description: "Which component reported the error";
-            readonly example: "SETTLER_AGENT";
-        };
-        readonly chain_id: {
-            readonly type: "string";
-            readonly description: "CAIP-2 chain where the error occurred (if on-chain)";
-            readonly example: "eip155:1";
-        };
-        readonly tx_hash: {
-            readonly type: "string";
-            readonly description: "Transaction hash of the failed on-chain attempt (if applicable)";
-        };
-        readonly revert_reason: {
-            readonly type: "string";
-            readonly description: "Smart-contract revert reason (if the error was an on-chain revert)";
-        };
-    };
-};
 declare const $TimelineStep: {
     readonly type: "object";
     readonly required: readonly ["name", "label", "status"];
@@ -3281,7 +1554,7 @@ declare const $TimelineStep: {
             readonly description: "CAIP-2 chain this step happened on (if on-chain)";
             readonly example: "eip155:1";
         };
-        readonly tx_hash: {
+        readonly transaction_hash: {
             readonly type: "string";
             readonly description: "Transaction hash associated with this step (if on-chain)";
         };
@@ -3334,12 +1607,17 @@ declare const $ErrorResponse: {
             readonly description: "What the caller should do next. Absent means the condition has not been classified, which is not the same as safe to retry.\nRe-sending the same `request_id` is an idempotent replay and always safe. This value is about submitting a new one, which starts a new operation. See https://docs.atum.xyz/errors for the value set.";
             readonly example: "RECONCILE_THEN_DECIDE";
         };
+        readonly request_id_reusable: {
+            readonly type: "boolean";
+            readonly description: "Whether the caller may re-send this same request_id. True means no payment was created for it, so the id is still free. False means a payment exists for it, so the id is spent and re-sending only replays this outcome. Absent means undetermined, which a caller should read as false. Separate from retry_classification, which answers what the caller must change rather than whether the id survived.";
+            readonly example: false;
+        };
     };
 };
 declare const $CreateQuoteRequest: {
     readonly type: "object";
     readonly description: "Request body for opening a quote-request batch. Structurally the existing PaymentRequest\nwith `sender_auth` omitted (the spend authorization is deferred to the award call); see\nschemas/declarations/PaymentRequest/v1/schema.json.\n";
-    readonly required: readonly ["version", "request_id", "source", "destination", "fulfillment_amount", "quote_deadline", "fulfillment_deadline"];
+    readonly required: readonly ["version", "request_id", "source", "destination", "fulfillment_amount", "quote_deadline", "fulfillment_deadline", "fulfillment_verifier", "escrow_contract_address"];
     readonly properties: {
         readonly version: {
             readonly type: "string";
@@ -3377,13 +1655,13 @@ declare const $CreateQuoteRequest: {
         readonly quote_deadline: {
             readonly type: "string";
             readonly format: "date-time";
-            readonly description: "Required. End of the collection window. After this point no new quotes are accepted.\nThe gateway injects no default and never mutates the originator-supplied body, so the\nvalue is carried through verbatim to the award call. It must be supplied and must be in\nthe future. Must be strictly earlier than fulfillment_deadline.\n";
+            readonly description: "Required. End of the collection window. After this point no new quotes are accepted.\nThe gateway injects no default and never mutates the originator-supplied body, so the\nvalue is carried through verbatim to the award call. It must be supplied and must be in\nthe future. Must be strictly earlier than fulfillment_deadline.\n\nKeep this window short. A settler holds its quoted price for a limited period of its\nown choosing, and the gateway selects only once the window has closed, so a deadline\nset beyond that hold leaves no quote still awardable and the request is declined with\nQUOTE_WINDOW_TOO_LONG. That hold is set by each settler and is not part of this\ncontract, so treat 60 seconds as a practical upper bound and prefer a shorter window\nwhere your integration allows.\n";
             readonly example: "2026-04-29T12:00:03Z";
         };
         readonly fulfillment_deadline: {
             readonly type: "string";
             readonly format: "date-time";
-            readonly description: "Required. Final deadline for completing the payment. Past it the payment is cancelled and\neligible for refund. The gateway injects no default and never mutates the\noriginator-supplied body, so the value is carried through verbatim to the award call. It\nmust be supplied and must be in the future. Must be strictly later than quote_deadline.\n";
+            readonly description: "Required. Final deadline for completing the payment. Past it the payment fails and\neligible for refund. The gateway injects no default and never mutates the\noriginator-supplied body, so the value is carried through verbatim to the award call. It\nmust be supplied and must be in the future. Must be strictly later than quote_deadline.\n";
             readonly example: "2026-04-29T12:30:00Z";
         };
         readonly settler_auth_required: {
@@ -3403,7 +1681,7 @@ declare const $CreateQuoteRequest: {
         };
         readonly fulfillment_verifier: {
             readonly type: "object";
-            readonly description: "Optional third-party service that independently verifies delivery. Leave empty for the default verifier.";
+            readonly description: "The verification service that confirms the payment was delivered before the escrow\nreleases the source funds, and the account it signs with. Required on every chain:\nthe gateway's `/v1/defaults` response supplies it for each chain.\n";
             readonly required: readonly ["account", "endpoint"];
             readonly properties: {
                 readonly account: {
@@ -3421,7 +1699,7 @@ declare const $CreateQuoteRequest: {
         };
         readonly escrow_contract_address: {
             readonly type: "string";
-            readonly description: "Optional escrow contract address. Leave empty to use the default.";
+            readonly description: "Escrow contract on the source chain that holds the source funds until proof of\nfulfillment has been verified. Required on every chain: the gateway's `/v1/defaults`\nresponse supplies it for each chain (`escrow_contract`).\n";
             readonly example: "0x742D35cC6634c0532925a3b844Bc9e7595F41360";
         };
         readonly fulfillment_proxy: {
@@ -3741,10 +2019,16 @@ declare const $DeclineSummaryEntry: {
         };
         readonly retry_classification: {
             readonly type: "string";
-            readonly description: "What would have to change for a settler giving this reason to bid, drawn from the same\nclosed set as the `retry_classification` on an error response so a caller reads one\nvocabulary.\n\nIt describes the decline only. The authoritative instruction for the payment is the\n`retry_classification` on its own error response: a payment can fail for a reason no\nsettler named, and it can succeed while some settlers declined.\n\nOptional, and a pattern-constrained string for the same reason `DeclineReason` is.\n";
+            readonly description: "What would have to change for a settler giving this reason to submit a price quote,\ndrawn from the same closed set as the `retry_classification` on an error response so\na caller reads one vocabulary.\n\nIt describes the decline only. The authoritative instruction for the payment is the\n`retry_classification` on its own error response: a payment can fail for a reason no\nsettler named, and it can succeed while some settlers declined.\n\nOptional, and a pattern-constrained string for the same reason `DeclineReason` is.\n";
             readonly pattern: "^[A-Z][A-Z0-9_]*$";
             readonly example: "RETRY_AFTER_DELAY";
         };
+        readonly docs_url: {
+            readonly type: "string";
+            readonly format: "uri";
+            readonly description: "Link to the documentation for this reason. Absent rather than empty when no page is\npublished, so a reader never follows a link to the site root.\n";
+            readonly example: "https://docs.atum.xyz/decline-reasons#insufficient-liquidity";
+        };
     };
 };
 declare const $DeclineReason: {
@@ -3826,6 +2110,11 @@ declare const $AwardResponse: {
         readonly fulfillment_confirmation: {
             readonly $ref: "#/components/schemas/FulfillmentConfirmation";
         };
+        readonly fulfillment_authorization: {
+            readonly type: "object";
+            readonly description: "The settler-signed FulfillmentAuthorization for this payment, returned verbatim as an\nopaque signed document (structurally the canonical FulfillmentAuthorization/v1 declaration at\nhttps://schemas.atum.xyz/declarations/FulfillmentAuthorization/v1; see also\n`#/components/schemas/FulfillmentAuthorization`). The inner declaration requires\n`version`, `scheme`, `authorization` (the signed EIP-3009 transfer, in `authorization.message_prehash`), `fulfillment_quote_json`,\nand `evidence` (the on-chain authorizeFulfillment transaction). On the wire the settler\ntypically wraps that declaration in JSON-LD with `@context`, `type`, and `proof` — those\nenvelope fields ride alongside the declaration and MUST be preserved byte-for-byte.\n\nPresent when the settler authorized an originator fulfill within the sync wait.\nMutually exclusive with `fulfillment_confirmation` until the originator fulfills: when\nthis field is populated, `fulfillment_confirmation` is absent.\n\nThe service returns these bytes verbatim and does not re-serialize through a typed\nrepresentation (which would normalize timestamps and reorder JSON-LD envelope fields).\n";
+            readonly 'x-go-type': "json.RawMessage";
+        };
     };
 };
 declare const $AwardAccepted: {
@@ -3894,12 +2183,6 @@ declare const $ChainDefaults: {
             readonly description: "The Permit2 this chain's escrow verifies against, sent only when it is not the canonical deployment. When absent, use the canonical Permit2 address for the chain. EVM and Tron only.";
             readonly example: "0x000000000022D473030F116dDEE9F6B43aC78BA3";
         };
-        readonly deposit_witness_version: {
-            readonly type: "integer";
-            readonly minimum: 3;
-            readonly description: "Which deposit witness this chain's escrow expects. `4` and above select the four-member witness, `3` the two-member one; absent means four. EVM and Tron only - on Solana this is carried by `svm_signature_domain_version`.";
-            readonly example: 4;
-        };
         readonly tokens: {
             readonly type: "array";
             readonly description: "Tokens this chain's escrow accepts for deposit. Absent when the gateway has no listing for the chain, which does not mean no token is accepted.";
@@ -3932,7 +2215,13 @@ declare const $ChainDefaults: {
         readonly svm_signature_domain_version: {
             readonly type: "integer";
             readonly minimum: 1;
-            readonly description: "Solana only. Version of the escrow's signing domain. Absent for EVM and Tron.";
+            readonly description: "Solana only. The escrow's signature domain version, which the deposit hash commits to. Absent for EVM and Tron.";
+            readonly example: 5;
+        };
+        readonly deposit_request_hash_version: {
+            readonly type: "integer";
+            readonly minimum: 1;
+            readonly description: "The depositRequestHash version to sign for a deposit from this chain: 1 is keccak256 of the request_id, 2 is the hash of the payment terms, computed over the request body exactly as it is then posted. Absent means 1. A deposit signed with version 1 is still accepted while the gateway publishes 2. The gateway publishes 2 for a chain only once every reader of the deposit there reads version 2, veri-fill's release check included, so this is the network-wide signal a client signs by and a merchant lists 2 in an x402 or MPP challenge by.";
             readonly example: 2;
         };
     };
@@ -4300,109 +2589,25 @@ declare function needsSourceApproval(params: ApprovalParams): Promise<boolean>;
 declare function ensureSourceApproval(params: ApprovalParams): Promise<EnsureApprovalResult>;
 
 /**
- * EVM Permit2 PermitWitnessTransferFrom deposit prehash + EIP-712 digest.
- *
- * Byte-for-byte counterpart of the sibling Go encoder (deposit_encoder.go,
- * `EscrowDepositEncoder`). This is the sender-authorization scheme the Atum
- * protocol uses on EVM chains: it authorizes Permit2 to move tokens into the
- * escrow contract, with a DepositWitness {reserver, releaser}.
+ * EVM Permit2 PermitWitnessTransferFrom deposit prehash and EIP-712 digest.
  *
- * The sender signs the digest this produces, and the serialized prehash travels
- * to the settler as `message_prehash`, so BOTH the digest and the JSON
- * serialization (top-level key order, and `chainId` as a lowercase hex string
- * matching the Go encoder's %#x form) must stay pinned to the Go output. See
- * deposit-encoder.test.ts.
+ * Byte-for-byte counterpart of the Go encoder (deposit_encoder.go, `EscrowDepositEncoder`). The
+ * sender signs the digest, and the serialized prehash travels as `message_prehash`, so both the
+ * digest and the JSON serialization (top-level key order, `chainId` as lowercase hex) are pinned
+ * to the Go output. See deposit-encoder.test.ts.
  */
 /**
- * The Permit2 contract address deployed at the same address on all supported
- * EVM chains; the EIP-712 domain verifyingContract for PermitWitnessTransferFrom.
+ * The Permit2 contract, deployed at the same address on all supported EVM chains; the EIP-712
+ * domain verifyingContract for PermitWitnessTransferFrom.
  */
 declare const PERMIT2_CONTRACT_ADDRESS = "0x000000000022D473030F116dDEE9F6B43aC78BA3";
-interface PermitWitnessTransferFromParams {
-    /** EIP-155 chain ID. */
-    chainId: number;
-    /** The Permit2 contract (PERMIT2_CONTRACT_ADDRESS). */
-    verifyingContract: string;
-    /** TokenPermissions: source token + amount (smallest units, decimal string). */
-    token: string;
-    amount: string;
-    /** The escrow contract address (spender). */
-    spender: string;
-    nonce: bigint;
-    deadline: bigint;
-    /** DepositWitness (V3): reserver (quote selector) + releaser (fulfillment verifier). */
-    reserver: string;
-    releaser: string;
-}
-/**
- * Build the structured prehash for PermitWitnessTransferFrom. The shape is a
- * direct argument set for `wallet.signTypedData(domain, types, message)`:
- *  - `domain` carries only Permit2's on-chain EIP712Domain fields (name,
- *    chainId, verifyingContract; no `version`, no `salt`).
- *  - `types` omits an EIP712Domain entry (ethers derives it from the domain
- *    object's keys and rejects an explicit one).
- *  - `chainId` is emitted as a lowercase hex string to match the Go encoder's
- *    %#x serialization and the settler's `message_prehash` contract; the EIP-712
- *    digest itself is invariant to the number-vs-hex representation.
- */
-declare function createPermitWitnessTransferFromPrehash(params: PermitWitnessTransferFromParams): {
-    types: {
-        PermitWitnessTransferFrom: {
-            name: string;
-            type: string;
-        }[];
-        TokenPermissions: {
-            name: string;
-            type: string;
-        }[];
-        DepositWitness: {
-            name: string;
-            type: string;
-        }[];
-    };
-    primaryType: string;
-    domain: {
-        name: string;
-        chainId: string;
-        verifyingContract: string;
-    };
-    message: {
-        permitted: {
-            token: string;
-            amount: string;
-        };
-        spender: string;
-        nonce: string;
-        deadline: string;
-        witness: {
-            reserver: string;
-            releaser: string;
-        };
-    };
-};
-/**
- * Hash a PermitWitnessTransferFrom prehash into its EIP-712 digest (0x-prefixed
- * 32-byte hex). Accepts the object returned by
- * createPermitWitnessTransferFromPrehash (or an equivalent parsed from JSON).
- */
+/** Hash a PermitWitnessTransferFrom prehash (or one parsed from JSON) into its EIP-712 digest. */
 declare function hashPermitWitnessTransferFrom(prehash: {
     domain: any;
     types: any;
     message: any;
 }): string;
 
-/**
- * EVM Permit2 PermitWitnessTransferFrom sender-auth scheme.
- *
- * The encoder now lives in the shared @atum-labs/evm-escrow-encoding package
- * (byte-parity with the Go EscrowDepositEncoder). This module re-exports it so
- * the pg-client public API and the EVM chain adapter keep the same import
- * surface.
- */
-
-/** Hash a request ID string to a 32-byte identifier. V1 legacy, unused by the V3 deposit witness. */
-declare function hashRequestId(requestId: string): string;
-
 /**
  * Masks a chain ID to 4 bytes for Tron TIP-712 compatibility.
  *
@@ -4445,83 +2650,17 @@ declare function base58ToHex(base58Address: string): string;
 declare function normalizeAddress(address: string): string;
 
 /**
- * TVM (Tron) Permit2 PermitWitnessTransferFrom deposit prehash + TIP-712 digest.
+ * TVM (Tron) Permit2 PermitWitnessTransferFrom deposit prehash and TIP-712 digest.
  *
- * Byte-for-byte counterpart of the sibling Go encoder (deposit_encoder.go,
- * `EscrowDepositEncoder`). Same shape as the EVM deposit encoder, with the
- * Tron-specific normalization applied here: the chainId is masked to its lower
- * 4 bytes (Tron's TIP-712 domain uses a uint32 chainId) and every address is
- * converted from base58 to bare 20-byte hex (0x41 prefix stripped).
- *
- * The sender signs the digest this produces, and the serialized prehash travels
- * to the settler as `message_prehash`, so BOTH the digest and the JSON
- * serialization (key order, and `chainId` as a lowercase hex string) must stay
- * pinned to the Go output. See deposit-encoder.test.ts.
- *
- * V3: DepositWitness is `{reserver, releaser}` — `requestId` is gone.
- */
-/**
- * Parameters for a TVM V3 Permit2 deposit prehash. Addresses may be base58 or
- * hex; they are normalized to bare 20-byte hex internally.
+ * Byte-for-byte counterpart of the Go encoder (deposit_encoder.go, `EscrowDepositEncoder`). Same
+ * shape as the EVM deposit encoder, with Tron's normalization: the chainId is masked to its lower
+ * 4 bytes (Tron's TIP-712 domain uses a uint32 chainId) and every address is converted from base58
+ * to bare 20-byte hex (0x41 prefix stripped). The digest and the JSON serialization (key order,
+ * `chainId` as lowercase hex) are pinned to the Go output. See deposit-encoder.test.ts.
  */
-interface TvmPermitWitnessTransferFromParams {
-    chainId: number;
-    permit2Address: string;
-    tokenAddress: string;
-    amount: string;
-    spenderAddress: string;
-    nonce: bigint;
-    deadline: bigint;
-    reserverAddress: string;
-    releaserAddress: string;
-}
-/**
- * Build the V3 TIP-712 prehash for a Permit2 deposit on Tron, shaped for direct
- * `wallet.signTypedData(domain, types, message)` consumption:
- *  - `domain` carries only name, chainId (pre-masked, lowercase hex string),
- *    verifyingContract — Permit2's on-chain EIP712Domain has no version/salt.
- *  - `types` omits an EIP712Domain entry (ethers derives it from the domain keys).
- *  - all addresses are hex-normalized (0x41 prefix stripped).
- */
-declare function createTvmPermitWitnessTransferFromPrehash(params: TvmPermitWitnessTransferFromParams): {
-    types: {
-        PermitWitnessTransferFrom: {
-            name: string;
-            type: string;
-        }[];
-        TokenPermissions: {
-            name: string;
-            type: string;
-        }[];
-        DepositWitness: {
-            name: string;
-            type: string;
-        }[];
-    };
-    primaryType: string;
-    domain: {
-        name: string;
-        chainId: string;
-        verifyingContract: string;
-    };
-    message: {
-        permitted: {
-            token: string;
-            amount: string;
-        };
-        spender: string;
-        nonce: string;
-        deadline: string;
-        witness: {
-            reserver: string;
-            releaser: string;
-        };
-    };
-};
 /**
- * Hash a TVM Permit2 prehash into its TIP-712 digest (0x-prefixed 32-byte hex).
- * The Tron-specific work (chainId mask, address normalization) already happened
- * in createTvmPermitWitnessTransferFromPrehash.
+ * Hash a TVM Permit2 prehash into its TIP-712 digest. The Tron-specific normalization happens in
+ * the builder.
  */
 declare function hashTvmPermitWitnessTransferFrom(prehash: {
     domain: any;
@@ -4538,32 +2677,13 @@ declare function encodeU64LE(value: bigint): Uint8Array;
 declare const MAX_VALID_SLOT: number;
 
 /**
- * Solana deposit message sender auth scheme implementation.
- *
- * This module provides utilities for creating and hashing Solana deposit
- * authorization messages for the Atum payment gateway.
- *
- * The deposit message is a 199-byte binary structure hashed with Keccak-256:
- *   keccak256("deposit" || payment_id[32] || depositor[32] || mint[32] ||
- *             amount[8,LE] || reserver[32] || releaser[32] ||
- *             nonce[8,LE] || issued_at[8,LE] || deadline[8,LE])
- *
- * encodeU64LE, generateSolanaNonce (generateNonce), and MAX_VALID_SLOT are
- * imported from the shared @atum-labs/solana-escrow-encoding package and
- * re-exported here to preserve the public API. base58ToBytes, payment-id
- * generation, and prehash creation stay local, because the local base58/hex
- * helpers carry the exact error messages the client tests assert.
+ * Solana deposit helpers: replay nonces and base58/hex encoding.
  *
- * NO DEPOSIT HASH IS COMPUTED HERE ANY MORE. hashSolanaDeposit computed the
- * pre-domain-separation layout above and now throws (see its doc comment), and
- * hashSolanaDepositV3 was deleted as an un-exported third copy of the package's
- * own call. Build a deposit through the shared sender_auth adapter, which selects
- * the preimage from the escrow domain version; reach for computeDepositHash /
- * computeDepositHashV2 from the package if you need the raw primitive.
- *
- * The canonical reference is the @atum-labs/solana-escrow-encoding package in
- * this repo (contracts/svm/escrow-encoding), the TypeScript sibling of the
- * on-chain Solana escrow program and the Go signing library.
+ * Deposit authorizations are built through the shared sender_auth adapter
+ * (`getChainAdapter(chainId).buildAuthMessage(...)`), which commits the destination and reads the
+ * escrow's signature domain. For the raw primitive, use computeDepositHashV2 from
+ * @atum-labs/solana-escrow-encoding (contracts/svm/bindings/typescript/escrow-encoding), the encoding shared with the
+ * on-chain program and the Go signing library.
  */
 
 /** Replay horizon in seconds — deposit deadline must be within this window of issuedAt. */
@@ -4573,35 +2693,10 @@ declare const REPLAY_HORIZON_SECS = 128;
  * bounded set the escrow-encoding package defines, which keeps the replay_bucket PDAs reusable.
  */
 declare const TOTAL_BUCKETS = 131072;
-/** Exact byte size of a serialized deposit message (7 + 32*5 + 8*3). */
-declare const DEPOSIT_MESSAGE_SIZE = 199;
-/**
- * Parameters for constructing a Solana deposit authorization message.
- */
-interface SolanaDepositParams {
-    /** Base58 Solana public key of the depositor. */
-    depositor: string;
-    /** Base58 SPL token mint address. */
-    mint: string;
-    /** Token amount in smallest units (uint64). */
-    amount: bigint;
-    /** Base58 public key authorized to reserve funds (quote selector). */
-    reserver: string;
-    /** Base58 public key authorized to release/refund funds (fulfillment verifier). */
-    releaser: string;
-    /** Replay protection nonce (uint64). */
-    nonce: bigint;
-    /** Unix timestamp (seconds) when the authorization was created (uint64). */
-    issuedAt: bigint;
-    /** Unix timestamp (seconds) when the deposit authorization expires (uint64). */
-    deadline: bigint;
-    /** Original request ID string (used for payment ID generation). */
-    requestId: string;
-}
 /**
- * Decodes a Base58-encoded Solana public key to a 32-byte Uint8Array. Kept local
- * rather than using Pubkey.fromBase58: the client tests assert this exact
- * "Invalid Solana public key length" message.
+ * Decodes a Base58-encoded Solana public key to a 32-byte Uint8Array.
+ *
+ * @throws If the decoded key is not 32 bytes.
  */
 declare function base58ToBytes(address: string): Uint8Array;
 /**
@@ -4612,79 +2707,10 @@ declare function bytesToHex(bytes: Uint8Array): string;
  * Converts a hex string (with or without 0x prefix) to a Uint8Array.
  */
 declare function hexToBytes(hex: string): Uint8Array;
-/**
- * Generates a 32-byte payment ID from the request ID and deposit parameters.
- *
- * Formula: keccak256(requestId_str || "deposit" || depositor[32] ||
- *                    amount[8,LE] || reserver[32] || releaser[32] ||
- *                    nonce[8,LE] || issuedAt[8,LE] || deadline[8,LE])
- *
- * TODO: the V3 gateway simplified this to
- * just keccak256(requestID). When we migrate to v3, this function should change
- * to: return keccak256(toUtf8Bytes(requestId)); and the params argument can be
- * removed. The gateway reads payment_id from the prehash so both approaches work.
- *
- * @returns 0x-prefixed hex string (32 bytes)
- */
-declare function generateSolanaPaymentId(requestId: string, params: Omit<SolanaDepositParams, 'requestId'>): string;
-/**
- * Prehash structure for a Solana deposit message.
- * Uses base58 addresses and string numbers for settler parsing.
- */
-interface SolanaDepositPrehash {
-    payment_id: string;
-    depositor: string;
-    mint: string;
-    amount: string;
-    reserver: string;
-    releaser: string;
-    nonce: string;
-    issued_at: string;
-    deadline: string;
-}
-/**
- * Creates the JSON prehash structure for a Solana deposit message.
- * The prehash contains base58 addresses and string numbers, matching the
- * format the settler agent expects in `message_prehash`.
- *
- * @param paymentId 0x-prefixed hex string (32 bytes) from generateSolanaPaymentId()
- * @param params The deposit parameters
- * @returns The structured prehash object
- */
-declare function createSolanaDepositPrehash(paymentId: string, params: SolanaDepositParams): SolanaDepositPrehash;
-/**
- * REMOVED — this function computed the PRE-DOMAIN-SEPARATION deposit hash, which no deployed
- * escrow program accepts. It now throws rather than returning one.
- *
- * The layout it used, kept here as a record of the historical scheme:
- *
- *   keccak256("deposit" || payment_id[32] || depositor[32] || mint[32] ||
- *             amount[8,LE] || reserver[32] || releaser[32] ||
- *             nonce[8,LE] || issued_at[8,LE] || deadline[8,LE])        = 199 bytes
- *
- * Every current program prefixes the preimage with its domain —
- * `"escrow" || signature_domain_version || cluster_id[32] || program_id[32]` — and from domain
- * version 4 also binds `destination_hash`. So the 199-byte hash is not merely out of date, it is
- * unverifiable everywhere: `escrow.rs`'s `require!(deposit_hash == message, InvalidData)` rejects
- * it on every cluster.
- *
- * WHY IT THROWS INSTEAD OF BEING DELETED OR LEFT ALONE. It was exported from this package's
- * entry point, so removing the symbol outright is a hard break for any consumer that imports it,
- * while leaving it was worse: it returned a well-formed 32-byte hash that fails on-chain with
- * `InvalidData` and no indication why. Throwing turns an undiagnosable on-chain rejection into an
- * error at the call site that names the replacement.
- *
- * Build deposit authorizations through the shared sender_auth adapter
- * (`getChainAdapter(chainId).buildAuthMessage(...)`), which selects the correct preimage from the
- * domain version it is given and is the same implementation the facilitator verifies against.
- *
- * @throws Always.
- */
-declare function hashSolanaDeposit(_prehash: SolanaDepositPrehash): never;
 /**
  * Generates a valid nonce for Solana replay protection (upper 32 bits: random
- * bucket, lower 8 bits: random slot 0..MAX_VALID_SLOT). Delegates to the shared
- * package's generateNonce (which uses a CSPRNG with rejection sampling).
+ * bucket, lower 8 bits: random slot 0..MAX_VALID_SLOT), using a CSPRNG with
+ * rejection sampling.
  *
  * @returns A bigint nonce suitable for the deposit message
  */
@@ -4697,14 +2723,13 @@ declare function generateSolanaNonce(): bigint;
  * manually-crafted utilities for the Atum payment gateway.
  */
 
-declare const PAYMENT_REQUEST_VERSION = "1.0";
-
 /**
  * Applies a SenderSigner to an unsigned PaymentRequest, signing every entry in
- * signed_messages (filling each signature, and payload.delegate_signer where the
- * chain requires it). Mirrors the CLI signing step for SDK consumers. The gateway
- * verifies every signed message, so a multi-message request must have them all
- * signed; the common single-message case is signed exactly as before.
+ * signed_messages as given (filling each signature, and payload.delegate_signer where the
+ * chain requires it). The gateway verifies every signed message. To check what a request
+ * commits to before signing it, see docs/signing.md.
+ *
+ * @throws If the request has no signed_messages.
  */
 declare function signPaymentRequest(request: PaymentRequest, signer: SenderSigner): Promise<PaymentRequest>;
 type HttpRequestConstructor = new (config: OpenAPIConfig) => BaseHttpRequest;
@@ -4718,50 +2743,48 @@ declare const defaultGateway: string;
  * Default request-layer configuration, with `BASE` set to this package's default
  * gateway ({@link defaultGateway}, production-testnet).
  *
- * The generated value mirrors the first `servers` entry of the OpenAPI contract,
- * which is mainnet. This package defaults to testnet instead, so a client created
- * without an explicit URL never targets a live-funds environment. The override
- * lives here rather than in `src/generated/`, which is reproduced from the
- * contract and stays in sync with it.
+ * The OpenAPI contract's first `servers` entry is mainnet; this package defaults to testnet
+ * so a client created without an explicit URL never targets a live-funds environment.
  *
  * Exported for callers that want the default configuration shape.
- * {@link PaymentGatewayClient} does not read it: the client resolves its own
- * `BASE` and passes it explicitly.
+ * {@link PaymentGatewayClient} does not read it: the client resolves its own `BASE`.
  */
 declare const OpenAPI: OpenAPIConfig;
 /**
  * Default quote-collection window for {@link PaymentGatewayClient.prepareQuoteRequest}
- * (`quote_deadline = now + this`, in seconds). Chosen as the largest value that still
- * lands under the gateway's `quote_sync_wait_seconds` cap (5s): a sync (`?wait=true`)
- * request holds for `min(quote_deadline − receipt, cap)`, so ≤5s returns `ready` with
- * quotes inline while ≥6s returns a poll-instead `collecting`. 5s also gives the widest
- * collection window under that cap — enough to catch slower / backup settlers, where a
- * shorter window can drop them — plus headroom against client↔gateway clock skew. A
- * caller on a badly-skewed clock can still pass a larger `quoteDeadlineSeconds`.
+ * (`quote_deadline = now + this`, in seconds). Bidding closes at the quote deadline and the
+ * gateway always waits until then, so the window is time every quote request spends. 3s
+ * leaves settlers ample time to quote and lets a sync (`?wait=true`) request return `ready`
+ * with its quotes inline. A caller whose clock lags the gateway's should pass a larger
+ * `quoteDeadlineSeconds`, since the gateway refuses a quote deadline already in its past.
  */
-declare const DEFAULT_QUOTE_DEADLINE_SECONDS = 5;
+declare const DEFAULT_QUOTE_DEADLINE_SECONDS = 3;
 /** Default settlement horizon (`fulfillment_deadline = now + this`, seconds); shared by both request builders. */
 declare const DEFAULT_FULFILLMENT_DEADLINE_SECONDS = 3600;
 /**
  * Default `quote_deadline` the single-shot payment path ({@link PaymentGatewayClient.preparePaymentRequest})
- * stamps (seconds) when the caller passes no `quoteDeadlineSeconds`. Higher than the
- * quote-request default because the payment path is not bound by the quote sync-wait cap.
+ * stamps (seconds) when the caller passes no `quoteDeadlineSeconds`. The gateway runs the
+ * auction until this deadline before it awards a settler, so the window is time every
+ * payment spends. It has to cover signing and submitting the request as well as settlers
+ * quoting; 3s fits a signer that answers in well under a second. It is also how long a signed
+ * request stays submittable. Pass a larger `quoteDeadlineSeconds` when signing takes longer
+ * (for example a signer that waits for an approval), to submit the request later, or when the
+ * caller's clock lags the gateway's.
  */
-declare const DEFAULT_PAYMENT_QUOTE_DEADLINE_SECONDS = 10;
+declare const DEFAULT_PAYMENT_QUOTE_DEADLINE_SECONDS = 3;
 /**
  * Extended PaymentGatewayClient with convenience methods
  */
 declare class PaymentGatewayClient extends PaymentGatewayClient$1 {
     constructor(config?: PaymentGatewayClientConfig, HttpRequest?: HttpRequestConstructor);
     /**
-     * Fetches chain defaults from the payment gateway.
-     *
-     * Goes through the generated typed client, so the request shares the payment calls'
-     * transport: one base URL, one timeout policy, and `/v1/defaults` is described by the
-     * OpenAPI contract rather than assembled by hand here.
+     * Fetches chain defaults from the payment gateway (`GET /v1/defaults`), using the same
+     * base URL and timeout policy as the payment calls.
      *
      * @param chainId The CAIP-2 chain identifier (e.g., "eip155:42161")
      * @returns The chain defaults including escrow, quote selector, and fulfillment verifier
+     * @throws If the chain id is empty, the request fails, or the response is missing a
+     *   required field or describes a different chain.
      */
     fetchChainDefaults(chainId: string): Promise<ChainDefaults>;
     /**
@@ -4786,8 +2809,10 @@ declare class PaymentGatewayClient extends PaymentGatewayClient$1 {
      *   destinationAccount: "0xMerchantAddress",
      *   destinationAsset: "eip155:42161/erc20:0xaf88d065e77c8cC2239327C5EDb3A432268e5831", // USDC on Arbitrum
      *   fulfillmentAmount: "10000000", // 10 USDC (6 decimals)
+     *   maxSourceAmount: "10010000",   // at most 10.01 USDC from the payer (source units)
+     *   requestId: "order-4711",
      * });
-     * // max_source_amount, deadlines, request id, and nonce are all defaulted.
+     * // Deadlines and the nonce are defaulted; the spend cap never is.
      *
      * const signer = createSenderSigner("eip155:8453", { provider: "raw", privateKey });
      * await signPaymentRequest(request, signer); // fills sender_auth, ready to submit
@@ -4802,7 +2827,12 @@ declare class PaymentGatewayClient extends PaymentGatewayClient$1 {
         sourceAsset: string;
         destinationAccount: string;
         destinationAsset: string;
-        maxSourceAmount?: string;
+        /**
+         * REQUIRED spend cap in the source token's smallest units: signed into the Permit2 as the most
+         * the escrow may take. Never derived here, because that needs both tokens' decimals and a
+         * price. Build it from a settler quote with `capFromQuote`, or state it explicitly.
+         */
+        maxSourceAmount: string;
         /**
          * REQUIRED idempotency key. It seeds the deterministic deposit nonce, so a retry that
          * reuses the same `requestId` reproduces the same single-use permit (no double-charge),
@@ -4823,24 +2853,24 @@ declare class PaymentGatewayClient extends PaymentGatewayClient$1 {
         /** Clock source used to stamp the deadlines. Defaults to `Date.now`; inject for offline/deterministic builds. */
         now?: () => number;
         /**
-         * Explicit deposit-nonce override. OMIT this in normal use: the deposit's single-use nonce is
-         * then derived deterministically from `requestId` + depositor, so rebuilding the same payment
-         * reproduces the same nonce. What that guarantees differs by chain:
-         *   - EVM/Tron: the Permit2 nonce is a PERMANENT on-chain bitmap, so across any number of
-         *     rebuilds only one deposit can EVER settle — retry-safe without a time bound.
-         *   - Solana: the escrow replay nonce only protects within a ~128s window — the nonce pins the
-         *     replay slot/bucket, but `issued_at` is re-read on each build, so a rebuild in a later
-         *     window is not blocked on-chain by the nonce alone. The payment gateway's `request_id`
-         *     dedup (and the init-only deposit PDA, which blocks a byte-identical re-POST forever) are
-         *     the durable backstop; pin `issued_at` via `solanaClockReader` to keep a rebuild inside
-         *     the same window.
-         * Pass a value only to override the derived nonce.
+         * Explicit deposit-nonce override. Omit in normal use: the nonce is then derived from
+         * `requestId` + depositor, so rebuilding the same payment reproduces it.
+         *   - EVM/Tron: the Permit2 nonce is a permanent on-chain bitmap, so only one deposit can
+         *     settle across any number of rebuilds.
+         *   - Solana: the replay nonce is scoped to a ~128s window from `issued_at`, which is re-read
+         *     on each build. The gateway also deduplicates on `request_id`; pin `issued_at` via
+         *     `solanaClockReader` to keep a rebuild in the same window.
          */
         nonce?: bigint | string;
         /** Solana-only: override the RPC used to read the cluster clock for issued_at. */
         solanaRpcUrl?: string;
         /** Solana-only: injectable clock reader for `issued_at` (offline / test seam). */
         solanaClockReader?: SolanaClusterUnixTimeReader;
+        /**
+         * Who performs deposit, reserve, and fulfill. Omitted leaves the key off. Omitted on the
+         * wire means settler. Send-payment does not set this.
+         */
+        executor?: PaymentRequest['executor'];
         /**
          * Pre-resolved corridor addresses. Omit to fetch them from the gateway
          * `/v1/defaults`; supply to build offline. Each side is resolved independently —
@@ -4854,34 +2884,15 @@ declare class PaymentGatewayClient extends PaymentGatewayClient$1 {
     }): Promise<PaymentRequest>;
     /**
      * Prepares a quote-request body (`CreateQuoteRequest`), ready to POST to
-     * `/v1/payments/quote-requests`. This is the quote-phase counterpart to
-     * `preparePaymentRequest`: it builds the same corridor shape but **without
-     * `sender_auth`** — quote-time is the unauthenticated browse step, so no
-     * signing (and no private key) is required. The spend authorization arrives
-     * later, at the award call.
+     * `/v1/payments/quote-requests`. It carries the same corridor and contract fields as
+     * `preparePaymentRequest` but no `sender_auth`: quoting needs no signature or private key,
+     * and the spend authorization is supplied at award time.
      *
-     * Both deadlines are populated here because the gateway requires them and
-     * injects no defaults — it never mutates the originator-supplied body.
-     * `quote_deadline` bounds the collection window (default
-     * `DEFAULT_QUOTE_DEADLINE_SECONDS`); `fulfillment_deadline` bounds settlement
-     * (default `DEFAULT_FULFILLMENT_DEADLINE_SECONDS`). `quote_deadline` must be
-     * strictly earlier than `fulfillment_deadline` (enforced server-side; guarded
-     * here for a clear client-side error).
-     *
-     * `quote_deadline` is stamped client-side and the gateway rejects it unless it
-     * is strictly in the gateway's future, so a caller whose clock may lag the
-     * gateway should pass a larger `quoteDeadlineSeconds` (see
-     * `DEFAULT_QUOTE_DEADLINE_SECONDS` for why the default is what it is).
-     *
-     * Like `preparePaymentRequest`, this fetches the source/destination chain
-     * defaults and populates the SAME contract fields (`escrow_contract_address`,
-     * `quote_selector`, `fulfillment_verifier`, `fulfillment_proxy`). These are not
-     * optional in practice: the gateway requires `fulfillment_verifier` to build the
-     * request event it broadcasts to settlers, so the quote-request body
-     * must carry the identical contract fields the payment flow does. The ONLY
-     * field this drops relative to `preparePaymentRequest` is `sender_auth`, which
-     * is supplied at award time (quote-time is unauthenticated — no signing, no
-     * private key).
+     * Both deadlines are populated because the gateway requires them and injects no defaults.
+     * `quote_deadline` (default `DEFAULT_QUOTE_DEADLINE_SECONDS`) must be strictly earlier than
+     * `fulfillment_deadline` (default `DEFAULT_FULFILLMENT_DEADLINE_SECONDS`) and strictly in the
+     * gateway's future, so a caller whose clock lags the gateway should pass a larger
+     * `quoteDeadlineSeconds`.
      *
      * @param params Quote-request parameters
      * @returns A complete `CreateQuoteRequest` body (no signature step needed)
@@ -4892,6 +2903,12 @@ declare class PaymentGatewayClient extends PaymentGatewayClient$1 {
         sourceAsset: string;
         destinationAccount: string;
         destinationAsset: string;
+        /**
+         * Spend cap in the source token's smallest units; settlers' quotes above it are filtered.
+         * Omit it to request quotes with no cap: nothing is sent, and the SDK never derives one.
+         * A supplied value must be a positive base-10 integer. To cap a later payment from a quote,
+         * see `capFromQuote`.
+         */
         maxSourceAmount?: string;
         /**
          * The request id. Reuse the SAME value to retry: the gateway returns the original batch
@@ -4908,4 +2925,4 @@ declare class PaymentGatewayClient extends PaymentGatewayClient$1 {
     }): Promise<CreateQuoteRequest>;
 }
 
-export { $AuthorizationResult, $AwardAccepted, $AwardRequest, $AwardResponse, $AwardedPayment, $AwardedQuote, $BidAward, $ChainDefaults, $ChainDefaultsByChain, $CreateQuoteRequest, $DataIntegrityProof, $DeclineReason, $DeclineSummaryEntry, $ErrorResponse, $FulfillmentConfirmation, $GetDefaultsResult, $GetPaymentStatusResponse, type $OpenApiTs, $OwnedAsset, $PaymentBlockchainContext, $PaymentError, $PaymentRequest, $PaymentResponse, $PaymentSummary, $PaymentTimelineResponse, $PreparePaymentRequest, $PreparePaymentResponse, $Quote, $QuoteRequestAccepted, $QuoteRequestResponse, $QuoteRequestStatusResponse, $ResolvePaymentResponse, $SenderAuth, $SenderAuthMessageScheme, $SignedMessage, $TimelineError, $TimelineStep, $VerifiableCredential, $VerifiableCredentialAuth, ApiError, type ApiRequestOptions, type ApiResult, type ApprovalParams, type AuthorizationResult, AuthorizationsService, type AuthorizePaymentData, type AuthorizePaymentResponse, type AwardAccepted, type AwardQuoteData, type AwardQuoteResponse, type AwardRequest, type AwardResponse, type AwardedPayment, type AwardedQuote, type BidAward, CancelError, CancelablePromise, type ChainDefaults, type ChainDefaultsByChain, ChainDefaultsService, type ChainDefaults$1 as ChainDefaultsWire, type ConfirmationOptions, type CreateQuoteRequest, type CreateQuoteRequestData, type CreateQuoteRequestResponse, DEFAULT_FULFILLMENT_DEADLINE_SECONDS, DEFAULT_PAYMENT_QUOTE_DEADLINE_SECONDS, DEFAULT_POLL_INTERVAL_MS, DEFAULT_QUOTE_DEADLINE_SECONDS, DEFAULT_REQUEST_TIMEOUT_MS, DEFAULT_SYNC_WAIT_TIMEOUT_MS, DEFAULT_WAIT_BUDGET_MS, DEPOSIT_MESSAGE_SIZE, type DataIntegrityProof, type DeclineReason, type DeclineSummaryEntry, type EnsureApprovalResult, type ErrorResponse, type FulfillmentConfirmation, GatewayTimeoutError, type GetDefaultsData, type GetDefaultsResponse, type GetDefaultsResult, type GetPaymentStatusData, type GetPaymentStatusResponse, type GetPaymentStatusResponse2, type GetPaymentTimelineData, type GetPaymentTimelineResponse, type GetQuoteRequestStatusData, type GetQuoteRequestStatusResponse, type HealthCheckResponse, HealthService, Interceptors, InvalidAccountError, type Reason as InvalidAccountReason, MAX_VALID_SLOT, type OnCancel, OpenAPI, type OpenAPIConfig, type OwnedAsset, PAYMENT_REQUEST_VERSION, PERMIT2_CONTRACT_ADDRESS, type ParsedAssetIdentifier, type PaymentBlockchainContext, type PaymentError, PaymentGatewayClient, type PaymentGatewayClientConfig, type PaymentRequest, type PaymentResponse, type PaymentSummary, type PaymentTimelineResponse, PaymentsService, type PermitWitnessTransferFromParams, type PreparePaymentData, type PreparePaymentRequest, type PreparePaymentResponse, type PreparePaymentResponse2, type Quote, type QuoteRequestAccepted, type QuoteRequestResponse, type QuoteRequestStatusResponse, QuoteRequestsService, REPLAY_HORIZON_SECS, type RequestTimeouts, type ResolvePaymentData, type ResolvePaymentResponse, type ResolvePaymentResponse2, type SenderAuth, type SenderAuthMessageScheme, type SenderSignature, type SenderSigner, type SenderSignerOptions, type SignedMessage, type SolanaClusterUnixTimeReader, type SolanaDepositParams, type SolanaDepositPrehash, type StatusSnapshot, type SubmitPaymentData, type SubmitPaymentResponse, TOTAL_BUCKETS, type TimelineError, type TimelineStep, type TronWebLike, type TurnkeyConfig, TurnkeySenderSigner, type TvmPermitWitnessTransferFromParams, type VerifiableCredential, type VerifiableCredentialAuth, type WaitOutcome, type WaitParams, assetChainId, base58ToBytes, base58ToHex, bytesToHex, createPermitWitnessTransferFromPrehash, createSenderSigner, createSolanaDepositPrehash, createTvmPermitWitnessTransferFromPrehash, defaultGateway, type domain, encodeU64LE, ensureSourceApproval, type error_code, generateSolanaNonce, generateSolanaPaymentId, getErrorResponse, hashPermitWitnessTransferFrom, hashRequestId, hashSolanaDeposit, hashTvmPermitWitnessTransferFrom, hexToBytes, isApiError, isGatewayTimeoutError, isTerminalStatus, isUnconfirmed, maskChainId, needsSourceApproval, normalizeAddress, parseAssetIdentifier, resolveTurnkeyAddresses, signPaymentRequest, type status, type status2, type status3, type status4, type status5, type status6, type status7, type status8, type status9, waitForTerminalStatus };
+export { $AuthorizationResult, $AwardAccepted, $AwardRequest, $AwardResponse, $AwardedPayment, $AwardedQuote, $BidAward, $ChainDefaults, $ChainDefaultsByChain, $CreateQuoteRequest, $DataIntegrityProof, $DeclineReason, $DeclineSummaryEntry, $ErrorResponse, $FulfillmentAuthorization, $FulfillmentConfirmation, $GetDefaultsResult, $GetPaymentStatusResponse, $OwnedAsset, $PaymentBlockchainContext, $PaymentFailure, $PaymentRequest, $PaymentResponse, $PaymentStatus, $PaymentSummary, $PaymentTimelineResponse, $PaymentTransaction, $PaymentTransactions, $PreparePaymentRequest, $PreparePaymentResponse, $Quote, $QuoteRequestAccepted, $QuoteRequestResponse, $QuoteRequestStatusResponse, $RefundSignature, $ResolvePaymentResponse, $SenderAuth, $SenderAuthMessageScheme, $SignedMessage, $TimelineStep, $VerifiableCredential, $VerifiableCredentialAuth, ApiError, type ApiRequestOptions, type ApiResult, type ApprovalParams, AuthorizationsService, AuthorizePaymentData, AuthorizePaymentResponse, AwardQuoteData, AwardQuoteResponse, CancelError, CancelablePromise, type ChainDefaults, ChainDefaultsService, type ConfirmationOptions, CreateQuoteRequest, CreateQuoteRequestData, CreateQuoteRequestResponse, DEFAULT_FULFILLMENT_DEADLINE_SECONDS, DEFAULT_PAYMENT_QUOTE_DEADLINE_SECONDS, DEFAULT_POLL_INTERVAL_MS, DEFAULT_QUOTE_DEADLINE_SECONDS, DEFAULT_REQUEST_TIMEOUT_MS, DEFAULT_SYNC_WAIT_TIMEOUT_MS, DEFAULT_WAIT_BUDGET_MS, type EnsureApprovalResult, ErrorResponse, GatewayTimeoutError, GetDefaultsData, GetDefaultsResponse, GetPaymentStatusData, GetPaymentStatusResponse2, GetPaymentTimelineData, GetPaymentTimelineResponse, GetQuoteRequestStatusData, GetQuoteRequestStatusResponse, HealthCheckResponse, HealthService, Interceptors, InvalidAccountError, type Reason as InvalidAccountReason, MAX_VALID_SLOT, type OnCancel, OpenAPI, type OpenAPIConfig, VERSION as PAYMENT_REQUEST_VERSION, PERMIT2_CONTRACT_ADDRESS, type ParsedAssetIdentifier, PaymentGatewayClient, type PaymentGatewayClientConfig, PaymentRequest, PaymentsService, PreparePaymentData, PreparePaymentResponse2, QuoteRequestsService, REPLAY_HORIZON_SECS, type RequestTimeouts, ResolvePaymentData, ResolvePaymentResponse2, type SenderSignature, type SenderSigner, type SenderSignerOptions, SignedMessage, type SolanaClusterUnixTimeReader, type StatusSnapshot, SubmitPaymentData, SubmitPaymentResponse, TOTAL_BUCKETS, type TronWebLike, type TurnkeyConfig, TurnkeySenderSigner, type WaitOutcome, type WaitParams, assetChainId, base58ToBytes, base58ToHex, bytesToHex, capFromQuote, createSenderSigner, defaultGateway, encodeU64LE, ensureSourceApproval, generateSolanaNonce, getErrorResponse, hashPermitWitnessTransferFrom, hashTvmPermitWitnessTransferFrom, hexToBytes, isApiError, isGatewayTimeoutError, isTerminalStatus, isUnconfirmed, maskChainId, needsSourceApproval, normalizeAddress, parseAssetIdentifier, resolveTurnkeyAddresses, signPaymentRequest, waitForTerminalStatus };