@delopay/sdk 0.118.0 → 0.120.0

package/dist/index.d.cts

@@ -527,14 +527,19 @@ interface PaymentAttemptsListResponse {
 /**
  * Which entity a status-history event belongs to.
  *
- * `risk` and `checkout` are timeline events with no underlying status change:
- * `risk` carries a processor risk signal (early fraud warning, manual review)
- * and `checkout` a buyer-side checkout event (native-pane selection, external
- * tab opened/blocked, abandonment). For both, `status` holds the event name
- * rather than a payment state, and `entity_id` names what it is about (the
- * processor's signal id, or the native-pane method key).
- */
-type PaymentStatusHistoryEntityType = 'payment' | 'attempt' | 'refund' | 'dispute' | 'risk' | 'checkout';
+ * `risk`, `checkout` and `routing` are timeline events with no underlying
+ * status change: `risk` carries a processor risk signal (early fraud warning,
+ * manual review), `checkout` a buyer-side checkout event (native-pane
+ * selection, external tab opened/blocked, abandonment), and `routing` a rail
+ * handover — the payment settled on a different provider than the one that
+ * last failed on the same attempt, which happens when a buyer falls back to
+ * the card form after a native pane errors. For all three, `status` holds the
+ * event name rather than a payment state, and `entity_id` names what it is
+ * about (the processor's signal id, the native-pane method key, or the
+ * connector the payment moved away from — with `connector` naming the one
+ * that settled it).
+ */
+type PaymentStatusHistoryEntityType = 'payment' | 'attempt' | 'refund' | 'dispute' | 'risk' | 'checkout' | 'routing';
 /**
  * One event on a payment's status timeline: the creation of, or a status
  * transition on, the payment intent or one of its attempts / refunds /

package/dist/index.d.ts

@@ -527,14 +527,19 @@ interface PaymentAttemptsListResponse {
 /**
  * Which entity a status-history event belongs to.
  *
- * `risk` and `checkout` are timeline events with no underlying status change:
- * `risk` carries a processor risk signal (early fraud warning, manual review)
- * and `checkout` a buyer-side checkout event (native-pane selection, external
- * tab opened/blocked, abandonment). For both, `status` holds the event name
- * rather than a payment state, and `entity_id` names what it is about (the
- * processor's signal id, or the native-pane method key).
- */
-type PaymentStatusHistoryEntityType = 'payment' | 'attempt' | 'refund' | 'dispute' | 'risk' | 'checkout';
+ * `risk`, `checkout` and `routing` are timeline events with no underlying
+ * status change: `risk` carries a processor risk signal (early fraud warning,
+ * manual review), `checkout` a buyer-side checkout event (native-pane
+ * selection, external tab opened/blocked, abandonment), and `routing` a rail
+ * handover — the payment settled on a different provider than the one that
+ * last failed on the same attempt, which happens when a buyer falls back to
+ * the card form after a native pane errors. For all three, `status` holds the
+ * event name rather than a payment state, and `entity_id` names what it is
+ * about (the processor's signal id, the native-pane method key, or the
+ * connector the payment moved away from — with `connector` naming the one
+ * that settled it).
+ */
+type PaymentStatusHistoryEntityType = 'payment' | 'attempt' | 'refund' | 'dispute' | 'risk' | 'checkout' | 'routing';
 /**
  * One event on a payment's status timeline: the creation of, or a status
  * transition on, the payment intent or one of its attempts / refunds /

package/dist/internal.cjs

@@ -8132,6 +8132,28 @@ var PlatformBilling = class {
       body: params
     });
   }
+  /**
+   * Set the merchant's hard floor — the balance at or below which the
+   * merchant stops being active. A negative value grants a credit line; zero
+   * means no negative balance at all. This moves the suspension line, it does
+   * not remove it. The value and the caller are written to the audit log
+   * before the floor changes, so the change is always attributable.
+   *
+   * Refused (412) for a positive amount, for a floor beyond the maximum
+   * credit line of 10,000,000 minor units, or for an empty `reason`.
+   *
+   * Requires a router that serves the hard-floor admin route; older ones
+   * answer `404`.
+   *
+   * @param merchantId - The merchant account ID.
+   * @param params - The new floor (zero or negative) and the audit reason.
+   * @returns The updated billing profile.
+   */
+  async setHardFloor(merchantId, params) {
+    return this.request("PATCH", `/billing/${encodeURIComponent(merchantId)}/admin/hard-floor`, {
+      body: params
+    });
+  }
   /**
    * Mark a merchant free (not billed), or put it back on the prepaid model.
    * While free, no platform fee is deducted, the payment gate never blocks on