@delopay/sdk 0.100.0 → 0.100.2

package/dist/index.d.cts

@@ -1965,7 +1965,7 @@ interface ApiKeyCreateResponse {
     /**
      * The shop (business profile) this key is pinned to, or `null`/absent for
      * merchant-wide keys. Only populated by backends with profile-scoped API
-     * key support (DeloPay-net/delopay-backend#344); absent on older backends.
+     * key support; absent on older backends.
      */
     profile_id?: string | null;
 }
@@ -1981,7 +1981,7 @@ interface ApiKeyResponse {
     /**
      * The shop (business profile) this key is pinned to, or `null`/absent for
      * merchant-wide keys. Only populated by backends with profile-scoped API
-     * key support (DeloPay-net/delopay-backend#344); absent on older backends.
+     * key support; absent on older backends.
      */
     profile_id?: string | null;
 }
@@ -2127,7 +2127,7 @@ interface ProfileDeniedConnectorsResponse {
     denied_connectors: string[];
 }
 /**
- * A buyer-facing surcharge added to the checkout amount (issue #195).
+ * A buyer-facing surcharge added to the checkout amount.
  *
  * Either a flat amount in minor units, or a percentage of the order amount.
  */
@@ -4731,7 +4731,7 @@ interface SettlementLineBase {
 }
 /**
  * A line whose processor cost is known — the rail reported it, or a
- * configured schedule estimated it (be#843).
+ * configured schedule estimated it.
  *
  * `processor_cost_amount` is minor units of `processor_cost_currency`, which
  * is the processor's **own** settlement currency and not necessarily the
@@ -4822,7 +4822,7 @@ type LimitedOperation = 'refund';
 type OperationLimitScope = 'merchant' | 'role' | 'user';
 /**
  * What happens when an operation would exceed its limit. v1 ships `block`
- * only; `require_approval` (four-eyes) arrives with backend#342 phase 2.
+ * only; `require_approval` (four-eyes) arrives in a later release.
  */
 type OperationLimitOnExceeded = 'block';
 /** How the usage window is anchored. Rolling is the default. */
@@ -8777,7 +8777,7 @@ declare class CheckoutSession {
      * own types and runtime gates — hence the loose return type.
      *
      * `theme` is the route's one declared query parameter (a named checkout
-     * variant, backend#793). `locale` travels as `Accept-Language` — the only
+     * variant). `locale` travels as `Accept-Language` — the only
      * channel the backend's locale resolution reads; a `?locale=` query is
      * silently ignored by this route.
      *
@@ -8857,10 +8857,17 @@ declare class CheckoutSession {
     /**
      * A short-lived VGS Collect session for browser-side card capture.
      *
-     * A 404 — or a 400 carrying the "shop has no vault" code — means the shop
-     * has no vault configured; other errors must NOT be treated that way (a
-     * refused vault falling back to an unprotected card pane is exactly the
-     * bug this endpoint's error contract exists to prevent).
+     * **Exactly one refusal means "this shop has no vault": a 400 carrying
+     * `IR_19`.** Every other refusal means a vault exists and could not be used,
+     * and answering it by falling back to the processor's own card pane sends an
+     * unprotected card number to the very processor the shop pays to hide it
+     * from — the bug this endpoint's error contract exists to prevent.
+     *
+     * A **404 is not benign.** The router answers it when the shop's vault
+     * account cannot be found — the state a shop is left in when its vault
+     * connector is deleted while the profile keeps naming the id: it still
+     * reports the vault as enabled and still expects its cards cloaked. The same
+     * status also covers a payment that does not exist.
      *
      * `GET /payment-link/{merchantId}/{paymentId}/vault/collect-session`
      */

package/dist/index.d.ts

@@ -1965,7 +1965,7 @@ interface ApiKeyCreateResponse {
     /**
      * The shop (business profile) this key is pinned to, or `null`/absent for
      * merchant-wide keys. Only populated by backends with profile-scoped API
-     * key support (DeloPay-net/delopay-backend#344); absent on older backends.
+     * key support; absent on older backends.
      */
     profile_id?: string | null;
 }
@@ -1981,7 +1981,7 @@ interface ApiKeyResponse {
     /**
      * The shop (business profile) this key is pinned to, or `null`/absent for
      * merchant-wide keys. Only populated by backends with profile-scoped API
-     * key support (DeloPay-net/delopay-backend#344); absent on older backends.
+     * key support; absent on older backends.
      */
     profile_id?: string | null;
 }
@@ -2127,7 +2127,7 @@ interface ProfileDeniedConnectorsResponse {
     denied_connectors: string[];
 }
 /**
- * A buyer-facing surcharge added to the checkout amount (issue #195).
+ * A buyer-facing surcharge added to the checkout amount.
  *
  * Either a flat amount in minor units, or a percentage of the order amount.
  */
@@ -4731,7 +4731,7 @@ interface SettlementLineBase {
 }
 /**
  * A line whose processor cost is known — the rail reported it, or a
- * configured schedule estimated it (be#843).
+ * configured schedule estimated it.
  *
  * `processor_cost_amount` is minor units of `processor_cost_currency`, which
  * is the processor's **own** settlement currency and not necessarily the
@@ -4822,7 +4822,7 @@ type LimitedOperation = 'refund';
 type OperationLimitScope = 'merchant' | 'role' | 'user';
 /**
  * What happens when an operation would exceed its limit. v1 ships `block`
- * only; `require_approval` (four-eyes) arrives with backend#342 phase 2.
+ * only; `require_approval` (four-eyes) arrives in a later release.
  */
 type OperationLimitOnExceeded = 'block';
 /** How the usage window is anchored. Rolling is the default. */
@@ -8777,7 +8777,7 @@ declare class CheckoutSession {
      * own types and runtime gates — hence the loose return type.
      *
      * `theme` is the route's one declared query parameter (a named checkout
-     * variant, backend#793). `locale` travels as `Accept-Language` — the only
+     * variant). `locale` travels as `Accept-Language` — the only
      * channel the backend's locale resolution reads; a `?locale=` query is
      * silently ignored by this route.
      *
@@ -8857,10 +8857,17 @@ declare class CheckoutSession {
     /**
      * A short-lived VGS Collect session for browser-side card capture.
      *
-     * A 404 — or a 400 carrying the "shop has no vault" code — means the shop
-     * has no vault configured; other errors must NOT be treated that way (a
-     * refused vault falling back to an unprotected card pane is exactly the
-     * bug this endpoint's error contract exists to prevent).
+     * **Exactly one refusal means "this shop has no vault": a 400 carrying
+     * `IR_19`.** Every other refusal means a vault exists and could not be used,
+     * and answering it by falling back to the processor's own card pane sends an
+     * unprotected card number to the very processor the shop pays to hide it
+     * from — the bug this endpoint's error contract exists to prevent.
+     *
+     * A **404 is not benign.** The router answers it when the shop's vault
+     * account cannot be found — the state a shop is left in when its vault
+     * connector is deleted while the profile keeps naming the id: it still
+     * reports the vault as enabled and still expects its cards cloaked. The same
+     * status also covers a payment that does not exist.
      *
      * `GET /payment-link/{merchantId}/{paymentId}/vault/collect-session`
      */

package/dist/index.js

@@ -88,7 +88,7 @@ import {
   surfacePadValue,
   verticalGapValue,
   visibleCustomFields
-} from "./chunk-HK4S2SQB.js";
+} from "./chunk-6ULG3SLG.js";
 export {
   ALL_CUSTOM_FIELD_CONDITION_SOURCES,
   ALL_CUSTOM_FIELD_OPERATORS,

package/dist/internal.cjs

@@ -231,8 +231,7 @@ var ApiKeys = class {
   // JWT-authenticated routes under `/account/{merchantId}/profile/api-keys`.
   // The caller's shop (business profile) comes from the JWT, never from the
   // request, so a shop-scoped user can only mint/list/manage keys pinned to
-  // their own shop. Requires a backend with profile-scoped API key support
-  // (DeloPay-net/delopay-backend#344).
+  // their own shop. Requires a backend with profile-scoped API key support.
   /**
    * Create a new API key pinned to the caller's shop (business profile).
    * `POST /account/{merchantId}/profile/api-keys`
@@ -5737,7 +5736,7 @@ var CheckoutSession = class {
    * own types and runtime gates — hence the loose return type.
    *
    * `theme` is the route's one declared query parameter (a named checkout
-   * variant, backend#793). `locale` travels as `Accept-Language` — the only
+   * variant). `locale` travels as `Accept-Language` — the only
    * channel the backend's locale resolution reads; a `?locale=` query is
    * silently ignored by this route.
    *
@@ -5892,10 +5891,17 @@ var CheckoutSession = class {
   /**
    * A short-lived VGS Collect session for browser-side card capture.
    *
-   * A 404 — or a 400 carrying the "shop has no vault" code — means the shop
-   * has no vault configured; other errors must NOT be treated that way (a
-   * refused vault falling back to an unprotected card pane is exactly the
-   * bug this endpoint's error contract exists to prevent).
+   * **Exactly one refusal means "this shop has no vault": a 400 carrying
+   * `IR_19`.** Every other refusal means a vault exists and could not be used,
+   * and answering it by falling back to the processor's own card pane sends an
+   * unprotected card number to the very processor the shop pays to hide it
+   * from — the bug this endpoint's error contract exists to prevent.
+   *
+   * A **404 is not benign.** The router answers it when the shop's vault
+   * account cannot be found — the state a shop is left in when its vault
+   * connector is deleted while the profile keeps naming the id: it still
+   * reports the vault as enabled and still expects its cards cloaked. The same
+   * status also covers a payment that does not exist.
    *
    * `GET /payment-link/{merchantId}/{paymentId}/vault/collect-session`
    */