Class: CyberSource::Ptsv2paymentsPaymentInformationTokenizedCard
- Inherits:
-
Object
- Object
- CyberSource::Ptsv2paymentsPaymentInformationTokenizedCard
- Defined in:
- lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb
Instance Attribute Summary collapse
-
#assurance_level ⇒ Object
Confidence level of the tokenization.
-
#cryptogram ⇒ Object
This field is used internally.
-
#expiration_month ⇒ Object
One of two possible meanings: - The two-digit month in which a token expires.
-
#expiration_year ⇒ Object
One of two possible meanings: - The four-digit year in which a token expires.
-
#number ⇒ Object
Customer’s payment network token value.
-
#requestor_id ⇒ Object
Value that identifies your business and indicates that the cardholder’s account number is tokenized.
-
#security_code ⇒ Object
Card Verification Number (CVN).
-
#storage_method ⇒ Object
Type of technology used in the device to store token data.
-
#transaction_type ⇒ Object
Type of transaction that provided the token data.
-
#type ⇒ Object
Three-digit value that indicates the card type.
Class Method Summary collapse
-
.attribute_map ⇒ Object
Attribute mapping from ruby-style variable name to JSON key.
-
.swagger_types ⇒ Object
Attribute type mapping.
Instance Method Summary collapse
-
#==(o) ⇒ Object
Checks equality by comparing each attribute.
-
#_deserialize(type, value) ⇒ Object
Deserializes the data based on type.
-
#_to_hash(value) ⇒ Hash
Outputs non-array value in the form of hash For object, use to_hash.
-
#build_from_hash(attributes) ⇒ Object
Builds the object from hash.
- #eql?(o) ⇒ Boolean
-
#hash ⇒ Fixnum
Calculates hash code according to all attributes.
-
#initialize(attributes = {}) ⇒ Ptsv2paymentsPaymentInformationTokenizedCard
constructor
Initializes the object.
-
#list_invalid_properties ⇒ Object
Show invalid properties with the reasons.
-
#to_body ⇒ Hash
to_body is an alias to to_hash (backward compatibility).
-
#to_hash ⇒ Hash
Returns the object in the form of hash.
-
#to_s ⇒ String
Returns the string representation of the object.
-
#valid? ⇒ Boolean
Check to see if the all the properties in the model are valid.
Constructor Details
#initialize(attributes = {}) ⇒ Ptsv2paymentsPaymentInformationTokenizedCard
Initializes the object
81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 81 def initialize(attributes = {}) return unless attributes.is_a?(Hash) # convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| h[k.to_sym] = v } if attributes.has_key?(:'number') self.number = attributes[:'number'] end if attributes.has_key?(:'expirationMonth') self.expiration_month = attributes[:'expirationMonth'] end if attributes.has_key?(:'expirationYear') self.expiration_year = attributes[:'expirationYear'] end if attributes.has_key?(:'type') self.type = attributes[:'type'] end if attributes.has_key?(:'cryptogram') self.cryptogram = attributes[:'cryptogram'] end if attributes.has_key?(:'requestorId') self.requestor_id = attributes[:'requestorId'] end if attributes.has_key?(:'transactionType') self.transaction_type = attributes[:'transactionType'] end if attributes.has_key?(:'assuranceLevel') self.assurance_level = attributes[:'assuranceLevel'] end if attributes.has_key?(:'storageMethod') self.storage_method = attributes[:'storageMethod'] end if attributes.has_key?(:'securityCode') self.security_code = attributes[:'securityCode'] end end |
Instance Attribute Details
#assurance_level ⇒ Object
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.
39 40 41 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 39 def assurance_level @assurance_level end |
#cryptogram ⇒ Object
This field is used internally.
30 31 32 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 30 def cryptogram @cryptogram end |
#expiration_month ⇒ Object
One of two possible meanings: - The two-digit month in which a token expires. - The two-digit month in which a card expires. Format: ‘MM` Possible values: `01` through `12` NOTE The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below. #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`01` through `12`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request. #### Encoded Account Numbers For encoded account numbers (`card_type=039`), if there is no expiration date on the card, use `12`.\ Important It is your responsibility to determine whether a field is required for the transaction you are requesting. #### Samsung Pay and Apple Pay Month in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction. For processor-specific information, see the `customer_cc_expmo` field in [Credit Card Services Using the SCMP API.](apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)
21 22 23 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 21 def expiration_month @expiration_month end |
#expiration_year ⇒ Object
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.](apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)
24 25 26 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 24 def expiration_year @expiration_year end |
#number ⇒ Object
Customer’s payment network token value.
18 19 20 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 18 def number @number end |
#requestor_id ⇒ Object
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.
33 34 35 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 33 def requestor_id @requestor_id end |
#security_code ⇒ Object
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.](apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)
45 46 47 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 45 def security_code @security_code end |
#storage_method ⇒ Object
Type of technology used in the device to store token data. Possible values: - ‘001`: Secure Element (SE). Smart card or memory with restricted access and encryption to prevent data tampering. For storing payment credentials, a SE is tested against a set of requirements defined by the payment networks. Note This field is supported only for _FDC Compass_. - 002: Host Card Emulation (HCE). Emulation of a smart card by using software to create a virtual and exact representation of the card. Sensitive data is stored in a database that is hosted in the cloud. For storing payment credentials, a database must meet very stringent security requirements that exceed PCI DSS. Note This field is supported only for _FDC Compass_.
42 43 44 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 42 def storage_method @storage_method end |
#transaction_type ⇒ Object
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.
36 37 38 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 36 def transaction_type @transaction_type end |
#type ⇒ Object
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, which is a European regional brand of Mastercard. - `003`: American Express - `004`: Discover - `005`: Diners Club - `006`: Carte Blanche - `007`: JCB - `014`: Enroute - `021`: JAL - `024`: Maestro (UK Domestic) - `031`: Delta: Use this value only for Ingenico ePayments. For other processors, use `001` for all Visa card types. - `033`: Visa Electron. Use this value only for Ingenico ePayments and SIX. For other processors, use `001` for all Visa card types. - `034`: Dankort - `036`: Cartes Bancaires - `037`: Carta Si - `039`: Encoded account number - `040`: UATP - `042`: Maestro (International) - `050`: Hipercard - `051`: Aura - `054`: Elo - `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
27 28 29 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 27 def type @type end |
Class Method Details
.attribute_map ⇒ Object
Attribute mapping from ruby-style variable name to JSON key.
48 49 50 51 52 53 54 55 56 57 58 59 60 61 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 48 def self.attribute_map { :'number' => :'number', :'expiration_month' => :'expirationMonth', :'expiration_year' => :'expirationYear', :'type' => :'type', :'cryptogram' => :'cryptogram', :'requestor_id' => :'requestorId', :'transaction_type' => :'transactionType', :'assurance_level' => :'assuranceLevel', :'storage_method' => :'storageMethod', :'security_code' => :'securityCode' } end |
.swagger_types ⇒ Object
Attribute type mapping.
64 65 66 67 68 69 70 71 72 73 74 75 76 77 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 64 def self.swagger_types { :'number' => :'String', :'expiration_month' => :'String', :'expiration_year' => :'String', :'type' => :'String', :'cryptogram' => :'String', :'requestor_id' => :'String', :'transaction_type' => :'String', :'assurance_level' => :'String', :'storage_method' => :'String', :'security_code' => :'String' } end |
Instance Method Details
#==(o) ⇒ Object
Checks equality by comparing each attribute.
197 198 199 200 201 202 203 204 205 206 207 208 209 210 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 197 def ==(o) return true if self.equal?(o) self.class == o.class && number == o.number && expiration_month == o.expiration_month && expiration_year == o.expiration_year && type == o.type && cryptogram == o.cryptogram && requestor_id == o.requestor_id && transaction_type == o.transaction_type && assurance_level == o.assurance_level && storage_method == o.storage_method && security_code == o.security_code end |
#_deserialize(type, value) ⇒ Object
Deserializes the data based on type
248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 248 def _deserialize(type, value) case type.to_sym when :DateTime DateTime.parse(value) when :Date Date.parse(value) when :String value.to_s when :Integer value.to_i when :Float value.to_f when :BOOLEAN if value.to_s =~ /\A(true|t|yes|y|1)\z/i true else false end when :Object # generic object (usually a Hash), return directly value when /\AArray<(?<inner_type>.+)>\z/ inner_type = Regexp.last_match[:inner_type] value.map { |v| _deserialize(inner_type, v) } when /\AHash<(?<k_type>.+?), (?<v_type>.+)>\z/ k_type = Regexp.last_match[:k_type] v_type = Regexp.last_match[:v_type] {}.tap do |hash| value.each do |k, v| hash[_deserialize(k_type, k)] = _deserialize(v_type, v) end end else # model temp_model = CyberSource.const_get(type).new temp_model.build_from_hash(value) end end |
#_to_hash(value) ⇒ Hash
Outputs non-array value in the form of hash For object, use to_hash. Otherwise, just return the value
314 315 316 317 318 319 320 321 322 323 324 325 326 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 314 def _to_hash(value) if value.is_a?(Array) value.compact.map { |v| _to_hash(v) } elsif value.is_a?(Hash) {}.tap do |hash| value.each { |k, v| hash[k] = _to_hash(v) } end elsif value.respond_to? :to_hash value.to_hash else value end end |
#build_from_hash(attributes) ⇒ Object
Builds the object from hash
227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 227 def build_from_hash(attributes) return nil unless attributes.is_a?(Hash) self.class.swagger_types.each_pair do |key, type| if type =~ /\AArray<(.*)>/i # check to ensure the input is an array given that the the attribute # is documented as an array but the input is not if attributes[self.class.attribute_map[key]].is_a?(Array) self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) }) end elsif !attributes[self.class.attribute_map[key]].nil? self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]])) end # or else data not found in attributes(hash), not an issue as the data can be optional end self end |
#eql?(o) ⇒ Boolean
214 215 216 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 214 def eql?(o) self == o end |
#hash ⇒ Fixnum
Calculates hash code according to all attributes.
220 221 222 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 220 def hash [number, expiration_month, expiration_year, type, cryptogram, requestor_id, transaction_type, assurance_level, storage_method, security_code].hash end |
#list_invalid_properties ⇒ Object
Show invalid properties with the reasons. Usually used together with valid?
130 131 132 133 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 130 def list_invalid_properties invalid_properties = Array.new invalid_properties end |
#to_body ⇒ Hash
to_body is an alias to to_hash (backward compatibility)
294 295 296 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 294 def to_body to_hash end |
#to_hash ⇒ Hash
Returns the object in the form of hash
300 301 302 303 304 305 306 307 308 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 300 def to_hash hash = {} self.class.attribute_map.each_pair do |attr, param| value = self.send(attr) next if value.nil? hash[param] = _to_hash(value) end hash end |
#to_s ⇒ String
Returns the string representation of the object
288 289 290 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 288 def to_s to_hash.to_s end |
#valid? ⇒ Boolean
Check to see if the all the properties in the model are valid
137 138 139 |
# File 'lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb', line 137 def valid? true end |