@delopay/sdk 0.246.0 → 0.248.0

package/dist/{chunk-LFNDWJ5X.js → chunk-RPPCA42D.js}

@@ -708,6 +708,21 @@ var Connectors = class {
       { body: params }
     );
   }
+  /**
+   * The shops whose card vault is switched on and whose vault account has
+   * stopped working, each with the cause. While a shop is listed, its card
+   * form cannot be shown and its card payments fail.
+   *
+   * An outage is listed once the vault has refused the account several times
+   * in a row over at least a minute, and is taken off the list when the vault
+   * serves the account again. Nothing switches a vault off by itself: see
+   * `profiles.switchVaultOff`.
+   *
+   * `GET /account/{accountId}/vault/outages`
+   */
+  async listVaultOutages(accountId) {
+    return this.request("GET", `/account/${encodeURIComponent(accountId)}/vault/outages`);
+  }
   /**
    * Compute the route document the vault SHOULD have and diff it against
    * what exists, without writing anything. The returned fingerprints must be
@@ -2972,6 +2987,25 @@ var Profiles = class {
       `/account/${encodeURIComponent(accountId)}/business-profile/${encodeURIComponent(profileId)}/toggle-connector-agnostic-mit`
     );
   }
+  /**
+   * Switch the shop's card vault off. From the next checkout on, the checkout
+   * draws each processor's own card form and card payments no longer depend on
+   * the vault account. Cards saved in the vault cannot be charged while it is
+   * off.
+   *
+   * The vault stays configured; switch it on again with {@link Profiles.update},
+   * which verifies the vault first. Needs the permission to edit the shop's
+   * connectors, not the one to edit the shop. Calling it for a shop whose vault
+   * is already off changes nothing.
+   *
+   * `POST /account/{accountId}/business-profile/{profileId}/vault/switch-off`
+   */
+  async switchVaultOff(accountId, profileId) {
+    return this.request(
+      "POST",
+      `/account/${encodeURIComponent(accountId)}/business-profile/${encodeURIComponent(profileId)}/vault/switch-off`
+    );
+  }
 };
 
 // src/resources/projects.ts
@@ -12077,6 +12111,37 @@ var CheckoutSession = class {
       headers: this.bearerHeaders(options?.headers)
     });
   }
+  /**
+   * Remove one of the buyer's saved cards, named by its `payment_token` from
+   * {@link vaultSavedCards}: from the customer's saved cards and from the
+   * shop's vault, with every saved copy of the same card. Only a card of the
+   * payment's own customer that the shop's vault holds can be removed, and
+   * only within the payment's session.
+   *
+   * Refusals throw a `DelopayError`:
+   *
+   * - `400` with code `IR_16` and `data.reason` set to a
+   *   {@link VaultSavedCardRemovalRefusal}: the card stays listed.
+   *   `saved_card_in_use` means a subscription or agreement still charges it,
+   *   `saved_card_payment_in_progress` a payment with it is in flight, and
+   *   `saved_card_removal_unavailable` that the shop cannot remove cards here.
+   * - `404`: the card is not one this buyer can remove, for example because it
+   *   is already gone.
+   * - `422` with code `IR_29`: the token is no longer held. Read
+   *   {@link vaultSavedCards} again and remove the card by its new token.
+   *
+   * `DELETE /payment-link/{merchantId}/{paymentId}/vault/saved-cards/{paymentToken}`
+   */
+  async vaultRemoveSavedCard(paymentToken, options) {
+    await this.client.request(
+      "DELETE",
+      `${this.linkBase}/vault/saved-cards/${encodeURIComponent(paymentToken)}`,
+      {
+        ...options,
+        headers: this.bearerHeaders(options?.headers)
+      }
+    );
+  }
   /**
    * Mint the security-code form for a saved card, on a shop whose vault keeps
    * the code itself (Enigma Vault). The buyer re-enters the code into the
@@ -12955,4 +13020,4 @@ export {
   decodeNativePanes,
   encodeNativePanes
 };
-//# sourceMappingURL=chunk-LFNDWJ5X.js.map
+//# sourceMappingURL=chunk-RPPCA42D.js.map