api.yaml in recurly-4.45.0

- old
+ new

@@ -19420,20 +19420,23 @@
           title: Net terms
           description: |-
             Integer paired with `Net Terms Type` and representing the number
             of days past the current date (for `net` Net Terms Type) or days after
             the last day of the current month (for `eom` Net Terms Type) that the
-            invoice will become past due. For any value, an additional 24 hours is
+            invoice will become past due. For `manual` collection method, an additional 24 hours is
             added to ensure the customer has the entire last day to make payment before
-            becoming past due.  For example:
+            becoming past due. For example:
 
             If an invoice is due `net 0`, it is due 'On Receipt' and will become past due 24 hours after it's created.
             If an invoice is due `net 30`, it will become past due at 31 days exactly.
             If an invoice is due `eom 30`, it will become past due 31 days from the last day of the current month.
 
+            For `automatic` collection method, the additional 24 hours is not added. For example, On-Receipt is due immediately, and `net 30` will become due exactly 30 days from invoice generation, at which point Recurly will attempt collection.
             When `eom` Net Terms Type is passed, the value for `Net Terms` is restricted to `0, 15, 30, 45, 60, or 90`.
-            For more information please visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+
+            For more information on how net terms work with `manual` collection visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+            or visit (https://docs.recurly.com/docs/automatic-invoicing-terms#section-collection-terms) for information about net terms using `automatic` collection.
           minimum: 0
           default: 0
         net_terms_type:
           "$ref": "#/components/schemas/NetTermsTypeEnum"
         address:
@@ -19615,20 +19618,23 @@
           title: Net terms
           description: |-
             Integer paired with `Net Terms Type` and representing the number
             of days past the current date (for `net` Net Terms Type) or days after
             the last day of the current month (for `eom` Net Terms Type) that the
-            invoice will become past due. For any value, an additional 24 hours is
+            invoice will become past due. For `manual` collection method, an additional 24 hours is
             added to ensure the customer has the entire last day to make payment before
-            becoming past due.  For example:
+            becoming past due. For example:
 
             If an invoice is due `net 0`, it is due 'On Receipt' and will become past due 24 hours after it's created.
             If an invoice is due `net 30`, it will become past due at 31 days exactly.
             If an invoice is due `eom 30`, it will become past due 31 days from the last day of the current month.
 
+            For `automatic` collection method, the additional 24 hours is not added. For example, On-Receipt is due immediately, and `net 30` will become due exactly 30 days from invoice generation, at which point Recurly will attempt collection.
             When `eom` Net Terms Type is passed, the value for `Net Terms` is restricted to `0, 15, 30, 45, 60, or 90`.
-            For more information please visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+
+            For more information on how net terms work with `manual` collection visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+            or visit (https://docs.recurly.com/docs/automatic-invoicing-terms#section-collection-terms) for information about net terms using `automatic` collection.
           minimum: 0
           default: 0
         net_terms_type:
           "$ref": "#/components/schemas/NetTermsTypeEnum"
         po_number:
@@ -21731,20 +21737,23 @@
           title: Net terms
           description: |-
             Integer paired with `Net Terms Type` and representing the number
             of days past the current date (for `net` Net Terms Type) or days after
             the last day of the current month (for `eom` Net Terms Type) that the
-            invoice will become past due. For any value, an additional 24 hours is
+            invoice will become past due. For `manual` collection method, an additional 24 hours is
             added to ensure the customer has the entire last day to make payment before
-            becoming past due.  For example:
+            becoming past due. For example:
 
             If an invoice is due `net 0`, it is due 'On Receipt' and will become past due 24 hours after it's created.
             If an invoice is due `net 30`, it will become past due at 31 days exactly.
             If an invoice is due `eom 30`, it will become past due 31 days from the last day of the current month.
 
+            For `automatic` collection method, the additional 24 hours is not added. For example, On-Receipt is due immediately, and `net 30` will become due exactly 30 days from invoice generation, at which point Recurly will attempt collection.
             When `eom` Net Terms Type is passed, the value for `Net Terms` is restricted to `0, 15, 30, 45, 60, or 90`.
-            For more information please visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+
+            For more information on how net terms work with `manual` collection visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+            or visit (https://docs.recurly.com/docs/automatic-invoicing-terms#section-collection-terms) for information about net terms using `automatic` collection.
           minimum: 0
           default: 0
         net_terms_type:
           "$ref": "#/components/schemas/NetTermsTypeEnum"
         terms_and_conditions:
@@ -22312,11 +22321,12 @@
             Integer normally paired with `Net Terms Type` and representing the number of days past
             the current date (for `net` Net Terms Type) or days after the last day of the current
             month (for `eom` Net Terms Type) that the invoice will become past due. During a subscription
             change, it's not necessary to provide both the `Net Terms Type` and `Net Terms` parameters.
 
-            For more information please visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+            For more information on how net terms work with `manual` collection visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+            or visit (https://docs.recurly.com/docs/automatic-invoicing-terms#section-collection-terms) for information about net terms using `automatic` collection.
           minimum: 0
           default: 0
         net_terms_type:
           "$ref": "#/components/schemas/NetTermsTypeEnum"
         transaction_type:
@@ -22525,20 +22535,23 @@
           title: Net terms
           description: |-
             Integer paired with `Net Terms Type` and representing the number
             of days past the current date (for `net` Net Terms Type) or days after
             the last day of the current month (for `eom` Net Terms Type) that the
-            invoice will become past due. For any value, an additional 24 hours is
+            invoice will become past due. For `manual` collection method, an additional 24 hours is
             added to ensure the customer has the entire last day to make payment before
-            becoming past due.  For example:
+            becoming past due. For example:
 
             If an invoice is due `net 0`, it is due 'On Receipt' and will become past due 24 hours after it's created.
             If an invoice is due `net 30`, it will become past due at 31 days exactly.
             If an invoice is due `eom 30`, it will become past due 31 days from the last day of the current month.
 
+            For `automatic` collection method, the additional 24 hours is not added. For example, On-Receipt is due immediately, and `net 30` will become due exactly 30 days from invoice generation, at which point Recurly will attempt collection.
             When `eom` Net Terms Type is passed, the value for `Net Terms` is restricted to `0, 15, 30, 45, 60, or 90`.
-            For more information please visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+
+            For more information on how net terms work with `manual` collection visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+            or visit (https://docs.recurly.com/docs/automatic-invoicing-terms#section-collection-terms) for information about net terms using `automatic` collection.
           minimum: 0
           default: 0
         net_terms_type:
           "$ref": "#/components/schemas/NetTermsTypeEnum"
         gateway_code:
@@ -22718,20 +22731,23 @@
           title: Terms that the subscription is due on
           description: |-
             Integer paired with `Net Terms Type` and representing the number
             of days past the current date (for `net` Net Terms Type) or days after
             the last day of the current month (for `eom` Net Terms Type) that the
-            invoice will become past due. For any value, an additional 24 hours is
+            invoice will become past due. For `manual` collection method, an additional 24 hours is
             added to ensure the customer has the entire last day to make payment before
-            becoming past due.  For example:
+            becoming past due. For example:
 
             If an invoice is due `net 0`, it is due 'On Receipt' and will become past due 24 hours after it's created.
             If an invoice is due `net 30`, it will become past due at 31 days exactly.
             If an invoice is due `eom 30`, it will become past due 31 days from the last day of the current month.
 
+            For `automatic` collection method, the additional 24 hours is not added. For example, On-Receipt is due immediately, and `net 30` will become due exactly 30 days from invoice generation, at which point Recurly will attempt collection.
             When `eom` Net Terms Type is passed, the value for `Net Terms` is restricted to `0, 15, 30, 45, 60, or 90`.
-            For more information please visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+
+            For more information on how net terms work with `manual` collection visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+            or visit (https://docs.recurly.com/docs/automatic-invoicing-terms#section-collection-terms) for information about net terms using `automatic` collection.
           minimum: 0
           default: 0
         net_terms_type:
           "$ref": "#/components/schemas/NetTermsTypeEnum"
         gateway_code:
@@ -23152,10 +23168,48 @@
           description: VAT number for the customer on this transaction. If the customer's
             Billing Info country is BR or AR, then this will be their Tax Identifier.
             For all other countries this will come from the VAT Number field in the
             Billing Info.
           title: VAT Number
+        fraud_info:
+          "$ref": "#/components/schemas/TransactionFraudInfo"
+    TransactionFraudInfo:
+      type: object
+      title: Fraud information
+      readOnly: true
+      properties:
+        object:
+          type: string
+          title: Object type
+          readOnly: true
+        score:
+          type: integer
+          title: Kount score
+          minimum: 1
+          maximum: 99
+        decision:
+          title: Kount decision
+          maxLength: 10
+          "$ref": "#/components/schemas/KountDecisionEnum"
+        reference:
+          type: string
+          title: Kount transaction reference ID
+        risk_rules_triggered:
+          type: array
+          title: Risk Rules Triggered
+          description: A list of fraud risk rules that were triggered for the transaction.
+          items:
+            "$ref": "#/components/schemas/FraudRiskRule"
+    FraudRiskRule:
+      type: object
+      properties:
+        code:
+          type: string
+          title: The Kount rule number.
+        message:
+          type: string
+          title: Description of why the rule was triggered
     ExternalTransaction:
       type: object
       properties:
         payment_method:
           type: string
@@ -23455,19 +23509,22 @@
           title: Net terms
           description: |-
             Integer paired with `Net Terms Type` and representing the number
             of days past the current date (for `net` Net Terms Type) or days after
             the last day of the current month (for `eom` Net Terms Type) that the
-            invoice will become past due. For any value, an additional 24 hours is
+            invoice will become past due. For `manual` collection method, an additional 24 hours is
             added to ensure the customer has the entire last day to make payment before
-            becoming past due.  For example:
+            becoming past due. For example:
 
             If an invoice is due `net 0`, it is due 'On Receipt' and will become past due 24 hours after it's created.
             If an invoice is due `net 30`, it will become past due at 31 days exactly.
             If an invoice is due `eom 30`, it will become past due 31 days from the last day of the current month.
 
+            For `automatic` collection method, the additional 24 hours is not added. For example, On-Receipt is due immediately, and `net 30` will become due exactly 30 days from invoice generation, at which point Recurly will attempt collection.
             When `eom` Net Terms Type is passed, the value for `Net Terms` is restricted to `0, 15, 30, 45, 60, or 90`.
-            For more information please visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+
+            For more information on how net terms work with `manual` collection visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+            or visit (https://docs.recurly.com/docs/automatic-invoicing-terms#section-collection-terms) for information about net terms using `automatic` collection.
           minimum: 0
           default: 0
         net_terms_type:
           "$ref": "#/components/schemas/NetTermsTypeEnum"
         terms_and_conditions: