recurly 4.44.0 → 4.46.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a6f7b9520933bcb659ed347252df909d49e49ea5b44c05f62e4e63abe5b344ee
-  data.tar.gz: 83d581c701db2790bc9522357594f713f54a0616f94df81e16d8fc97dacbc49d
+  metadata.gz: 7dd8c1ad69f0c7c5ea813a4f56a25b5dfaf96ee9561e236fd1ec620abe5eefe4
+  data.tar.gz: 673ac6c57dd16992733535a4938f6838a30da0f496258e0f56a3266ab6ff02d4
 SHA512:
-  metadata.gz: dc77ed0330c88e1b883dd90052709f03e8bbf8445e5dae3465098a4e69ae48c2c3fdc7eca3ca6a1e48466815d1f635510983bf6b342e8284f4d441a76ab74837
-  data.tar.gz: 5408f63bce4954ec15b459d9d05fabfa6e4f50d4dcb419eddaee3dc0553f97f8399c23d27b2de20582505fff54220a94468475f7e7559e0bd6a3d0f04a38942c
+  metadata.gz: 47be621f579e122d5d5175c8e048114d4f202b294866e9c8b6926060d9886c2c74ffa3436ee2dff26664bd407c1899a4bf587c16c72e03eeec5a516bda5c2a79
+  data.tar.gz: 9fb5ca4d631dce16fb0ac292a3db39daf16e94a06e82f546d9221aef0252464f11118a5fe701188c7d0bf1d05b595a66a26945e4ca8192ab724a496769250f59

data/.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 4.44.0
+current_version = 4.46.0
 parse = (?P<major>\d+)
 	\.(?P<minor>\d+)
 	\.(?P<patch>\d+)

data/CHANGELOG.md

@@ -1,5 +1,27 @@
 # Changelog
 
+## [4.46.0](https://github.com/recurly/recurly-client-ruby/tree/4.46.0) (2024-01-24)
+
+[Full Changelog](https://github.com/recurly/recurly-client-ruby/compare/4.45.0...4.46.0)
+
+
+**Merged Pull Requests**
+
+- Generated Latest Changes for v2021-02-25 [#877](https://github.com/recurly/recurly-client-ruby/pull/877) ([recurly-integrations](https://github.com/recurly-integrations))
+
+
+
+## [4.45.0](https://github.com/recurly/recurly-client-ruby/tree/4.45.0) (2024-01-18)
+
+[Full Changelog](https://github.com/recurly/recurly-client-ruby/compare/4.44.0...4.45.0)
+
+
+**Merged Pull Requests**
+
+- Generated Latest Changes for v2021-02-25 [#872](https://github.com/recurly/recurly-client-ruby/pull/872) ([recurly-integrations](https://github.com/recurly-integrations))
+
+
+
 ## [4.44.0](https://github.com/recurly/recurly-client-ruby/tree/4.44.0) (2023-12-06)
 
 [Full Changelog](https://github.com/recurly/recurly-client-ruby/compare/4.43.0...4.44.0)

data/GETTING_STARTED.md

@@ -5,7 +5,7 @@ This repository houses the official ruby client for Recurly's V3 API.
 In your Gemfile, add `recurly` as a dependency.
 
 ```ruby
-gem 'recurly', '~> 4.44'
+gem 'recurly', '~> 4.46'
 ```
 
 > *Note*: We try to follow [semantic versioning](https://semver.org/) and will only apply breaking changes to major versions.

data/lib/recurly/requests/invoice_create.rb

@@ -23,7 +23,7 @@ module Recurly
       define_attribute :currency, String
 
       # @!attribute net_terms
-      #   @return [Integer] 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 added to ensure the customer has the entire last day to make payment before 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.  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)
+      #   @return [Integer] 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 `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:  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 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.
       define_attribute :net_terms, Integer
 
       # @!attribute net_terms_type

data/lib/recurly/requests/purchase_create.rb

@@ -47,7 +47,7 @@ module Recurly
       define_attribute :line_items, Array, { :item_type => :LineItemCreate }
 
       # @!attribute net_terms
-      #   @return [Integer] 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 added to ensure the customer has the entire last day to make payment before 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.  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)
+      #   @return [Integer] 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 `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:  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 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.
       define_attribute :net_terms, Integer
 
       # @!attribute net_terms_type

data/lib/recurly/requests/subscription_change_create.rb

@@ -27,7 +27,7 @@ module Recurly
       define_attribute :custom_fields, Array, { :item_type => :CustomField }
 
       # @!attribute net_terms
-      #   @return [Integer] 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)
+      #   @return [Integer] 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 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.
       define_attribute :net_terms, Integer
 
       # @!attribute net_terms_type

data/lib/recurly/requests/subscription_create.rb

@@ -55,7 +55,7 @@ module Recurly
       define_attribute :gift_card_redemption_code, String
 
       # @!attribute net_terms
-      #   @return [Integer] 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 added to ensure the customer has the entire last day to make payment before 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.  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)
+      #   @return [Integer] 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 `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:  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 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.
       define_attribute :net_terms, Integer
 
       # @!attribute net_terms_type

data/lib/recurly/requests/subscription_update.rb

@@ -31,7 +31,7 @@ module Recurly
       define_attribute :gateway_code, String
 
       # @!attribute net_terms
-      #   @return [Integer] 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 added to ensure the customer has the entire last day to make payment before 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.  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)
+      #   @return [Integer] 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 `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:  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 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.
       define_attribute :net_terms, Integer
 
       # @!attribute net_terms_type

data/lib/recurly/resources/fraud_risk_rule.rb

@@ -0,0 +1,18 @@
+# This file is automatically created by Recurly's OpenAPI generation process
+# and thus any edits you make by hand will be lost. If you wish to make a
+# change to this file, please create a Github issue explaining the changes you
+# need and we will usher them to the appropriate places.
+module Recurly
+  module Resources
+    class FraudRiskRule < Resource
+
+      # @!attribute code
+      #   @return [String] The Kount rule number.
+      define_attribute :code, String
+
+      # @!attribute message
+      #   @return [String] Description of why the rule was triggered
+      define_attribute :message, String
+    end
+  end
+end

data/lib/recurly/resources/invoice.rb

@@ -83,7 +83,7 @@ module Recurly
       define_attribute :line_items, Array, { :item_type => :LineItem }
 
       # @!attribute net_terms
-      #   @return [Integer] 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 added to ensure the customer has the entire last day to make payment before 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.  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)
+      #   @return [Integer] 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 `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:  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 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.
       define_attribute :net_terms, Integer
 
       # @!attribute net_terms_type

data/lib/recurly/resources/subscription.rb

@@ -107,7 +107,7 @@ module Recurly
       define_attribute :id, String
 
       # @!attribute net_terms
-      #   @return [Integer] 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 added to ensure the customer has the entire last day to make payment before 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.  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)
+      #   @return [Integer] 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 `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:  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 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.
       define_attribute :net_terms, Integer
 
       # @!attribute net_terms_type

data/lib/recurly/resources/transaction.rb

@@ -58,6 +58,10 @@ module Recurly
       #   @return [String] When processed, result from checking the CVV/CVC value on the transaction.
       define_attribute :cvv_check, String
 
+      # @!attribute fraud_info
+      #   @return [TransactionFraudInfo] Fraud information
+      define_attribute :fraud_info, :TransactionFraudInfo
+
       # @!attribute gateway_approval_code
       #   @return [String] Transaction approval code from the payment gateway.
       define_attribute :gateway_approval_code, String

data/lib/recurly/resources/transaction_error.rb

@@ -18,6 +18,10 @@ module Recurly
       #   @return [String] Decline code
       define_attribute :decline_code, String
 
+      # @!attribute fraud_info
+      #   @return [TransactionFraudInfo] Fraud information
+      define_attribute :fraud_info, :TransactionFraudInfo
+
       # @!attribute merchant_advice
       #   @return [String] Merchant message
       define_attribute :merchant_advice, String

data/lib/recurly/resources/transaction_fraud_info.rb

@@ -0,0 +1,30 @@
+# This file is automatically created by Recurly's OpenAPI generation process
+# and thus any edits you make by hand will be lost. If you wish to make a
+# change to this file, please create a Github issue explaining the changes you
+# need and we will usher them to the appropriate places.
+module Recurly
+  module Resources
+    class TransactionFraudInfo < Resource
+
+      # @!attribute decision
+      #   @return [String] Kount decision
+      define_attribute :decision, String
+
+      # @!attribute object
+      #   @return [String] Object type
+      define_attribute :object, String
+
+      # @!attribute reference
+      #   @return [String] Kount transaction reference ID
+      define_attribute :reference, String
+
+      # @!attribute risk_rules_triggered
+      #   @return [Array[FraudRiskRule]] A list of fraud risk rules that were triggered for the transaction.
+      define_attribute :risk_rules_triggered, Array, { :item_type => :FraudRiskRule }
+
+      # @!attribute score
+      #   @return [Integer] Kount score
+      define_attribute :score, Integer
+    end
+  end
+end

data/lib/recurly/version.rb

@@ -1,3 +1,3 @@
 module Recurly
-  VERSION = "4.44.0"
+  VERSION = "4.46.0"
 end

data/openapi/api.yaml

@@ -956,7 +956,7 @@ paths:
           Alabama St.\"),\n\t\t\tCity:       recurly.String(\"San Francisco\"),\n\t\t\tPostalCode:
           recurly.String(\"94110\"),\n\t\t\tCountry:    recurly.String(\"US\"),\n\t\t\tRegion:
           \    recurly.String(\"CA\"),\n\t\t},\n\t\tNumber: recurly.String(\"4111111111111111\"),\n\t\tMonth:
-          \ recurly.String(\"12\"),\n\t\tYear:   recurly.String(\"22\"),\n\t\tCvv:
+          \ recurly.String(\"12\"),\n\t\tYear:   recurly.String(\"30\"),\n\t\tCvv:
           \   recurly.String(\"123\"),\n\t},\n}\n\naccount, err := client.CreateAccount(accountReq)\nif
           e, ok := err.(*recurly.Error); ok {\n\tif e.Type == recurly.ErrorTypeValidation
           {\n\t\tfmt.Printf(\"Failed validation: %v\", e)\n\t\treturn nil, err\n\t}\n\tfmt.Printf(\"Unexpected
@@ -19422,16 +19422,19 @@ components:
             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:
@@ -19617,16 +19620,19 @@ components:
             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:
@@ -21733,16 +21739,19 @@ components:
             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:
@@ -22314,7 +22323,8 @@ components:
             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:
@@ -22527,16 +22537,19 @@ components:
             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:
@@ -22720,16 +22733,19 @@ components:
             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:
@@ -23154,6 +23170,44 @@ components:
             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:
@@ -23457,16 +23511,19 @@ components:
             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:
@@ -24776,6 +24833,8 @@ components:
                   a transaction. Pass this value to Recurly.js so it can continue
                   the challenge flow.
                 maxLength: 22
+              fraud_info:
+                "$ref": "#/components/schemas/TransactionFraudInfo"
     RelatedTypeEnum:
       type: string
       enum:

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: recurly
 version: !ruby/object:Gem::Version
-  version: 4.44.0
+  version: 4.46.0
 platform: ruby
 authors:
 - Recurly
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-12-06 00:00:00.000000000 Z
+date: 2024-01-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -276,6 +276,7 @@ files:
 - lib/recurly/resources/external_product_reference_mini.rb
 - lib/recurly/resources/external_subscription.rb
 - lib/recurly/resources/fraud_info.rb
+- lib/recurly/resources/fraud_risk_rule.rb
 - lib/recurly/resources/gateway_attributes.rb
 - lib/recurly/resources/gift_card.rb
 - lib/recurly/resources/gift_card_delivery.rb
@@ -318,6 +319,7 @@ files:
 - lib/recurly/resources/tier_pricing.rb
 - lib/recurly/resources/transaction.rb
 - lib/recurly/resources/transaction_error.rb
+- lib/recurly/resources/transaction_fraud_info.rb
 - lib/recurly/resources/transaction_payment_gateway.rb
 - lib/recurly/resources/unique_coupon_code.rb
 - lib/recurly/resources/unique_coupon_code_params.rb
@@ -348,7 +350,7 @@ metadata:
   changelog_uri: https://github.com/recurly/recurly-client-ruby/blob/master/CHANGELOG.md
   documentation_uri: https://recurly.github.io/recurly-client-ruby/
   homepage_uri: https://github.com/recurly/recurly-client-ruby
-  source_code_uri: https://github.com/recurly/recurly-client-ruby/tree/4.44.0
+  source_code_uri: https://github.com/recurly/recurly-client-ruby/tree/4.46.0
 post_install_message:
 rdoc_options: []
 require_paths:
@@ -364,7 +366,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.6
+rubygems_version: 3.4.10
 signing_key:
 specification_version: 4
 summary: The ruby client for Recurly's V3 API