cybersource_rest_client 0.0.59 → 0.0.60

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: efbdf0543589c3b5c3f5c596aacde6ddf3fb9f8820c62bebe4f387e6d48b3052
-  data.tar.gz: 82c740f7108ffa12616b7f5cbe255bbdab111583f6ebbca7f0e6cc8354b9d8a5
+  metadata.gz: 72f93dac3cb9a306139e36c407182d0ac99ed33d89b2817119d6017da3a23e17
+  data.tar.gz: a5c6fe36a7d69aea415250d4f48ac482669b16c95887ef8d68246d67d04fa4a3
 SHA512:
-  metadata.gz: 86864aa92da7190a38a4fd6765ae4af0e53945383107121385c5b1b88e279bca21319b9a49746c2d217dba4f3e0b6223192aa2135e1a2283e287afbf5d03d9cd
-  data.tar.gz: ec0998a1b58bf55510241cc4ed5ded3375b6befdd5605fffd00086a5005aca2a8f7bf4819347dc9b9814d54e467e8036f567da19083f4be0a67bb92935801256
+  metadata.gz: 4776e29c88123acc2e18e887d84a0ac636b2494af66a1a9e70ac09da7d42fe339e2506becc17a6bb2a0cb46636bb8c6dc2b531c243e588ae042c04b3bd73a744
+  data.tar.gz: 7bf51f772a8bcac560b66fc07a6aaef9ebcfd4aeebe5f4c500712e76a7fbd2a444f17f021a21983a13f7e5725f6683d2d4a9a217b954c0d257f9d42ca6373ff3

data/lib/cybersource_rest_client/api/billing_agreements_api.rb

@@ -20,25 +20,25 @@ module CyberSource
       @api_client = api_client
       @api_client.set_configuration(config)
     end
-    # Standing Instruction Cancellation or Modification
-    # Standing Instruction with or without Token
+    # Modify a Billing Agreement
+    # #### Standing Instruction: Standing Instruction with or without Token.  #### Revoke Mandate: When you revoke a mandate, any pending direct debits linked to that mandate are canceled. No notifications are sent. When you revoke a mandate with no pending direct debits, the Bacs scheme or customer's bank notify you of any subsequent direct debit events. When you revoke a mandate, you cannot send a direct debit request using the mandate ID. Customer payments cannot be made against a revoked mandate. You can revoke a mandate when the customer:   - Requests that you revoke the mandate.   - Closes their account with you. Possible revoke mandate status values -   - Revoked—the revoke mandate request was successfully processed.   - Failed—the revoke mandate request was not accepted.  #### Update Mandate: In most cases, the account details of an existing mandate cannot be updated in the Bacs schema, except by creating a new mandate. However, some very limited customer information, like name and address, can be updated to the mandate without needing to revoke it first  #### Mandate Status: After the customer signs the mandate, request that the mandate status service verify the mandate status. Possible mandate status values:   - Active—the mandate is successfully created. A direct debit can be sent for this mandate ID.   - Pending—a pending mandate means the mandate is not yet signed.   - Failed—the customer did not authenticate.   - Expired—the deadline to create the mandate passed.   - Revoked—the mandate is cancelled.  #### Paypal Billing Agreement:  A billing agreement is set up between PayPal and your customer. When you collect the details of a customer's billing agreement, you are able to bill that customer without requiring an authorization for each payment.  You can bill the customer at the same time you process their PayPal Express checkout order, which simplifies your business processes. 
     #
     # @param modify_billing_agreement 
     # @param id ID for de-registration or cancellation of Billing Agreement
     # @param [Hash] opts the optional parameters
-    # @return [PtsV2CreditsPost201Response1]
+    # @return [PtsV2ModifyBillingAgreementPost201Response]
     #
     def billing_agreements_de_registration(modify_billing_agreement, id, opts = {})
       data, status_code, headers = billing_agreements_de_registration_with_http_info(modify_billing_agreement, id, opts)
       return data, status_code, headers
     end
 
-    # Standing Instruction Cancellation or Modification
-    # Standing Instruction with or without Token
+    # Modify a Billing Agreement
+    # #### Standing Instruction: Standing Instruction with or without Token.  #### Revoke Mandate: When you revoke a mandate, any pending direct debits linked to that mandate are canceled. No notifications are sent. When you revoke a mandate with no pending direct debits, the Bacs scheme or customer's bank notify you of any subsequent direct debit events. When you revoke a mandate, you cannot send a direct debit request using the mandate ID. Customer payments cannot be made against a revoked mandate. You can revoke a mandate when the customer:   - Requests that you revoke the mandate.   - Closes their account with you. Possible revoke mandate status values -   - Revoked—the revoke mandate request was successfully processed.   - Failed—the revoke mandate request was not accepted.  #### Update Mandate: In most cases, the account details of an existing mandate cannot be updated in the Bacs schema, except by creating a new mandate. However, some very limited customer information, like name and address, can be updated to the mandate without needing to revoke it first  #### Mandate Status: After the customer signs the mandate, request that the mandate status service verify the mandate status. Possible mandate status values:   - Active—the mandate is successfully created. A direct debit can be sent for this mandate ID.   - Pending—a pending mandate means the mandate is not yet signed.   - Failed—the customer did not authenticate.   - Expired—the deadline to create the mandate passed.   - Revoked—the mandate is cancelled.  #### Paypal Billing Agreement:  A billing agreement is set up between PayPal and your customer. When you collect the details of a customer's billing agreement, you are able to bill that customer without requiring an authorization for each payment.  You can bill the customer at the same time you process their PayPal Express checkout order, which simplifies your business processes. 
     # @param modify_billing_agreement 
     # @param id ID for de-registration or cancellation of Billing Agreement
     # @param [Hash] opts the optional parameters
-    # @return [Array<(PtsV2CreditsPost201Response1, Fixnum, Hash)>] PtsV2CreditsPost201Response1 data, response status code and response headers
+    # @return [Array<(PtsV2ModifyBillingAgreementPost201Response, Fixnum, Hash)>] PtsV2ModifyBillingAgreementPost201Response data, response status code and response headers
     def billing_agreements_de_registration_with_http_info(modify_billing_agreement, id, opts = {})
 
       if @api_client.config.debugging
@@ -84,7 +84,7 @@ module CyberSource
         :form_params => form_params,
         :body => post_body,
         :auth_names => auth_names,
-        :return_type => 'PtsV2CreditsPost201Response1')
+        :return_type => 'PtsV2ModifyBillingAgreementPost201Response')
       if @api_client.config.debugging
         begin
         raise
@@ -170,23 +170,23 @@ module CyberSource
       end
       return data, status_code, headers
     end
-    # Standing Instruction completion registration
-    # Standing Instruction with or without Token. Transaction amount in case First payment is coming along with registration. Only 2 decimal places allowed
+    # Create a Billing Agreement
+    # #### Standing Instruction: Standing Instruction with or without Token. Transaction amount in case First payment is coming along with registration. Only 2 decimal places allowed  #### Create Mandate: You can create a mandate through the direct debit mandate flow. Possible create mandate status values:   - Pending—the create mandate request was successfully processed.   - Failed—the create mandate request was not accepted.  #### Import Mandate: In the Bacs scheme, a mandate is created with a status of active. Direct debit collections can be made against it immediately. You can import a mandate to the CyberSource database when:   - You have existing customers with signed, active mandates   - You manage mandates outside of CyberSource.  When you import an existing mandate to the CyberSource database, provide a unique value for the mandate ID or the request results in an error. If an import mandate request is not accepted, the import mandate status value is failed. 
     #
     # @param create_billing_agreement 
     # @param [Hash] opts the optional parameters
-    # @return [PtsV2CreditsPost201Response1]
+    # @return [PtsV2CreateBillingAgreementPost201Response]
     #
     def billing_agreements_registration(create_billing_agreement, opts = {})
       data, status_code, headers = billing_agreements_registration_with_http_info(create_billing_agreement, opts)
       return data, status_code, headers
     end
 
-    # Standing Instruction completion registration
-    # Standing Instruction with or without Token. Transaction amount in case First payment is coming along with registration. Only 2 decimal places allowed
+    # Create a Billing Agreement
+    # #### Standing Instruction: Standing Instruction with or without Token. Transaction amount in case First payment is coming along with registration. Only 2 decimal places allowed  #### Create Mandate: You can create a mandate through the direct debit mandate flow. Possible create mandate status values:   - Pending—the create mandate request was successfully processed.   - Failed—the create mandate request was not accepted.  #### Import Mandate: In the Bacs scheme, a mandate is created with a status of active. Direct debit collections can be made against it immediately. You can import a mandate to the CyberSource database when:   - You have existing customers with signed, active mandates   - You manage mandates outside of CyberSource.  When you import an existing mandate to the CyberSource database, provide a unique value for the mandate ID or the request results in an error. If an import mandate request is not accepted, the import mandate status value is failed. 
     # @param create_billing_agreement 
     # @param [Hash] opts the optional parameters
-    # @return [Array<(PtsV2CreditsPost201Response1, Fixnum, Hash)>] PtsV2CreditsPost201Response1 data, response status code and response headers
+    # @return [Array<(PtsV2CreateBillingAgreementPost201Response, Fixnum, Hash)>] PtsV2CreateBillingAgreementPost201Response data, response status code and response headers
     def billing_agreements_registration_with_http_info(create_billing_agreement, opts = {})
 
       if @api_client.config.debugging
@@ -228,7 +228,7 @@ module CyberSource
         :form_params => form_params,
         :body => post_body,
         :auth_names => auth_names,
-        :return_type => 'PtsV2CreditsPost201Response1')
+        :return_type => 'PtsV2CreateBillingAgreementPost201Response')
       if @api_client.config.debugging
         begin
         raise

data/lib/cybersource_rest_client/api/payments_api.rb

@@ -20,6 +20,81 @@ module CyberSource
       @api_client = api_client
       @api_client.set_configuration(config)
     end
+    # Create a Payment Order Request
+    # Create a Payment Order Request
+    #
+    # @param order_payment_request 
+    # @param id Request identifier number for the order request. 
+    # @param [Hash] opts the optional parameters
+    # @return [PtsV2PaymentsOrderPost201Response]
+    #
+    def create_order_request(order_payment_request, id, opts = {})
+      data, status_code, headers = create_order_request_with_http_info(order_payment_request, id, opts)
+      return data, status_code, headers
+    end
+
+    # Create a Payment Order Request
+    # Create a Payment Order Request
+    # @param order_payment_request 
+    # @param id Request identifier number for the order request. 
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(PtsV2PaymentsOrderPost201Response, Fixnum, Hash)>] PtsV2PaymentsOrderPost201Response data, response status code and response headers
+    def create_order_request_with_http_info(order_payment_request, id, opts = {})
+
+      if @api_client.config.debugging
+          begin
+            raise
+                @api_client.config.logger.debug 'Calling API: PaymentsApi.create_order_request ...'
+            rescue
+                puts 'Cannot write to log'
+            end
+      end
+      # verify the required parameter 'order_payment_request' is set
+      if @api_client.config.client_side_validation && order_payment_request.nil?
+        fail ArgumentError, "Missing the required parameter 'order_payment_request' when calling PaymentsApi.create_order_request"
+      end
+      # verify the required parameter 'id' is set
+      if @api_client.config.client_side_validation && id.nil?
+        fail ArgumentError, "Missing the required parameter 'id' when calling PaymentsApi.create_order_request"
+      end
+      # resource path
+      local_var_path = 'pts/v2/payment-references/{id}/intents'.sub('{' + 'id' + '}', id.to_s)
+
+      # query parameters
+      query_params = {}
+
+      # header parameters
+      header_params = {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/hal+json;charset=utf-8'])
+      # HTTP header 'Content-Type'
+      header_params['Content-Type'] = @api_client.select_header_content_type(['application/json;charset=utf-8'])
+
+      # form parameters
+      form_params = {}
+
+      # http body (model)
+      post_body = @api_client.object_to_http_body(order_payment_request)
+      sdk_tracker = SdkTracker.new
+      post_body = sdk_tracker.insert_developer_id_tracker(post_body, 'OrderPaymentRequest', @api_client.config.host)
+      auth_names = []
+      data, status_code, headers = @api_client.call_api(:POST, local_var_path,
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => 'PtsV2PaymentsOrderPost201Response')
+      if @api_client.config.debugging
+        begin
+        raise
+            @api_client.config.logger.debug "API called: PaymentsApi#create_order_request\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+        rescue
+            puts 'Cannot write to log'
+        end
+      end
+      return data, status_code, headers
+    end
     # Process a Payment
     # A payment authorizes the amount for the transaction. There are a number of supported payment features, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc..  A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/docs/cybs/en-us/payments/developer/ctv/rest/payments/payments-intro.html).  Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation. 
     #
@@ -89,6 +164,75 @@ module CyberSource
       end
       return data, status_code, headers
     end
+    # Create Alternative Payments Sessions Request
+    # Create Alternative Payments Sessions Request
+    #
+    # @param create_session_req 
+    # @param [Hash] opts the optional parameters
+    # @return [PtsV2PaymentsPost201Response2]
+    #
+    def create_session_request(create_session_req, opts = {})
+      data, status_code, headers = create_session_request_with_http_info(create_session_req, opts)
+      return data, status_code, headers
+    end
+
+    # Create Alternative Payments Sessions Request
+    # Create Alternative Payments Sessions Request
+    # @param create_session_req 
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(PtsV2PaymentsPost201Response2, Fixnum, Hash)>] PtsV2PaymentsPost201Response2 data, response status code and response headers
+    def create_session_request_with_http_info(create_session_req, opts = {})
+
+      if @api_client.config.debugging
+          begin
+            raise
+                @api_client.config.logger.debug 'Calling API: PaymentsApi.create_session_request ...'
+            rescue
+                puts 'Cannot write to log'
+            end
+      end
+      # verify the required parameter 'create_session_req' is set
+      if @api_client.config.client_side_validation && create_session_req.nil?
+        fail ArgumentError, "Missing the required parameter 'create_session_req' when calling PaymentsApi.create_session_request"
+      end
+      # resource path
+      local_var_path = 'pts/v2/payment-references'
+
+      # query parameters
+      query_params = {}
+
+      # header parameters
+      header_params = {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/hal+json;charset=utf-8'])
+      # HTTP header 'Content-Type'
+      header_params['Content-Type'] = @api_client.select_header_content_type(['application/json;charset=utf-8'])
+
+      # form parameters
+      form_params = {}
+
+      # http body (model)
+      post_body = @api_client.object_to_http_body(create_session_req)
+      sdk_tracker = SdkTracker.new
+      post_body = sdk_tracker.insert_developer_id_tracker(post_body, 'CreateSessionReq', @api_client.config.host)
+      auth_names = []
+      data, status_code, headers = @api_client.call_api(:POST, local_var_path,
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => 'PtsV2PaymentsPost201Response2')
+      if @api_client.config.debugging
+        begin
+        raise
+            @api_client.config.logger.debug "API called: PaymentsApi#create_session_request\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+        rescue
+            puts 'Cannot write to log'
+        end
+      end
+      return data, status_code, headers
+    end
     # Increment an Authorization
     # Use this service to authorize additional charges in a lodging or autorental transaction. Include the ID returned from the original authorization in the PATCH request to add additional charges to that authorization. 
     #
@@ -239,5 +383,80 @@ module CyberSource
       end
       return data, status_code, headers
     end
+    # Update Alternative Payments Sessions Request
+    # Update Alternative Payments Sessions Request
+    #
+    # @param create_session_request 
+    # @param id The payment ID. This ID is returned from a previous payment request.
+    # @param [Hash] opts the optional parameters
+    # @return [PtsV2PaymentsPost201Response2]
+    #
+    def update_session_req(create_session_request, id, opts = {})
+      data, status_code, headers = update_session_req_with_http_info(create_session_request, id, opts)
+      return data, status_code, headers
+    end
+
+    # Update Alternative Payments Sessions Request
+    # Update Alternative Payments Sessions Request
+    # @param create_session_request 
+    # @param id The payment ID. This ID is returned from a previous payment request.
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(PtsV2PaymentsPost201Response2, Fixnum, Hash)>] PtsV2PaymentsPost201Response2 data, response status code and response headers
+    def update_session_req_with_http_info(create_session_request, id, opts = {})
+
+      if @api_client.config.debugging
+          begin
+            raise
+                @api_client.config.logger.debug 'Calling API: PaymentsApi.update_session_req ...'
+            rescue
+                puts 'Cannot write to log'
+            end
+      end
+      # verify the required parameter 'create_session_request' is set
+      if @api_client.config.client_side_validation && create_session_request.nil?
+        fail ArgumentError, "Missing the required parameter 'create_session_request' when calling PaymentsApi.update_session_req"
+      end
+      # verify the required parameter 'id' is set
+      if @api_client.config.client_side_validation && id.nil?
+        fail ArgumentError, "Missing the required parameter 'id' when calling PaymentsApi.update_session_req"
+      end
+      # resource path
+      local_var_path = 'pts/v2/payment-references/{id}'.sub('{' + 'id' + '}', id.to_s)
+
+      # query parameters
+      query_params = {}
+
+      # header parameters
+      header_params = {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/hal+json;charset=utf-8'])
+      # HTTP header 'Content-Type'
+      header_params['Content-Type'] = @api_client.select_header_content_type(['application/json;charset=utf-8'])
+
+      # form parameters
+      form_params = {}
+
+      # http body (model)
+      post_body = @api_client.object_to_http_body(create_session_request)
+      sdk_tracker = SdkTracker.new
+      post_body = sdk_tracker.insert_developer_id_tracker(post_body, 'CreateSessionRequest', @api_client.config.host)
+      auth_names = []
+      data, status_code, headers = @api_client.call_api(:PATCH, local_var_path,
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => 'PtsV2PaymentsPost201Response2')
+      if @api_client.config.debugging
+        begin
+        raise
+            @api_client.config.logger.debug "API called: PaymentsApi#update_session_req\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+        rescue
+            puts 'Cannot write to log'
+        end
+      end
+      return data, status_code, headers
+    end
   end
 end

data/lib/cybersource_rest_client/api/transient_token_data_api.rb

@@ -20,6 +20,77 @@ module CyberSource
       @api_client = api_client
       @api_client.set_configuration(config)
     end
+    # Get Payment Credentials
+    # Retrieve the Payment data captured by Unified Checkout. This API is used to retrieve the detailed data represented by the Transient Token. This API will return PCI payment data captured by the Unified Checkout platform.
+    #
+    # @param jti The jti field contained within the Transient token returned from a successful Unified Checkout transaction 
+    # @param [Hash] opts the optional parameters
+    # @return [String]
+    #
+    def get_payment_credentials_for_transient_token(jti, opts = {})
+      data, status_code, headers = get_payment_credentials_for_transient_token_with_http_info(jti, opts)
+      return data, status_code, headers
+    end
+
+    # Get Payment Credentials
+    # Retrieve the Payment data captured by Unified Checkout. This API is used to retrieve the detailed data represented by the Transient Token. This API will return PCI payment data captured by the Unified Checkout platform.
+    # @param jti The jti field contained within the Transient token returned from a successful Unified Checkout transaction 
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(String, Fixnum, Hash)>] String data, response status code and response headers
+    def get_payment_credentials_for_transient_token_with_http_info(jti, opts = {})
+
+      if @api_client.config.debugging
+          begin
+            raise
+                @api_client.config.logger.debug 'Calling API: TransientTokenDataApi.get_payment_credentials_for_transient_token ...'
+            rescue
+                puts 'Cannot write to log'
+            end
+      end
+      # verify the required parameter 'jti' is set
+      if @api_client.config.client_side_validation && jti.nil?
+        fail ArgumentError, "Missing the required parameter 'jti' when calling TransientTokenDataApi.get_payment_credentials_for_transient_token"
+      end
+      # resource path
+      local_var_path = 'up/v1/payment-credentials/{jti}'.sub('{' + 'jti' + '}', jti.to_s)
+
+      # query parameters
+      query_params = {}
+
+      # header parameters
+      header_params = {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      # HTTP header 'Content-Type'
+      header_params['Content-Type'] = @api_client.select_header_content_type(['application/json;charset=utf-8'])
+
+      # form parameters
+      form_params = {}
+
+      # http body (model)
+      if 'GET' == 'POST'
+        post_body = '{}'
+      else
+        post_body = nil
+      end
+      auth_names = []
+      data, status_code, headers = @api_client.call_api(:GET, local_var_path,
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => 'String')
+      if @api_client.config.debugging
+        begin
+        raise
+            @api_client.config.logger.debug "API called: TransientTokenDataApi#get_payment_credentials_for_transient_token\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+        rescue
+            puts 'Cannot write to log'
+        end
+      end
+      return data, status_code, headers
+    end
     # Get Transient Token Data
     # Retrieve the data captured by Unified Checkout. This API is used to retrieve the detailed data represented by the Transient Token. This API will not return PCI payment data (PAN). Include the Request ID in the GET request to retrieve the transaction details.
     #

data/lib/cybersource_rest_client/api/unified_checkout_capture_context_api.rb

@@ -21,7 +21,7 @@ module CyberSource
       @api_client.set_configuration(config)
     end
     # Generate Unified Checkout Capture Context
-    # Generate a one-time use capture context used for the invocation of Unified Checkout. The Request wil contain all of the parameters for how Unified Checkout will operate within a client webpage. The resulting payload will be a JWT signed object that can be used to initiate Unified Checkout within a merchant web page
+    # Unified Checkout is a powerful product within the Digital Acceptance Suite. Unified Checkout is designed to assist merchants with the adoption and inclusion of digital payments within their payment acceptance page. With Unified Checkout Integration you can add digital payment methods to create familiar, convenient and seamless payment experiences that are designed to reduce checkout friction and increase conversions. Click to Pay Drop-in UI is built on the Unified Checkout platform. For more information about Unified Checkout, see the [Unified Checkout Developer Guides Page](https://developer.cybersource.com/docs/cybs/en-us/unified-checkout/developer/all/rest/unified-checkout/uc-intro.html). For examples on how to integrate Unified Checkout within your webpage please see our [GitHub Unified Checkout Samples](https://github.com/CyberSource/cybersource-unified-checkout-sample-java). For more information about Click to Pay drop in UI, see the [Click to Pay Drop-in UI Developer Guides Page](https://developer.cybersource.com/docs/cybs/en-us/click-to-pay/developer/all/rest/click-to-pay/ctp-intro.html). Generate Unified Checkout Capture Context Generate a one-time use capture context used for the invocation of Unified Checkout. The Request wil contain all of the parameters for how Unified Checkout will operate within a client webpage. The resulting payload will be a JWT signed object that can be used to initiate Unified Checkout or Click to Pay Drop-in UI within a web page
     #
     # @param generate_unified_checkout_capture_context_request 
     # @param [Hash] opts the optional parameters
@@ -33,7 +33,7 @@ module CyberSource
     end
 
     # Generate Unified Checkout Capture Context
-    # Generate a one-time use capture context used for the invocation of Unified Checkout. The Request wil contain all of the parameters for how Unified Checkout will operate within a client webpage. The resulting payload will be a JWT signed object that can be used to initiate Unified Checkout within a merchant web page
+    # Unified Checkout is a powerful product within the Digital Acceptance Suite. Unified Checkout is designed to assist merchants with the adoption and inclusion of digital payments within their payment acceptance page. With Unified Checkout Integration you can add digital payment methods to create familiar, convenient and seamless payment experiences that are designed to reduce checkout friction and increase conversions. Click to Pay Drop-in UI is built on the Unified Checkout platform. For more information about Unified Checkout, see the [Unified Checkout Developer Guides Page](https://developer.cybersource.com/docs/cybs/en-us/unified-checkout/developer/all/rest/unified-checkout/uc-intro.html). For examples on how to integrate Unified Checkout within your webpage please see our [GitHub Unified Checkout Samples](https://github.com/CyberSource/cybersource-unified-checkout-sample-java). For more information about Click to Pay drop in UI, see the [Click to Pay Drop-in UI Developer Guides Page](https://developer.cybersource.com/docs/cybs/en-us/click-to-pay/developer/all/rest/click-to-pay/ctp-intro.html). Generate Unified Checkout Capture Context Generate a one-time use capture context used for the invocation of Unified Checkout. The Request wil contain all of the parameters for how Unified Checkout will operate within a client webpage. The resulting payload will be a JWT signed object that can be used to initiate Unified Checkout or Click to Pay Drop-in UI within a web page
     # @param generate_unified_checkout_capture_context_request 
     # @param [Hash] opts the optional parameters
     # @return [Array<(String, Fixnum, Hash)>] String data, response status code and response headers