@notabene/javascript-sdk 2.20.0-next.3 → 2.20.0-next.5

package/dist/cjs/notabene.d.ts

@@ -3347,6 +3347,63 @@ export declare interface TransactionOptions {
     contactSupport?: ContactSupportConfig;
     consent?: ConsentConfig;
     autoSubmit?: boolean;
+    /**
+     * Wallet connection behaviour.
+     */
+    wallets?: {
+        /**
+         * EXPERIMENTAL. No stability guarantee; may change or be removed in a minor release.
+         *
+         * Prefer a wallet's `https://` universal link over its custom scheme (for example
+         * `metamask://`) when connecting a mobile wallet. Useful when embedding inside a mobile
+         * in-app webview, which cannot launch another app on its own and so needs the host app
+         * to handle every custom scheme it might encounter.
+         *
+         * Off by default. Has no effect for wallets whose registry entry declares no universal
+         * link, which is most of them today. Where a wallet does declare one, this also changes
+         * behaviour in an ordinary mobile browser, and a universal link can be worse there if
+         * the wallet's Android app links are not verified.
+         *
+         * Behaviour therefore depends on the wallet and on your host app. Verify against the
+         * wallets your users actually use before enabling this in production.
+         *
+         * @defaultValue false
+         */
+        experimentalPreferUniversalLinks?: boolean;
+        /**
+         * Restrict the mobile wallets offered over WalletConnect to this list.
+         *
+         * Useful when you only support a fixed set of wallets, for example because your app
+         * allowlists their deep links, or because your compliance policy approves specific
+         * wallets.
+         *
+         * Entries are WalletConnect Explorer wallet ids, 64-character hex strings. Wallet names
+         * are not accepted, because the Explorer registry keys on these ids. Look them up in
+         * Reown's Wallets List (https://docs.reown.com/cloud/wallets/wallet-list) or WalletGuide
+         * (https://walletguide.walletconnect.network/).
+         *
+         * A wallet can have more than one id. Coinbase, Binance, OKX and Talisman each have two
+         * Explorer listings, so list every id for a wallet or one of its listings will still be
+         * offered.
+         *
+         * This restricts WalletConnect's own wallet list only. It does not restrict browser
+         * extension wallets, does not affect hardware wallets, and does not control whether
+         * WalletConnect is offered at all.
+         *
+         * Absent or empty means no restriction.
+         *
+         * @example
+         * ```ts
+         * // MetaMask and both Coinbase listings
+         * allowedWalletConnectIds: [
+         *   'c57ca95b47569778a828d19178114f4db188b89b763c899ba0be274e97267d96',
+         *   'fd20dc426fb37566d803205b19bbc1d4096b248ac04548e3cfb6b3a38bd033aa',
+         *   'd0ca99ff52b99abc48743dad0f7fc891e041be73574f7fac4afe5d4bb83845c8'
+         * ]
+         * ```
+         */
+        allowedWalletConnectIds?: string[];
+    };
 }
 
 /**

package/dist/cjs/package.json

@@ -10,7 +10,7 @@
   "author": "Notabene <developers@notabene.id>",
   "license": "MIT",
   "packageManager": "yarn@4.5.1",
-  "version": "2.20.0-next.3",
+  "version": "2.20.0-next.5",
   "source": "src/notabene.ts",
   "main": "dist/cjs/notabene.cjs",
   "module": "dist/esm/notabene.js",

package/dist/esm/notabene.d.ts

@@ -3347,6 +3347,63 @@ export declare interface TransactionOptions {
     contactSupport?: ContactSupportConfig;
     consent?: ConsentConfig;
     autoSubmit?: boolean;
+    /**
+     * Wallet connection behaviour.
+     */
+    wallets?: {
+        /**
+         * EXPERIMENTAL. No stability guarantee; may change or be removed in a minor release.
+         *
+         * Prefer a wallet's `https://` universal link over its custom scheme (for example
+         * `metamask://`) when connecting a mobile wallet. Useful when embedding inside a mobile
+         * in-app webview, which cannot launch another app on its own and so needs the host app
+         * to handle every custom scheme it might encounter.
+         *
+         * Off by default. Has no effect for wallets whose registry entry declares no universal
+         * link, which is most of them today. Where a wallet does declare one, this also changes
+         * behaviour in an ordinary mobile browser, and a universal link can be worse there if
+         * the wallet's Android app links are not verified.
+         *
+         * Behaviour therefore depends on the wallet and on your host app. Verify against the
+         * wallets your users actually use before enabling this in production.
+         *
+         * @defaultValue false
+         */
+        experimentalPreferUniversalLinks?: boolean;
+        /**
+         * Restrict the mobile wallets offered over WalletConnect to this list.
+         *
+         * Useful when you only support a fixed set of wallets, for example because your app
+         * allowlists their deep links, or because your compliance policy approves specific
+         * wallets.
+         *
+         * Entries are WalletConnect Explorer wallet ids, 64-character hex strings. Wallet names
+         * are not accepted, because the Explorer registry keys on these ids. Look them up in
+         * Reown's Wallets List (https://docs.reown.com/cloud/wallets/wallet-list) or WalletGuide
+         * (https://walletguide.walletconnect.network/).
+         *
+         * A wallet can have more than one id. Coinbase, Binance, OKX and Talisman each have two
+         * Explorer listings, so list every id for a wallet or one of its listings will still be
+         * offered.
+         *
+         * This restricts WalletConnect's own wallet list only. It does not restrict browser
+         * extension wallets, does not affect hardware wallets, and does not control whether
+         * WalletConnect is offered at all.
+         *
+         * Absent or empty means no restriction.
+         *
+         * @example
+         * ```ts
+         * // MetaMask and both Coinbase listings
+         * allowedWalletConnectIds: [
+         *   'c57ca95b47569778a828d19178114f4db188b89b763c899ba0be274e97267d96',
+         *   'fd20dc426fb37566d803205b19bbc1d4096b248ac04548e3cfb6b3a38bd033aa',
+         *   'd0ca99ff52b99abc48743dad0f7fc891e041be73574f7fac4afe5d4bb83845c8'
+         * ]
+         * ```
+         */
+        allowedWalletConnectIds?: string[];
+    };
 }
 
 /**

package/dist/esm/package.json

@@ -10,7 +10,7 @@
   "author": "Notabene <developers@notabene.id>",
   "license": "MIT",
   "packageManager": "yarn@4.5.1",
-  "version": "2.20.0-next.3",
+  "version": "2.20.0-next.5",
   "source": "src/notabene.ts",
   "main": "dist/cjs/notabene.cjs",
   "module": "dist/esm/notabene.js",

package/dist/notabene.d.ts

@@ -3347,6 +3347,63 @@ export declare interface TransactionOptions {
     contactSupport?: ContactSupportConfig;
     consent?: ConsentConfig;
     autoSubmit?: boolean;
+    /**
+     * Wallet connection behaviour.
+     */
+    wallets?: {
+        /**
+         * EXPERIMENTAL. No stability guarantee; may change or be removed in a minor release.
+         *
+         * Prefer a wallet's `https://` universal link over its custom scheme (for example
+         * `metamask://`) when connecting a mobile wallet. Useful when embedding inside a mobile
+         * in-app webview, which cannot launch another app on its own and so needs the host app
+         * to handle every custom scheme it might encounter.
+         *
+         * Off by default. Has no effect for wallets whose registry entry declares no universal
+         * link, which is most of them today. Where a wallet does declare one, this also changes
+         * behaviour in an ordinary mobile browser, and a universal link can be worse there if
+         * the wallet's Android app links are not verified.
+         *
+         * Behaviour therefore depends on the wallet and on your host app. Verify against the
+         * wallets your users actually use before enabling this in production.
+         *
+         * @defaultValue false
+         */
+        experimentalPreferUniversalLinks?: boolean;
+        /**
+         * Restrict the mobile wallets offered over WalletConnect to this list.
+         *
+         * Useful when you only support a fixed set of wallets, for example because your app
+         * allowlists their deep links, or because your compliance policy approves specific
+         * wallets.
+         *
+         * Entries are WalletConnect Explorer wallet ids, 64-character hex strings. Wallet names
+         * are not accepted, because the Explorer registry keys on these ids. Look them up in
+         * Reown's Wallets List (https://docs.reown.com/cloud/wallets/wallet-list) or WalletGuide
+         * (https://walletguide.walletconnect.network/).
+         *
+         * A wallet can have more than one id. Coinbase, Binance, OKX and Talisman each have two
+         * Explorer listings, so list every id for a wallet or one of its listings will still be
+         * offered.
+         *
+         * This restricts WalletConnect's own wallet list only. It does not restrict browser
+         * extension wallets, does not affect hardware wallets, and does not control whether
+         * WalletConnect is offered at all.
+         *
+         * Absent or empty means no restriction.
+         *
+         * @example
+         * ```ts
+         * // MetaMask and both Coinbase listings
+         * allowedWalletConnectIds: [
+         *   'c57ca95b47569778a828d19178114f4db188b89b763c899ba0be274e97267d96',
+         *   'fd20dc426fb37566d803205b19bbc1d4096b248ac04548e3cfb6b3a38bd033aa',
+         *   'd0ca99ff52b99abc48743dad0f7fc891e041be73574f7fac4afe5d4bb83845c8'
+         * ]
+         * ```
+         */
+        allowedWalletConnectIds?: string[];
+    };
 }
 
 /**

package/package.json

@@ -10,7 +10,7 @@
   "author": "Notabene <developers@notabene.id>",
   "license": "MIT",
   "packageManager": "yarn@4.5.1",
-  "version": "2.20.0-next.3",
+  "version": "2.20.0-next.5",
   "source": "src/notabene.ts",
   "main": "dist/cjs/notabene.cjs",
   "module": "dist/esm/notabene.js",

package/src/types.ts

@@ -1044,6 +1044,63 @@ export interface TransactionOptions {
   contactSupport?: ContactSupportConfig; // Requires 'contact-support' in agentSections
   consent?: ConsentConfig; // Defaults to true
   autoSubmit?: boolean; // Defaults to false
+  /**
+   * Wallet connection behaviour.
+   */
+  wallets?: {
+    /**
+     * EXPERIMENTAL. No stability guarantee; may change or be removed in a minor release.
+     *
+     * Prefer a wallet's `https://` universal link over its custom scheme (for example
+     * `metamask://`) when connecting a mobile wallet. Useful when embedding inside a mobile
+     * in-app webview, which cannot launch another app on its own and so needs the host app
+     * to handle every custom scheme it might encounter.
+     *
+     * Off by default. Has no effect for wallets whose registry entry declares no universal
+     * link, which is most of them today. Where a wallet does declare one, this also changes
+     * behaviour in an ordinary mobile browser, and a universal link can be worse there if
+     * the wallet's Android app links are not verified.
+     *
+     * Behaviour therefore depends on the wallet and on your host app. Verify against the
+     * wallets your users actually use before enabling this in production.
+     *
+     * @defaultValue false
+     */
+    experimentalPreferUniversalLinks?: boolean;
+    /**
+     * Restrict the mobile wallets offered over WalletConnect to this list.
+     *
+     * Useful when you only support a fixed set of wallets, for example because your app
+     * allowlists their deep links, or because your compliance policy approves specific
+     * wallets.
+     *
+     * Entries are WalletConnect Explorer wallet ids, 64-character hex strings. Wallet names
+     * are not accepted, because the Explorer registry keys on these ids. Look them up in
+     * Reown's Wallets List (https://docs.reown.com/cloud/wallets/wallet-list) or WalletGuide
+     * (https://walletguide.walletconnect.network/).
+     *
+     * A wallet can have more than one id. Coinbase, Binance, OKX and Talisman each have two
+     * Explorer listings, so list every id for a wallet or one of its listings will still be
+     * offered.
+     *
+     * This restricts WalletConnect's own wallet list only. It does not restrict browser
+     * extension wallets, does not affect hardware wallets, and does not control whether
+     * WalletConnect is offered at all.
+     *
+     * Absent or empty means no restriction.
+     *
+     * @example
+     * ```ts
+     * // MetaMask and both Coinbase listings
+     * allowedWalletConnectIds: [
+     *   'c57ca95b47569778a828d19178114f4db188b89b763c899ba0be274e97267d96',
+     *   'fd20dc426fb37566d803205b19bbc1d4096b248ac04548e3cfb6b3a38bd033aa',
+     *   'd0ca99ff52b99abc48743dad0f7fc891e041be73574f7fac4afe5d4bb83845c8'
+     * ]
+     * ```
+     */
+    allowedWalletConnectIds?: string[];
+  };
 }
 /**
  * Component Message Type enum representing different message types that can be sent