@atumlabs/payment-gateway-client 2.0.0 → 2.2.0

package/dist/index.d.ts

@@ -65,7 +65,6 @@ type OpenAPIConfig = {
         response: Interceptors<AxiosResponse>;
     };
 };
-declare const OpenAPI: OpenAPIConfig;
 
 declare abstract class BaseHttpRequest {
     readonly config: OpenAPIConfig;
@@ -203,7 +202,10 @@ type PaymentRequest = {
          */
         account: string;
         /**
-         * The API endpoint URL where the verification service can be reached
+         * Origin of the fulfillment verifier service, with no path — the caller
+         * appends the verifier's own API paths. The gateway's `/defaults` response
+         * supplies the default fulfillment verifier for each chain.
+         *
          */
         endpoint: string;
     };
@@ -443,10 +445,16 @@ type VerifiableCredential = {
     };
 };
 /**
- * Response from submitting a payment request. If processing completes within 30 seconds,
- * the response will include a fulfillment_confirmation with full settlement details.
- * Otherwise, you'll receive a payment_id that you can use to poll the
- * /v1/payments/{paymentId}/status endpoint for updates.
+ * 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.
  *
  */
 type PaymentResponse = {
@@ -454,9 +462,71 @@ type PaymentResponse = {
      * Unique ID for tracking this payment. Save this to check status later.
      *
      */
-    payment_id?: string;
+    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;
     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.
@@ -479,15 +549,6 @@ type GetPaymentStatusResponse = {
     fulfillment_confirmation?: FulfillmentConfirmation;
     error?: PaymentError;
 };
-/**
- * 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
- *
- */
-type status2 = 'pending' | 'completed' | 'failed' | 'cancelled';
 /**
  * Error details when payment status is "failed".
  * Only present when the payment has failed. Contains a machine-readable
@@ -893,7 +954,10 @@ type CreateQuoteRequest = {
          */
         account: string;
         /**
-         * The API endpoint URL where the verification service can be reached
+         * Origin of the fulfillment verifier service, with no path — the caller
+         * appends the verifier's own API paths. The gateway's `/defaults` response
+         * supplies the default fulfillment verifier for each chain.
+         *
          */
         endpoint: string;
     };
@@ -975,7 +1039,7 @@ type Quote = {
     quote_id: string;
     /**
      * The settler-signed FulfillmentQuote (structurally the canonical FulfillmentQuote/v1
-     * declaration at https://schemas.atum.network/declarations/FulfillmentQuote/v1), returned
+     * 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
@@ -997,7 +1061,7 @@ type AwardedQuote = {
     quote_id: string;
     /**
      * The settler-signed FulfillmentQuote (structurally the canonical FulfillmentQuote/v1
-     * declaration at https://schemas.atum.network/declarations/FulfillmentQuote/v1), returned
+     * 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
@@ -1322,6 +1386,14 @@ type $OpenApiTs = {
                  * 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
                  */
@@ -1550,8 +1622,26 @@ declare class PaymentsService {
      * 2. Find optimal settlement routes across chains/assets
      * 3. Secure funds in escrow
      * 4. Coordinate with settlement agents for execution
-     * 5. Return a real-time result if processing completes within 30 seconds,
-     * otherwise return a payment ID for status polling
+     * 5. Return a real-time result if settlement completes inside the synchronous window,
+     * otherwise return a payment ID and status for polling
+     *
+     * **Idempotency.** `request_id` is the idempotency key, scoped to the source account
+     * and originator. Submitting the same `request_id` again returns the ORIGINAL payment
+     * instead of charging a second time, so a client whose request timed out or failed
+     * in transit can safely re-submit.
+     *
+     * Because a re-submission must be admissible on its own, some fields legitimately
+     * differ between attempts and are excluded from the comparison: `quote_deadline` and
+     * `fulfillment_deadline` (both must be in the future, so a later attempt has to move
+     * them), and the `sender_auth` signature they are signed into.
+     *
+     * What must NOT differ is the payment's economics — source account and asset,
+     * destination accounts and assets, `fulfillment_amount`, and `max_source_amount` (the
+     * payer's own risk cap; lowering it on a retry describes a different payment, not the
+     * same one with less headroom). Re-using one `request_id` for a genuinely different
+     * payment is a client bug that would otherwise be silently collapsed onto the first
+     * payment, so it is rejected with `409` and `IDEMPOTENCY_TERMS_MISMATCH`. Use a
+     * distinct `request_id` per payment.
      *
      * @param data The data for the request.
      * @param data.requestBody
@@ -1996,8 +2086,8 @@ declare const $PaymentRequest: {
                 readonly endpoint: {
                     readonly type: "string";
                     readonly format: "uri";
-                    readonly description: "The API endpoint URL where the verification service can be reached";
-                    readonly example: "https://verifier.atum.network/api/v1/verify";
+                    readonly description: "Origin of the fulfillment verifier service, with no path — the caller\nappends the verifier's own API paths. The gateway's `/defaults` response\nsupplies the default fulfillment verifier for each chain.\n";
+                    readonly example: "https://veri-fill.production-testnet.atum.xyz";
                 };
             };
         };
@@ -2246,16 +2336,30 @@ declare const $VerifiableCredential: {
 };
 declare const $PaymentResponse: {
     readonly type: "object";
-    readonly description: "Response from submitting a payment request. If processing completes within 30 seconds,\nthe response will include a fulfillment_confirmation with full settlement details.\nOtherwise, you'll receive a payment_id that you can use to poll the\n/v1/payments/{paymentId}/status endpoint for updates.\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` 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";
+    readonly required: readonly ["payment_id", "status", "idempotent_replay"];
     readonly properties: {
         readonly payment_id: {
             readonly type: "string";
             readonly description: "Unique ID for tracking this payment. Save this to check status later.\n";
             readonly example: "550e8400-e29b-41d4-a716-446655440000";
         };
+        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 idempotent_replay: {
+            readonly type: "boolean";
+            readonly description: "Whether this response describes a payment that already existed, rather than one\ncreated by this request. `true` means the request_id had been used before and you\nare being handed the ORIGINAL payment — no second payment was created and nothing\nadditional was charged.\n\n**Re-attempting a payment.** Re-submit the same request and you get the same payment\nback. You may re-send the original bytes unchanged: the deadlines will have expired by\nthen — `quote_deadline` bounds the auction and is short, while this endpoint may hold a\nsubmission for up to 30 seconds — and an expired deadline on a re-submission is not an\nerror, because the request is resolved onto the payment that already exists rather than\nused to create one.\n\nRe-signing with fresh deadlines is equally fine and returns the same payment. What you\nmust NOT change is the request_id, and what you must not change under it is the\npayment's economics — source, destination, fulfillment_amount, max_source_amount — which\nare rejected with 409 IDEMPOTENCY_TERMS_MISMATCH. Deadlines and the signature are\nexempt precisely so that a re-attempt is possible.\n\nA genuinely new payment needs a NEW request_id. In particular a `failed` payment is\nterminal: re-submitting its request_id keeps returning that dead payment, so recovering\nmeans starting a new one under a new key.\n\nPresent on every response, `false` for a newly created payment. A response without\nthe field is from a gateway predating it, not a newly created payment.\n\nThis is the field to read when reconciling a suspected double charge: two\nsubmissions where the second reports `true` are one payment, whereas two both\nreporting `false` are two. It says nothing about how far the payment has got —\nread `status` for that.\n";
+            readonly example: false;
+        };
         readonly fulfillment_confirmation: {
             readonly $ref: "#/components/schemas/FulfillmentConfirmation";
         };
+        readonly error: {
+            readonly $ref: "#/components/schemas/PaymentError";
+        };
     };
 };
 declare const $GetPaymentStatusResponse: {
@@ -2705,8 +2809,8 @@ declare const $CreateQuoteRequest: {
                 readonly endpoint: {
                     readonly type: "string";
                     readonly format: "uri";
-                    readonly description: "The API endpoint URL where the verification service can be reached";
-                    readonly example: "https://verifier.atum.network/api/v1/verify";
+                    readonly description: "Origin of the fulfillment verifier service, with no path — the caller\nappends the verifier's own API paths. The gateway's `/defaults` response\nsupplies the default fulfillment verifier for each chain.\n";
+                    readonly example: "https://veri-fill.production-testnet.atum.xyz";
                 };
             };
         };
@@ -2817,7 +2921,7 @@ declare const $Quote: {
         };
         readonly fulfillment_quote: {
             readonly type: "object";
-            readonly description: "The settler-signed FulfillmentQuote (structurally the canonical FulfillmentQuote/v1\ndeclaration at https://schemas.atum.network/declarations/FulfillmentQuote/v1), returned\nverbatim as an opaque signed document. A client recomputes quote_hash over the returned\nbytes and verifies the settler signature, then re-embeds them into\nbid_award.fulfillment_quote_json at award. quote_hash is canonicalization-based\n(URDNA2015), so it is stable across JSON key-order/whitespace normalization. The\nreturned bytes are hash-equivalent to, but not necessarily byte-identical with, what the\nsettler emitted (quotes are stored as JSONB, which normalizes on write). The gateway\nstill never re-serializes the quote through a typed struct (that renormalizes timestamp\nvalues and WOULD change quote_hash), so the Go binding exposes it as a raw JSON passthrough.\n";
+            readonly description: "The settler-signed FulfillmentQuote (structurally the canonical FulfillmentQuote/v1\ndeclaration at https://schemas.atum.xyz/declarations/FulfillmentQuote/v1), returned\nverbatim as an opaque signed document. A client recomputes quote_hash over the returned\nbytes and verifies the settler signature, then re-embeds them into\nbid_award.fulfillment_quote_json at award. quote_hash is canonicalization-based\n(URDNA2015), so it is stable across JSON key-order/whitespace normalization. The\nreturned bytes are hash-equivalent to, but not necessarily byte-identical with, what the\nsettler emitted (quotes are stored as JSONB, which normalizes on write). The gateway\nstill never re-serializes the quote through a typed struct (that renormalizes timestamp\nvalues and WOULD change quote_hash), so the Go binding exposes it as a raw JSON passthrough.\n";
             readonly 'x-go-type': "json.RawMessage";
         };
     };
@@ -2833,7 +2937,7 @@ declare const $AwardedQuote: {
         };
         readonly fulfillment_quote: {
             readonly type: "object";
-            readonly description: "The settler-signed FulfillmentQuote (structurally the canonical FulfillmentQuote/v1\ndeclaration at https://schemas.atum.network/declarations/FulfillmentQuote/v1), returned\nverbatim as an opaque signed document. A client recomputes quote_hash over the returned\nbytes and verifies the settler signature, then re-embeds them into\nbid_award.fulfillment_quote_json at award. quote_hash is canonicalization-based\n(URDNA2015), so it is stable across JSON key-order/whitespace normalization. The\nreturned bytes are hash-equivalent to, but not necessarily byte-identical with, what the\nsettler emitted (quotes are stored as JSONB, which normalizes on write). The gateway\nstill never re-serializes the quote through a typed struct (that renormalizes timestamp\nvalues and WOULD change quote_hash), so the Go binding exposes it as a raw JSON passthrough.\n";
+            readonly description: "The settler-signed FulfillmentQuote (structurally the canonical FulfillmentQuote/v1\ndeclaration at https://schemas.atum.xyz/declarations/FulfillmentQuote/v1), returned\nverbatim as an opaque signed document. A client recomputes quote_hash over the returned\nbytes and verifies the settler signature, then re-embeds them into\nbid_award.fulfillment_quote_json at award. quote_hash is canonicalization-based\n(URDNA2015), so it is stable across JSON key-order/whitespace normalization. The\nreturned bytes are hash-equivalent to, but not necessarily byte-identical with, what the\nsettler emitted (quotes are stored as JSONB, which normalizes on write). The gateway\nstill never re-serializes the quote through a typed struct (that renormalizes timestamp\nvalues and WOULD change quote_hash), so the Go binding exposes it as a raw JSON passthrough.\n";
             readonly 'x-go-type': "json.RawMessage";
         };
         readonly awarded_payment_id: {
@@ -3096,6 +3200,38 @@ declare class ApiError extends Error {
     constructor(request: ApiRequestOptions, response: ApiResult, message: string);
 }
 
+/**
+ * Type guard for the SDK's transport-level error.
+ *
+ * Every non-2xx gateway response is thrown by the generated client as an
+ * {@link ApiError}, which also carries the transport detail (`status`, `url`).
+ */
+declare function isApiError(err: unknown): err is ApiError;
+/**
+ * Return the typed, public-facing gateway error carried by a caught
+ * {@link ApiError}, or `undefined` when the value is not an `ApiError` or its
+ * body is not the public {@link ErrorResponse} shape.
+ *
+ * The gateway serializes errors as an {@link ErrorResponse}
+ * (`{ code, message, request_id?, docs_url?, domain? }`), but the generated
+ * client widens the parsed body to `unknown`. This helper narrows it back so
+ * consumers can branch on `code` and quote `request_id` to support. It only
+ * ever exposes this outward-facing shape — never any internal error taxonomy.
+ *
+ * @example
+ * try {
+ *   await client.payments.submitPayment({ requestBody });
+ * } catch (err) {
+ *   const gwError = getErrorResponse(err);
+ *   if (gwError) {
+ *     console.error(gwError.code, gwError.message, gwError.request_id);
+ *   } else {
+ *     throw err;
+ *   }
+ * }
+ */
+declare function getErrorResponse(err: unknown): ErrorResponse | undefined;
+
 /**
  * EVM Permit2 PermitWitnessTransferFrom deposit prehash + EIP-712 digest.
  *
@@ -3486,6 +3622,21 @@ declare const PAYMENT_REQUEST_VERSION = "1.0";
 declare function signPaymentRequest(request: PaymentRequest, signer: SenderSigner): Promise<PaymentRequest>;
 type HttpRequestConstructor = new (config: OpenAPIConfig) => BaseHttpRequest;
 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.
+ *
+ * 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.
+ */
+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
@@ -3658,4 +3809,4 @@ declare class PaymentGatewayClient extends PaymentGatewayClient$1 {
     }): Promise<CreateQuoteRequest>;
 }
 
-export { $AuthorizationResult, $AwardAccepted, $AwardRequest, $AwardResponse, $AwardedPayment, $AwardedQuote, $BidAward, $CreateQuoteRequest, $DataIntegrityProof, $ErrorResponse, $FulfillmentConfirmation, $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 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 CreateQuoteRequest, type CreateQuoteRequestData, type CreateQuoteRequestResponse, DEFAULT_FULFILLMENT_DEADLINE_SECONDS, DEFAULT_PAYMENT_QUOTE_DEADLINE_SECONDS, DEFAULT_QUOTE_DEADLINE_SECONDS, DEPOSIT_MESSAGE_SIZE, type DataIntegrityProof, type ErrorResponse, type FulfillmentConfirmation, type GetPaymentStatusData, type GetPaymentStatusResponse, type GetPaymentStatusResponse2, type GetPaymentTimelineData, type GetPaymentTimelineResponse, type GetQuoteRequestStatusData, type GetQuoteRequestStatusResponse, type HealthCheckResponse, HealthService, Interceptors, MAX_VALID_SLOT, type OnCancel, OpenAPI, type OpenAPIConfig, type OwnedAsset, PAYMENT_REQUEST_VERSION, PERMIT2_CONTRACT_ADDRESS, type PaymentBlockchainContext, type PaymentError, PaymentGatewayClient, 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 ResolvePaymentData, type ResolvePaymentResponse, type ResolvePaymentResponse2, type SenderAuth, type SenderAuthMessageScheme, type SenderSignature, type SenderSigner, type SenderSignerOptions, type SignedMessage, type SolanaClusterUnixTimeReader, type SolanaDepositParams, type SolanaDepositPrehash, type SubmitPaymentData, type SubmitPaymentResponse, TOTAL_BUCKETS, type TimelineError, type TimelineStep, type TurnkeyConfig, TurnkeySenderSigner, type TvmPermitWitnessTransferFromParams, type VerifiableCredential, type VerifiableCredentialAuth, base58ToBytes, base58ToHex, bytesToHex, createPermitWitnessTransferFromPrehash, createSenderSigner, createSolanaDepositPrehash, createTvmPermitWitnessTransferFromPrehash, defaultGateway, type domain, encodeU64LE, type error_code, generateSolanaNonce, generateSolanaPaymentId, hashPermitWitnessTransferFrom, hashRequestId, hashSolanaDeposit, hashTvmPermitWitnessTransferFrom, hexToBytes, maskChainId, normalizeAddress, resolveTurnkeyAddresses, signPaymentRequest, type status, type status2, type status3, type status4, type status5, type status6, type status7, type status8, type status9 };
+export { $AuthorizationResult, $AwardAccepted, $AwardRequest, $AwardResponse, $AwardedPayment, $AwardedQuote, $BidAward, $CreateQuoteRequest, $DataIntegrityProof, $ErrorResponse, $FulfillmentConfirmation, $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 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 CreateQuoteRequest, type CreateQuoteRequestData, type CreateQuoteRequestResponse, DEFAULT_FULFILLMENT_DEADLINE_SECONDS, DEFAULT_PAYMENT_QUOTE_DEADLINE_SECONDS, DEFAULT_QUOTE_DEADLINE_SECONDS, DEPOSIT_MESSAGE_SIZE, type DataIntegrityProof, type ErrorResponse, type FulfillmentConfirmation, type GetPaymentStatusData, type GetPaymentStatusResponse, type GetPaymentStatusResponse2, type GetPaymentTimelineData, type GetPaymentTimelineResponse, type GetQuoteRequestStatusData, type GetQuoteRequestStatusResponse, type HealthCheckResponse, HealthService, Interceptors, MAX_VALID_SLOT, type OnCancel, OpenAPI, type OpenAPIConfig, type OwnedAsset, PAYMENT_REQUEST_VERSION, PERMIT2_CONTRACT_ADDRESS, type PaymentBlockchainContext, type PaymentError, PaymentGatewayClient, 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 ResolvePaymentData, type ResolvePaymentResponse, type ResolvePaymentResponse2, type SenderAuth, type SenderAuthMessageScheme, type SenderSignature, type SenderSigner, type SenderSignerOptions, type SignedMessage, type SolanaClusterUnixTimeReader, type SolanaDepositParams, type SolanaDepositPrehash, type SubmitPaymentData, type SubmitPaymentResponse, TOTAL_BUCKETS, type TimelineError, type TimelineStep, type TurnkeyConfig, TurnkeySenderSigner, type TvmPermitWitnessTransferFromParams, type VerifiableCredential, type VerifiableCredentialAuth, base58ToBytes, base58ToHex, bytesToHex, createPermitWitnessTransferFromPrehash, createSenderSigner, createSolanaDepositPrehash, createTvmPermitWitnessTransferFromPrehash, defaultGateway, type domain, encodeU64LE, type error_code, generateSolanaNonce, generateSolanaPaymentId, getErrorResponse, hashPermitWitnessTransferFrom, hashRequestId, hashSolanaDeposit, hashTvmPermitWitnessTransferFrom, hexToBytes, isApiError, maskChainId, normalizeAddress, resolveTurnkeyAddresses, signPaymentRequest, type status, type status2, type status3, type status4, type status5, type status6, type status7, type status8, type status9 };