@delopay/sdk 0.100.2 → 0.101.0

package/dist/{chunk-6ULG3SLG.js → chunk-NLUEZQZF.js}

@@ -3703,6 +3703,53 @@ var Subscriptions = class {
   async lookupPayments(params, options) {
     return this.request("POST", "/subscriptions/payments/lookup", { body: params, ...options });
   }
+  /**
+   * One subscription's billing history, newest cycle first.
+   * `GET /subscriptions/{subscriptionId}/invoices`
+   *
+   * {@link retrieve} carries only the *latest* invoice, which is the current
+   * cycle — a subscription that has renewed monthly for a year has one of those
+   * and twelve of these. Use this wherever a merchant needs to see what a
+   * subscription has actually billed, in particular on self-charging processors
+   * (Creem, PayPal) where each renewal is charged by the processor and mirrored
+   * here rather than raised as a DeloPay payment.
+   *
+   * Two things to render honestly, both decided rather than incidental:
+   *
+   * - `amount` is **gross** and `refunded_amount` sits beside it. Do not net
+   *   them: the difference between the two is not a smaller charge.
+   * - A `refunded_amount` of `null` is "not reported" and must not render as
+   *   `0`. Likewise a processor-hosted origination records a bootstrap invoice
+   *   at `0` before the buyer has paid anything, so a zero amount on such a
+   *   subscription is a placeholder rather than a free cycle.
+   *
+   * Profile-scoped like every other subscription route.
+   */
+  async listInvoices(subscriptionId, params, options) {
+    return this.request("GET", `/subscriptions/${encodeURIComponent(subscriptionId)}/invoices`, {
+      query: params,
+      ...options
+    });
+  }
+  /**
+   * Which billing processor this shop's subscriptions run on.
+   * `GET /subscriptions/billing_processor`
+   *
+   * The same mapping is derivable from the connector inventory
+   * (`GET /account/{merchant_id}/connectors`), but that route is gated by a
+   * connector-read permission granted independently of subscriptions — so a
+   * role authorised to create subscriptions could be unable to learn which
+   * processor it was creating them on. This answers under the same
+   * authorization as the rest of the subscription API.
+   *
+   * Reach for it when the client must branch on the processor *before* calling
+   * — origination differs by processor, and guessing is destructive. Resolve
+   * the shop's `billing_processor_id` first: a shop that runs no subscriptions
+   * has none assigned, and this route has no identity to report for it.
+   */
+  async getBillingProcessor(options) {
+    return this.request("GET", "/subscriptions/billing_processor", { ...options });
+  }
 };
 
 // src/resources/settlement.ts
@@ -6174,4 +6221,4 @@ export {
   focusedCheckoutUrl,
   CHECKOUT_EVENT_KINDS
 };
-//# sourceMappingURL=chunk-6ULG3SLG.js.map
+//# sourceMappingURL=chunk-NLUEZQZF.js.map