cybersource_rest_client 0.0.22 → 0.0.28

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_payment_information_card.rb

@@ -14,16 +14,16 @@ require 'date'
 
 module CyberSource
   class TssV2TransactionsGet200ResponsePaymentInformationCard
-    # Last four digits of the cardholder’s account number. This field is returned only for tokenized transactions. You can use this value on the receipt that you give to the cardholder.  **Note** This field is returned only for CyberSource through VisaNet and FDC Nashville Global.  #### CyberSource through VisaNet The value for this field corresponds to the following data in the TC 33 capture file: - Record: CP01 TCRB - Position: 85 - Field: American Express last 4 PAN return indicator. 
+    # Last four digits of the cardholder’s account number. 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.  #### PIN debit This field is returned only for tokenized transactions. You can use this value on the receipt that you give to the cardholder.  Returned by PIN debit credit and PIN debit purchase.  This field is supported only by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX 
     attr_accessor :suffix
 
     # Bank Identification Number (BIN). This is the initial four to six numbers on a credit card account number. 
     attr_accessor :prefix
 
-    # Two-digit month in which the payment card expires.  Format: `MM`.  Valid values: `01` through `12`.  #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`01` through `12`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request.  #### Encoded Account Numbers For encoded account numbers (_type_=039), if there is no expiration date on the card, use `12`.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  For processor-specific information, see the `customer_cc_expmo` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
+    # Two-digit month in which the payment card expires.  Format: `MM`.  Valid values: `01` through `12`. Leading 0 is required.  #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`01` through `12`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request.  #### Encoded Account Numbers For encoded account numbers (_type_=039), if there is no expiration date on the card, use `12`.  #### FDMS Nashville Required field.  #### GPX Required if `pointOfSaleInformation.entryMode=keyed`. However, this field is optional if your account is configured for relaxed requirements for address data and expiration date. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### All other processors Required if `pointOfSaleInformation.entryMode=keyed`. However, this field is optional if your account is configured for relaxed requirements for address data and expiration date. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting. 
     attr_accessor :expiration_month
 
-    # Four-digit year in which the credit card expires.  Format: `YYYY`.  #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`1900` through `3000`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request.  #### Encoded Account Numbers For encoded account numbers (**_type_**`=039`), if there is no expiration date on the card, use `2021`.  #### FDC Nashville Global and FDMS South You can send in 2 digits or 4 digits. If you send in 2 digits, they must be the last 2 digits of the year.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  For processor-specific information, see the `customer_cc_expyr` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
+    # Four-digit year in which the payment card expires.  Format: `YYYY`.  #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`1900` through `3000`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request.  #### Encoded Account Numbers For encoded account numbers (**_type_**`=039`), if there is no expiration date on the card, use `2021`.  #### FDMS Nashville Required field.  #### FDC Nashville Global and FDMS South You can send in 2 digits or 4 digits. If you send in 2 digits, they must be the last 2 digits of the year.  #### GPX Required if `pointOfSaleInformation.entryMode=keyed`. However, this field is optional if your account is configured for relaxed requirements for address data and expiration date. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### All other processors Required if `pointOfSaleInformation.entryMode=keyed`. However, this field is optional if your account is configured for relaxed requirements for address data and expiration date. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting. 
     attr_accessor :expiration_year
 
     # Month of the start of the Maestro (UK Domestic) card validity period. Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card. `Format: MM`. Possible values: 01 through 12.  **Note** The start date is not required for Maestro (UK Domestic) transactions. 
@@ -35,7 +35,7 @@ module CyberSource
     # Number of times a Maestro (UK Domestic) card has been issued to the account holder. The card might or might not have an issue number. The number can consist of one or two digits, and the first digit might be a zero. When you include this value in your request, include exactly what is printed on the card. A value of 2 is different than a value of 02. Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card.  **Note** The issue number is not required for Maestro (UK Domestic) transactions. 
     attr_accessor :issue_number
 
-    # Three-digit value that indicates the card type.  Type of card to authorize. - 001 Visa - 002 Mastercard - 003 Amex - 004 Discover - 005: Diners Club - 007: JCB - 024: Maestro (UK Domestic) - 036: Cartes Bancaires - 039 Encoded account number - 042: Maestro (International)  For the complete list of possible values, see `card_type` field description in the [Credit Card Services Using the SCMP API Guide.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
+    # 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] - `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.  #### 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  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International 
     attr_accessor :type
 
     # Identifier for the issuing bank that provided the customer’s encoded account number. Contact your processor for the bank’s ID. 
@@ -129,132 +129,60 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if !@prefix.nil? && @prefix.to_s.length > 6
-        invalid_properties.push('invalid value for "prefix", the character length must be smaller than or equal to 6.')
-      end
-
-      if !@expiration_month.nil? && @expiration_month.to_s.length > 2
-        invalid_properties.push('invalid value for "expiration_month", the character length must be smaller than or equal to 2.')
-      end
-
-      if !@expiration_year.nil? && @expiration_year.to_s.length > 4
-        invalid_properties.push('invalid value for "expiration_year", the character length must be smaller than or equal to 4.')
-      end
-
-      if !@start_month.nil? && @start_month.to_s.length > 2
-        invalid_properties.push('invalid value for "start_month", the character length must be smaller than or equal to 2.')
-      end
-
-      if !@start_year.nil? && @start_year.to_s.length > 4
-        invalid_properties.push('invalid value for "start_year", the character length must be smaller than or equal to 4.')
-      end
-
-      if !@issue_number.nil? && @issue_number.to_s.length > 5
-        invalid_properties.push('invalid value for "issue_number", the character length must be smaller than or equal to 5.')
-      end
-
-      if !@account_encoder_id.nil? && @account_encoder_id.to_s.length > 3
-        invalid_properties.push('invalid value for "account_encoder_id", the character length must be smaller than or equal to 3.')
-      end
-
-      if !@use_as.nil? && @use_as.to_s.length > 20
-        invalid_properties.push('invalid value for "use_as", the character length must be smaller than or equal to 20.')
-      end
-
       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?
-      return false if !@prefix.nil? && @prefix.to_s.length > 6
-      return false if !@expiration_month.nil? && @expiration_month.to_s.length > 2
-      return false if !@expiration_year.nil? && @expiration_year.to_s.length > 4
-      return false if !@start_month.nil? && @start_month.to_s.length > 2
-      return false if !@start_year.nil? && @start_year.to_s.length > 4
-      return false if !@issue_number.nil? && @issue_number.to_s.length > 5
-      return false if !@account_encoder_id.nil? && @account_encoder_id.to_s.length > 3
-      return false if !@use_as.nil? && @use_as.to_s.length > 20
       true
     end
 
     # Custom attribute writer method with validation
     # @param [Object] prefix Value to be assigned
     def prefix=(prefix)
-      if !prefix.nil? && prefix.to_s.length > 6
-        fail ArgumentError, 'invalid value for "prefix", the character length must be smaller than or equal to 6.'
-      end
-
       @prefix = prefix
     end
 
     # Custom attribute writer method with validation
     # @param [Object] expiration_month Value to be assigned
     def expiration_month=(expiration_month)
-      if !expiration_month.nil? && expiration_month.to_s.length > 2
-        fail ArgumentError, 'invalid value for "expiration_month", the character length must be smaller than or equal to 2.'
-      end
-
       @expiration_month = expiration_month
     end
 
     # Custom attribute writer method with validation
     # @param [Object] expiration_year Value to be assigned
     def expiration_year=(expiration_year)
-      if !expiration_year.nil? && expiration_year.to_s.length > 4
-        fail ArgumentError, 'invalid value for "expiration_year", the character length must be smaller than or equal to 4.'
-      end
-
       @expiration_year = expiration_year
     end
 
     # Custom attribute writer method with validation
     # @param [Object] start_month Value to be assigned
     def start_month=(start_month)
-      if !start_month.nil? && start_month.to_s.length > 2
-        fail ArgumentError, 'invalid value for "start_month", the character length must be smaller than or equal to 2.'
-      end
-
       @start_month = start_month
     end
 
     # Custom attribute writer method with validation
     # @param [Object] start_year Value to be assigned
     def start_year=(start_year)
-      if !start_year.nil? && start_year.to_s.length > 4
-        fail ArgumentError, 'invalid value for "start_year", the character length must be smaller than or equal to 4.'
-      end
-
       @start_year = start_year
     end
 
     # Custom attribute writer method with validation
     # @param [Object] issue_number Value to be assigned
     def issue_number=(issue_number)
-      if !issue_number.nil? && issue_number.to_s.length > 5
-        fail ArgumentError, 'invalid value for "issue_number", the character length must be smaller than or equal to 5.'
-      end
-
       @issue_number = issue_number
     end
 
     # Custom attribute writer method with validation
     # @param [Object] account_encoder_id Value to be assigned
     def account_encoder_id=(account_encoder_id)
-      if !account_encoder_id.nil? && account_encoder_id.to_s.length > 3
-        fail ArgumentError, 'invalid value for "account_encoder_id", the character length must be smaller than or equal to 3.'
-      end
-
       @account_encoder_id = account_encoder_id
     end
 
     # Custom attribute writer method with validation
     # @param [Object] use_as Value to be assigned
     def use_as=(use_as)
-      if !use_as.nil? && use_as.to_s.length > 20
-        fail ArgumentError, 'invalid value for "use_as", the character length must be smaller than or equal to 20.'
-      end
-
       @use_as = use_as
     end
 

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_payment_information_payment_type.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class TssV2TransactionsGet200ResponsePaymentInformationPaymentType
-    # A Payment Type is an agreed means for a payee to receive legal tender from a payer. The way one pays for a commercial financial transaction. Examples: Card, Bank Transfer, Digital, Direct Debit. Possible values: - `CARD` (use this for a PIN debit transaction) - `CHECK` (use this for eCheck payment and this is equivalent to invoke ics_ecp_debit or ics_ecp_credit service) 
+    # A Payment Type is an agreed means for a payee to receive legal tender from a payer. The way one pays for a commercial financial transaction. Examples: Card, Bank Transfer, Digital, Direct Debit. Possible values: - `CARD` (use this for a PIN debit transaction) - `CHECK` (use this for all eCheck payment transactions - ECP Debit, ECP Follow-on Credit, ECP StandAlone Credit) 
     attr_accessor :name
 
     # Indicates the payment type used in this payment transaction. Example: credit card, check

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_point_of_sale_information.rb

@@ -14,10 +14,13 @@ require 'date'
 
 module CyberSource
   class TssV2TransactionsGet200ResponsePointOfSaleInformation
-    # Method of entering credit card information into the POS terminal. Possible values:   - `contact`: Read from direct contact with chip card.  - `contactless`: Read from a contactless interface using chip data.  - `keyed`: Manually keyed into POS terminal.  - `msd`: Read from a contactless interface using magnetic stripe data (MSD).  - `swiped`: Read from credit card magnetic stripe.  The contact, contactless, and msd values are supported only for EMV transactions.  For details, see the `pos_entry_mode` field description in [Card-Present Processing Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/Retail_SCMP_API/html/) 
+    # Identifier for the terminal at your retail location. You can define this value yourself, but consult the processor for requirements.  #### CyberSource through VisaNet A list of all possible values is stored in your CyberSource account. If terminal ID validation is enabled for your CyberSource account, the value you send for this field is validated against the list each time you include the field in a request. To enable or disable terminal ID validation, contact CyberSource Customer Support.  When you do not include this field in a request, CyberSource uses the default value that is defined in your CyberSource account.  #### FDC Nashville Global To have your account configured to support this field, contact CyberSource Customer Support. This value must be a value that FDC Nashville Global issued to you.  #### For Payouts This field is applicable for CyberSource through VisaNet.  #### GPX Identifier for the terminal at your retail location. A list of all possible values is stored in your account. If terminal ID validation is enabled for your account, the value you send for this field is validated against the list each time you include the field in a request. To enable or disable terminal ID validation, contact customer support.  When you do not include this field in a request, the default value that is defined in your account is used.  Optional for authorizations.  #### Used by **Authorization** Optional for the following processors. When you do not include this field in a request, the default value that is defined in your account is used.   - American Express Direct   - Credit Mutuel-CIC   - FDC Nashville Global   - SIX - Chase Paymentech Solutions: Optional field. If you include this field in your request, you must also include `pointOfSaleInformation.catLevel`. - FDMS Nashville: The default value that is defined in your account is used. - GPX - OmniPay Direct: Optional field.  For the following processors, this field is not used. - GPN - JCN Gateway - RBS WorldPay Atlanta - TSYS Acquiring Solutions - Worldpay VAP  #### Card Present reply Terminal identifier assigned by the acquirer. This value must be printed on the receipt. 
+    attr_accessor :terminal_id
+
+    # Method of entering payment card information into the POS terminal. Possible values:   - `contact`: Read from direct contact with chip card.  - `contactless`: Read from a contactless interface using chip data.  - `keyed`: Manually keyed into POS terminal. This value is not supported on OmniPay Direct.  - `msd`: Read from a contactless interface using magnetic stripe data (MSD). This value is not supported on OmniPay Direct.  - `swiped`: Read from credit card magnetic stripe.  The `contact`, `contactless`, and `msd` values are supported only for EMV transactions.  #### Used by **Authorization** Required field.  #### Card Present Card present information about EMV applies only to credit card processing and PIN debit processing. All other card present information applies only to credit card processing.  #### PIN debit Required for a PIN debit purchase and a PIN debit credit request. 
     attr_accessor :entry_mode
 
-    # POS terminal’s capability. Possible values:   - `1`: Terminal has a magnetic stripe reader only.  - `2`: Terminal has a magnetic stripe reader and manual entry capability.  - `3`: Terminal has manual entry capability only.  - `4`: Terminal can read chip cards.  - `5`: Terminal can read contactless chip cards.  The values of 4 and 5 are supported only for EMV transactions. * Applicable only for CTV for Payouts.  For processor-specific details, see the `terminal_capability` field description in [Card-Present Processing Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/Retail_SCMP_API/html/) 
+    # POS terminal’s capability. Possible values:   - `1`: Terminal has a magnetic stripe reader only.  - `2`: Terminal has a magnetic stripe reader and manual entry capability.  - `3`: Terminal has manual entry capability only.  - `4`: Terminal can read chip cards.  - `5`: Terminal can read contactless chip cards; cannot use contact to read chip cards.  For an EMV transaction, the value of this field must be `4` or `5`.  #### PIN debit Required for PIN debit purchase and PIN debit credit request.  #### Used by **Authorization** Required for the following processors: - American Express Direct - Chase Paymentech Solutions - Credit Mutuel-CIC - FDC Nashville Global - FDMS Nashville - OmniPay Direct - SIX - Worldpay VAP  Optional for the following processors: - CyberSource through VisaNet - GPN - GPX - JCN Gateway - RBS WorldPay Atlanta - TSYS Acquiring Solutions 
     attr_accessor :terminal_capability
 
     attr_accessor :emv
@@ -25,6 +28,7 @@ module CyberSource
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
+        :'terminal_id' => :'terminalId',
         :'entry_mode' => :'entryMode',
         :'terminal_capability' => :'terminalCapability',
         :'emv' => :'emv'
@@ -34,6 +38,7 @@ module CyberSource
     # Attribute type mapping.
     def self.swagger_types
       {
+        :'terminal_id' => :'String',
         :'entry_mode' => :'String',
         :'terminal_capability' => :'Integer',
         :'emv' => :'Ptsv2paymentsidreversalsPointOfSaleInformationEmv'
@@ -48,6 +53,10 @@ module CyberSource
       # convert string to symbol for hash key
       attributes = attributes.each_with_object({}) { |(k, v), h| h[k.to_sym] = v }
 
+      if attributes.has_key?(:'terminalId')
+        self.terminal_id = attributes[:'terminalId']
+      end
+
       if attributes.has_key?(:'entryMode')
         self.entry_mode = attributes[:'entryMode']
       end
@@ -65,10 +74,6 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if !@entry_mode.nil? && @entry_mode.to_s.length > 11
-        invalid_properties.push('invalid value for "entry_mode", the character length must be smaller than or equal to 11.')
-      end
-
       if !@terminal_capability.nil? && @terminal_capability > 5
         invalid_properties.push('invalid value for "terminal_capability", must be smaller than or equal to 5.')
       end
@@ -83,19 +88,20 @@ module CyberSource
     # Check to see if the all the properties in the model are valid
     # @return true if the model is valid
     def valid?
-      return false if !@entry_mode.nil? && @entry_mode.to_s.length > 11
       return false if !@terminal_capability.nil? && @terminal_capability > 5
       return false if !@terminal_capability.nil? && @terminal_capability < 1
       true
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] terminal_id Value to be assigned
+    def terminal_id=(terminal_id)
+      @terminal_id = terminal_id
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] entry_mode Value to be assigned
     def entry_mode=(entry_mode)
-      if !entry_mode.nil? && entry_mode.to_s.length > 11
-        fail ArgumentError, 'invalid value for "entry_mode", the character length must be smaller than or equal to 11.'
-      end
-
       @entry_mode = entry_mode
     end
 
@@ -118,6 +124,7 @@ module CyberSource
     def ==(o)
       return true if self.equal?(o)
       self.class == o.class &&
+          terminal_id == o.terminal_id &&
           entry_mode == o.entry_mode &&
           terminal_capability == o.terminal_capability &&
           emv == o.emv
@@ -132,7 +139,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [entry_mode, terminal_capability, emv].hash
+      [terminal_id, entry_mode, terminal_capability, emv].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processing_information.rb

@@ -14,10 +14,13 @@ require 'date'
 
 module CyberSource
   class TssV2TransactionsGet200ResponseProcessingInformation
-    # Type of digital payment solution for the transaction. Possible Values:   - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/)  - `001`: Apple Pay.  - `004`: Cybersource In-App Solution.  - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  - `006`: Android Pay.  - `007`: Chase Pay.  - `008`: Samsung Pay.  - `012`: Google Pay. 
+    # Indicates that the transaction includes industry-specific data.  Possible Values: - `airline` - `restaurant` - `lodging` - `auto_rental` - `transit` - `healthcare_medical` - `healthcare_transit` - `transit`  #### Card Present, Airlines and Auto Rental You must set this field to `airline` in order for airline data to be sent to the processor. For example, if this field is not set to `airline` or is not included in the request, no airline data is sent to the processor.  You must set this field to `restaurant` in order for restaurant data to be sent to the processor. When this field is not set to `restaurant` or is not included in the request, no restaurant data is sent to the processor.  You must set this field to `auto_rental` in order for auto rental data to be sent to the processor. For example, if this field is not set to `auto_rental` or is not included in the request, no auto rental data is sent to the processor.  Restaurant data is supported only on CyberSource through VisaNet. 
+    attr_accessor :industry_data_type
+
+    # Type of digital payment solution for the transaction.  
     attr_accessor :payment_solution
 
-    # Type of transaction. Certain card associations use this information when determining discount rates to charge you. Required for Verified by Visa and MasterCard SecureCode transactions.      This field can contain one of these values:      * 5: `vbv` (Successful Verified by Visa transaction)     * 6: `spa` (MasterCard SecureCode transaction)     * 7: `internet` (default) (eCommerce order placed by     using a Web site)     * 8: `vbv_attempted` (Verified by Visa transaction     was attempted but not authenticated)     * E: `vbv_failure` (Depending on your payment     processor, you may receive this result if Visa’s     directory service is not available)     * F: `spa_failure` (MasterCard SecureCode     authentication failed)     * M: `moto` (Mail order or telephone order)     * P: `retail` (Point-of-sale transaction)     * R: `recurring` (Recurring transaction)     * S: `install` (Installment payment) 
+    # Type of transaction. Some payment card companies use this information when determining discount rates.  #### Used by **Authorization** Required payer authentication transactions; otherwise, optional. **Credit** Required for standalone credits on Chase Paymentech solutions; otherwise, optional. Only `internet`, `moto`, `install`, `recurring`, and `recurring_internet` are valid values.  #### Ingenico ePayments When you omit this field for Ingenico ePayments, the processor uses the default transaction type they have on file for you instead of the default value (listed in Appendix I, \"Commerce Indicators,\" on page 441.)  #### Payer Authentication Transactions For the possible values and requirements, see \"Payer Authentication,\" page 195.  #### Other Types of Transactions See Appendix I, \"Commerce Indicators,\" on page 441.  #### Card Present You must set this field to `retail`. This field is required for a card-present transaction. Note that this should ONLY be used when the cardholder and card are present at the time of the transaction. For all keyed transactions originated from a POS terminal where the cardholder and card are not present, commerceIndicator should be submitted as “moto\" 
     attr_accessor :commerce_indicator
 
     # Payouts transaction type. Required for OCT transactions. This field is a pass-through, which means that CyberSource does not verify the value or modify it in any way before sending it to the processor. **Note** When the request includes this field, this value overrides the information in your CyberSource account.  For valid values, see the `invoiceHeader_businessApplicationID` field description in [Payouts Using the Simple Order API.](http://apps.cybersource.com/library/documentation/dev_guides/payouts_SO/Payouts_SO_API.pdf) 
@@ -32,6 +35,7 @@ module CyberSource
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
+        :'industry_data_type' => :'industryDataType',
         :'payment_solution' => :'paymentSolution',
         :'commerce_indicator' => :'commerceIndicator',
         :'business_application_id' => :'businessApplicationId',
@@ -44,6 +48,7 @@ module CyberSource
     # Attribute type mapping.
     def self.swagger_types
       {
+        :'industry_data_type' => :'String',
         :'payment_solution' => :'String',
         :'commerce_indicator' => :'String',
         :'business_application_id' => :'String',
@@ -61,6 +66,10 @@ module CyberSource
       # convert string to symbol for hash key
       attributes = attributes.each_with_object({}) { |(k, v), h| h[k.to_sym] = v }
 
+      if attributes.has_key?(:'industryDataType')
+        self.industry_data_type = attributes[:'industryDataType']
+      end
+
       if attributes.has_key?(:'paymentSolution')
         self.payment_solution = attributes[:'paymentSolution']
       end
@@ -90,42 +99,30 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if !@payment_solution.nil? && @payment_solution.to_s.length > 12
-        invalid_properties.push('invalid value for "payment_solution", the character length must be smaller than or equal to 12.')
-      end
-
-      if !@commerce_indicator.nil? && @commerce_indicator.to_s.length > 20
-        invalid_properties.push('invalid value for "commerce_indicator", the character length must be smaller than or equal to 20.')
-      end
-
       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?
-      return false if !@payment_solution.nil? && @payment_solution.to_s.length > 12
-      return false if !@commerce_indicator.nil? && @commerce_indicator.to_s.length > 20
       true
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] industry_data_type Value to be assigned
+    def industry_data_type=(industry_data_type)
+      @industry_data_type = industry_data_type
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] payment_solution Value to be assigned
     def payment_solution=(payment_solution)
-      if !payment_solution.nil? && payment_solution.to_s.length > 12
-        fail ArgumentError, 'invalid value for "payment_solution", the character length must be smaller than or equal to 12.'
-      end
-
       @payment_solution = payment_solution
     end
 
     # Custom attribute writer method with validation
     # @param [Object] commerce_indicator Value to be assigned
     def commerce_indicator=(commerce_indicator)
-      if !commerce_indicator.nil? && commerce_indicator.to_s.length > 20
-        fail ArgumentError, 'invalid value for "commerce_indicator", the character length must be smaller than or equal to 20.'
-      end
-
       @commerce_indicator = commerce_indicator
     end
 
@@ -134,6 +131,7 @@ module CyberSource
     def ==(o)
       return true if self.equal?(o)
       self.class == o.class &&
+          industry_data_type == o.industry_data_type &&
           payment_solution == o.payment_solution &&
           commerce_indicator == o.commerce_indicator &&
           business_application_id == o.business_application_id &&
@@ -151,7 +149,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [payment_solution, commerce_indicator, business_application_id, authorization_options, bank_transfer_options, japan_payment_options].hash
+      [industry_data_type, payment_solution, commerce_indicator, business_application_id, authorization_options, bank_transfer_options, japan_payment_options].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processing_information_authorization_options.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class TssV2TransactionsGet200ResponseProcessingInformationAuthorizationOptions
-    # Authorization type. Possible values:   - `AUTOCAPTURE`: automatic capture.  - `STANDARDCAPTURE`: standard capture.  - `VERBAL`: forced capture. Include it in the payment request for a forced capture. Include it in the capture request for a verbal payment.  #### Asia, Middle East, and Africa Gateway; Cielo; Comercio Latino; and CyberSource Latin American Processing Set this field to `AUTOCAPTURE` and include it in a bundled request to indicate that you are requesting an automatic capture. If your account is configured to enable automatic captures, set this field to `STANDARDCAPTURE` and include it in a standard authorization or bundled request to indicate that you are overriding an automatic capture. For more information, see the `auth_type` field description in [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  #### Forced Capture Set this field to `VERBAL` and include it in the authorization request to indicate that you are performing a forced capture; therefore, you receive the authorization code outside the CyberSource system.  For more information, see \"Forced Captures\" in [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/).  #### Verbal Authorization Set this field to `VERBAL` and include it in the capture request to indicate that the request is for a verbal authorization. For more information, see \"Verbal Authorizations\" in [Credit Card Services Using the SCMP API](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html).  For processor-specific information, see the `auth_type` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
+    # Authorization type. Possible values:   - `AUTOCAPTURE`: automatic capture.  - `STANDARDCAPTURE`: standard capture.  - `VERBAL`: forced capture. Include it in the payment request for a forced capture. Include it in the capture request for a verbal payment.  #### Asia, Middle East, and Africa Gateway; Cielo; Comercio Latino; and CyberSource Latin American Processing Set this field to `AUTOCAPTURE` and include it in a bundled request to indicate that you are requesting an automatic capture. If your account is configured to enable automatic captures, set this field to `STANDARDCAPTURE` and include it in a standard authorization or bundled request to indicate that you are overriding an automatic capture. For more information, see the `auth_type` field description in [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  #### Forced Capture Set this field to `VERBAL` and include it in the authorization request to indicate that you are performing a forced capture; therefore, you receive the authorization code outside the CyberSource system.  #### Verbal Authorization Set this field to `VERBAL` and include it in the capture request to indicate that the request is for a verbal authorization. For more information, see \"Verbal Authorizations\" in [Credit Card Services Using the SCMP API](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html). 
     attr_accessor :auth_type
 
     # Attribute mapping from ruby-style variable name to JSON key.
@@ -48,27 +48,18 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if !@auth_type.nil? && @auth_type.to_s.length > 15
-        invalid_properties.push('invalid value for "auth_type", the character length must be smaller than or equal to 15.')
-      end
-
       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?
-      return false if !@auth_type.nil? && @auth_type.to_s.length > 15
       true
     end
 
     # Custom attribute writer method with validation
     # @param [Object] auth_type Value to be assigned
     def auth_type=(auth_type)
-      if !auth_type.nil? && auth_type.to_s.length > 15
-        fail ArgumentError, 'invalid value for "auth_type", the character length must be smaller than or equal to 15.'
-      end
-
       @auth_type = auth_type
     end
 

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processing_information_bank_transfer_options.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class TssV2TransactionsGet200ResponseProcessingInformationBankTransferOptions
-    # Specifies the authorization method for the transaction.  Possible values: - `ARC`: account receivable conversion - `CCD`: corporate cash disbursement - `POP`: point of purchase conversion - `PPD`: prearranged payment and deposit entry - `TEL`: telephone-initiated entry - `WEB`: internet-initiated entry  For details, see `ecp_sec_code` field description in the [Electronic Check Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/EChecks_SCMP_API/html/) 
+    # Specifies the authorization method for the transaction.  Possible values: - `ARC`: account receivable conversion - `CCD`: corporate cash disbursement - `POP`: point of purchase conversion - `PPD`: prearranged payment and deposit entry - `TEL`: telephone-initiated entry - `WEB`: internet-initiated entry 
     attr_accessor :sec_code
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processing_information_japan_payment_options.rb

@@ -17,7 +17,7 @@ module CyberSource
     # This value is a 2-digit code indicating the payment method. Use Payment Method Code value that applies to the tranasction. - 10 (One-time payment) - 21, 22, 23, 24  (Bonus(one-time)payment) - 61 (Installment payment) - 31, 32, 33, 34  (Integrated (Bonus + Installment)payment) - 80 (Revolving payment) 
     attr_accessor :payment_method
 
-    # This value is the 13-digit JCCA number.
+    # Unique Japan Credit Card Association (JCCA) terminal identifier.  The difference between this field and the `pointOfSaleInformation.terminalID` field is that you can define `pointOfSaleInformation.terminalID`, but `processingInformation.japanPaymentOptions.terminalId` is defined by the JCCA and is used only in Japan.  This field is supported only on CyberSource through VisaNet and JCN Gateway.  Optional field. 
     attr_accessor :terminal_id
 
     # Business name in Japanese characters. This field is supported only on JCN Gateway and for the Sumitomo Mitsui Card Co. acquirer on CyberSource through VisaNet. 
@@ -75,72 +75,36 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if !@payment_method.nil? && @payment_method.to_s.length > 2
-        invalid_properties.push('invalid value for "payment_method", the character length must be smaller than or equal to 2.')
-      end
-
-      if !@terminal_id.nil? && @terminal_id.to_s.length > 13
-        invalid_properties.push('invalid value for "terminal_id", the character length must be smaller than or equal to 13.')
-      end
-
-      if !@business_name.nil? && @business_name.to_s.length > 25
-        invalid_properties.push('invalid value for "business_name", the character length must be smaller than or equal to 25.')
-      end
-
-      if !@business_name_katakana.nil? && @business_name_katakana.to_s.length > 25
-        invalid_properties.push('invalid value for "business_name_katakana", the character length must be smaller than or equal to 25.')
-      end
-
       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?
-      return false if !@payment_method.nil? && @payment_method.to_s.length > 2
-      return false if !@terminal_id.nil? && @terminal_id.to_s.length > 13
-      return false if !@business_name.nil? && @business_name.to_s.length > 25
-      return false if !@business_name_katakana.nil? && @business_name_katakana.to_s.length > 25
       true
     end
 
     # Custom attribute writer method with validation
     # @param [Object] payment_method Value to be assigned
     def payment_method=(payment_method)
-      if !payment_method.nil? && payment_method.to_s.length > 2
-        fail ArgumentError, 'invalid value for "payment_method", the character length must be smaller than or equal to 2.'
-      end
-
       @payment_method = payment_method
     end
 
     # Custom attribute writer method with validation
     # @param [Object] terminal_id Value to be assigned
     def terminal_id=(terminal_id)
-      if !terminal_id.nil? && terminal_id.to_s.length > 13
-        fail ArgumentError, 'invalid value for "terminal_id", the character length must be smaller than or equal to 13.'
-      end
-
       @terminal_id = terminal_id
     end
 
     # Custom attribute writer method with validation
     # @param [Object] business_name Value to be assigned
     def business_name=(business_name)
-      if !business_name.nil? && business_name.to_s.length > 25
-        fail ArgumentError, 'invalid value for "business_name", the character length must be smaller than or equal to 25.'
-      end
-
       @business_name = business_name
     end
 
     # Custom attribute writer method with validation
     # @param [Object] business_name_katakana Value to be assigned
     def business_name_katakana=(business_name_katakana)
-      if !business_name_katakana.nil? && business_name_katakana.to_s.length > 25
-        fail ArgumentError, 'invalid value for "business_name_katakana", the character length must be smaller than or equal to 25.'
-      end
-
       @business_name_katakana = business_name_katakana
     end