vesant-sdk 1.8.0-dev.9f7204d → 1.8.0-dev.a509f3d

package/dist/kyc/index.d.mts

@@ -269,6 +269,14 @@ interface KycVerificationTriggers {
     first_purchase: boolean;
     /** Re-trigger verification once the customer's identity document has expired. */
     auto_trigger_on_id_expiration: boolean;
+    /**
+     * Manual KYC Verification: whether customers may start a verification
+     * themselves (`trigger_event: "manual"`), independent of the event
+     * triggers. On by default. When off, a `manual` request answers
+     * `kyc_required: false` with reason `KYC_NOT_REQUIRED_TRIGGER_DISABLED`;
+     * hide your Verification option in that case.
+     */
+    manual: boolean;
     /** Hold sensitive profile changes (name, DOB, address) behind KYC. */
     account_sensitive_action?: AccountSensitiveActionTrigger;
 }
@@ -438,8 +446,9 @@ interface UpdateKycStatusRequest {
 }
 /**
  * Events that can trigger a KYC request. Each maps to a per-event toggle in
- * the tenant's KYC verification trigger preferences, except `manual` (always
- * required) and `login` (only for an expired identity document).
+ * the tenant's KYC verification trigger preferences (`manual` to the Manual
+ * KYC Verification toggle), except `login` (only for an expired identity
+ * document).
  */
 type KycTriggerEvent = 'onboarding' | 'first_withdrawal' | 'first_purchase'
 /** Aliases of `first_withdrawal` / `first_purchase` — same tenant toggles. */
@@ -501,8 +510,11 @@ interface RequestKycSubmitLinkRequest {
     /**
      * Event that triggered the KYC request. The tenant's KYC verification
      * trigger preferences decide, per event, whether KYC is required
-     * (`kyc_required` in the response). "manual" always requires KYC and
-     * honors the tenant's allow-skip-on-manual option (`can_skip`). "login"
+     * (`kyc_required` in the response). "manual" — the customer starting
+     * verification themselves — is governed by the tenant's Manual KYC
+     * Verification toggle (on by default) and honors the allow-skip-on-manual
+     * option (`can_skip`); when the toggle is off it answers `kyc_required:
+     * false` with `KYC_NOT_REQUIRED_TRIGGER_DISABLED`. "login"
      * answers for any customer state — never verified (asked, not skippable),
      * document expired (asked, skippable so you can offer "Remind me later"),
      * or verified and valid (not asked) — so a platform that gates entry on KYC

package/dist/kyc/index.d.ts

@@ -269,6 +269,14 @@ interface KycVerificationTriggers {
     first_purchase: boolean;
     /** Re-trigger verification once the customer's identity document has expired. */
     auto_trigger_on_id_expiration: boolean;
+    /**
+     * Manual KYC Verification: whether customers may start a verification
+     * themselves (`trigger_event: "manual"`), independent of the event
+     * triggers. On by default. When off, a `manual` request answers
+     * `kyc_required: false` with reason `KYC_NOT_REQUIRED_TRIGGER_DISABLED`;
+     * hide your Verification option in that case.
+     */
+    manual: boolean;
     /** Hold sensitive profile changes (name, DOB, address) behind KYC. */
     account_sensitive_action?: AccountSensitiveActionTrigger;
 }
@@ -438,8 +446,9 @@ interface UpdateKycStatusRequest {
 }
 /**
  * Events that can trigger a KYC request. Each maps to a per-event toggle in
- * the tenant's KYC verification trigger preferences, except `manual` (always
- * required) and `login` (only for an expired identity document).
+ * the tenant's KYC verification trigger preferences (`manual` to the Manual
+ * KYC Verification toggle), except `login` (only for an expired identity
+ * document).
  */
 type KycTriggerEvent = 'onboarding' | 'first_withdrawal' | 'first_purchase'
 /** Aliases of `first_withdrawal` / `first_purchase` — same tenant toggles. */
@@ -501,8 +510,11 @@ interface RequestKycSubmitLinkRequest {
     /**
      * Event that triggered the KYC request. The tenant's KYC verification
      * trigger preferences decide, per event, whether KYC is required
-     * (`kyc_required` in the response). "manual" always requires KYC and
-     * honors the tenant's allow-skip-on-manual option (`can_skip`). "login"
+     * (`kyc_required` in the response). "manual" — the customer starting
+     * verification themselves — is governed by the tenant's Manual KYC
+     * Verification toggle (on by default) and honors the allow-skip-on-manual
+     * option (`can_skip`); when the toggle is off it answers `kyc_required:
+     * false` with `KYC_NOT_REQUIRED_TRIGGER_DISABLED`. "login"
      * answers for any customer state — never verified (asked, not skippable),
      * document expired (asked, skippable so you can offer "Remind me later"),
      * or verified and valid (not asked) — so a platform that gates entry on KYC