Release 4.3.0.

Worldline.Connect.Sdk.Examples/Worldline.Connect.Sdk.Examples.csproj

@@ -3,8 +3,8 @@
   <PropertyGroup>
     <TargetFrameworks>net45;netstandard2.0;netstandard2.1</TargetFrameworks>
     <RootNamespace>Worldline.Connect.Sdk</RootNamespace>
-    <AssemblyVersion>4.2.0</AssemblyVersion>
-    <Version>4.2.0</Version>
+    <AssemblyVersion>4.3.0</AssemblyVersion>
+    <Version>4.3.0</Version>
     <GeneratePackageOnBuild>false</GeneratePackageOnBuild>
     <Company>Worldline Global Collect</Company>
     <Product>Worldline Connect .NET SDK examples</Product>

Worldline.Connect.Sdk.IntegrationTests/Worldline.Connect.Sdk.IntegrationTests.csproj

@@ -3,8 +3,8 @@
   <PropertyGroup>
     <TargetFrameworks>net45;netcoreapp2.1;netcoreapp3.1</TargetFrameworks>
     <RootNamespace>Worldline.Connect.Sdk</RootNamespace>
-    <AssemblyVersion>4.2.0</AssemblyVersion>
-    <Version>4.2.0</Version>
+    <AssemblyVersion>4.3.0</AssemblyVersion>
+    <Version>4.3.0</Version>
     <GeneratePackageOnBuild>false</GeneratePackageOnBuild>
     <Company>Worldline Global Collect</Company>
     <Product>Worldline Connect .NET SDK integration tests</Product>

Worldline.Connect.Sdk.StrongName/Worldline.Connect.Sdk.StrongName.csproj

@@ -3,8 +3,8 @@
   <PropertyGroup>
     <TargetFrameworks>net45;netstandard2.0;netstandard2.1</TargetFrameworks>
     <RootNamespace>Worldline.Connect.Sdk</RootNamespace>
-    <AssemblyVersion>4.2.0</AssemblyVersion>
-    <Version>4.2.0</Version>
+    <AssemblyVersion>4.3.0</AssemblyVersion>
+    <Version>4.3.0</Version>
     <GeneratePackageOnBuild>true</GeneratePackageOnBuild>
     <Company>Worldline Global Collect</Company>
     <Product>Worldline Connect .NET SDK</Product>

Worldline.Connect.Sdk.Tests/Worldline.Connect.Sdk.Tests.csproj

@@ -3,8 +3,8 @@
   <PropertyGroup>
     <TargetFrameworks>net45;netcoreapp2.1;netcoreapp3.1</TargetFrameworks>
     <RootNamespace>Worldline.Connect.Sdk</RootNamespace>
-    <AssemblyVersion>4.2.0</AssemblyVersion>
-    <Version>4.2.0</Version>
+    <AssemblyVersion>4.3.0</AssemblyVersion>
+    <Version>4.3.0</Version>
     <GeneratePackageOnBuild>false</GeneratePackageOnBuild>
     <Company>Worldline Global Collect</Company>
     <Product>Worldline Connect .NET SDK unit tests</Product>

Worldline.Connect.Sdk/Communication/MetadataProvider.cs

@@ -95,7 +95,7 @@ internal class ServerMetaInfo
             .Append(Environment.Version)
             .ToString();
 
-        private const string SdkVersion = "4.2.0";
+        private const string SdkVersion = "4.3.0";
 
         private const string ServerMetaInfoHeader = "X-GCS-ServerMetaInfo";
 

Worldline.Connect.Sdk/V1/Domain/CardPaymentMethodSpecificInput.cs

@@ -45,7 +45,7 @@ public class CardPaymentMethodSpecificInput : AbstractCardPaymentMethodSpecificI
 
         /// <summary>
         /// The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process.
-        /// <br />Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of 
+        /// <br />Note: The provided URL should be absolute and contain the https:// protocol. IP addresses are not supported, neither localhost. For use on mobile devices a custom protocol can be used in the form of 
         /// <i>protocol</i>://. This protocol must be registered on the device first.
         /// <br />URLs without a protocol will be rejected.
         /// </summary>

Worldline.Connect.Sdk/V1/Domain/CashPaymentProduct1503SpecificInput.cs

@@ -11,7 +11,7 @@ public class CashPaymentProduct1503SpecificInput
     {
         /// <summary>
         /// The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process.
-        /// <br />Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of 
+        /// <br />Note: The provided URL should be absolute and contain the https:// protocol. IP addresses are not supported, neither localhost. For use on mobile devices a custom protocol can be used in the form of 
         /// <i>protocol</i>://. This protocol must be registered on the device first.
         /// <br />URLs without a protocol will be rejected.
         /// </summary>

Worldline.Connect.Sdk/V1/Domain/CreateMandateWithReturnUrl.cs

@@ -8,6 +8,9 @@ public class CreateMandateWithReturnUrl : CreateMandateBase
     {
         /// <summary>
         /// Return URL to use if the mandate signing requires redirection.
+        /// <br />Note: The provided URL should be absolute and contain the https:// protocol. IP addresses are not supported, neither localhost. For use on mobile devices a custom protocol can be used in the form of 
+        /// <i>protocol</i>://. This protocol must be registered on the device first.
+        /// <br />URLs without a protocol will be rejected.
         /// </summary>
         public string ReturnUrl { get; set; }
     }

Worldline.Connect.Sdk/V1/Domain/CybersourceDecisionManager.cs

@@ -0,0 +1,31 @@
+/*
+ * This class was auto-generated from the API references found at
+ * https://apireference.connect.worldline-solutions.com/
+ */
+using System.Collections.Generic;
+
+namespace Worldline.Connect.Sdk.V1.Domain
+{
+    public class CybersourceDecisionManager
+    {
+        /// <summary>
+        /// Name of the clause within the applied policy that was triggered during the evaluation of this transaction.
+        /// </summary>
+        public string ClauseName { get; set; }
+
+        /// <summary>
+        /// Result of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
+        /// </summary>
+        public int? FraudScore { get; set; }
+
+        /// <summary>
+        /// Name of the policy that was applied during the evaluation of this transaction.
+        /// </summary>
+        public string PolicyApplied { get; set; }
+
+        /// <summary>
+        /// List of one or more reason codes.
+        /// </summary>
+        public IList<string> ReasonCodes { get; set; }
+    }
+}

Worldline.Connect.Sdk/V1/Domain/FraudResults.cs

@@ -6,6 +6,11 @@ namespace Worldline.Connect.Sdk.V1.Domain
 {
     public class FraudResults
     {
+        /// <summary>
+        /// This object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
+        /// </summary>
+        public CybersourceDecisionManager CybersourceDecisionManager { get; set; }
+
         /// <summary>
         /// Results from the fraud prevention check. Possible values are: 
         /// <list type="bullet">

Worldline.Connect.Sdk/V1/Domain/HostedCheckoutSpecificInput.cs

@@ -43,7 +43,7 @@ public class HostedCheckoutSpecificInput
 
         /// <summary>
         /// The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process.
-        /// <br />Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of 
+        /// <br />Note: The provided URL should be absolute and contain the https:// protocol. IP addresses are not supported, neither localhost. For use on mobile devices a custom protocol can be used in the form of 
         /// <i>protocol</i>://. This protocol must be registered on the device first.
         /// <br />URLs without a protocol will be rejected.
         /// </summary>

Worldline.Connect.Sdk/V1/Domain/HostedMandateManagementSpecificInput.cs

@@ -13,7 +13,7 @@ public class HostedMandateManagementSpecificInput
 
         /// <summary>
         /// The URL that the customer is redirect to after the mandate flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process.
-        /// <br />Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of 
+        /// <br />Note: The provided URL should be absolute and contain the https:// protocol. IP addresses are not supported, neither localhost. For use on mobile devices a custom protocol can be used in the form of 
         /// <i>protocol</i>://. This protocol must be registered on the device first.
         /// <br />URLs without a protocol will be rejected.
         /// </summary>

Worldline.Connect.Sdk/V1/Domain/MicrosoftFraudResults.cs

@@ -2,6 +2,8 @@
  * This class was auto-generated from the API references found at
  * https://apireference.connect.worldline-solutions.com/
  */
+using System.Collections.Generic;
+
 namespace Worldline.Connect.Sdk.V1.Domain
 {
     public class MicrosoftFraudResults
@@ -31,6 +33,11 @@ public class MicrosoftFraudResults
         /// </summary>
         public string PolicyApplied { get; set; }
 
+        /// <summary>
+        /// List of one or more reason codes.
+        /// </summary>
+        public IList<string> ReasonCodes { get; set; }
+
         /// <summary>
         /// The true IP address as determined by Microsoft Device Fingerprinting.
         /// </summary>

Worldline.Connect.Sdk/V1/Domain/RedirectPaymentMethodSpecificInput.cs

@@ -58,7 +58,7 @@ public class RedirectPaymentMethodSpecificInput : AbstractRedirectPaymentMethodS
 
         /// <summary>
         /// The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process.
-        /// <br />Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of 
+        /// <br />Note: The provided URL should be absolute and contain the https:// protocol. IP addresses are not supported, neither localhost. For use on mobile devices a custom protocol can be used in the form of 
         /// <i>protocol</i>://. This protocol must be registered on the device first.
         /// <br />URLs without a protocol will be rejected.
         /// </summary>

Worldline.Connect.Sdk/V1/Domain/RedirectionData.cs

@@ -8,7 +8,7 @@ public class RedirectionData
     {
         /// <summary>
         /// The URL that the customer is redirect to after the payment flow has finished. You can add any number of key value pairs in the query string that, for instance help you to identify the customer when they return to your site. Please note that we will also append some additional key value pairs that will also help you with this identification process.
-        /// <br />Note: The provided URL should be absolute and contain the protocol to use, e.g. http:// or https://. For use on mobile devices a custom protocol can be used in the form of 
+        /// <br />Note: The provided URL should be absolute and contain the https:// protocol. IP addresses are not supported, neither localhost. For use on mobile devices a custom protocol can be used in the form of 
         /// <i>protocol</i>://. This protocol must be registered on the device first.
         /// <br />URLs without a protocol will be rejected.
         /// </summary>

Worldline.Connect.Sdk/Worldline.Connect.Sdk.csproj

@@ -3,8 +3,8 @@
   <PropertyGroup>
     <TargetFrameworks>net45;netstandard2.0;netstandard2.1</TargetFrameworks>
     <RootNamespace>Worldline.Connect.Sdk</RootNamespace>
-    <AssemblyVersion>4.2.0</AssemblyVersion>
-    <Version>4.2.0</Version>
+    <AssemblyVersion>4.3.0</AssemblyVersion>
+    <Version>4.3.0</Version>
     <GeneratePackageOnBuild>true</GeneratePackageOnBuild>
     <Company>Worldline Global Collect</Company>
     <Product>Worldline Connect .NET SDK</Product>