@delopay/sdk 0.118.0 → 0.119.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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@delopay/sdk",
-  "version": "0.118.0",
+  "version": "0.119.0",
   "description": "Official Delopay TypeScript SDK",
   "type": "module",
   "sideEffects": false,