Generated Latest Changes for v2021-02-25

Recurly/Resources/FraudRiskRule.cs

@@ -0,0 +1,27 @@
+/**
+ * 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.
+ */
+using System;
+using System.Collections.Generic;
+using System.Diagnostics.CodeAnalysis;
+using Newtonsoft.Json;
+
+namespace Recurly.Resources
+{
+    [ExcludeFromCodeCoverage]
+    public class FraudRiskRule : Resource
+    {
+
+        /// <value>The Kount rule number.</value>
+        [JsonProperty("code")]
+        public string Code { get; set; }
+
+        /// <value>Description of why the rule was triggered</value>
+        [JsonProperty("message")]
+        public string Message { get; set; }
+
+    }
+}

Recurly/Resources/Invoice.cs

@@ -96,16 +96,19 @@ public class Invoice : Resource
         /// 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)</value>
+        /// 
+        /// 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.</value>
         [JsonProperty("net_terms")]
         public int? NetTerms { get; set; }
 

Recurly/Resources/InvoiceCreate.cs

@@ -36,16 +36,19 @@ public class InvoiceCreate : Request
         /// 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)</value>
+        /// 
+        /// 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.</value>
         [JsonProperty("net_terms")]
         public int? NetTerms { get; set; }
 

Recurly/Resources/PurchaseCreate.cs

@@ -60,16 +60,19 @@ public class PurchaseCreate : Request
         /// 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)</value>
+        /// 
+        /// 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.</value>
         [JsonProperty("net_terms")]
         public int? NetTerms { get; set; }
 

Recurly/Resources/Subscription.cs

@@ -120,16 +120,19 @@ public class Subscription : Resource
         /// 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)</value>
+        /// 
+        /// 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.</value>
         [JsonProperty("net_terms")]
         public int? NetTerms { get; set; }
 

Recurly/Resources/SubscriptionChangeCreate.cs

@@ -60,7 +60,8 @@ public class SubscriptionChangeCreate : Request
         /// 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)</value>
+        /// 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.</value>
         [JsonProperty("net_terms")]
         public int? NetTerms { get; set; }
 

Recurly/Resources/SubscriptionCreate.cs

@@ -68,16 +68,19 @@ public class SubscriptionCreate : Request
         /// 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)</value>
+        /// 
+        /// 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.</value>
         [JsonProperty("net_terms")]
         public int? NetTerms { get; set; }
 

Recurly/Resources/SubscriptionUpdate.cs

@@ -44,16 +44,19 @@ public class SubscriptionUpdate : Request
         /// 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)</value>
+        /// 
+        /// 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.</value>
         [JsonProperty("net_terms")]
         public int? NetTerms { get; set; }
 

Recurly/Resources/Transaction.cs

@@ -70,6 +70,10 @@ public class Transaction : Resource
         [JsonConverter(typeof(RecurlyStringEnumConverter))]
         public Constants.CvvCheck? CvvCheck { get; set; }
 
+        /// <value>Fraud information</value>
+        [JsonProperty("fraud_info")]
+        public TransactionFraudInfo FraudInfo { get; set; }
+
         /// <value>Transaction approval code from the payment gateway.</value>
         [JsonProperty("gateway_approval_code")]
         public string GatewayApprovalCode { get; set; }

Recurly/Resources/TransactionFraudInfo.cs

@@ -0,0 +1,40 @@
+/**
+ * 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.
+ */
+using System;
+using System.Collections.Generic;
+using System.Diagnostics.CodeAnalysis;
+using Newtonsoft.Json;
+
+namespace Recurly.Resources
+{
+    [ExcludeFromCodeCoverage]
+    public class TransactionFraudInfo : Resource
+    {
+
+        /// <value>Kount decision</value>
+        [JsonProperty("decision")]
+        [JsonConverter(typeof(RecurlyStringEnumConverter))]
+        public Constants.KountDecision? Decision { get; set; }
+
+        /// <value>Object type</value>
+        [JsonProperty("object")]
+        public string Object { get; set; }
+
+        /// <value>Kount transaction reference ID</value>
+        [JsonProperty("reference")]
+        public string Reference { get; set; }
+
+        /// <value>A list of fraud risk rules that were triggered for the transaction.</value>
+        [JsonProperty("risk_rules_triggered")]
+        public List<FraudRiskRule> RiskRulesTriggered { get; set; }
+
+        /// <value>Kount score</value>
+        [JsonProperty("score")]
+        public int? Score { get; set; }
+
+    }
+}