cybersource_rest_client 0.0.26 → 0.0.31

data/lib/cybersource_rest_client/models/riskv1authentications_payment_information_tokenized_card.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Riskv1authenticationsPaymentInformationTokenizedCard
-    # 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 
+    # 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  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International 
     attr_accessor :type
 
     # One of two possible meanings: - The two-digit month in which a token expires. - The two-digit month in which a card expires. Format: `MM` Possible values: `01` through `12`  **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below.  #### 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 (`card_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.  #### Samsung Pay and Apple Pay Month in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction.  For processor-specific information, see the `customer_cc_expmo` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
@@ -83,26 +83,14 @@ module CyberSource
         invalid_properties.push('invalid value for "expiration_month", expiration_month cannot be nil.')
       end
 
-      if @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?
         invalid_properties.push('invalid value for "expiration_year", expiration_year cannot be nil.')
       end
 
-      if @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 @number.nil?
         invalid_properties.push('invalid value for "number", number cannot be nil.')
       end
 
-      if @number.to_s.length > 20
-        invalid_properties.push('invalid value for "number", the character length must be smaller than or equal to 20.')
-      end
-
       invalid_properties
     end
 
@@ -111,11 +99,8 @@ module CyberSource
     def valid?
       return false if @type.nil?
       return false if @expiration_month.nil?
-      return false if @expiration_month.to_s.length > 2
       return false if @expiration_year.nil?
-      return false if @expiration_year.to_s.length > 4
       return false if @number.nil?
-      return false if @number.to_s.length > 20
       true
     end
 
@@ -126,10 +111,6 @@ module CyberSource
         fail ArgumentError, 'expiration_month cannot be nil'
       end
 
-      if 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
 
@@ -140,10 +121,6 @@ module CyberSource
         fail ArgumentError, 'expiration_year cannot be nil'
       end
 
-      if 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
 
@@ -154,10 +131,6 @@ module CyberSource
         fail ArgumentError, 'number cannot be nil'
       end
 
-      if number.to_s.length > 20
-        fail ArgumentError, 'invalid value for "number", the character length must be smaller than or equal to 20.'
-      end
-
       @number = number
     end
 

data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_card.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Riskv1authenticationsetupsPaymentInformationCard
-    # 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 
+    # 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  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International 
     attr_accessor :type
 
     # 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. 
@@ -79,26 +79,14 @@ module CyberSource
         invalid_properties.push('invalid value for "expiration_month", expiration_month cannot be nil.')
       end
 
-      if @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?
         invalid_properties.push('invalid value for "expiration_year", expiration_year cannot be nil.')
       end
 
-      if @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 @number.nil?
         invalid_properties.push('invalid value for "number", number cannot be nil.')
       end
 
-      if @number.to_s.length > 20
-        invalid_properties.push('invalid value for "number", the character length must be smaller than or equal to 20.')
-      end
-
       invalid_properties
     end
 
@@ -106,11 +94,8 @@ module CyberSource
     # @return true if the model is valid
     def valid?
       return false if @expiration_month.nil?
-      return false if @expiration_month.to_s.length > 2
       return false if @expiration_year.nil?
-      return false if @expiration_year.to_s.length > 4
       return false if @number.nil?
-      return false if @number.to_s.length > 20
       true
     end
 
@@ -121,10 +106,6 @@ module CyberSource
         fail ArgumentError, 'expiration_month cannot be nil'
       end
 
-      if 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
 
@@ -135,10 +116,6 @@ module CyberSource
         fail ArgumentError, 'expiration_year cannot be nil'
       end
 
-      if 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
 
@@ -149,10 +126,6 @@ module CyberSource
         fail ArgumentError, 'number cannot be nil'
       end
 
-      if number.to_s.length > 20
-        fail ArgumentError, 'invalid value for "number", the character length must be smaller than or equal to 20.'
-      end
-
       @number = number
     end
 

data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_customer.rb

@@ -48,27 +48,18 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if !@customer_id.nil? && @customer_id.to_s.length < 16
-        invalid_properties.push('invalid value for "customer_id", the character length must be great than or equal to 16.')
-      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 !@customer_id.nil? && @customer_id.to_s.length < 16
       true
     end
 
     # Custom attribute writer method with validation
     # @param [Object] customer_id Value to be assigned
     def customer_id=(customer_id)
-      if !customer_id.nil? && customer_id.to_s.length < 16
-        fail ArgumentError, 'invalid value for "customer_id", the character length must be great than or equal to 16.'
-      end
-
       @customer_id = customer_id
     end
 

data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_fluid_data.rb

@@ -79,18 +79,6 @@ module CyberSource
         invalid_properties.push('invalid value for "value", value cannot be nil.')
       end
 
-      if @value.to_s.length > 3072
-        invalid_properties.push('invalid value for "value", the character length must be smaller than or equal to 3072.')
-      end
-
-      if !@descriptor.nil? && @descriptor.to_s.length > 128
-        invalid_properties.push('invalid value for "descriptor", the character length must be smaller than or equal to 128.')
-      end
-
-      if !@encoding.nil? && @encoding.to_s.length > 6
-        invalid_properties.push('invalid value for "encoding", the character length must be smaller than or equal to 6.')
-      end
-
       invalid_properties
     end
 
@@ -98,9 +86,6 @@ module CyberSource
     # @return true if the model is valid
     def valid?
       return false if @value.nil?
-      return false if @value.to_s.length > 3072
-      return false if !@descriptor.nil? && @descriptor.to_s.length > 128
-      return false if !@encoding.nil? && @encoding.to_s.length > 6
       true
     end
 
@@ -111,30 +96,18 @@ module CyberSource
         fail ArgumentError, 'value cannot be nil'
       end
 
-      if value.to_s.length > 3072
-        fail ArgumentError, 'invalid value for "value", the character length must be smaller than or equal to 3072.'
-      end
-
       @value = value
     end
 
     # Custom attribute writer method with validation
     # @param [Object] descriptor Value to be assigned
     def descriptor=(descriptor)
-      if !descriptor.nil? && descriptor.to_s.length > 128
-        fail ArgumentError, 'invalid value for "descriptor", the character length must be smaller than or equal to 128.'
-      end
-
       @descriptor = descriptor
     end
 
     # Custom attribute writer method with validation
     # @param [Object] encoding Value to be assigned
     def encoding=(encoding)
-      if !encoding.nil? && encoding.to_s.length > 6
-        fail ArgumentError, 'invalid value for "encoding", the character length must be smaller than or equal to 6.'
-      end
-
       @encoding = encoding
     end
 

data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_tokenized_card.rb

@@ -17,7 +17,7 @@ module CyberSource
     # 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. 
     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] - `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 
+    # 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  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International 
     attr_accessor :type
 
     # One of two possible meanings: - The two-digit month in which a token expires. - The two-digit month in which a card expires. Format: `MM` Possible values: `01` through `12`  **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below.  #### 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 (`card_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.  #### Samsung Pay and Apple Pay Month in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction.  For processor-specific information, see the `customer_cc_expmo` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
@@ -88,10 +88,6 @@ module CyberSource
         invalid_properties.push('invalid value for "transaction_type", transaction_type cannot be nil.')
       end
 
-      if @transaction_type.to_s.length > 1
-        invalid_properties.push('invalid value for "transaction_type", the character length must be smaller than or equal to 1.')
-      end
-
       if @type.nil?
         invalid_properties.push('invalid value for "type", type cannot be nil.')
       end
@@ -100,26 +96,14 @@ module CyberSource
         invalid_properties.push('invalid value for "expiration_month", expiration_month cannot be nil.')
       end
 
-      if @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?
         invalid_properties.push('invalid value for "expiration_year", expiration_year cannot be nil.')
       end
 
-      if @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 @number.nil?
         invalid_properties.push('invalid value for "number", number cannot be nil.')
       end
 
-      if @number.to_s.length > 20
-        invalid_properties.push('invalid value for "number", the character length must be smaller than or equal to 20.')
-      end
-
       invalid_properties
     end
 
@@ -127,14 +111,10 @@ module CyberSource
     # @return true if the model is valid
     def valid?
       return false if @transaction_type.nil?
-      return false if @transaction_type.to_s.length > 1
       return false if @type.nil?
       return false if @expiration_month.nil?
-      return false if @expiration_month.to_s.length > 2
       return false if @expiration_year.nil?
-      return false if @expiration_year.to_s.length > 4
       return false if @number.nil?
-      return false if @number.to_s.length > 20
       true
     end
 
@@ -145,10 +125,6 @@ module CyberSource
         fail ArgumentError, 'transaction_type cannot be nil'
       end
 
-      if transaction_type.to_s.length > 1
-        fail ArgumentError, 'invalid value for "transaction_type", the character length must be smaller than or equal to 1.'
-      end
-
       @transaction_type = transaction_type
     end
 
@@ -159,10 +135,6 @@ module CyberSource
         fail ArgumentError, 'expiration_month cannot be nil'
       end
 
-      if 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
 
@@ -173,10 +145,6 @@ module CyberSource
         fail ArgumentError, 'expiration_year cannot be nil'
       end
 
-      if 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
 
@@ -187,10 +155,6 @@ module CyberSource
         fail ArgumentError, 'number cannot be nil'
       end
 
-      if number.to_s.length > 20
-        fail ArgumentError, 'invalid value for "number", the character length must be smaller than or equal to 20.'
-      end
-
       @number = number
     end
 

data/lib/cybersource_rest_client/models/riskv1authenticationsetups_processing_information.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Riskv1authenticationsetupsProcessingInformation
-    # 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. 
+    # 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.  - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.  - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. 
     attr_accessor :payment_solution
 
     # Identifier for the **Visa Checkout** order. Visa Checkout provides a unique order ID for every transaction in the Visa Checkout **callID** field. 
@@ -57,42 +57,24 @@ 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 !@visa_checkout_id.nil? && @visa_checkout_id.to_s.length > 48
-        invalid_properties.push('invalid value for "visa_checkout_id", the character length must be smaller than or equal to 48.')
-      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 !@visa_checkout_id.nil? && @visa_checkout_id.to_s.length > 48
       true
     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] visa_checkout_id Value to be assigned
     def visa_checkout_id=(visa_checkout_id)
-      if !visa_checkout_id.nil? && visa_checkout_id.to_s.length > 48
-        fail ArgumentError, 'invalid value for "visa_checkout_id", the character length must be smaller than or equal to 48.'
-      end
-
       @visa_checkout_id = visa_checkout_id
     end
 

data/lib/cybersource_rest_client/models/riskv1decisions_buyer_information.rb

@@ -86,72 +86,36 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if !@merchant_customer_id.nil? && @merchant_customer_id.to_s.length > 100
-        invalid_properties.push('invalid value for "merchant_customer_id", the character length must be smaller than or equal to 100.')
-      end
-
-      if !@username.nil? && @username.to_s.length > 255
-        invalid_properties.push('invalid value for "username", the character length must be smaller than or equal to 255.')
-      end
-
-      if !@hashed_password.nil? && @hashed_password.to_s.length > 100
-        invalid_properties.push('invalid value for "hashed_password", the character length must be smaller than or equal to 100.')
-      end
-
-      if !@date_of_birth.nil? && @date_of_birth.to_s.length > 8
-        invalid_properties.push('invalid value for "date_of_birth", the character length must be smaller than or equal to 8.')
-      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 !@merchant_customer_id.nil? && @merchant_customer_id.to_s.length > 100
-      return false if !@username.nil? && @username.to_s.length > 255
-      return false if !@hashed_password.nil? && @hashed_password.to_s.length > 100
-      return false if !@date_of_birth.nil? && @date_of_birth.to_s.length > 8
       true
     end
 
     # Custom attribute writer method with validation
     # @param [Object] merchant_customer_id Value to be assigned
     def merchant_customer_id=(merchant_customer_id)
-      if !merchant_customer_id.nil? && merchant_customer_id.to_s.length > 100
-        fail ArgumentError, 'invalid value for "merchant_customer_id", the character length must be smaller than or equal to 100.'
-      end
-
       @merchant_customer_id = merchant_customer_id
     end
 
     # Custom attribute writer method with validation
     # @param [Object] username Value to be assigned
     def username=(username)
-      if !username.nil? && username.to_s.length > 255
-        fail ArgumentError, 'invalid value for "username", the character length must be smaller than or equal to 255.'
-      end
-
       @username = username
     end
 
     # Custom attribute writer method with validation
     # @param [Object] hashed_password Value to be assigned
     def hashed_password=(hashed_password)
-      if !hashed_password.nil? && hashed_password.to_s.length > 100
-        fail ArgumentError, 'invalid value for "hashed_password", the character length must be smaller than or equal to 100.'
-      end
-
       @hashed_password = hashed_password
     end
 
     # Custom attribute writer method with validation
     # @param [Object] date_of_birth Value to be assigned
     def date_of_birth=(date_of_birth)
-      if !date_of_birth.nil? && date_of_birth.to_s.length > 8
-        fail ArgumentError, 'invalid value for "date_of_birth", the character length must be smaller than or equal to 8.'
-      end
-
       @date_of_birth = date_of_birth
     end