vesant-sdk 1.8.0-dev.0a33430 → 1.8.0-dev.237d268

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -272,9 +272,11 @@ interface KycVerificationTriggers {
272
272
  /**
273
273
  * Manual KYC Verification: whether customers may start a verification
274
274
  * themselves (`trigger_event: "manual"`), independent of the event
275
- * triggers. On by default. When off, a `manual` request answers
276
- * `kyc_required: false` with reason `KYC_NOT_REQUIRED_TRIGGER_DISABLED`;
277
- * hide your Verification option in that case.
275
+ * triggers and of their status. On by default. When on, a `manual`
276
+ * request always returns a link — an already verified customer included.
277
+ * When off, it answers `kyc_required: false` with reason
278
+ * `KYC_NOT_REQUIRED_TRIGGER_DISABLED`; hide your Verification option in
279
+ * that case.
278
280
  */
279
281
  manual: boolean;
280
282
  /** Hold sensitive profile changes (name, DOB, address) behind KYC. */
@@ -512,9 +514,10 @@ interface RequestKycSubmitLinkRequest {
512
514
  * trigger preferences decide, per event, whether KYC is required
513
515
  * (`kyc_required` in the response). "manual" — the customer starting
514
516
  * verification themselves — is governed by the tenant's Manual KYC
515
- * Verification toggle (on by default) and honors the allow-skip-on-manual
516
- * option (`can_skip`); when the toggle is off it answers `kyc_required:
517
- * false` with `KYC_NOT_REQUIRED_TRIGGER_DISABLED`. "login"
517
+ * Verification toggle (on by default): when on it always returns a link,
518
+ * even for an already verified customer, and honors the
519
+ * allow-skip-on-manual option (`can_skip`); when off it answers
520
+ * `kyc_required: false` with `KYC_NOT_REQUIRED_TRIGGER_DISABLED`. "login"
518
521
  * answers for any customer state — never verified (asked, not skippable),
519
522
  * document expired (asked, skippable so you can offer "Remind me later"),
520
523
  * or verified and valid (not asked) — so a platform that gates entry on KYC
@@ -639,7 +642,8 @@ interface RequestKycSubmitLinkResponse {
639
642
  * Whether the user may skip verification. `true` for
640
643
  * `trigger_event: "manual"` when the tenant enables allow-skip-on-manual,
641
644
  * for `"login"` when an expired identity document triggered the request
642
- * (offer "Remind me later"), and when the customer is already verified.
645
+ * (offer "Remind me later"), and when the customer is already verified
646
+ * (except on `"manual"`, which always issues a link while enabled).
643
647
  * Always `false` at `"withdrawal"` / `"purchase"` — that is where a
644
648
  * postponed re-verification becomes mandatory.
645
649
  */
@@ -272,9 +272,11 @@ interface KycVerificationTriggers {
272
272
  /**
273
273
  * Manual KYC Verification: whether customers may start a verification
274
274
  * themselves (`trigger_event: "manual"`), independent of the event
275
- * triggers. On by default. When off, a `manual` request answers
276
- * `kyc_required: false` with reason `KYC_NOT_REQUIRED_TRIGGER_DISABLED`;
277
- * hide your Verification option in that case.
275
+ * triggers and of their status. On by default. When on, a `manual`
276
+ * request always returns a link — an already verified customer included.
277
+ * When off, it answers `kyc_required: false` with reason
278
+ * `KYC_NOT_REQUIRED_TRIGGER_DISABLED`; hide your Verification option in
279
+ * that case.
278
280
  */
279
281
  manual: boolean;
280
282
  /** Hold sensitive profile changes (name, DOB, address) behind KYC. */
@@ -512,9 +514,10 @@ interface RequestKycSubmitLinkRequest {
512
514
  * trigger preferences decide, per event, whether KYC is required
513
515
  * (`kyc_required` in the response). "manual" — the customer starting
514
516
  * verification themselves — is governed by the tenant's Manual KYC
515
- * Verification toggle (on by default) and honors the allow-skip-on-manual
516
- * option (`can_skip`); when the toggle is off it answers `kyc_required:
517
- * false` with `KYC_NOT_REQUIRED_TRIGGER_DISABLED`. "login"
517
+ * Verification toggle (on by default): when on it always returns a link,
518
+ * even for an already verified customer, and honors the
519
+ * allow-skip-on-manual option (`can_skip`); when off it answers
520
+ * `kyc_required: false` with `KYC_NOT_REQUIRED_TRIGGER_DISABLED`. "login"
518
521
  * answers for any customer state — never verified (asked, not skippable),
519
522
  * document expired (asked, skippable so you can offer "Remind me later"),
520
523
  * or verified and valid (not asked) — so a platform that gates entry on KYC
@@ -639,7 +642,8 @@ interface RequestKycSubmitLinkResponse {
639
642
  * Whether the user may skip verification. `true` for
640
643
  * `trigger_event: "manual"` when the tenant enables allow-skip-on-manual,
641
644
  * for `"login"` when an expired identity document triggered the request
642
- * (offer "Remind me later"), and when the customer is already verified.
645
+ * (offer "Remind me later"), and when the customer is already verified
646
+ * (except on `"manual"`, which always issues a link while enabled).
643
647
  * Always `false` at `"withdrawal"` / `"purchase"` — that is where a
644
648
  * postponed re-verification becomes mandatory.
645
649
  */