cybersource_rest_client 0.0.41 → 0.0.44

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/ptsv2paymentsid_processing_information_authorization_options_initiator.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Ptsv2paymentsidProcessingInformationAuthorizationOptionsInitiator
-    # 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
 
     # Attribute mapping from ruby-style variable name to JSON key.
@@ -27,7 +27,7 @@ module CyberSource
     # Attribute type mapping.
     def self.swagger_types
       {
-        :'stored_credential_used' => :'String'
+        :'stored_credential_used' => :'BOOLEAN'
       }
     end
 

data/lib/cybersource_rest_client/models/reporting_v3_chargeback_details_get200_response_chargeback_details.rb

@@ -80,6 +80,9 @@ module CyberSource
     # Event Request Date
     attr_accessor :event_requested_time
 
+    # Pre Dispute Flag
+    attr_accessor :pre_dispute_flag
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -104,7 +107,8 @@ module CyberSource
         :'reason_code' => :'reasonCode',
         :'representment_cp_time' => :'representmentCPTime',
         :'applications' => :'applications',
-        :'event_requested_time' => :'eventRequestedTime'
+        :'event_requested_time' => :'eventRequestedTime',
+        :'pre_dispute_flag' => :'preDisputeFlag'
       }
     end
 
@@ -132,7 +136,8 @@ module CyberSource
         :'reason_code' => :'String',
         :'representment_cp_time' => :'DateTime',
         :'applications' => :'String',
-        :'event_requested_time' => :'DateTime'
+        :'event_requested_time' => :'DateTime',
+        :'pre_dispute_flag' => :'String'
       }
     end
 
@@ -231,6 +236,10 @@ module CyberSource
       if attributes.has_key?(:'eventRequestedTime')
         self.event_requested_time = attributes[:'eventRequestedTime']
       end
+
+      if attributes.has_key?(:'preDisputeFlag')
+        self.pre_dispute_flag = attributes[:'preDisputeFlag']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -272,7 +281,8 @@ module CyberSource
           reason_code == o.reason_code &&
           representment_cp_time == o.representment_cp_time &&
           applications == o.applications &&
-          event_requested_time == o.event_requested_time
+          event_requested_time == o.event_requested_time &&
+          pre_dispute_flag == o.pre_dispute_flag
     end
 
     # @see the `==` method
@@ -284,7 +294,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [processor_merchant_id, merchant_name, transaction_reference_number, merchant_reference_number, nature_of_dispute, alert_type, amount, sign, action, card_type, original_settlement_time, tracking_number, currency_code, request_id, response_due_time, time, action_description, customer_id, reason_code, representment_cp_time, applications, event_requested_time].hash
+      [processor_merchant_id, merchant_name, transaction_reference_number, merchant_reference_number, nature_of_dispute, alert_type, amount, sign, action, card_type, original_settlement_time, tracking_number, currency_code, request_id, response_due_time, time, action_description, customer_id, reason_code, representment_cp_time, applications, event_requested_time, pre_dispute_flag].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/risk_v1_authentication_results_post201_response_consumer_authentication_information.rb

@@ -26,6 +26,15 @@ module CyberSource
     # Message that explains the authenticationResult reply field. 
     attr_accessor :authentication_status_msg
 
+    # Payer authentication transaction identifier is used to link the check enrollment and validate authentication messages. For Rupay, this field should be passed as request only for Resend OTP use case. 
+    attr_accessor :authentication_transaction_id
+
+    # Payer authentication transaction identifier passed to link the validation and authorization calls. 
+    attr_accessor :authentication_transaction_context_id
+
+    # Web based token used to authenticate consumer with Rupay authentication provider. 
+    attr_accessor :transaction_token
+
     # The Base64 encoded JSON Payload of CB specific Authorization Values returned in the challenge Flow 
     attr_accessor :authorization_payload
 
@@ -90,6 +99,9 @@ module CyberSource
         :'acs_transaction_id' => :'acsTransactionId',
         :'authentication_result' => :'authenticationResult',
         :'authentication_status_msg' => :'authenticationStatusMsg',
+        :'authentication_transaction_id' => :'authenticationTransactionId',
+        :'authentication_transaction_context_id' => :'authenticationTransactionContextId',
+        :'transaction_token' => :'transactionToken',
         :'authorization_payload' => :'authorizationPayload',
         :'cavv' => :'cavv',
         :'cavv_algorithm' => :'cavvAlgorithm',
@@ -119,6 +131,9 @@ module CyberSource
         :'acs_transaction_id' => :'String',
         :'authentication_result' => :'String',
         :'authentication_status_msg' => :'String',
+        :'authentication_transaction_id' => :'String',
+        :'authentication_transaction_context_id' => :'String',
+        :'transaction_token' => :'String',
         :'authorization_payload' => :'String',
         :'cavv' => :'String',
         :'cavv_algorithm' => :'String',
@@ -165,6 +180,18 @@ module CyberSource
         self.authentication_status_msg = attributes[:'authenticationStatusMsg']
       end
 
+      if attributes.has_key?(:'authenticationTransactionId')
+        self.authentication_transaction_id = attributes[:'authenticationTransactionId']
+      end
+
+      if attributes.has_key?(:'authenticationTransactionContextId')
+        self.authentication_transaction_context_id = attributes[:'authenticationTransactionContextId']
+      end
+
+      if attributes.has_key?(:'transactionToken')
+        self.transaction_token = attributes[:'transactionToken']
+      end
+
       if attributes.has_key?(:'authorizationPayload')
         self.authorization_payload = attributes[:'authorizationPayload']
       end
@@ -261,6 +288,24 @@ module CyberSource
       @acs_transaction_id = acs_transaction_id
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] authentication_transaction_id Value to be assigned
+    def authentication_transaction_id=(authentication_transaction_id)
+      @authentication_transaction_id = authentication_transaction_id
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] authentication_transaction_context_id Value to be assigned
+    def authentication_transaction_context_id=(authentication_transaction_context_id)
+      @authentication_transaction_context_id = authentication_transaction_context_id
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] transaction_token Value to be assigned
+    def transaction_token=(transaction_token)
+      @transaction_token = transaction_token
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] cavv Value to be assigned
     def cavv=(cavv)
@@ -324,6 +369,9 @@ module CyberSource
           acs_transaction_id == o.acs_transaction_id &&
           authentication_result == o.authentication_result &&
           authentication_status_msg == o.authentication_status_msg &&
+          authentication_transaction_id == o.authentication_transaction_id &&
+          authentication_transaction_context_id == o.authentication_transaction_context_id &&
+          transaction_token == o.transaction_token &&
           authorization_payload == o.authorization_payload &&
           cavv == o.cavv &&
           cavv_algorithm == o.cavv_algorithm &&
@@ -354,7 +402,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [acs_rendering_type, acs_transaction_id, authentication_result, authentication_status_msg, authorization_payload, cavv, cavv_algorithm, directory_server_error_code, directory_server_error_description, indicator, interaction_counter, eci, eci_raw, pares_status, sdk_transaction_id, specification_version, three_ds_server_transaction_id, ucaf_authentication_data, ucaf_collection_indicator, white_list_status, white_list_status_source, xid, directory_server_transaction_id].hash
+      [acs_rendering_type, acs_transaction_id, authentication_result, authentication_status_msg, authentication_transaction_id, authentication_transaction_context_id, transaction_token, authorization_payload, cavv, cavv_algorithm, directory_server_error_code, directory_server_error_description, indicator, interaction_counter, eci, eci_raw, pares_status, sdk_transaction_id, specification_version, three_ds_server_transaction_id, ucaf_authentication_data, ucaf_collection_indicator, white_list_status, white_list_status_source, xid, directory_server_transaction_id].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/risk_v1_decisions_post201_response_consumer_authentication_information.rb

@@ -32,9 +32,18 @@ module CyberSource
     # The Base64 encoded JSON Payload of CB specific Authorization Values returned in the challenge Flow 
     attr_accessor :authorization_payload
 
-    # Payer authentication transaction identifier passed to link the check enrollment and validate authentication messages. 
+    # Indicates the type of authentication that will be used to challenge the card holder.  Possible Values:  01 - Static  02 - Dynamic  03 - OOB (Out of Band)  04 - Decoupled  20 - OTP hosted at merchant end. (Rupay S2S flow) **NOTE**:  EMV 3-D Secure version 2.1.0 supports values 01-03.  Version 2.2.0 supports values 01-04.  Decoupled authentication is not supported at this time. 
+    attr_accessor :authentication_type
+
+    # Payer authentication transaction identifier is used to link the check enrollment and validate authentication messages. For Rupay, this field should be passed as request only for Resend OTP use case. 
     attr_accessor :authentication_transaction_id
 
+    # Payer authentication transaction identifier passed to link the validation and authorization calls. 
+    attr_accessor :authentication_transaction_context_id
+
+    # Describes validity of OTP in minutes for incoming transaction.        . 
+    attr_accessor :validity_period
+
     # Text provided by the ACS/Issuer to Cardholder during a Frictionless or Decoupled transaction.The Issuer can provide information to Cardholder. For example, “Additional authentication is needed for this transaction, please contact (Issuer Name) at xxx-xxx-xxxx.”. The Issuing Bank can optionally support this value. 
     attr_accessor :cardholder_message
 
@@ -130,7 +139,10 @@ module CyberSource
         :'acs_url' => :'acsUrl',
         :'authentication_path' => :'authenticationPath',
         :'authorization_payload' => :'authorizationPayload',
+        :'authentication_type' => :'authenticationType',
         :'authentication_transaction_id' => :'authenticationTransactionId',
+        :'authentication_transaction_context_id' => :'authenticationTransactionContextId',
+        :'validity_period' => :'validityPeriod',
         :'cardholder_message' => :'cardholderMessage',
         :'cavv' => :'cavv',
         :'cavv_algorithm' => :'cavvAlgorithm',
@@ -172,7 +184,10 @@ module CyberSource
         :'acs_url' => :'String',
         :'authentication_path' => :'String',
         :'authorization_payload' => :'String',
+        :'authentication_type' => :'String',
         :'authentication_transaction_id' => :'String',
+        :'authentication_transaction_context_id' => :'String',
+        :'validity_period' => :'Integer',
         :'cardholder_message' => :'String',
         :'cavv' => :'String',
         :'cavv_algorithm' => :'String',
@@ -237,10 +252,22 @@ module CyberSource
         self.authorization_payload = attributes[:'authorizationPayload']
       end
 
+      if attributes.has_key?(:'authenticationType')
+        self.authentication_type = attributes[:'authenticationType']
+      end
+
       if attributes.has_key?(:'authenticationTransactionId')
         self.authentication_transaction_id = attributes[:'authenticationTransactionId']
       end
 
+      if attributes.has_key?(:'authenticationTransactionContextId')
+        self.authentication_transaction_context_id = attributes[:'authenticationTransactionContextId']
+      end
+
+      if attributes.has_key?(:'validityPeriod')
+        self.validity_period = attributes[:'validityPeriod']
+      end
+
       if attributes.has_key?(:'cardholderMessage')
         self.cardholder_message = attributes[:'cardholderMessage']
       end
@@ -383,12 +410,24 @@ module CyberSource
       @acs_url = acs_url
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] authentication_type Value to be assigned
+    def authentication_type=(authentication_type)
+      @authentication_type = authentication_type
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] authentication_transaction_id Value to be assigned
     def authentication_transaction_id=(authentication_transaction_id)
       @authentication_transaction_id = authentication_transaction_id
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] authentication_transaction_context_id Value to be assigned
+    def authentication_transaction_context_id=(authentication_transaction_context_id)
+      @authentication_transaction_context_id = authentication_transaction_context_id
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] cardholder_message Value to be assigned
     def cardholder_message=(cardholder_message)
@@ -496,7 +535,10 @@ module CyberSource
           acs_url == o.acs_url &&
           authentication_path == o.authentication_path &&
           authorization_payload == o.authorization_payload &&
+          authentication_type == o.authentication_type &&
           authentication_transaction_id == o.authentication_transaction_id &&
+          authentication_transaction_context_id == o.authentication_transaction_context_id &&
+          validity_period == o.validity_period &&
           cardholder_message == o.cardholder_message &&
           cavv == o.cavv &&
           cavv_algorithm == o.cavv_algorithm &&
@@ -537,7 +579,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [access_token, acs_rendering_type, acs_transaction_id, acs_url, authentication_path, authorization_payload, authentication_transaction_id, cardholder_message, cavv, cavv_algorithm, challenge_cancel_code, challenge_required, decoupled_authentication_indicator, directory_server_error_code, directory_server_error_description, ecommerce_indicator, eci, eci_raw, effective_authentication_type, ivr, network_score, pareq, pares_status, proof_xml, proxy_pan, sdk_transaction_id, signed_pares_status_reason, specification_version, step_up_url, three_ds_server_transaction_id, ucaf_authentication_data, ucaf_collection_indicator, veres_enrolled, white_list_status_source, xid, directory_server_transaction_id].hash
+      [access_token, acs_rendering_type, acs_transaction_id, acs_url, authentication_path, authorization_payload, authentication_type, authentication_transaction_id, authentication_transaction_context_id, validity_period, cardholder_message, cavv, cavv_algorithm, challenge_cancel_code, challenge_required, decoupled_authentication_indicator, directory_server_error_code, directory_server_error_description, ecommerce_indicator, eci, eci_raw, effective_authentication_type, ivr, network_score, pareq, pares_status, proof_xml, proxy_pan, sdk_transaction_id, signed_pares_status_reason, specification_version, step_up_url, three_ds_server_transaction_id, ucaf_authentication_data, ucaf_collection_indicator, veres_enrolled, white_list_status_source, xid, directory_server_transaction_id].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/riskv1authenticationresults_consumer_authentication_information.rb

@@ -14,10 +14,16 @@ require 'date'
 
 module CyberSource
   class Riskv1authenticationresultsConsumerAuthenticationInformation
-    # Payer authentication transaction identifier passed to link the check enrollment and validate authentication messages. **Note**: Required for Standard integration for enroll service. Required for Hybrid integration for validate service. 
+    # Payer authentication transaction identifier passed to link the check enrollment and validate authentication messages.For Rupay,this is passed only in Re-Send OTP usecase. **Note**: Required for Standard integration, Rupay Seamless server to server integration for enroll service. Required for Hybrid integration for validate service. 
     attr_accessor :authentication_transaction_id
 
-    # Indicates the type of authentication that will be used to challenge the card holder.  Possible Values:  01 - Static  02 - Dynamic  03 - OOB (Out of Band)  04 - Decoupled **NOTE**:  EMV 3-D Secure version 2.1.0 supports values 01-03.  Version 2.2.0 supports values 01-04.  Decoupled authentication is not supported at this time. 
+    # Authentication transaction context is used as a unique identifier to link enroll and validate call. 
+    attr_accessor :authentication_transaction_context
+
+    # OTP entered by the card holder. 
+    attr_accessor :otp_token
+
+    # Indicates the type of authentication that will be used to challenge the card holder.  Possible Values:  01 - Static  02 - Dynamic  03 - OOB (Out of Band)  04 - Decoupled  20 - OTP hosted at merchant end. (Rupay S2S flow) **NOTE**:  EMV 3-D Secure version 2.1.0 supports values 01-03.  Version 2.2.0 supports values 01-04.  Decoupled authentication is not supported at this time. 
     attr_accessor :authentication_type
 
     # This field describes the type of 3DS transaction flow that took place.  It can be one of three possible flows; CH - Challenge FR - Frictionless FD - Frictionless with delegation, (challenge not generated by the issuer but by the scheme on behalf of the issuer). 
@@ -39,6 +45,8 @@ module CyberSource
     def self.attribute_map
       {
         :'authentication_transaction_id' => :'authenticationTransactionId',
+        :'authentication_transaction_context' => :'authenticationTransactionContext',
+        :'otp_token' => :'otpToken',
         :'authentication_type' => :'authenticationType',
         :'effective_authentication_type' => :'effectiveAuthenticationType',
         :'response_access_token' => :'responseAccessToken',
@@ -52,6 +60,8 @@ module CyberSource
     def self.swagger_types
       {
         :'authentication_transaction_id' => :'String',
+        :'authentication_transaction_context' => :'String',
+        :'otp_token' => :'String',
         :'authentication_type' => :'String',
         :'effective_authentication_type' => :'String',
         :'response_access_token' => :'String',
@@ -73,6 +83,14 @@ module CyberSource
         self.authentication_transaction_id = attributes[:'authenticationTransactionId']
       end
 
+      if attributes.has_key?(:'authenticationTransactionContext')
+        self.authentication_transaction_context = attributes[:'authenticationTransactionContext']
+      end
+
+      if attributes.has_key?(:'otpToken')
+        self.otp_token = attributes[:'otpToken']
+      end
+
       if attributes.has_key?(:'authenticationType')
         self.authentication_type = attributes[:'authenticationType']
       end
@@ -117,6 +135,18 @@ module CyberSource
       @authentication_transaction_id = authentication_transaction_id
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] authentication_transaction_context Value to be assigned
+    def authentication_transaction_context=(authentication_transaction_context)
+      @authentication_transaction_context = authentication_transaction_context
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] otp_token Value to be assigned
+    def otp_token=(otp_token)
+      @otp_token = otp_token
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] authentication_type Value to be assigned
     def authentication_type=(authentication_type)
@@ -147,6 +177,8 @@ module CyberSource
       return true if self.equal?(o)
       self.class == o.class &&
           authentication_transaction_id == o.authentication_transaction_id &&
+          authentication_transaction_context == o.authentication_transaction_context &&
+          otp_token == o.otp_token &&
           authentication_type == o.authentication_type &&
           effective_authentication_type == o.effective_authentication_type &&
           response_access_token == o.response_access_token &&
@@ -164,7 +196,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [authentication_transaction_id, authentication_type, effective_authentication_type, response_access_token, signed_pares_status_reason, signed_pares, white_list_status].hash
+      [authentication_transaction_id, authentication_transaction_context, otp_token, authentication_type, effective_authentication_type, response_access_token, signed_pares_status_reason, signed_pares, white_list_status].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/{tss_v2_transactions_post201_response__embedded_device_information.rb → riskv1authenticationresults_device_information.rb}

@@ -13,7 +13,7 @@ Swagger Codegen version: 2.2.3
 require 'date'
 
 module CyberSource
-  class TssV2TransactionsPost201ResponseEmbeddedDeviceInformation
+  class Riskv1authenticationresultsDeviceInformation
     # IP address of the customer.  #### Used by **Authorization, Capture, and Credit** Optional field. 
     attr_accessor :ip_address
 

data/lib/cybersource_rest_client/models/riskv1authenticationresults_payment_information_tokenized_card.rb

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

data/lib/cybersource_rest_client/models/riskv1authentications_payment_information_tokenized_card.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Riskv1authenticationsPaymentInformationTokenizedCard
-    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  #### Visa Platform Connect - `1`: In App tokenization. Example: InApp apple pay. - `3`: Card/Credential On File Tokenization.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
+    # 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
 
     # 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 
@@ -26,6 +26,12 @@ module CyberSource
     # One of two possible meanings: - The four-digit year in which a token expires. - The four-digit year in which a card expires. Format: `YYYY` Possible values: `1900` through `3000` Data type: Non-negative integer  **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 (1900 through 3000) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request.  #### Encoded Account Numbers For encoded account numbers (`card_ type=039`), if there is no expiration date on the card, use `2021`.  #### FDC Nashville Global and FDMS South You can send in 2 digits or 4 digits. When you send in 2 digits, they must be the last 2 digits of the year.  #### Samsung Pay and Apple Pay Year in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  For processor-specific information, see the `customer_cc_expyr` or `token_expiration_year` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
     attr_accessor :expiration_year
 
+    # This field contains token information.
+    attr_accessor :cryptogram
+
+    # 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
+
     # Customer’s payment network token value. 
     attr_accessor :number
 
@@ -36,6 +42,8 @@ module CyberSource
         :'type' => :'type',
         :'expiration_month' => :'expirationMonth',
         :'expiration_year' => :'expirationYear',
+        :'cryptogram' => :'cryptogram',
+        :'security_code' => :'securityCode',
         :'number' => :'number'
       }
     end
@@ -47,6 +55,8 @@ module CyberSource
         :'type' => :'String',
         :'expiration_month' => :'String',
         :'expiration_year' => :'String',
+        :'cryptogram' => :'String',
+        :'security_code' => :'String',
         :'number' => :'String'
       }
     end
@@ -75,6 +85,14 @@ module CyberSource
         self.expiration_year = attributes[:'expirationYear']
       end
 
+      if attributes.has_key?(:'cryptogram')
+        self.cryptogram = attributes[:'cryptogram']
+      end
+
+      if attributes.has_key?(:'securityCode')
+        self.security_code = attributes[:'securityCode']
+      end
+
       if attributes.has_key?(:'number')
         self.number = attributes[:'number']
       end
@@ -84,6 +102,10 @@ module CyberSource
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
+      if @transaction_type.nil?
+        invalid_properties.push('invalid value for "transaction_type", transaction_type cannot be nil.')
+      end
+
       if @type.nil?
         invalid_properties.push('invalid value for "type", type cannot be nil.')
       end
@@ -96,6 +118,14 @@ module CyberSource
         invalid_properties.push('invalid value for "expiration_year", expiration_year cannot be nil.')
       end
 
+      if @cryptogram.nil?
+        invalid_properties.push('invalid value for "cryptogram", cryptogram cannot be nil.')
+      end
+
+      if @security_code.nil?
+        invalid_properties.push('invalid value for "security_code", security_code cannot be nil.')
+      end
+
       if @number.nil?
         invalid_properties.push('invalid value for "number", number cannot be nil.')
       end
@@ -106,9 +136,12 @@ module CyberSource
     # Check to see if the all the properties in the model are valid
     # @return true if the model is valid
     def valid?
+      return false if @transaction_type.nil?
       return false if @type.nil?
       return false if @expiration_month.nil?
       return false if @expiration_year.nil?
+      return false if @cryptogram.nil?
+      return false if @security_code.nil?
       return false if @number.nil?
       true
     end
@@ -116,6 +149,10 @@ module CyberSource
     # Custom attribute writer method with validation
     # @param [Object] transaction_type Value to be assigned
     def transaction_type=(transaction_type)
+      if transaction_type.nil?
+        fail ArgumentError, 'transaction_type cannot be nil'
+      end
+
       @transaction_type = transaction_type
     end
 
@@ -139,6 +176,26 @@ module CyberSource
       @expiration_year = expiration_year
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] cryptogram Value to be assigned
+    def cryptogram=(cryptogram)
+      if cryptogram.nil?
+        fail ArgumentError, 'cryptogram cannot be nil'
+      end
+
+      @cryptogram = cryptogram
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] security_code Value to be assigned
+    def security_code=(security_code)
+      if security_code.nil?
+        fail ArgumentError, 'security_code cannot be nil'
+      end
+
+      @security_code = security_code
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] number Value to be assigned
     def number=(number)
@@ -158,6 +215,8 @@ module CyberSource
           type == o.type &&
           expiration_month == o.expiration_month &&
           expiration_year == o.expiration_year &&
+          cryptogram == o.cryptogram &&
+          security_code == o.security_code &&
           number == o.number
     end
 
@@ -170,7 +229,7 @@ module CyberSource
     # Calculates hash code according to all attributes.
     # @return [Fixnum] Hash code
     def hash
-      [transaction_type, type, expiration_month, expiration_year, number].hash
+      [transaction_type, type, expiration_month, expiration_year, cryptogram, security_code, number].hash
     end
 
     # Builds the object from hash

data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_tokenized_card.rb

@@ -14,7 +14,7 @@ require 'date'
 
 module CyberSource
   class Riskv1authenticationsetupsPaymentInformationTokenizedCard
-    # Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  #### Visa Platform Connect - `1`: In App tokenization. Example: InApp apple pay. - `3`: Card/Credential On File Tokenization.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
+    # 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
 
     # 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