cybersource_rest_client 0.0.49 → 0.0.51

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_bank_account.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultPaymentInstrumentBankAccount
-    # Account type.  Valid values:  - checking : C  - general ledger : G This value is supported only on Wells Fargo ACH  - savings : S (U.S. dollars only)  - corporate checking : X (U.S. dollars only) 
+    # Account type.  Possible Values:  - checking : C  - general ledger : G This value is supported only on Wells Fargo ACH  - savings : S (U.S. dollars only)  - corporate checking : X (U.S. dollars only) 
     attr_accessor :type
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_buyer_information_personal_identification.rb

@@ -17,7 +17,7 @@ module CyberSource
     # The value of the identification type. 
     attr_accessor :id
 
-    # The type of the identification.  Valid values:   - driver license 
+    # The type of the identification.  Possible Values:   - driver license 
     attr_accessor :type
 
     attr_accessor :issued_by

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_card.rb

@@ -14,19 +14,19 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultPaymentInstrumentCard
-    # Two-digit month in which the payment card expires.  Format: `MM`.  Valid values: `01` through `12`. 
+    # Two-digit month in which the payment card expires.  Format: `MM`.  Possible Values: `01` through `12`. 
     attr_accessor :expiration_month
 
     # Four-digit year in which the credit card expires.  Format: `YYYY`. 
     attr_accessor :expiration_year
 
-    # Value that indicates the card type. Valid v2 : v1 - description values:   * 001 : visa   * 002 : mastercard - Eurocard—European regional brand of Mastercard   * 003 : american express   * 004 : discover   * 005 : diners club   * 006 : carte blanche   * 007 : jcb   * 008 : optima   * 011 : twinpay credit   * 012 : twinpay debit   * 013 : walmart   * 014 : enRoute   * 015 : lowes consumer   * 016 : home depot consumer   * 017 : mbna   * 018 : dicks sportswear   * 019 : casual corner   * 020 : sears   * 021 : jal   * 023 : disney   * 024 : maestro uk domestic   * 025 : sams club consumer   * 026 : sams club business   * 028 : bill me later   * 029 : bebe   * 030 : restoration hardware   * 031 : delta online — use this value only for Ingenico ePayments. For other processors, use 001 for all Visa card types.   * 032 : solo   * 033 : visa electron   * 034 : dankort   * 035 : laser   * 036 : carte bleue — formerly Cartes Bancaires   * 037 : carta si   * 038 : pinless debit   * 039 : encoded account   * 040 : uatp   * 041 : household   * 042 : maestro international   * 043 : ge money uk   * 044 : korean cards   * 045 : style   * 046 : jcrew   * 047 : payease china processing ewallet   * 048 : payease china processing bank transfer   * 049 : meijer private label   * 050 : hipercard — supported only by the Comercio Latino processor.   * 051 : aura — supported only by the Comercio Latino processor.   * 052 : redecard   * 054 : elo — supported only by the Comercio Latino processor.   * 055 : capital one private label   * 056 : synchrony private label   * 057 : costco private label   * 060 : mada   * 062 : china union pay   * 063 : falabella private label 
+    # Value that indicates the card type. Possible Values v2 : v1:   * 001 : visa   * 002 : mastercard - Eurocard—European regional brand of Mastercard   * 003 : american express   * 004 : discover   * 005 : diners club   * 006 : carte blanche   * 007 : jcb   * 008 : optima   * 011 : twinpay credit   * 012 : twinpay debit   * 013 : walmart   * 014 : enRoute   * 015 : lowes consumer   * 016 : home depot consumer   * 017 : mbna   * 018 : dicks sportswear   * 019 : casual corner   * 020 : sears   * 021 : jal   * 023 : disney   * 024 : maestro uk domestic   * 025 : sams club consumer   * 026 : sams club business   * 028 : bill me later   * 029 : bebe   * 030 : restoration hardware   * 031 : delta online — use this value only for Ingenico ePayments. For other processors, use 001 for all Visa card types.   * 032 : solo   * 033 : visa electron   * 034 : dankort   * 035 : laser   * 036 : carte bleue — formerly Cartes Bancaires   * 037 : carta si   * 038 : pinless debit   * 039 : encoded account   * 040 : uatp   * 041 : household   * 042 : maestro international   * 043 : ge money uk   * 044 : korean cards   * 045 : style   * 046 : jcrew   * 047 : payease china processing ewallet   * 048 : payease china processing bank transfer   * 049 : meijer private label   * 050 : hipercard — supported only by the Comercio Latino processor.   * 051 : aura — supported only by the Comercio Latino processor.   * 052 : redecard   * 054 : elo — supported only by the Comercio Latino processor.   * 055 : capital one private label   * 056 : synchrony private label   * 057 : costco private label   * 060 : mada   * 062 : china union pay   * 063 : falabella private label 
     attr_accessor :type
 
     # 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
 
-    # 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`. Valid values: 01 through 12.  **Note** The start date is not required for Maestro (UK Domestic) transactions. 
+    # 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. 
     attr_accessor :start_month
 
     # Year 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: YYYY`.  **Note** The start date is not required for Maestro (UK Domestic) transactions. 
@@ -35,6 +35,11 @@ module CyberSource
     # 'Payment Instrument was created / updated as part of a pinless debit transaction.' 
     attr_accessor :use_as
 
+    # Hash value representing the card. 
+    attr_accessor :hash
+    alias :hash_value :hash
+    alias :hash_value= :hash=
+
     attr_accessor :tokenized_information
 
     # Attribute mapping from ruby-style variable name to JSON key.
@@ -47,6 +52,7 @@ module CyberSource
         :'start_month' => :'startMonth',
         :'start_year' => :'startYear',
         :'use_as' => :'useAs',
+        :'hash_value' => :'hashValue',
         :'tokenized_information' => :'tokenizedInformation'
       }
     end
@@ -61,6 +67,7 @@ module CyberSource
         :'start_month' => :'String',
         :'start_year' => :'String',
         :'use_as' => :'String',
+        :'hash_value' => :'String',
         :'tokenized_information' => :'Tmsv2customersEmbeddedDefaultPaymentInstrumentCardTokenizedInformation'
       }
     end
@@ -101,6 +108,10 @@ module CyberSource
         self.use_as = attributes[:'useAs']
       end
 
+      if attributes.has_key?(:'hashValue')
+        self.hash_value = attributes[:'hashValue']
+      end
+
       if attributes.has_key?(:'tokenizedInformation')
         self.tokenized_information = attributes[:'tokenizedInformation']
       end
@@ -149,6 +160,12 @@ module CyberSource
       @start_year = start_year
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] hash Value to be assigned
+    def hash_value=(hash_value)
+      @hash_value = hash_value
+    end
+
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)
@@ -161,6 +178,7 @@ module CyberSource
           start_month == o.start_month &&
           start_year == o.start_year &&
           use_as == o.use_as &&
+          hash_value == o.hash_value &&
           tokenized_information == o.tokenized_information
     end
 
@@ -173,7 +191,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [expiration_month, expiration_year, type, issue_number, start_month, start_year, use_as, tokenized_information].hash
+      [expiration_month, expiration_year, type, issue_number, start_month, start_year, use_as, hash_value, tokenized_information].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_card_tokenized_information.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultPaymentInstrumentCardTokenizedInformation
-    # Value that identifies your business and indicates that the cardholder’s account number is tokenized. This value is assigned by the token service provider and is unique within the token service provider’s database.  **Note** This field is supported only for **CyberSource through VisaNet** and **FDC Nashville Global**. 
+    # Value that identifies your business and indicates that the cardholder’s account number is tokenized. This value is assigned by the token service provider and is unique within the token service provider’s database.  **Note** This field is supported only through **VisaNet** and **FDC Nashville Global**. 
     attr_accessor :requestor_id
 
     # 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.  Set the value for this field to 1. An application on the customer’s mobile device provided the token data. 

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_instrument_identifier.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultPaymentInstrumentInstrumentIdentifier
-    # The id of the Instrument Identifier token linked to the Payment Instrument. 
+    # The Id of the Instrument Identifier linked to the Payment Instrument. 
     attr_accessor :id
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_merchant_information_merchant_descriptor.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultPaymentInstrumentMerchantInformationMerchantDescriptor
-    # Alternate contact information for your business,such as an email address or URL. This value might be displayed on the cardholder’s statement. When you do not include this value in your capture or credit request, CyberSource uses the merchant URL from your CyberSource account. Important This value must consist of English characters 
+    # Alternate contact information for your business,such as an email address or URL. This value might be displayed on the cardholder’s statement. When you do not include this value in your capture or credit request, the merchant URL from your CyberSource account is used. Important This value must consist of English characters 
     attr_accessor :alternate_name
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_metadata.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultPaymentInstrumentMetadata
-    # The creator of the Payment Instrument token. 
+    # The creator of the Payment Instrument. 
     attr_accessor :creator
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_processing_information.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultPaymentInstrumentProcessingInformation
-    # Flag that indicates that this is a payment for a bill or for an existing contractual loan. For processor-specific details, see the `bill_payment` field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  Valid values: - `true`: Bill payment or loan payment. - `false` (default): Not a bill payment or loan payment. 
+    # Flag that indicates that this is a payment for a bill or for an existing contractual loan. For processor-specific details, see the `bill_payment` field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  Possible Values: - `true`: Bill payment or loan payment. - `false` (default): Not a bill payment or loan payment. 
     attr_accessor :bill_payment_program_enabled
 
     attr_accessor :bank_transfer_options

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_processing_information_bank_transfer_options.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultPaymentInstrumentProcessingInformationBankTransferOptions
-    # Specifies the authorization method for the transaction.  #### TeleCheck Valid 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.  #### TeleCheck 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/) 
     attr_accessor :sec_code
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_shipping_address.rb

@@ -16,10 +16,10 @@ module CyberSource
   class Tmsv2customersEmbeddedDefaultShippingAddress
     attr_accessor :_links
 
-    # The id of the Shipping Address Token.
+    # The Id of the Shipping Address Token.
     attr_accessor :id
 
-    # Flag that indicates whether customer shipping address is the dafault. Valid values:  - `true`: Shipping Address is customer's default.  - `false`: Shipping Address is not customer's default. 
+    # Flag that indicates whether customer shipping address is the dafault. Possible Values:  - `true`: Shipping Address is customer's default.  - `false`: Shipping Address is not customer's default. 
     attr_accessor :default
 
     attr_accessor :ship_to

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_shipping_address_metadata.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultShippingAddressMetadata
-    # The creator of the Shipping Address token.
+    # The creator of the Shipping Address.
     attr_accessor :creator
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_shipping_address_ship_to.rb

@@ -35,7 +35,7 @@ module CyberSource
     # State or province of the shipping address. Use 2 character the State, Province, and Territory Codes for the United States and Canada. 
     attr_accessor :administrative_area
 
-    # Postal code for the shipping address. The postal code must consist of 5 to 9 digits.  When the billing country is the U.S., the 9-digit postal code must follow this format: [5 digits][dash][4 digits]  Example 12345-6789  When the billing country is Canada, the 6-digit postal code must follow this format: [alpha][numeric][alpha][space][numeric][alpha][numeric]  Example A1B 2C3  **American Express Direct**\\ Before sending the postal code to the processor, CyberSource removes all nonalphanumeric characters and, if the remaining value is longer than nine characters, truncates the value starting from the right side. 
+    # Postal code for the shipping address. The postal code must consist of 5 to 9 digits.  When the billing country is the U.S., the 9-digit postal code must follow this format: [5 digits][dash][4 digits]  Example 12345-6789  When the billing country is Canada, the 6-digit postal code must follow this format: [alpha][numeric][alpha][space][numeric][alpha][numeric]  Example A1B 2C3  **American Express Direct**\\ Before sending the postal code to the processor, all nonalphanumeric characters are removed and, if the remaining value is longer than nine characters, truncates the value starting from the right side. 
     attr_accessor :postal_code
 
     # Country of the shipping address. Use the two-character ISO Standard Country Codes. 

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_merchant_initiated_transaction.rb

@@ -17,17 +17,22 @@ module CyberSource
     # Network transaction identifier that was returned in the payment response field _processorInformation.transactionID_ in the reply message for either the original merchant-initiated payment in the series or the previous merchant-initiated payment in the series. 
     attr_accessor :previous_transaction_id
 
+    # Amount of the original authorization. 
+    attr_accessor :original_authorized_amount
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
-        :'previous_transaction_id' => :'previousTransactionId'
+        :'previous_transaction_id' => :'previousTransactionId',
+        :'original_authorized_amount' => :'originalAuthorizedAmount'
       }
     end
 
     # Attribute type mapping.
     def self.swagger_types
       {
-        :'previous_transaction_id' => :'String'
+        :'previous_transaction_id' => :'String',
+        :'original_authorized_amount' => :'String'
       }
     end
 
@@ -42,6 +47,10 @@ module CyberSource
       if attributes.has_key?(:'previousTransactionId')
         self.previous_transaction_id = attributes[:'previousTransactionId']
       end
+
+      if attributes.has_key?(:'originalAuthorizedAmount')
+        self.original_authorized_amount = attributes[:'originalAuthorizedAmount']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -63,12 +72,19 @@ module CyberSource
       @previous_transaction_id = previous_transaction_id
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] original_authorized_amount Value to be assigned
+    def original_authorized_amount=(original_authorized_amount)
+      @original_authorized_amount = original_authorized_amount
+    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 &&
-          previous_transaction_id == o.previous_transaction_id
+          previous_transaction_id == o.previous_transaction_id &&
+          original_authorized_amount == o.original_authorized_amount
     end
 
     # @see the `==` method
@@ -80,7 +96,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [previous_transaction_id].hash
+      [previous_transaction_id, original_authorized_amount].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_tokenized_card.rb

@@ -14,16 +14,19 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersEmbeddedDefaultPaymentInstrumentEmbeddedInstrumentIdentifierTokenizedCard
-    # The network token card association brand Valid values: - visa - mastercard 
+    # The network token card association brand Possible Values: - visa - mastercard 
     attr_accessor :type
 
-    # Issuers state for the network token Valid values: - ACTIVE - SUSPENDED : This state can change to ACTIVE or DELETED. - DELETED : This is a final state for the network token. 
+    # State of the network token or network token provision Possible Values: - ACTIVE : Network token is active. - SUSPENDED : Network token is suspended. This state can change back to ACTIVE. - DELETED : This is a final state for a network token instance. - UNPROVISIONED : A previous network token provision was unsuccessful. 
     attr_accessor :state
 
-    # The token requestors customer’s payment network token 
+    # Issuers state for the network token Possible Values: - INVALID_REQUEST : The network token provision request contained invalid data. - CARD_VERIFICATION_FAILED : The network token provision request contained data that could not be verified. - CARD_NOT_ELIGIBLE : Card can currently not be used with issuer for tokenization. - CARD_NOT_ALLOWED : Card can currently not be used with card association for tokenization. - DECLINED : Card can currently not be used with issuer for tokenization. - SERVICE_UNAVAILABLE : The network token service was unavailable or timed out. - SYSTEM_ERROR : An unexpected error occurred with network token service, check configuration. 
+    attr_accessor :reason
+
+    # The token requestors network token 
     attr_accessor :number
 
-    # Two-digit month in which the network token expires.  Format: `MM`.  Valid values: `01` through `12`. 
+    # Two-digit month in which the network token expires.  Format: `MM`.  Possible Values: `01` through `12`. 
     attr_accessor :expiration_month
 
     # Four-digit year in which the network token expires.  Format: `YYYY`. 
@@ -39,6 +42,7 @@ module CyberSource
       {
         :'type' => :'type',
         :'state' => :'state',
+        :'reason' => :'reason',
         :'number' => :'number',
         :'expiration_month' => :'expirationMonth',
         :'expiration_year' => :'expirationYear',
@@ -52,6 +56,7 @@ module CyberSource
       {
         :'type' => :'String',
         :'state' => :'String',
+        :'reason' => :'String',
         :'number' => :'String',
         :'expiration_month' => :'String',
         :'expiration_year' => :'String',
@@ -76,6 +81,10 @@ module CyberSource
         self.state = attributes[:'state']
       end
 
+      if attributes.has_key?(:'reason')
+        self.reason = attributes[:'reason']
+      end
+
       if attributes.has_key?(:'number')
         self.number = attributes[:'number']
       end
@@ -129,6 +138,7 @@ module CyberSource
       self.class == o.class &&
           type == o.type &&
           state == o.state &&
+          reason == o.reason &&
           number == o.number &&
           expiration_month == o.expiration_month &&
           expiration_year == o.expiration_year &&
@@ -145,7 +155,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [type, state, number, expiration_month, expiration_year, cryptogram, card].hash
+      [type, state, reason, number, expiration_month, expiration_year, cryptogram, card].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/tmsv2customers__embedded_tokenized_card_card.rb

@@ -18,7 +18,7 @@ module CyberSource
     # The customer’s latest payment card number suffix 
     attr_accessor :suffix
 
-    #  Two-digit month in which the customer’s latest payment card expires.  Format: `MM`.  Valid values: `01` through `12`. 
+    #  Two-digit month in which the customer’s latest payment card expires.  Format: `MM`.  Possible Values: `01` through `12`. 
     attr_accessor :expiration_month
 
     # Four-digit year in which the customer’s latest payment card expires.  Format: `YYYY`. 

data/lib/cybersource_rest_client/models/tmsv2customers_default_payment_instrument.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersDefaultPaymentInstrument
-    # The id of the Customers default Payment Instrument 
+    # The Id of the Customers default Payment Instrument 
     attr_accessor :id
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tmsv2customers_default_shipping_address.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersDefaultShippingAddress
-    # The id of the Customers default Shipping Address 
+    # The Id of the Customers default Shipping Address 
     attr_accessor :id
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tmsv2customers_merchant_defined_information.rb

@@ -14,10 +14,10 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersMerchantDefinedInformation
-    # The number you assign as the name for your merchant-defined data or secure field. Valid values are data1 to data4 and sensitive1 to sensitive4  For example, to set the name for merchant-defined data 2 field, you would reference merchantDefinedInformation[x].name as data2 Valid values: - data1 - data2 - data3 - data4 - sensitive1 - sensitive2 - sensitive3 - sensitive4 
+    # The number you assign as the name for your merchant-defined data or secure field. Possible Values are data1 to data4 and sensitive1 to sensitive4  For example, to set the name for merchant-defined data 2 field, you would reference merchantDefinedInformation[x].name as data2 Possible Values: - data1 - data2 - data3 - data4 - sensitive1 - sensitive2 - sensitive3 - sensitive4 
     attr_accessor :name
 
-    # The value you assign for your merchant-defined data field.  **Warning** Merchant-defined data fields are not intended to and must not be used to capture personally identifying information. Accordingly, merchants are prohibited from capturing, obtaining, and/or transmitting any personally identifying information in or via the merchant-defined data fields. Personally identifying information includes, but is not limited to, address, credit card number, social security number, driver's license number, state-issued identification number, passport number, and card verification numbers (CVV, CVC2, CVV2, CID, CVN). In the event CyberSource discovers that a merchant is capturing and/or transmitting personally identifying information via the merchant-defined data fields, whether or not intentionally, CyberSource will immediately suspend the merchant's account, which will result in a rejection of any and all transaction requests submitted by the merchant after the point of suspension. 
+    # The value you assign for your merchant-defined data field.  **Warning** Merchant-defined data fields are not intended to and must not be used to capture personally identifying information. Accordingly, merchants are prohibited from capturing, obtaining, and/or transmitting any personally identifying information in or via the merchant-defined data fields. Personally identifying information includes, but is not limited to, address, credit card number, social security number, driver's license number, state-issued identification number, passport number, and card verification numbers (CVV, CVC2, CVV2, CID, CVN). In the event it is discovered a merchant is capturing and/or transmitting personally identifying information via the merchant-defined data fields, whether or not intentionally, the merchant's account will immediately be suspended, which will result in a rejection of any and all transaction requests submitted by the merchant after the point of suspension. 
     attr_accessor :value
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tmsv2customers_metadata.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Tmsv2customersMetadata
-    # The creator of the Customer token. 
+    # The creator of the Customer. 
     attr_accessor :creator
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_order_information_invoice_details.rb

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

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_order_information_line_items.rb

@@ -102,22 +102,12 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if !@quantity.nil? && @quantity > 999999999
-        invalid_properties.push('invalid value for "quantity", must be smaller than or equal to 999999999.')
-      end
-
-      if !@quantity.nil? && @quantity < 1
-        invalid_properties.push('invalid value for "quantity", must be greater than or equal to 1.')
-      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 !@quantity.nil? && @quantity > 999999999
-      return false if !@quantity.nil? && @quantity < 1
       true
     end
 
@@ -148,14 +138,6 @@ module CyberSource
     # Custom attribute writer method with validation
     # @param [Object] quantity Value to be assigned
     def quantity=(quantity)
-      if !quantity.nil? && quantity > 999999999
-        fail ArgumentError, 'invalid value for "quantity", must be smaller than or equal to 999999999.'
-      end
-
-      if !quantity.nil? && quantity < 1
-        fail ArgumentError, 'invalid value for "quantity", must be greater than or equal to 1.'
-      end
-
       @quantity = quantity
     end
 

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_payment_information_card.rb

@@ -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.  **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 
+    # 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 - '070': EFTPOS  [^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 
     attr_accessor :type
 
     # Identifier for the issuing bank that provided the customer’s encoded account number. Contact your processor for the bank’s ID. 

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_point_of_sale_information.rb

@@ -83,22 +83,12 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if !@terminal_capability.nil? && @terminal_capability > 5
-        invalid_properties.push('invalid value for "terminal_capability", must be smaller than or equal to 5.')
-      end
-
-      if !@terminal_capability.nil? && @terminal_capability < 1
-        invalid_properties.push('invalid value for "terminal_capability", must be greater than or equal to 1.')
-      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 !@terminal_capability.nil? && @terminal_capability > 5
-      return false if !@terminal_capability.nil? && @terminal_capability < 1
       true
     end
 
@@ -117,14 +107,6 @@ module CyberSource
     # Custom attribute writer method with validation
     # @param [Object] terminal_capability Value to be assigned
     def terminal_capability=(terminal_capability)
-      if !terminal_capability.nil? && terminal_capability > 5
-        fail ArgumentError, 'invalid value for "terminal_capability", must be smaller than or equal to 5.'
-      end
-
-      if !terminal_capability.nil? && terminal_capability < 1
-        fail ArgumentError, 'invalid value for "terminal_capability", must be greater than or equal to 1.'
-      end
-
       @terminal_capability = terminal_capability
     end
 

data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processor_information_electronic_verification_results.rb

@@ -20,10 +20,10 @@ module CyberSource
     # Raw Electronic Verification response code from the processor for the customer’s email address.
     attr_accessor :email_raw
 
-    # Mapped Electronic Verification response code for the customer’s name. 
+    # #### Visa Platform Connect Mapped Electronic Verification response code for the customer’s name.  Valid values :  'Y'   Yes, the data Matches 'N'   No Match 'O'   Partial Match 
     attr_accessor :name
 
-    # Raw Electronic Verification response code from the processor for the customer’s name. 
+    # #### Visa Platform Connect Raw Electronic Verification response code from the processor for the customer’s name.  Valid values :  '01'     Match '50'     Partial Match '99'     No Match 
     attr_accessor :name_raw
 
     # Mapped Electronic Verification response code for the customer’s phone number.  For details, see `auth_ev_phone_number` field description in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) 

data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_payment_information_card.rb

@@ -20,7 +20,7 @@ module CyberSource
     # Bank Identification Number (BIN). This is the initial four to six numbers on a credit card account number.  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response. 
     attr_accessor :prefix
 
-    # 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 
+    # 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 - '070': EFTPOS  [^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 
     attr_accessor :type
 
     # Attribute mapping from ruby-style variable name to JSON key.

data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_point_of_sale_information.rb

@@ -25,13 +25,16 @@ module CyberSource
 
     attr_accessor :partner
 
+    attr_accessor :emv
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
         :'terminal_id' => :'terminalId',
         :'terminal_serial_number' => :'terminalSerialNumber',
         :'device_id' => :'deviceId',
-        :'partner' => :'partner'
+        :'partner' => :'partner',
+        :'emv' => :'emv'
       }
     end
 
@@ -41,7 +44,8 @@ module CyberSource
         :'terminal_id' => :'String',
         :'terminal_serial_number' => :'String',
         :'device_id' => :'String',
-        :'partner' => :'TssV2TransactionsPost201ResponseEmbeddedPointOfSaleInformationPartner'
+        :'partner' => :'TssV2TransactionsPost201ResponseEmbeddedPointOfSaleInformationPartner',
+        :'emv' => :'Ptsv2paymentsidreversalsPointOfSaleInformationEmv'
       }
     end
 
@@ -68,6 +72,10 @@ module CyberSource
       if attributes.has_key?(:'partner')
         self.partner = attributes[:'partner']
       end
+
+      if attributes.has_key?(:'emv')
+        self.emv = attributes[:'emv']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -103,7 +111,8 @@ module CyberSource
           terminal_id == o.terminal_id &&
           terminal_serial_number == o.terminal_serial_number &&
           device_id == o.device_id &&
-          partner == o.partner
+          partner == o.partner &&
+          emv == o.emv
     end
 
     # @see the `==` method
@@ -115,7 +124,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [terminal_id, terminal_serial_number, device_id, partner].hash
+      [terminal_id, terminal_serial_number, device_id, partner, emv].hash
     end
 
     # Builds the object from hash