vesant-sdk 2.0.0-next.c8fef46 → 2.0.0-next.f2f4e87

package/dist/kyc/index.d.mts

@@ -120,14 +120,13 @@ interface UpdateKycAlertRequest {
     status?: KycAlertStatus;
 }
 /**
- * Threshold-gated trigger for transaction events.
+ * Threshold-gated trigger for transaction events. Each rule is
+ * self-contained — there is no umbrella flag.
  *
- * - `enabled=false` + umbrella `transaction=false` → event blocked.
+ * - `enabled=false` → event blocked.
  * - `enabled=true`, `threshold=0` (or null/omitted) → every event of this
  *   type triggers Re-Use KYC, regardless of amount.
  * - `enabled=true`, `threshold>0` → only amounts `>= threshold` trigger.
- * - `enabled=false` + umbrella `transaction=true` → triggers on any
- *   amount; the threshold is ignored when the specific rule is disabled.
  */
 interface ReuseKycThresholdTrigger {
     enabled: boolean;
@@ -159,11 +158,6 @@ interface ReuseKycTriggers {
     new_device_or_location: boolean;
     device_fingerprint_change: boolean;
     payment_method_change: boolean;
-    /**
-     * Legacy umbrella flag. When true and a specific transaction rule is
-     * not configured, any transaction triggers Re-Use KYC.
-     */
-    transaction: boolean;
     deposit: ReuseKycThresholdTrigger;
     withdrawal: ReuseKycThresholdTrigger;
     large_bet_placement: ReuseKycThresholdTrigger;
@@ -312,27 +306,22 @@ interface RequestKycSubmitLinkRequest {
  * Trigger events that can request Re-Use KYC.
  *
  * Account-sensitive: any sensitive change to the account profile.
- * Transaction events: covered by the per-event threshold rules in
- * `ReuseKycTriggers` (`deposit`, `withdrawal`, `large_bet_placement`) or
- * the umbrella `transaction` flag.
- *
- * The legacy `"login"` and `"transactions"` strings are accepted for
- * backwards compatibility with older SDK clients that didn't have the
- * fine-grained event enum.
+ * Transaction events: covered by the per-event rules in
+ * `ReuseKycTriggers` (`deposit`, `withdrawal`, `large_bet_placement`,
+ * `high_frequency_betting`, `account_balance_transfer`).
  */
-type ReuseKycEvent = 'login' | 'password_change' | 'name_change' | 'phone_number_change' | 'two_factor_auth_change' | 'new_device_or_location' | 'device_fingerprint_change' | 'payment_method_change' | 'deposit' | 'withdrawal' | 'large_bet_placement' | 'high_frequency_betting' | 'account_balance_transfer'
-/** Legacy umbrella string accepted by the server. */
- | 'transactions';
+type ReuseKycEvent = 'login' | 'password_change' | 'name_change' | 'phone_number_change' | 'two_factor_auth_change' | 'new_device_or_location' | 'device_fingerprint_change' | 'payment_method_change' | 'deposit' | 'withdrawal' | 'large_bet_placement' | 'high_frequency_betting' | 'account_balance_transfer';
 interface CreateReuseKycSessionRequest {
     /** Unique reference for the KYC session (e.g., customer ID or transaction ID) */
     reference: string;
     /** Customer ID to associate with the KYC session */
     customer_id: string;
     /**
-     * The triggering event. Preferred over `path`. When both are sent, the
-     * server uses `event` and silently ignores `path`.
+     * The triggering event. One of the `ReuseKycEvent` union members.
+     * Required — when empty, the server falls through to the unknown-event
+     * passthrough and allows the request silently.
      */
-    event?: ReuseKycEvent;
+    event: ReuseKycEvent;
     /**
      * USD amount associated with the event. Required for threshold-gated
      * events (`deposit`, `withdrawal`, `large_bet_placement`); ignored for
@@ -340,12 +329,6 @@ interface CreateReuseKycSessionRequest {
      * session.
      */
     amount?: number;
-    /**
-     * Legacy path field — `"login"` or `"transactions"`. Use `event`
-     * instead. Kept for older SDK clients.
-     * @deprecated Send `event` instead.
-     */
-    path?: string;
     /**
      * Number of qualifying events the customer has performed in the
      * window described by `event_window_minutes`. Required for

package/dist/kyc/index.d.ts

@@ -120,14 +120,13 @@ interface UpdateKycAlertRequest {
     status?: KycAlertStatus;
 }
 /**
- * Threshold-gated trigger for transaction events.
+ * Threshold-gated trigger for transaction events. Each rule is
+ * self-contained — there is no umbrella flag.
  *
- * - `enabled=false` + umbrella `transaction=false` → event blocked.
+ * - `enabled=false` → event blocked.
  * - `enabled=true`, `threshold=0` (or null/omitted) → every event of this
  *   type triggers Re-Use KYC, regardless of amount.
  * - `enabled=true`, `threshold>0` → only amounts `>= threshold` trigger.
- * - `enabled=false` + umbrella `transaction=true` → triggers on any
- *   amount; the threshold is ignored when the specific rule is disabled.
  */
 interface ReuseKycThresholdTrigger {
     enabled: boolean;
@@ -159,11 +158,6 @@ interface ReuseKycTriggers {
     new_device_or_location: boolean;
     device_fingerprint_change: boolean;
     payment_method_change: boolean;
-    /**
-     * Legacy umbrella flag. When true and a specific transaction rule is
-     * not configured, any transaction triggers Re-Use KYC.
-     */
-    transaction: boolean;
     deposit: ReuseKycThresholdTrigger;
     withdrawal: ReuseKycThresholdTrigger;
     large_bet_placement: ReuseKycThresholdTrigger;
@@ -312,27 +306,22 @@ interface RequestKycSubmitLinkRequest {
  * Trigger events that can request Re-Use KYC.
  *
  * Account-sensitive: any sensitive change to the account profile.
- * Transaction events: covered by the per-event threshold rules in
- * `ReuseKycTriggers` (`deposit`, `withdrawal`, `large_bet_placement`) or
- * the umbrella `transaction` flag.
- *
- * The legacy `"login"` and `"transactions"` strings are accepted for
- * backwards compatibility with older SDK clients that didn't have the
- * fine-grained event enum.
+ * Transaction events: covered by the per-event rules in
+ * `ReuseKycTriggers` (`deposit`, `withdrawal`, `large_bet_placement`,
+ * `high_frequency_betting`, `account_balance_transfer`).
  */
-type ReuseKycEvent = 'login' | 'password_change' | 'name_change' | 'phone_number_change' | 'two_factor_auth_change' | 'new_device_or_location' | 'device_fingerprint_change' | 'payment_method_change' | 'deposit' | 'withdrawal' | 'large_bet_placement' | 'high_frequency_betting' | 'account_balance_transfer'
-/** Legacy umbrella string accepted by the server. */
- | 'transactions';
+type ReuseKycEvent = 'login' | 'password_change' | 'name_change' | 'phone_number_change' | 'two_factor_auth_change' | 'new_device_or_location' | 'device_fingerprint_change' | 'payment_method_change' | 'deposit' | 'withdrawal' | 'large_bet_placement' | 'high_frequency_betting' | 'account_balance_transfer';
 interface CreateReuseKycSessionRequest {
     /** Unique reference for the KYC session (e.g., customer ID or transaction ID) */
     reference: string;
     /** Customer ID to associate with the KYC session */
     customer_id: string;
     /**
-     * The triggering event. Preferred over `path`. When both are sent, the
-     * server uses `event` and silently ignores `path`.
+     * The triggering event. One of the `ReuseKycEvent` union members.
+     * Required — when empty, the server falls through to the unknown-event
+     * passthrough and allows the request silently.
      */
-    event?: ReuseKycEvent;
+    event: ReuseKycEvent;
     /**
      * USD amount associated with the event. Required for threshold-gated
      * events (`deposit`, `withdrawal`, `large_bet_placement`); ignored for
@@ -340,12 +329,6 @@ interface CreateReuseKycSessionRequest {
      * session.
      */
     amount?: number;
-    /**
-     * Legacy path field — `"login"` or `"transactions"`. Use `event`
-     * instead. Kept for older SDK clients.
-     * @deprecated Send `event` instead.
-     */
-    path?: string;
     /**
      * Number of qualifying events the customer has performed in the
      * window described by `event_window_minutes`. Required for