@stacknet/keyutils 0.5.0 → 0.6.0

package/dist/types/index.d.cts

@@ -94,10 +94,19 @@ type EligibleKey = NodeKeyInfo & {
 };
 type PayoutAccountMethod = 'stripe' | 'solana';
 /**
- * The user's saved payout account. One method per user, by design — switching
- * methods replaces the previous record. Stripe Connect uses Express accounts
- * driven by the stack's platform credentials; Solana uses a wallet address
- * the user proved control of by signing a server-issued nonce.
+ * The user's saved payout config in the context of one stack.
+ *
+ * Stripe Connect is per-(user, stack) — each stack runs its own platform
+ * under its own secret, so a given user has independent connected accounts
+ * across stacks. The `stripe` field reflects the connection for the SCOPE
+ * stack only; query other stacks via `useUserStripeStacks()` or by passing
+ * a different `stackId` to `usePayoutAccount`.
+ *
+ * The Solana wallet is global (one verified address services every stack).
+ *
+ * `method` records the user's preferred rail. The active filing flow
+ * verifies the chosen rail is configured for the key's originating stack
+ * and falls back to a clear error if not.
  */
 interface PayoutAccount {
     /** Which method is currently configured. `null` when nothing is set up. */
@@ -123,6 +132,19 @@ interface PayoutAccount {
         verifiedAt: string;
     };
 }
+/**
+ * One stack the user has a Stripe Connect account on. Returned by
+ * `useUserStripeStacks()` for the multi-stack settings view.
+ */
+interface StripeStackPayout {
+    stackId: string;
+    accountIdMasked: string;
+    chargesEnabled: boolean;
+    payoutsEnabled: boolean;
+    detailsSubmitted: boolean;
+    pendingOnboardingUrl?: string | null;
+    updatedAt: string;
+}
 interface CryptoNonceResponse {
     nonce: string;
     /** Canonical message the wallet must sign — includes the nonce. */
@@ -224,4 +246,4 @@ interface KeyUtilsCallbacks {
     onFilingError?: (error: Error) => void;
 }
 
-export type { CryptoNonceResponse, DirectTransferResult, EligibleKey, FilingDetail, FilingHistoryEntry, FilingResult, FilingStatus, FilingTrackerState, FilingTrackerStatus, FilingTrackerStep, KeyListing, KeyUtilsCallbacks, KeyUtilsConfig, KeyWidgetTab, LedgerEntry, ListingResult, MintResult, NodeKeyInfo, PaymentMethod, PayoutAccount, PayoutAccountMethod, PayoutMethod, Platform, PlatformDownload, PricingInfo, StackPayoutCapabilities, StripeConnectStartResponse };
+export type { CryptoNonceResponse, DirectTransferResult, EligibleKey, FilingDetail, FilingHistoryEntry, FilingResult, FilingStatus, FilingTrackerState, FilingTrackerStatus, FilingTrackerStep, KeyListing, KeyUtilsCallbacks, KeyUtilsConfig, KeyWidgetTab, LedgerEntry, ListingResult, MintResult, NodeKeyInfo, PaymentMethod, PayoutAccount, PayoutAccountMethod, PayoutMethod, Platform, PlatformDownload, PricingInfo, StackPayoutCapabilities, StripeConnectStartResponse, StripeStackPayout };

package/dist/types/index.d.ts

@@ -94,10 +94,19 @@ type EligibleKey = NodeKeyInfo & {
 };
 type PayoutAccountMethod = 'stripe' | 'solana';
 /**
- * The user's saved payout account. One method per user, by design — switching
- * methods replaces the previous record. Stripe Connect uses Express accounts
- * driven by the stack's platform credentials; Solana uses a wallet address
- * the user proved control of by signing a server-issued nonce.
+ * The user's saved payout config in the context of one stack.
+ *
+ * Stripe Connect is per-(user, stack) — each stack runs its own platform
+ * under its own secret, so a given user has independent connected accounts
+ * across stacks. The `stripe` field reflects the connection for the SCOPE
+ * stack only; query other stacks via `useUserStripeStacks()` or by passing
+ * a different `stackId` to `usePayoutAccount`.
+ *
+ * The Solana wallet is global (one verified address services every stack).
+ *
+ * `method` records the user's preferred rail. The active filing flow
+ * verifies the chosen rail is configured for the key's originating stack
+ * and falls back to a clear error if not.
  */
 interface PayoutAccount {
     /** Which method is currently configured. `null` when nothing is set up. */
@@ -123,6 +132,19 @@ interface PayoutAccount {
         verifiedAt: string;
     };
 }
+/**
+ * One stack the user has a Stripe Connect account on. Returned by
+ * `useUserStripeStacks()` for the multi-stack settings view.
+ */
+interface StripeStackPayout {
+    stackId: string;
+    accountIdMasked: string;
+    chargesEnabled: boolean;
+    payoutsEnabled: boolean;
+    detailsSubmitted: boolean;
+    pendingOnboardingUrl?: string | null;
+    updatedAt: string;
+}
 interface CryptoNonceResponse {
     nonce: string;
     /** Canonical message the wallet must sign — includes the nonce. */
@@ -224,4 +246,4 @@ interface KeyUtilsCallbacks {
     onFilingError?: (error: Error) => void;
 }
 
-export type { CryptoNonceResponse, DirectTransferResult, EligibleKey, FilingDetail, FilingHistoryEntry, FilingResult, FilingStatus, FilingTrackerState, FilingTrackerStatus, FilingTrackerStep, KeyListing, KeyUtilsCallbacks, KeyUtilsConfig, KeyWidgetTab, LedgerEntry, ListingResult, MintResult, NodeKeyInfo, PaymentMethod, PayoutAccount, PayoutAccountMethod, PayoutMethod, Platform, PlatformDownload, PricingInfo, StackPayoutCapabilities, StripeConnectStartResponse };
+export type { CryptoNonceResponse, DirectTransferResult, EligibleKey, FilingDetail, FilingHistoryEntry, FilingResult, FilingStatus, FilingTrackerState, FilingTrackerStatus, FilingTrackerStep, KeyListing, KeyUtilsCallbacks, KeyUtilsConfig, KeyWidgetTab, LedgerEntry, ListingResult, MintResult, NodeKeyInfo, PaymentMethod, PayoutAccount, PayoutAccountMethod, PayoutMethod, Platform, PlatformDownload, PricingInfo, StackPayoutCapabilities, StripeConnectStartResponse, StripeStackPayout };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stacknet/keyutils",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "Reusable components for buying and managing StackNet node keys",
   "type": "module",
   "main": "./dist/index.cjs",