moltspay 1.5.0 → 2.0.0

package/dist/client/index.d.mts

@@ -10,6 +10,13 @@ interface ClientConfig {
         maxPerTx: number;
         maxPerDay: number;
     };
+    /**
+     * Ordered rail preference (2.0.0). When the server's 402 offers more than
+     * one rail (e.g. USDC on Base AND CNY via Alipay) and the caller didn't
+     * pass an explicit `rail`, the first entry here that the server also
+     * accepts wins. e.g. `["base", "alipay"]`.
+     */
+    railPreference?: string[];
 }
 interface WalletData {
     address: string;
@@ -62,6 +69,10 @@ interface VerifyResponse {
 }
 interface MoltsPayClientOptions {
     configDir?: string;
+    /** Ordered rail preference; see {@link ClientConfig.railPreference}. */
+    railPreference?: string[];
+    /** Stable Alipay session id (else AIPAY_SESSION_ID, else a fresh UUID). */
+    alipaySessionId?: string;
 }
 
 /**
@@ -84,14 +95,35 @@ interface PayOptions {
     chain?: 'base' | 'polygon' | 'base_sepolia' | 'tempo_moderato' | 'bnb' | 'bnb_testnet' | 'solana' | 'solana_devnet';
     /** Send raw data at top level instead of wrapped in { params } */
     rawData?: boolean;
+    /**
+     * Explicit payment rail (2.0.0): `'alipay'` or a chain name. When set,
+     * routing skips the default crypto path. `'alipay'` dispatches to the
+     * alipay-bot-backed {@link AlipayClient} and needs no EVM wallet.
+     */
+    rail?: string;
+    /** Alipay: surfaced once the payment URL + tradeNo are known. */
+    onPaymentPending?: (info: {
+        paymentUrl: string;
+        shortenUrl?: string;
+        tradeNo: string;
+    }) => void;
+    /** Alipay: forward CLI output to the user verbatim (line by line). */
+    onLine?: (line: string) => void;
+    /** Alipay: overall budget; defaults to the challenge's pay_before window. */
+    timeoutMs?: number;
+    /** Cancellation (alipay poll loop). */
+    signal?: AbortSignal;
 }
 declare class MoltsPayClient {
     private configDir;
     private config;
     private walletData;
     private wallet;
+    private signer;
     private todaySpending;
     private lastSpendingReset;
+    private railPreference?;
+    private alipaySessionId?;
     constructor(options?: MoltsPayClientOptions);
     /**
      * Check if client is initialized (has wallet)
@@ -129,6 +161,16 @@ declare class MoltsPayClient {
      * @param options - Payment options (token selection)
      */
     pay(serverUrl: string, service: string, params: Record<string, any>, options?: PayOptions): Promise<Record<string, any>>;
+    /**
+     * Pay for a service over the Alipay fiat rail (2.0.0).
+     *
+     * Unlike the crypto path this needs no EVM wallet — it shells out to
+     * alipay-bot via {@link AlipayClient}. Flow: hit the resource with no
+     * payment to get the 402 challenge, confirm the server actually offers the
+     * alipay rail (selectRail), then run the 8-step state machine and return the
+     * resource body.
+     */
+    private payViaAlipay;
     /**
      * Handle MPP (Machine Payments Protocol) payment flow
      * Called when pay() detects WWW-Authenticate header in 402 response
@@ -161,6 +203,10 @@ declare class MoltsPayClient {
      * Sign EIP-3009 transferWithAuthorization (GASLESS)
      * This only signs - no on-chain transaction, no gas needed.
      * Supports both USDC and USDT.
+     *
+     * Delegates typed-data construction to `core/eip3009.ts` and the signature
+     * itself to `this.signer`. That way Web Client (Phase 4) can reuse the same
+     * flow with an EIP-1193 signer without duplicating typed-data layout.
      */
     private signEIP3009;
     /**

package/dist/client/index.d.ts

@@ -10,6 +10,13 @@ interface ClientConfig {
         maxPerTx: number;
         maxPerDay: number;
     };
+    /**
+     * Ordered rail preference (2.0.0). When the server's 402 offers more than
+     * one rail (e.g. USDC on Base AND CNY via Alipay) and the caller didn't
+     * pass an explicit `rail`, the first entry here that the server also
+     * accepts wins. e.g. `["base", "alipay"]`.
+     */
+    railPreference?: string[];
 }
 interface WalletData {
     address: string;
@@ -62,6 +69,10 @@ interface VerifyResponse {
 }
 interface MoltsPayClientOptions {
     configDir?: string;
+    /** Ordered rail preference; see {@link ClientConfig.railPreference}. */
+    railPreference?: string[];
+    /** Stable Alipay session id (else AIPAY_SESSION_ID, else a fresh UUID). */
+    alipaySessionId?: string;
 }
 
 /**
@@ -84,14 +95,35 @@ interface PayOptions {
     chain?: 'base' | 'polygon' | 'base_sepolia' | 'tempo_moderato' | 'bnb' | 'bnb_testnet' | 'solana' | 'solana_devnet';
     /** Send raw data at top level instead of wrapped in { params } */
     rawData?: boolean;
+    /**
+     * Explicit payment rail (2.0.0): `'alipay'` or a chain name. When set,
+     * routing skips the default crypto path. `'alipay'` dispatches to the
+     * alipay-bot-backed {@link AlipayClient} and needs no EVM wallet.
+     */
+    rail?: string;
+    /** Alipay: surfaced once the payment URL + tradeNo are known. */
+    onPaymentPending?: (info: {
+        paymentUrl: string;
+        shortenUrl?: string;
+        tradeNo: string;
+    }) => void;
+    /** Alipay: forward CLI output to the user verbatim (line by line). */
+    onLine?: (line: string) => void;
+    /** Alipay: overall budget; defaults to the challenge's pay_before window. */
+    timeoutMs?: number;
+    /** Cancellation (alipay poll loop). */
+    signal?: AbortSignal;
 }
 declare class MoltsPayClient {
     private configDir;
     private config;
     private walletData;
     private wallet;
+    private signer;
     private todaySpending;
     private lastSpendingReset;
+    private railPreference?;
+    private alipaySessionId?;
     constructor(options?: MoltsPayClientOptions);
     /**
      * Check if client is initialized (has wallet)
@@ -129,6 +161,16 @@ declare class MoltsPayClient {
      * @param options - Payment options (token selection)
      */
     pay(serverUrl: string, service: string, params: Record<string, any>, options?: PayOptions): Promise<Record<string, any>>;
+    /**
+     * Pay for a service over the Alipay fiat rail (2.0.0).
+     *
+     * Unlike the crypto path this needs no EVM wallet — it shells out to
+     * alipay-bot via {@link AlipayClient}. Flow: hit the resource with no
+     * payment to get the 402 challenge, confirm the server actually offers the
+     * alipay rail (selectRail), then run the 8-step state machine and return the
+     * resource body.
+     */
+    private payViaAlipay;
     /**
      * Handle MPP (Machine Payments Protocol) payment flow
      * Called when pay() detects WWW-Authenticate header in 402 response
@@ -161,6 +203,10 @@ declare class MoltsPayClient {
      * Sign EIP-3009 transferWithAuthorization (GASLESS)
      * This only signs - no on-chain transaction, no gas needed.
      * Supports both USDC and USDT.
+     *
+     * Delegates typed-data construction to `core/eip3009.ts` and the signature
+     * itself to `this.signer`. That way Web Client (Phase 4) can reuse the same
+     * flow with an EIP-1193 signer without duplicating typed-data layout.
      */
     private signEIP3009;
     /**