cybersource_rest_client 0.0.40 → 0.0.41

data/lib/cybersource_rest_client/models/ptsv2payouts_processing_information_funding_options_initiator.rb

@@ -0,0 +1,190 @@
+=begin
+#CyberSource Merged Spec
+
+#All CyberSource API specs merged together. These are available at https://developer.cybersource.com/api/reference/api-reference.html
+
+OpenAPI spec version: 0.0.1
+
+Generated by: https://github.com/swagger-api/swagger-codegen.git
+Swagger Codegen version: 2.2.3
+
+=end
+
+require 'date'
+
+module CyberSource
+  class Ptsv2payoutsProcessingInformationFundingOptionsInitiator
+    # #### Visa Platform Connect : This API will contain a code that denotes whether the customer identification data belongs to the sender or the recipient.  The valid values are: • S (Payer (sender)) • R (Payee (recipient)) 
+    attr_accessor :type
+
+    # Attribute mapping from ruby-style variable name to JSON key.
+    def self.attribute_map
+      {
+        :'type' => :'type'
+      }
+    end
+
+    # Attribute type mapping.
+    def self.swagger_types
+      {
+        :'type' => :'String'
+      }
+    end
+
+    # Initializes the object
+    # @param [Hash] attributes Model attributes in the form of hash
+    def initialize(attributes = {})
+      return unless attributes.is_a?(Hash)
+
+      # convert string to symbol for hash key
+      attributes = attributes.each_with_object({}) { |(k, v), h| h[k.to_sym] = v }
+
+      if attributes.has_key?(:'type')
+        self.type = attributes[:'type']
+      end
+    end
+
+    # Show invalid properties with the reasons. Usually used together with valid?
+    # @return Array for valid properties with the reasons
+    def list_invalid_properties
+      invalid_properties = Array.new
+      invalid_properties
+    end
+
+    # Check to see if the all the properties in the model are valid
+    # @return true if the model is valid
+    def valid?
+      true
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] type Value to be assigned
+    def type=(type)
+      @type = type
+    end
+
+    # Checks equality by comparing each attribute.
+    # @param [Object] Object to be compared
+    def ==(o)
+      return true if self.equal?(o)
+      self.class == o.class &&
+          type == o.type
+    end
+
+    # @see the `==` method
+    # @param [Object] Object to be compared
+    def eql?(o)
+      self == o
+    end
+
+    # Calculates hash code according to all attributes.
+    # @return [Fixnum] Hash code
+    def hash
+      [type].hash
+    end
+
+    # Builds the object from hash
+    # @param [Hash] attributes Model attributes in the form of hash
+    # @return [Object] Returns the model itself
+    def build_from_hash(attributes)
+      return nil unless attributes.is_a?(Hash)
+      self.class.swagger_types.each_pair do |key, type|
+        if type =~ /\AArray<(.*)>/i
+          # check to ensure the input is an array given that the the attribute
+          # is documented as an array but the input is not
+          if attributes[self.class.attribute_map[key]].is_a?(Array)
+            self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) })
+          end
+        elsif !attributes[self.class.attribute_map[key]].nil?
+          self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]]))
+        end # or else data not found in attributes(hash), not an issue as the data can be optional
+      end
+
+      self
+    end
+
+    # Deserializes the data based on type
+    # @param string type Data type
+    # @param string value Value to be deserialized
+    # @return [Object] Deserialized data
+    def _deserialize(type, value)
+      case type.to_sym
+      when :DateTime
+        DateTime.parse(value)
+      when :Date
+        Date.parse(value)
+      when :String
+        value.to_s
+      when :Integer
+        value.to_i
+      when :Float
+        value.to_f
+      when :BOOLEAN
+        if value.to_s =~ /\A(true|t|yes|y|1)\z/i
+          true
+        else
+          false
+        end
+      when :Object
+        # generic object (usually a Hash), return directly
+        value
+      when /\AArray<(?<inner_type>.+)>\z/
+        inner_type = Regexp.last_match[:inner_type]
+        value.map { |v| _deserialize(inner_type, v) }
+      when /\AHash<(?<k_type>.+?), (?<v_type>.+)>\z/
+        k_type = Regexp.last_match[:k_type]
+        v_type = Regexp.last_match[:v_type]
+        {}.tap do |hash|
+          value.each do |k, v|
+            hash[_deserialize(k_type, k)] = _deserialize(v_type, v)
+          end
+        end
+      else # model
+        temp_model = CyberSource.const_get(type).new
+        temp_model.build_from_hash(value)
+      end
+    end
+
+    # Returns the string representation of the object
+    # @return [String] String presentation of the object
+    def to_s
+      to_hash.to_s
+    end
+
+    # to_body is an alias to to_hash (backward compatibility)
+    # @return [Hash] Returns the object in the form of hash
+    def to_body
+      to_hash
+    end
+
+    # Returns the object in the form of hash
+    # @return [Hash] Returns the object in the form of hash
+    def to_hash
+      hash = {}
+      self.class.attribute_map.each_pair do |attr, param|
+        value = self.send(attr)
+        next if value.nil?
+        hash[param] = _to_hash(value)
+      end
+      hash
+    end
+
+    # Outputs non-array value in the form of hash
+    # For object, use to_hash. Otherwise, just return the value
+    # @param [Object] value Any valid value
+    # @return [Hash] Returns the value in the form of hash
+    def _to_hash(value)
+      if value.is_a?(Array)
+        value.compact.map { |v| _to_hash(v) }
+      elsif value.is_a?(Hash)
+        {}.tap do |hash|
+          value.each { |k, v| hash[k] = _to_hash(v) }
+        end
+      elsif value.respond_to? :to_hash
+        value.to_hash
+      else
+        value
+      end
+    end
+  end
+end

data/lib/cybersource_rest_client/models/ptsv2payouts_sender_information.rb

@@ -58,6 +58,15 @@ module CyberSource
     # Customer's government-assigned tax identification number. 
     attr_accessor :vat_registration_number
 
+    # #### Visa Platform Connect This tag will contain the type of sender identification. The valid values are: • BTHD (Date of birth) • CUID (Customer identification (unspecified)) • NTID (National identification) • PASN (Passport number) • DRLN (Driver license) • TXIN (Tax identification) • CPNY (Company registration number) • PRXY (Proxy identification) • SSNB (Social security number) • ARNB (Alien registration number) • LAWE (Law enforcement identification) • MILI (Military identification) • TRVL (Travel identification (non-passport)) • EMAL (Email) • PHON (Phone number) 
+    attr_accessor :personal_id_type
+
+    # #### Visa Platform Connect This tag will denote whether the tax ID is a business or individual tax ID when personal ID Type contains the value of TXIN (Tax identification).  The valid values are: • B (Business) • I (Individual) 
+    attr_accessor :type
+
+    # #### Visa Platform Connect This tag will contain an acquirer-populated value associated with the API : senderInformation.personalIdType which will identify the personal ID type of the sender. 
+    attr_accessor :identification_number
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -75,7 +84,10 @@ module CyberSource
         :'postal_code' => :'postalCode',
         :'phone_number' => :'phoneNumber',
         :'date_of_birth' => :'dateOfBirth',
-        :'vat_registration_number' => :'vatRegistrationNumber'
+        :'vat_registration_number' => :'vatRegistrationNumber',
+        :'personal_id_type' => :'personalIdType',
+        :'type' => :'type',
+        :'identification_number' => :'identificationNumber'
       }
     end
 
@@ -96,7 +108,10 @@ module CyberSource
         :'postal_code' => :'String',
         :'phone_number' => :'String',
         :'date_of_birth' => :'String',
-        :'vat_registration_number' => :'String'
+        :'vat_registration_number' => :'String',
+        :'personal_id_type' => :'String',
+        :'type' => :'String',
+        :'identification_number' => :'String'
       }
     end
 
@@ -167,6 +182,18 @@ module CyberSource
       if attributes.has_key?(:'vatRegistrationNumber')
         self.vat_registration_number = attributes[:'vatRegistrationNumber']
       end
+
+      if attributes.has_key?(:'personalIdType')
+        self.personal_id_type = attributes[:'personalIdType']
+      end
+
+      if attributes.has_key?(:'type')
+        self.type = attributes[:'type']
+      end
+
+      if attributes.has_key?(:'identificationNumber')
+        self.identification_number = attributes[:'identificationNumber']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -266,6 +293,24 @@ module CyberSource
       @vat_registration_number = vat_registration_number
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] personal_id_type Value to be assigned
+    def personal_id_type=(personal_id_type)
+      @personal_id_type = personal_id_type
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] type Value to be assigned
+    def type=(type)
+      @type = type
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] identification_number Value to be assigned
+    def identification_number=(identification_number)
+      @identification_number = identification_number
+    end
+
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)
@@ -285,7 +330,10 @@ module CyberSource
           postal_code == o.postal_code &&
           phone_number == o.phone_number &&
           date_of_birth == o.date_of_birth &&
-          vat_registration_number == o.vat_registration_number
+          vat_registration_number == o.vat_registration_number &&
+          personal_id_type == o.personal_id_type &&
+          type == o.type &&
+          identification_number == o.identification_number
     end
 
     # @see the `==` method
@@ -297,7 +345,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [reference_number, account, first_name, middle_initial, middle_name, last_name, name, address1, locality, administrative_area, country_code, postal_code, phone_number, date_of_birth, vat_registration_number].hash
+      [reference_number, account, first_name, middle_initial, middle_name, last_name, name, address1, locality, administrative_area, country_code, postal_code, phone_number, date_of_birth, vat_registration_number, personal_id_type, type, identification_number].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/riskv1authenticationresults_payment_information_tokenized_card.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Riskv1authenticationresultsPaymentInformationTokenizedCard
-    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
+    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  #### Visa Platform Connect - `1`: In App tokenization. Example: InApp apple pay. - `3`: Card/Credential On File Tokenization.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
     attr_accessor :transaction_type
 
     # Three-digit value that indicates the card type.  **IMPORTANT** It is strongly recommended that you include the card type field in request messages even if it is optional for your processor and card type. Omitting the card type can cause the transaction to be processed with the wrong card type.  Possible values: - `001`: Visa. For card-present transactions on all processors except SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type value `001` for Visa Electron. - `002`: Mastercard, Eurocard[^1], which is a European regional brand of Mastercard. - `003`: American Express - `004`: Discover - `005`: Diners Club - `006`: Carte Blanche[^1] - `007`: JCB[^1] - `014`: Enroute[^1] - `021`: JAL[^1] - `024`: Maestro (UK Domestic)[^1] - `031`: Delta[^1]: Use this value only for Ingenico ePayments. For other processors, use `001` for all Visa card types. - `033`: Visa Electron[^1]. Use this value only for Ingenico ePayments and SIX. For other processors, use `001` for all Visa card types. - `034`: Dankort[^1] - `036`: Cartes Bancaires[^1,4] - `037`: Carta Si[^1] - `039`: Encoded account number[^1] - `040`: UATP[^1] - `042`: Maestro (International)[^1] - `050`: Hipercard[^2,3] - `051`: Aura - `054`: Elo[^3] - `062`: China UnionPay  [^1]: For this card type, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in your request for an authorization or a stand-alone credit. [^2]: For this card type on Cielo 3.0, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. This card type is not supported on Cielo 1.5. [^3]: For this card type on Getnet and Rede, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. [^4]: For this card type, you must include the `paymentInformation.card.type` in your request for any payer authentication services.  #### Used by **Authorization** Required for Carte Blanche and JCB. Optional for all other card types.  #### Card Present reply This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details. You must contact customer support to have your account enabled to receive these fields in the credit reply message.  Returned by the Credit service.  This reply field is only supported by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International 

data/lib/cybersource_rest_client/models/riskv1authentications_payment_information_tokenized_card.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Riskv1authenticationsPaymentInformationTokenizedCard
-    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
+    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  #### Visa Platform Connect - `1`: In App tokenization. Example: InApp apple pay. - `3`: Card/Credential On File Tokenization.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
     attr_accessor :transaction_type
 
     # Three-digit value that indicates the card type.  **IMPORTANT** It is strongly recommended that you include the card type field in request messages even if it is optional for your processor and card type. Omitting the card type can cause the transaction to be processed with the wrong card type.  Possible values: - `001`: Visa. For card-present transactions on all processors except SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type value `001` for Visa Electron. - `002`: Mastercard, Eurocard[^1], which is a European regional brand of Mastercard. - `003`: American Express - `004`: Discover - `005`: Diners Club - `006`: Carte Blanche[^1] - `007`: JCB[^1] - `014`: Enroute[^1] - `021`: JAL[^1] - `024`: Maestro (UK Domestic)[^1] - `031`: Delta[^1]: Use this value only for Ingenico ePayments. For other processors, use `001` for all Visa card types. - `033`: Visa Electron[^1]. Use this value only for Ingenico ePayments and SIX. For other processors, use `001` for all Visa card types. - `034`: Dankort[^1] - `036`: Cartes Bancaires[^1,4] - `037`: Carta Si[^1] - `039`: Encoded account number[^1] - `040`: UATP[^1] - `042`: Maestro (International)[^1] - `050`: Hipercard[^2,3] - `051`: Aura - `054`: Elo[^3] - `062`: China UnionPay  [^1]: For this card type, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in your request for an authorization or a stand-alone credit. [^2]: For this card type on Cielo 3.0, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. This card type is not supported on Cielo 1.5. [^3]: For this card type on Getnet and Rede, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. [^4]: For this card type, you must include the `paymentInformation.card.type` in your request for any payer authentication services.  #### Used by **Authorization** Required for Carte Blanche and JCB. Optional for all other card types.  #### Card Present reply This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details. You must contact customer support to have your account enabled to receive these fields in the credit reply message.  Returned by the Credit service.  This reply field is only supported by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International 

data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_tokenized_card.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Riskv1authenticationsetupsPaymentInformationTokenizedCard
-    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
+    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  #### Visa Platform Connect - `1`: In App tokenization. Example: InApp apple pay. - `3`: Card/Credential On File Tokenization.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
     attr_accessor :transaction_type
 
     # Three-digit value that indicates the card type.  **IMPORTANT** It is strongly recommended that you include the card type field in request messages even if it is optional for your processor and card type. Omitting the card type can cause the transaction to be processed with the wrong card type.  Possible values: - `001`: Visa. For card-present transactions on all processors except SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type value `001` for Visa Electron. - `002`: Mastercard, Eurocard[^1], which is a European regional brand of Mastercard. - `003`: American Express - `004`: Discover - `005`: Diners Club - `006`: Carte Blanche[^1] - `007`: JCB[^1] - `014`: Enroute[^1] - `021`: JAL[^1] - `024`: Maestro (UK Domestic)[^1] - `031`: Delta[^1]: Use this value only for Ingenico ePayments. For other processors, use `001` for all Visa card types. - `033`: Visa Electron[^1]. Use this value only for Ingenico ePayments and SIX. For other processors, use `001` for all Visa card types. - `034`: Dankort[^1] - `036`: Cartes Bancaires[^1,4] - `037`: Carta Si[^1] - `039`: Encoded account number[^1] - `040`: UATP[^1] - `042`: Maestro (International)[^1] - `050`: Hipercard[^2,3] - `051`: Aura - `054`: Elo[^3] - `062`: China UnionPay  [^1]: For this card type, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in your request for an authorization or a stand-alone credit. [^2]: For this card type on Cielo 3.0, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. This card type is not supported on Cielo 1.5. [^3]: For this card type on Getnet and Rede, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. [^4]: For this card type, you must include the `paymentInformation.card.type` in your request for any payer authentication services.  #### Used by **Authorization** Required for Carte Blanche and JCB. Optional for all other card types.  #### Card Present reply This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details. You must contact customer support to have your account enabled to receive these fields in the credit reply message.  Returned by the Credit service.  This reply field is only supported by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International 

data/lib/cybersource_rest_client/models/riskv1decisions_payment_information_tokenized_card.rb

@@ -15,7 +15,7 @@ require 'date'
 module CyberSource
   # Use this object to submit a payment network token instead of card-based values.
   class Riskv1decisionsPaymentInformationTokenizedCard
-    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
+    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  #### Visa Platform Connect - `1`: In App tokenization. Example: InApp apple pay. - `3`: Card/Credential On File Tokenization.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
     attr_accessor :transaction_type
 
     # Three-digit value that indicates the card type.  **IMPORTANT** It is strongly recommended that you include the card type field in request messages even if it is optional for your processor and card type. Omitting the card type can cause the transaction to be processed with the wrong card type.  Possible values: - `001`: Visa. For card-present transactions on all processors except SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type value `001` for Visa Electron. - `002`: Mastercard, Eurocard[^1], which is a European regional brand of Mastercard. - `003`: American Express - `004`: Discover - `005`: Diners Club - `006`: Carte Blanche[^1] - `007`: JCB[^1] - `014`: Enroute[^1] - `021`: JAL[^1] - `024`: Maestro (UK Domestic)[^1] - `031`: Delta[^1]: Use this value only for Ingenico ePayments. For other processors, use `001` for all Visa card types. - `033`: Visa Electron[^1]. Use this value only for Ingenico ePayments and SIX. For other processors, use `001` for all Visa card types. - `034`: Dankort[^1] - `036`: Cartes Bancaires[^1,4] - `037`: Carta Si[^1] - `039`: Encoded account number[^1] - `040`: UATP[^1] - `042`: Maestro (International)[^1] - `050`: Hipercard[^2,3] - `051`: Aura - `054`: Elo[^3] - `062`: China UnionPay  [^1]: For this card type, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in your request for an authorization or a stand-alone credit. [^2]: For this card type on Cielo 3.0, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. This card type is not supported on Cielo 1.5. [^3]: For this card type on Getnet and Rede, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. [^4]: For this card type, you must include the `paymentInformation.card.type` in your request for any payer authentication services.  #### Used by **Authorization** Required for Carte Blanche and JCB. Optional for all other card types.  #### Card Present reply This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details. You must contact customer support to have your account enabled to receive these fields in the credit reply message.  Returned by the Credit service.  This reply field is only supported by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International 

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_order_information_amount_details.rb

@@ -56,7 +56,7 @@ module CyberSource
         :'authorized_amount' => :'String',
         :'settlement_amount' => :'String',
         :'settlement_currency' => :'String',
-        :'surcharge' => :'Ptsv2paymentsOrderInformationAmountDetailsSurcharge'
+        :'surcharge' => :'Ptsv2payoutsOrderInformationAmountDetailsSurcharge'
       }
     end
 

data/lib/cybersource_rest_client/models/void_capture_request.rb

@@ -18,11 +18,14 @@ module CyberSource
 
     attr_accessor :payment_information
 
+    attr_accessor :order_information
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
         :'client_reference_information' => :'clientReferenceInformation',
-        :'payment_information' => :'paymentInformation'
+        :'payment_information' => :'paymentInformation',
+        :'order_information' => :'orderInformation'
       }
     end
 
@@ -30,7 +33,8 @@ module CyberSource
     def self.swagger_types
       {
         :'client_reference_information' => :'Ptsv2paymentsidreversalsClientReferenceInformation',
-        :'payment_information' => :'Ptsv2paymentsidvoidsPaymentInformation'
+        :'payment_information' => :'Ptsv2paymentsidvoidsPaymentInformation',
+        :'order_information' => :'Ptsv2paymentsidvoidsOrderInformation'
       }
     end
 
@@ -49,6 +53,10 @@ module CyberSource
       if attributes.has_key?(:'paymentInformation')
         self.payment_information = attributes[:'paymentInformation']
       end
+
+      if attributes.has_key?(:'orderInformation')
+        self.order_information = attributes[:'orderInformation']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -70,7 +78,8 @@ module CyberSource
       return true if self.equal?(o)
       self.class == o.class &&
           client_reference_information == o.client_reference_information &&
-          payment_information == o.payment_information
+          payment_information == o.payment_information &&
+          order_information == o.order_information
     end
 
     # @see the `==` method
@@ -82,7 +91,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [client_reference_information, payment_information].hash
+      [client_reference_information, payment_information, order_information].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/void_credit_request.rb

@@ -18,11 +18,14 @@ module CyberSource
 
     attr_accessor :payment_information
 
+    attr_accessor :order_information
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
         :'client_reference_information' => :'clientReferenceInformation',
-        :'payment_information' => :'paymentInformation'
+        :'payment_information' => :'paymentInformation',
+        :'order_information' => :'orderInformation'
       }
     end
 
@@ -30,7 +33,8 @@ module CyberSource
     def self.swagger_types
       {
         :'client_reference_information' => :'Ptsv2paymentsidreversalsClientReferenceInformation',
-        :'payment_information' => :'Ptsv2paymentsidvoidsPaymentInformation'
+        :'payment_information' => :'Ptsv2paymentsidvoidsPaymentInformation',
+        :'order_information' => :'Ptsv2paymentsidvoidsOrderInformation'
       }
     end
 
@@ -49,6 +53,10 @@ module CyberSource
       if attributes.has_key?(:'paymentInformation')
         self.payment_information = attributes[:'paymentInformation']
       end
+
+      if attributes.has_key?(:'orderInformation')
+        self.order_information = attributes[:'orderInformation']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -70,7 +78,8 @@ module CyberSource
       return true if self.equal?(o)
       self.class == o.class &&
           client_reference_information == o.client_reference_information &&
-          payment_information == o.payment_information
+          payment_information == o.payment_information &&
+          order_information == o.order_information
     end
 
     # @see the `==` method
@@ -82,7 +91,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [client_reference_information, payment_information].hash
+      [client_reference_information, payment_information, order_information].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/void_payment_request.rb

@@ -18,11 +18,14 @@ module CyberSource
 
     attr_accessor :payment_information
 
+    attr_accessor :order_information
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
         :'client_reference_information' => :'clientReferenceInformation',
-        :'payment_information' => :'paymentInformation'
+        :'payment_information' => :'paymentInformation',
+        :'order_information' => :'orderInformation'
       }
     end
 
@@ -30,7 +33,8 @@ module CyberSource
     def self.swagger_types
       {
         :'client_reference_information' => :'Ptsv2paymentsidreversalsClientReferenceInformation',
-        :'payment_information' => :'Ptsv2paymentsidvoidsPaymentInformation'
+        :'payment_information' => :'Ptsv2paymentsidvoidsPaymentInformation',
+        :'order_information' => :'Ptsv2paymentsidvoidsOrderInformation'
       }
     end
 
@@ -49,6 +53,10 @@ module CyberSource
       if attributes.has_key?(:'paymentInformation')
         self.payment_information = attributes[:'paymentInformation']
       end
+
+      if attributes.has_key?(:'orderInformation')
+        self.order_information = attributes[:'orderInformation']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -70,7 +78,8 @@ module CyberSource
       return true if self.equal?(o)
       self.class == o.class &&
           client_reference_information == o.client_reference_information &&
-          payment_information == o.payment_information
+          payment_information == o.payment_information &&
+          order_information == o.order_information
     end
 
     # @see the `==` method
@@ -82,7 +91,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [client_reference_information, payment_information].hash
+      [client_reference_information, payment_information, order_information].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/void_refund_request.rb

@@ -18,11 +18,14 @@ module CyberSource
 
     attr_accessor :payment_information
 
+    attr_accessor :order_information
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
         :'client_reference_information' => :'clientReferenceInformation',
-        :'payment_information' => :'paymentInformation'
+        :'payment_information' => :'paymentInformation',
+        :'order_information' => :'orderInformation'
       }
     end
 
@@ -30,7 +33,8 @@ module CyberSource
     def self.swagger_types
       {
         :'client_reference_information' => :'Ptsv2paymentsidreversalsClientReferenceInformation',
-        :'payment_information' => :'Ptsv2paymentsidvoidsPaymentInformation'
+        :'payment_information' => :'Ptsv2paymentsidvoidsPaymentInformation',
+        :'order_information' => :'Ptsv2paymentsidvoidsOrderInformation'
       }
     end
 
@@ -49,6 +53,10 @@ module CyberSource
       if attributes.has_key?(:'paymentInformation')
         self.payment_information = attributes[:'paymentInformation']
       end
+
+      if attributes.has_key?(:'orderInformation')
+        self.order_information = attributes[:'orderInformation']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -70,7 +78,8 @@ module CyberSource
       return true if self.equal?(o)
       self.class == o.class &&
           client_reference_information == o.client_reference_information &&
-          payment_information == o.payment_information
+          payment_information == o.payment_information &&
+          order_information == o.order_information
     end
 
     # @see the `==` method
@@ -82,7 +91,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [client_reference_information, payment_information].hash
+      [client_reference_information, payment_information, order_information].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client.rb

@@ -339,6 +339,7 @@ require 'cybersource_rest_client/models/ptsv2payments_processing_information_loa
 require 'cybersource_rest_client/models/ptsv2payments_processing_information_purchase_options'
 require 'cybersource_rest_client/models/ptsv2payments_processing_information_recurring_options'
 require 'cybersource_rest_client/models/ptsv2payments_processor_information'
+require 'cybersource_rest_client/models/ptsv2payments_processor_information_authorization_options'
 require 'cybersource_rest_client/models/ptsv2payments_promotion_information'
 require 'cybersource_rest_client/models/ptsv2payments_recipient_information'
 require 'cybersource_rest_client/models/ptsv2payments_recurring_payment_information'
@@ -412,6 +413,7 @@ require 'cybersource_rest_client/models/ptsv2paymentsidreversals_point_of_sale_i
 require 'cybersource_rest_client/models/ptsv2paymentsidreversals_processing_information'
 require 'cybersource_rest_client/models/ptsv2paymentsidreversals_reversal_information'
 require 'cybersource_rest_client/models/ptsv2paymentsidreversals_reversal_information_amount_details'
+require 'cybersource_rest_client/models/ptsv2paymentsidvoids_order_information'
 require 'cybersource_rest_client/models/ptsv2paymentsidvoids_payment_information'
 require 'cybersource_rest_client/models/ptsv2payouts_client_reference_information'
 require 'cybersource_rest_client/models/ptsv2payouts_merchant_information'
@@ -423,6 +425,8 @@ require 'cybersource_rest_client/models/ptsv2payouts_order_information_bill_to'
 require 'cybersource_rest_client/models/ptsv2payouts_payment_information'
 require 'cybersource_rest_client/models/ptsv2payouts_payment_information_card'
 require 'cybersource_rest_client/models/ptsv2payouts_processing_information'
+require 'cybersource_rest_client/models/ptsv2payouts_processing_information_funding_options'
+require 'cybersource_rest_client/models/ptsv2payouts_processing_information_funding_options_initiator'
 require 'cybersource_rest_client/models/ptsv2payouts_processing_information_payouts_options'
 require 'cybersource_rest_client/models/ptsv2payouts_recipient_information'
 require 'cybersource_rest_client/models/ptsv2payouts_sender_information'