cybersource_rest_client 0.0.40 → 0.0.44

data/lib/cybersource_rest_client/models/ptsv2payments_order_information_invoice_details.rb

@@ -61,6 +61,9 @@ module CyberSource
     # Cost centre of the merchant
     attr_accessor :cost_center
 
+    # Text message from the issuer. If you give the customer a receipt, display this value on the receipt.
+    attr_accessor :issuer_message
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -79,7 +82,8 @@ module CyberSource
         :'reference_data_number' => :'referenceDataNumber',
         :'sales_slip_number' => :'salesSlipNumber',
         :'invoice_date' => :'invoiceDate',
-        :'cost_center' => :'costCenter'
+        :'cost_center' => :'costCenter',
+        :'issuer_message' => :'issuerMessage'
       }
     end
 
@@ -101,7 +105,8 @@ module CyberSource
         :'reference_data_number' => :'String',
         :'sales_slip_number' => :'Integer',
         :'invoice_date' => :'String',
-        :'cost_center' => :'String'
+        :'cost_center' => :'String',
+        :'issuer_message' => :'String'
       }
     end
 
@@ -178,6 +183,10 @@ module CyberSource
       if attributes.has_key?(:'costCenter')
         self.cost_center = attributes[:'costCenter']
       end
+
+      if attributes.has_key?(:'issuerMessage')
+        self.issuer_message = attributes[:'issuerMessage']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -262,6 +271,12 @@ module CyberSource
       @cost_center = cost_center
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] issuer_message Value to be assigned
+    def issuer_message=(issuer_message)
+      @issuer_message = issuer_message
+    end
+
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)
@@ -282,7 +297,8 @@ module CyberSource
           reference_data_number == o.reference_data_number &&
           sales_slip_number == o.sales_slip_number &&
           invoice_date == o.invoice_date &&
-          cost_center == o.cost_center
+          cost_center == o.cost_center &&
+          issuer_message == o.issuer_message
     end
 
     # @see the `==` method
@@ -294,7 +310,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [invoice_number, barcode_number, expiration_date, purchase_order_number, purchase_order_date, purchase_contact_name, taxable, vat_invoice_reference_number, commodity_code, merchandise_code, transaction_advice_addendum, reference_data_code, reference_data_number, sales_slip_number, invoice_date, cost_center].hash
+      [invoice_number, barcode_number, expiration_date, purchase_order_number, purchase_order_date, purchase_contact_name, taxable, vat_invoice_reference_number, commodity_code, merchandise_code, transaction_advice_addendum, reference_data_code, reference_data_number, sales_slip_number, invoice_date, cost_center, issuer_message].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_card.rb

@@ -56,6 +56,9 @@ module CyberSource
     # Name of the card product.  Possible value: - BNDES  This field is supported only for BNDES transactions on CyberSource through VisaNet.  The value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP07 TCR4 - Position: 115-120 - Field: Brazil Country Data 
     attr_accessor :product_name
 
+    # Flag that identifies how the card type was selected.  Possible values: - 0: Card type was selected based on default acquirer settings. - 1: Customer selected the card type. 
+    attr_accessor :type_selection_indicator
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -72,7 +75,8 @@ module CyberSource
         :'issue_number' => :'issueNumber',
         :'start_month' => :'startMonth',
         :'start_year' => :'startYear',
-        :'product_name' => :'productName'
+        :'product_name' => :'productName',
+        :'type_selection_indicator' => :'typeSelectionIndicator'
       }
     end
 
@@ -92,7 +96,8 @@ module CyberSource
         :'issue_number' => :'String',
         :'start_month' => :'String',
         :'start_year' => :'String',
-        :'product_name' => :'String'
+        :'product_name' => :'String',
+        :'type_selection_indicator' => :'String'
       }
     end
 
@@ -159,6 +164,10 @@ module CyberSource
       if attributes.has_key?(:'productName')
         self.product_name = attributes[:'productName']
       end
+
+      if attributes.has_key?(:'typeSelectionIndicator')
+        self.type_selection_indicator = attributes[:'typeSelectionIndicator']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -252,6 +261,12 @@ module CyberSource
       @product_name = product_name
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] type_selection_indicator Value to be assigned
+    def type_selection_indicator=(type_selection_indicator)
+      @type_selection_indicator = type_selection_indicator
+    end
+
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)
@@ -270,7 +285,8 @@ module CyberSource
           issue_number == o.issue_number &&
           start_month == o.start_month &&
           start_year == o.start_year &&
-          product_name == o.product_name
+          product_name == o.product_name &&
+          type_selection_indicator == o.type_selection_indicator
     end
 
     # @see the `==` method
@@ -282,7 +298,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [number, expiration_month, expiration_year, type, use_as, source_account_type, source_account_type_details, security_code, security_code_indicator, account_encoder_id, issue_number, start_month, start_year, product_name].hash
+      [number, expiration_month, expiration_year, type, use_as, source_account_type, source_account_type_details, security_code, security_code_indicator, account_encoder_id, issue_number, start_month, start_year, product_name, type_selection_indicator].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb

@@ -26,13 +26,13 @@ module CyberSource
     # 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 
     attr_accessor :type
 
-    # This field is used internally.
+    # This field contains token information.
     attr_accessor :cryptogram
 
     # 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**.  #### PIN debit Optional field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
     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.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
+    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  #### Visa Platform Connect - `1`: For Rupay and In App tokenization. Example: InApp apple pay. - `3`: Card/Credential On File Tokenization.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
     attr_accessor :transaction_type
 
     # Confidence level of the tokenization. This value is assigned by the token service provider.  **Note** This field is supported only for **CyberSource through VisaNet** and **FDC Nashville Global**.  Returned by PIN debit credit or PIN debit purchase. 
@@ -44,6 +44,9 @@ module CyberSource
     # Card Verification Number (CVN).  #### Ingenico ePayments Do not include this field when **commerceIndicator=recurring**. **Note** Ingenico ePayments was previously called _Global Collect_.  For details, see `customer_cc_cv_number` field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) 
     attr_accessor :security_code
 
+    # Indicates whether a CVN code was sent. Possible values:   - `0` (default): CVN service not requested. This default value is used when you do not include      `securityCode` field in the request.  - `1` (default): CVN service requested and supported. This default value is used when you include      `securityCode` field in the request.  - `2`: CVN on credit card is illegible.  - `9`: CVN was not imprinted on credit card.  #### FDMS Nashville Required for American Express cards; otherwise, optional.  #### TSYS Acquiring Solutions Optional if `pointOfSaleInformation.entryMode=keyed`; otherwise, not used.  #### All other processors Optional. 
+    attr_accessor :security_code_indicator
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -56,7 +59,8 @@ module CyberSource
         :'transaction_type' => :'transactionType',
         :'assurance_level' => :'assuranceLevel',
         :'storage_method' => :'storageMethod',
-        :'security_code' => :'securityCode'
+        :'security_code' => :'securityCode',
+        :'security_code_indicator' => :'securityCodeIndicator'
       }
     end
 
@@ -72,7 +76,8 @@ module CyberSource
         :'transaction_type' => :'String',
         :'assurance_level' => :'String',
         :'storage_method' => :'String',
-        :'security_code' => :'String'
+        :'security_code' => :'String',
+        :'security_code_indicator' => :'String'
       }
     end
 
@@ -123,6 +128,10 @@ module CyberSource
       if attributes.has_key?(:'securityCode')
         self.security_code = attributes[:'securityCode']
       end
+
+      if attributes.has_key?(:'securityCodeIndicator')
+        self.security_code_indicator = attributes[:'securityCodeIndicator']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -192,6 +201,12 @@ module CyberSource
       @security_code = security_code
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] security_code_indicator Value to be assigned
+    def security_code_indicator=(security_code_indicator)
+      @security_code_indicator = security_code_indicator
+    end
+
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)
@@ -206,7 +221,8 @@ module CyberSource
           transaction_type == o.transaction_type &&
           assurance_level == o.assurance_level &&
           storage_method == o.storage_method &&
-          security_code == o.security_code
+          security_code == o.security_code &&
+          security_code_indicator == o.security_code_indicator
     end
 
     # @see the `==` method
@@ -218,7 +234,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [number, expiration_month, expiration_year, type, cryptogram, requestor_id, transaction_type, assurance_level, storage_method, security_code].hash
+      [number, expiration_month, expiration_year, type, cryptogram, requestor_id, transaction_type, assurance_level, storage_method, security_code, security_code_indicator].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/ptsv2payments_point_of_sale_information.rb

@@ -91,6 +91,9 @@ module CyberSource
     # This is the manufacturer name of the reader which is used to accept the payment. Possible values:  - PAX  - Verifone  - Ingenico 
     attr_accessor :terminal_make
 
+    # #### Visa Platform Connect Mastercard service code that is included in the track data. You can extract the service code from the track data and provide it in this API field. This field is supported only for Mastercard on Visa Platform Connect. 
+    attr_accessor :service_code
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -119,7 +122,8 @@ module CyberSource
         :'terminal_compliance' => :'terminalCompliance',
         :'is_dedicated_hardware_terminal' => :'isDedicatedHardwareTerminal',
         :'terminal_model' => :'terminalModel',
-        :'terminal_make' => :'terminalMake'
+        :'terminal_make' => :'terminalMake',
+        :'service_code' => :'serviceCode'
       }
     end
 
@@ -151,7 +155,8 @@ module CyberSource
         :'terminal_compliance' => :'String',
         :'is_dedicated_hardware_terminal' => :'String',
         :'terminal_model' => :'String',
-        :'terminal_make' => :'String'
+        :'terminal_make' => :'String',
+        :'service_code' => :'String'
       }
     end
 
@@ -270,6 +275,10 @@ module CyberSource
       if attributes.has_key?(:'terminalMake')
         self.terminal_make = attributes[:'terminalMake']
       end
+
+      if attributes.has_key?(:'serviceCode')
+        self.service_code = attributes[:'serviceCode']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -456,6 +465,12 @@ module CyberSource
       @terminal_make = terminal_make
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] service_code Value to be assigned
+    def service_code=(service_code)
+      @service_code = service_code
+    end
+
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)
@@ -486,7 +501,8 @@ module CyberSource
           terminal_compliance == o.terminal_compliance &&
           is_dedicated_hardware_terminal == o.is_dedicated_hardware_terminal &&
           terminal_model == o.terminal_model &&
-          terminal_make == o.terminal_make
+          terminal_make == o.terminal_make &&
+          service_code == o.service_code
     end
 
     # @see the `==` method
@@ -498,7 +514,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [terminal_id, terminal_serial_number, lane_number, cat_level, entry_mode, terminal_capability, operating_environment, emv, amex_capn_data, track_data, store_and_forward_indicator, cardholder_verification_method, terminal_input_capability, terminal_card_capture_capability, terminal_output_capability, terminal_pin_capability, device_id, pin_block_encoding_format, encrypted_pin, encrypted_key_serial_number, partner_sdk_version, emv_application_identifier_and_dedicated_file_name, terminal_compliance, is_dedicated_hardware_terminal, terminal_model, terminal_make].hash
+      [terminal_id, terminal_serial_number, lane_number, cat_level, entry_mode, terminal_capability, operating_environment, emv, amex_capn_data, track_data, store_and_forward_indicator, cardholder_verification_method, terminal_input_capability, terminal_card_capture_capability, terminal_output_capability, terminal_pin_capability, device_id, pin_block_encoding_format, encrypted_pin, encrypted_key_serial_number, partner_sdk_version, emv_application_identifier_and_dedicated_file_name, terminal_compliance, is_dedicated_hardware_terminal, terminal_model, terminal_make, service_code].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/ptsv2payments_point_of_sale_information_emv.rb

@@ -26,9 +26,12 @@ module CyberSource
     # Indicates whether a fallback method was used to enter credit card information into the POS terminal. When a technical problem prevents a successful exchange of information between a chip card and a chip-capable terminal:   1. Swipe the card or key the credit card information into the POS terminal.  2. Use the pointOfSaleInformation.entryMode field to indicate whether the information was swiped or keyed.   Possible values: - `true`: Fallback method was used. - `false` (default): Fallback method was not used.  This field is supported only on American Express Direct, Chase Paymentech Solutions, CyberSource through VisaNet, FDC Nashville Global, GPN, JCN Gateway, OmniPay Direct, and SIX. 
     attr_accessor :fallback
 
-    # Reason for the EMV fallback transaction. An EMV fallback transaction occurs when an EMV transaction fails for one of these reasons:   - Technical failure: the EMV terminal or EMV card cannot read and process chip data.  - Empty candidate list failure: the EMV terminal does not have any applications in common with the EMV card.    EMV terminals are coded to determine whether the terminal and EMV card have any applications in common.    EMV terminals provide this information to you.  Possible values:   - `1`: Transaction was initiated with information from a magnetic stripe, and the previous transaction at the       EMV terminal either used information from a successful chip read or it was not a chip transaction.  - `2`: Transaction was initiated with information from a magnetic stripe, and the previous transaction at the       EMV terminal was an EMV fallback transaction because the attempted chip read was unsuccessful.  This field is supported only on **GPN** and **JCN Gateway**.  **NOTE**: This field is required when an EMV transaction fails for a technical reason. Do not include this field  when the EMV terminal does not have any applications in common with the EMV card. 
+    # Reason for the EMV fallback transaction. An EMV fallback transaction occurs when an EMV transaction fails for one of these reasons:   - Technical failure: the EMV terminal or EMV card cannot read and process chip data.  - Empty candidate list failure: the EMV terminal does not have any applications in common with the EMV card.    EMV terminals are coded to determine whether the terminal and EMV card have any applications in common.    EMV terminals provide this information to you.  Possible values:   - `1`: Transaction was initiated with information from a magnetic stripe, and the previous transaction at the     EMV terminal either used information from a successful chip read or it was not a chip transaction.  - `2`: Transaction was initiated with information from a magnetic stripe, and the previous transaction at the     EMV terminal was an EMV fallback transaction because the attempted chip read was unsuccessful.  This field is supported only on **GPN** and **JCN Gateway**. **NOTE**: This field is required when an EMV transaction fails for a technical reason. Do not include this field when the EMV terminal does not have any applications in common with the EMV card. 
     attr_accessor :fallback_condition
 
+    # #### Visa Platform Connect Value “true” indicates this transaction is intentionally duplicated . The field contains value “true” which indicates that merchant has intentionally duplicated single tap transaction. Merchant is intentionally sending a duplicate auth request for a single tap txn because the issuer requested a PIN. 
+    attr_accessor :is_repeat
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -36,7 +39,8 @@ module CyberSource
         :'cardholder_verification_method_used' => :'cardholderVerificationMethodUsed',
         :'card_sequence_number' => :'cardSequenceNumber',
         :'fallback' => :'fallback',
-        :'fallback_condition' => :'fallbackCondition'
+        :'fallback_condition' => :'fallbackCondition',
+        :'is_repeat' => :'isRepeat'
       }
     end
 
@@ -47,7 +51,8 @@ module CyberSource
         :'cardholder_verification_method_used' => :'Integer',
         :'card_sequence_number' => :'String',
         :'fallback' => :'BOOLEAN',
-        :'fallback_condition' => :'Integer'
+        :'fallback_condition' => :'Integer',
+        :'is_repeat' => :'BOOLEAN'
       }
     end
 
@@ -73,13 +78,15 @@ module CyberSource
 
       if attributes.has_key?(:'fallback')
         self.fallback = attributes[:'fallback']
-      else
-        self.fallback = false
       end
 
       if attributes.has_key?(:'fallbackCondition')
         self.fallback_condition = attributes[:'fallbackCondition']
       end
+
+      if attributes.has_key?(:'isRepeat')
+        self.is_repeat = attributes[:'isRepeat']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -116,7 +123,8 @@ module CyberSource
           cardholder_verification_method_used == o.cardholder_verification_method_used &&
           card_sequence_number == o.card_sequence_number &&
           fallback == o.fallback &&
-          fallback_condition == o.fallback_condition
+          fallback_condition == o.fallback_condition &&
+          is_repeat == o.is_repeat
     end
 
     # @see the `==` method
@@ -128,7 +136,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [tags, cardholder_verification_method_used, card_sequence_number, fallback, fallback_condition].hash
+      [tags, cardholder_verification_method_used, card_sequence_number, fallback, fallback_condition, is_repeat].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/ptsv2payments_processing_information.rb

@@ -87,6 +87,9 @@ module CyberSource
     # Flag that indicates if the transaction is pay by points transaction true: Transaction uses loyalty points false: Transaction does not use loyalty points Default: false 
     attr_accessor :pay_by_points_indicator
 
+    # Flag that indicates the functionality we are having for merchants for which auth is done through Cybersource but settlement is done by themselves. true: functionality is supported. Processor should send raw processor auth response to Merchant. false: functionality is not supported. Default: false 
+    attr_accessor :is_return_auth_record_enabled
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -116,7 +119,8 @@ module CyberSource
         :'mobile_remote_payment_type' => :'mobileRemotePaymentType',
         :'extended_credit_total_count' => :'extendedCreditTotalCount',
         :'network_routing_order' => :'networkRoutingOrder',
-        :'pay_by_points_indicator' => :'payByPointsIndicator'
+        :'pay_by_points_indicator' => :'payByPointsIndicator',
+        :'is_return_auth_record_enabled' => :'isReturnAuthRecordEnabled'
       }
     end
 
@@ -149,7 +153,8 @@ module CyberSource
         :'mobile_remote_payment_type' => :'String',
         :'extended_credit_total_count' => :'String',
         :'network_routing_order' => :'String',
-        :'pay_by_points_indicator' => :'BOOLEAN'
+        :'pay_by_points_indicator' => :'BOOLEAN',
+        :'is_return_auth_record_enabled' => :'BOOLEAN'
       }
     end
 
@@ -274,6 +279,10 @@ module CyberSource
       if attributes.has_key?(:'payByPointsIndicator')
         self.pay_by_points_indicator = attributes[:'payByPointsIndicator']
       end
+
+      if attributes.has_key?(:'isReturnAuthRecordEnabled')
+        self.is_return_auth_record_enabled = attributes[:'isReturnAuthRecordEnabled']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -404,7 +413,8 @@ module CyberSource
           mobile_remote_payment_type == o.mobile_remote_payment_type &&
           extended_credit_total_count == o.extended_credit_total_count &&
           network_routing_order == o.network_routing_order &&
-          pay_by_points_indicator == o.pay_by_points_indicator
+          pay_by_points_indicator == o.pay_by_points_indicator &&
+          is_return_auth_record_enabled == o.is_return_auth_record_enabled
     end
 
     # @see the `==` method
@@ -416,7 +426,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [action_list, action_token_types, capture, processor_id, business_application_id, commerce_indicator, payment_solution, reconciliation_id, link_id, purchase_level, report_group, visa_checkout_id, industry_data_type, authorization_options, capture_options, recurring_options, bank_transfer_options, purchase_options, electronic_benefits_transfer, loan_options, wallet_type, national_net_domestic_data, japan_payment_options, mobile_remote_payment_type, extended_credit_total_count, network_routing_order, pay_by_points_indicator].hash
+      [action_list, action_token_types, capture, processor_id, business_application_id, commerce_indicator, payment_solution, reconciliation_id, link_id, purchase_level, report_group, visa_checkout_id, industry_data_type, authorization_options, capture_options, recurring_options, bank_transfer_options, purchase_options, electronic_benefits_transfer, loan_options, wallet_type, national_net_domestic_data, japan_payment_options, mobile_remote_payment_type, extended_credit_total_count, network_routing_order, pay_by_points_indicator, is_return_auth_record_enabled].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/ptsv2payments_processing_information_authorization_options.rb

@@ -17,6 +17,9 @@ module CyberSource
     # 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
 
+    # #### Visa Platform Connect The field contains the PAN translation indicator for American Express Contactless Transaction. Valid value is   1- Expresspay Translation, PAN request 2- Expresspay Translation, PAN and Expiry date request 
+    attr_accessor :pan_return_indicator
+
     # Authorization code.  #### Forced Capture Use this field to send the authorization code you received from a payment that you authorized outside the CyberSource system.  #### PIN debit Authorization code that is returned by the processor.  Returned by PIN debit purchase.  #### Verbal Authorization Use this field in CAPTURE API to send the verbally received authorization code.  For processor-specific information, see the `auth_code` field description in [Credit Card Services Using the SCMP API](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html). 
     attr_accessor :verbal_auth_code
 
@@ -68,6 +71,7 @@ module CyberSource
     def self.attribute_map
       {
         :'auth_type' => :'authType',
+        :'pan_return_indicator' => :'panReturnIndicator',
         :'verbal_auth_code' => :'verbalAuthCode',
         :'verbal_auth_transaction_id' => :'verbalAuthTransactionId',
         :'auth_indicator' => :'authIndicator',
@@ -91,6 +95,7 @@ module CyberSource
     def self.swagger_types
       {
         :'auth_type' => :'String',
+        :'pan_return_indicator' => :'String',
         :'verbal_auth_code' => :'String',
         :'verbal_auth_transaction_id' => :'String',
         :'auth_indicator' => :'String',
@@ -122,6 +127,10 @@ module CyberSource
         self.auth_type = attributes[:'authType']
       end
 
+      if attributes.has_key?(:'panReturnIndicator')
+        self.pan_return_indicator = attributes[:'panReturnIndicator']
+      end
+
       if attributes.has_key?(:'verbalAuthCode')
         self.verbal_auth_code = attributes[:'verbalAuthCode']
       end
@@ -212,6 +221,12 @@ module CyberSource
       @auth_type = auth_type
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] pan_return_indicator Value to be assigned
+    def pan_return_indicator=(pan_return_indicator)
+      @pan_return_indicator = pan_return_indicator
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] verbal_auth_code Value to be assigned
     def verbal_auth_code=(verbal_auth_code)
@@ -236,6 +251,7 @@ module CyberSource
       return true if self.equal?(o)
       self.class == o.class &&
           auth_type == o.auth_type &&
+          pan_return_indicator == o.pan_return_indicator &&
           verbal_auth_code == o.verbal_auth_code &&
           verbal_auth_transaction_id == o.verbal_auth_transaction_id &&
           auth_indicator == o.auth_indicator &&
@@ -263,7 +279,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [auth_type, verbal_auth_code, verbal_auth_transaction_id, auth_indicator, partial_auth_indicator, balance_inquiry, ignore_avs_result, decline_avs_flags, ignore_cv_result, initiator, bill_payment, bill_payment_type, redemption_inquiry, transportation_mode, aggregated_auth_indicator, debt_recovery_indicator, deferred_auth_indicator].hash
+      [auth_type, pan_return_indicator, verbal_auth_code, verbal_auth_transaction_id, auth_indicator, partial_auth_indicator, balance_inquiry, ignore_avs_result, decline_avs_flags, ignore_cv_result, initiator, bill_payment, bill_payment_type, redemption_inquiry, transportation_mode, aggregated_auth_indicator, debt_recovery_indicator, deferred_auth_indicator].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/ptsv2payments_processing_information_authorization_options_initiator.rb

@@ -20,7 +20,7 @@ module CyberSource
     # Indicates to the issuing bank two things: - The merchant has received consent from the cardholder to store their card details on file - The merchant wants the issuing bank to check out the card details before the merchant initiates their first transaction for this cardholder. The purpose of the merchant-initiated transaction is to ensure that the cardholder’s credentials are valid (that the card is not stolen or has restrictions) and that the card details are good to be stored on the merchant’s file for future transactions.  Valid values: - `true` means merchant will use this transaction to store payment credentials for follow-up merchant-initiated transactions. - `false` means merchant will not use this transaction to store payment credentials for follow-up merchant-initiated transactions.  For details, see `subsequent_auth_first` 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/)  **NOTE:** The value for this field does not correspond to any data in the TC 33 capture file5.  This field is supported only for Visa transactions on CyberSource through VisaNet. 
     attr_accessor :credential_stored_on_file
 
-    # Indicates to an issuing bank whether a merchant-initiated transaction came from a card that was already stored on file.  Possible values: - **Y** means the merchant-initiated transaction came from a card that was already stored on file. - **N**  means the merchant-initiated transaction came from a card that was not stored on file. 
+    # Indicates to an issuing bank whether a merchant-initiated transaction came from a card that was already stored on file.  Possible values: - **true** means the merchant-initiated transaction came from a card that was already stored on file. - **false**  means the merchant-initiated transaction came from a card that was not stored on file. 
     attr_accessor :stored_credential_used
 
     attr_accessor :merchant_initiated_transaction
@@ -40,7 +40,7 @@ module CyberSource
       {
         :'type' => :'String',
         :'credential_stored_on_file' => :'BOOLEAN',
-        :'stored_credential_used' => :'String',
+        :'stored_credential_used' => :'BOOLEAN',
         :'merchant_initiated_transaction' => :'Ptsv2paymentsProcessingInformationAuthorizationOptionsInitiatorMerchantInitiatedTransaction'
       }
     end

data/lib/cybersource_rest_client/models/ptsv2payments_processor_information.rb

@@ -18,17 +18,21 @@ module CyberSource
     # Token received in original session service.
     attr_accessor :pre_approval_token
 
+    attr_accessor :authorization_options
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
-        :'pre_approval_token' => :'preApprovalToken'
+        :'pre_approval_token' => :'preApprovalToken',
+        :'authorization_options' => :'authorizationOptions'
       }
     end
 
     # Attribute type mapping.
     def self.swagger_types
       {
-        :'pre_approval_token' => :'String'
+        :'pre_approval_token' => :'String',
+        :'authorization_options' => :'Ptsv2paymentsProcessorInformationAuthorizationOptions'
       }
     end
 
@@ -43,6 +47,10 @@ module CyberSource
       if attributes.has_key?(:'preApprovalToken')
         self.pre_approval_token = attributes[:'preApprovalToken']
       end
+
+      if attributes.has_key?(:'authorizationOptions')
+        self.authorization_options = attributes[:'authorizationOptions']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -69,7 +77,8 @@ module CyberSource
     def ==(o)
       return true if self.equal?(o)
       self.class == o.class &&
-          pre_approval_token == o.pre_approval_token
+          pre_approval_token == o.pre_approval_token &&
+          authorization_options == o.authorization_options
     end
 
     # @see the `==` method
@@ -81,7 +90,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [pre_approval_token].hash
+      [pre_approval_token, authorization_options].hash
     end
 
     # Builds the object from hash