cybersource_rest_client 0.0.32 → 0.0.33

Sign up to get free protection for your applications and to get access to all the features.
Files changed (28) hide show
  1. checksums.yaml +4 -4
  2. data/lib/cybersource_rest_client.rb +2 -1
  3. data/lib/cybersource_rest_client/api/payments_api.rb +2 -2
  4. data/lib/cybersource_rest_client/api/refund_api.rb +4 -4
  5. data/lib/cybersource_rest_client/api/void_api.rb +4 -4
  6. data/lib/cybersource_rest_client/models/invoicing_v2_invoices_all_get200_response_customer_information.rb +20 -4
  7. data/lib/cybersource_rest_client/models/invoicingv2invoices_customer_information.rb +20 -4
  8. data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response.rb +10 -1
  9. data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_account_information.rb +183 -0
  10. data/lib/cybersource_rest_client/models/{pts_v2_payments_post201_response_payment_information_card.rb → pts_v2_payments_post201_response_payment_account_information_card.rb} +1 -1
  11. data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information.rb +1 -1
  12. data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_processing_information.rb +1 -1
  13. data/lib/cybersource_rest_client/models/pts_v2_payouts_post201_response_merchant_information_merchant_descriptor.rb +6 -0
  14. data/lib/cybersource_rest_client/models/ptsv2credits_processing_information.rb +1 -1
  15. data/lib/cybersource_rest_client/models/ptsv2payments_merchant_information_merchant_descriptor.rb +6 -0
  16. data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_fluid_data.rb +3 -3
  17. data/lib/cybersource_rest_client/models/ptsv2payments_point_of_sale_information.rb +36 -38
  18. data/lib/cybersource_rest_client/models/ptsv2payments_processing_information.rb +1 -1
  19. data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_processing_information.rb +1 -1
  20. data/lib/cybersource_rest_client/models/ptsv2paymentsidrefunds_processing_information.rb +1 -1
  21. data/lib/cybersource_rest_client/models/ptsv2paymentsidreversals_processing_information.rb +1 -1
  22. data/lib/cybersource_rest_client/models/ptsv2payouts_merchant_information_merchant_descriptor.rb +6 -0
  23. data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_fluid_data.rb +3 -3
  24. data/lib/cybersource_rest_client/models/riskv1authenticationsetups_processing_information.rb +1 -1
  25. data/lib/cybersource_rest_client/models/riskv1decisions_device_information.rb +1 -11
  26. data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processing_information_authorization_options.rb +13 -4
  27. data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_processing_information.rb +1 -1
  28. metadata +4 -3
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 6e87a4cdca2fcacb354ce0a8d584c1dcea1f2cac2802569f97f0ad7c7e57eaa2
4
- data.tar.gz: 5475dff47053b81d0650127fd18557999f87119eb95bd52b15b58c13f28c99c1
3
+ metadata.gz: 24ef8c5c250397dd132257948c7593810309c5e98c737b3f0b49cd816cb2cae3
4
+ data.tar.gz: bc1876ffa7d0dedc87fdf4056d944a7b6d21a07593b94bc7e93921c9ca202de8
5
5
  SHA512:
6
- metadata.gz: 36636bfb53cfdca034d0b71a2df218f7b69614572050f07a8bd470f27e0c945591e60cc35f177514ad82ac22d13af3589c6fe7e391003d96cba52907c017029c
7
- data.tar.gz: f6821f4da200bc7b1128eeba394d13107253e370d8422498b56c23640c0617f90df7a230fb5e265d0d24c24d0f9d710e12ec704b56f0c977a41ad860f3e2c43a
6
+ metadata.gz: 1d7defc6a9a4ffdcd3b2e60c5d6d95e293e42fdf7b3b8b56025aaa49faa025290de080bfc789cc4731ed9d13083a1bd8b37b9a61328cb14ab60069c3611953bd
7
+ data.tar.gz: 9d916792b1fa803359cd2591350685d7bb895a991fe35ad68ccefd7ad6ed370f82b384e9e1ce52f212a59d603eb80571411d1613db1b029dd3613293dcca64ef
@@ -194,12 +194,13 @@ require 'cybersource_rest_client/models/pts_v2_payments_post201_response_order_i
194
194
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_order_information_amount_details'
195
195
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_order_information_invoice_details'
196
196
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_order_information_reward_points_details'
197
+ require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_account_information'
198
+ require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_account_information_card'
197
199
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information'
198
200
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_account_features'
199
201
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_account_features_balances'
200
202
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_bank'
201
203
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_bank_account'
202
- require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_card'
203
204
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_instrument_identifier'
204
205
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_tokenized_card'
205
206
  require 'cybersource_rest_client/models/pts_v2_payments_post201_response_point_of_sale_information'
@@ -21,7 +21,7 @@ module CyberSource
21
21
  @api_client.set_configuration(config)
22
22
  end
23
23
  # Process a Payment
24
- # A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/api/developer-guides/dita-payments/GettingStarted.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation. Find more on [Authorization with Add-On Features page.] (https://developer.cybersource.com/api/authorization-add-ons.html) Possible [RESPONSE CODES](https://developer.cybersource.com/api/reference/response-codes.html) . Processor specific [Testing Triggers](https://developer.cybersource.com/hello-world/testing-guide.html).
24
+ # A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/api/developer-guides/dita-payments/GettingStarted.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation. Find more on [Authorization with Add-On Features page.](https://developer.cybersource.com/api/authorization-add-ons.html)
25
25
  # @param create_payment_request
26
26
  # @param [Hash] opts the optional parameters
27
27
  # @return [PtsV2PaymentsPost201Response]
@@ -31,7 +31,7 @@ module CyberSource
31
31
  end
32
32
 
33
33
  # Process a Payment
34
- # A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/api/developer-guides/dita-payments/GettingStarted.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation. Find more on [Authorization with Add-On Features page.] (https://developer.cybersource.com/api/authorization-add-ons.html) Possible [RESPONSE CODES](https://developer.cybersource.com/api/reference/response-codes.html) . Processor specific [Testing Triggers](https://developer.cybersource.com/hello-world/testing-guide.html).
34
+ # A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/api/developer-guides/dita-payments/GettingStarted.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation. Find more on [Authorization with Add-On Features page.](https://developer.cybersource.com/api/authorization-add-ons.html)
35
35
  # @param create_payment_request
36
36
  # @param [Hash] opts the optional parameters
37
37
  # @return [Array<(PtsV2PaymentsPost201Response, Fixnum, Hash)>] PtsV2PaymentsPost201Response data, response status code and response headers
@@ -21,7 +21,7 @@ module CyberSource
21
21
  @api_client.set_configuration(config)
22
22
  end
23
23
  # Refund a Capture
24
- # Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call Include the capture ID in the POST request to refund the captured amount.
24
+ # Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to refund the captured amount.
25
25
  # @param refund_capture_request
26
26
  # @param id The capture ID. This ID is returned from a previous capture request.
27
27
  # @param [Hash] opts the optional parameters
@@ -32,7 +32,7 @@ module CyberSource
32
32
  end
33
33
 
34
34
  # Refund a Capture
35
- # Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call Include the capture ID in the POST request to refund the captured amount.
35
+ # Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to refund the captured amount.
36
36
  # @param refund_capture_request
37
37
  # @param id The capture ID. This ID is returned from a previous capture request.
38
38
  # @param [Hash] opts the optional parameters
@@ -92,7 +92,7 @@ module CyberSource
92
92
  return data, status_code, headers
93
93
  end
94
94
  # Refund a Payment
95
- # Refund a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to refund the payment amount.
95
+ # Refund a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to refund the payment amount.
96
96
  # @param refund_payment_request
97
97
  # @param id The payment ID. This ID is returned from a previous payment request.
98
98
  # @param [Hash] opts the optional parameters
@@ -103,7 +103,7 @@ module CyberSource
103
103
  end
104
104
 
105
105
  # Refund a Payment
106
- # Refund a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to refund the payment amount.
106
+ # Refund a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to refund the payment amount.
107
107
  # @param refund_payment_request
108
108
  # @param id The payment ID. This ID is returned from a previous payment request.
109
109
  # @param [Hash] opts the optional parameters
@@ -86,7 +86,7 @@ module CyberSource
86
86
  return data, status_code, headers
87
87
  end
88
88
  # Void a Capture
89
- # Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to cancel the capture.
89
+ # Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to cancel the capture.
90
90
  # @param void_capture_request
91
91
  # @param id The capture ID returned from a previous capture request.
92
92
  # @param [Hash] opts the optional parameters
@@ -97,7 +97,7 @@ module CyberSource
97
97
  end
98
98
 
99
99
  # Void a Capture
100
- # Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to cancel the capture.
100
+ # Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to cancel the capture.
101
101
  # @param void_capture_request
102
102
  # @param id The capture ID returned from a previous capture request.
103
103
  # @param [Hash] opts the optional parameters
@@ -228,7 +228,7 @@ module CyberSource
228
228
  return data, status_code, headers
229
229
  end
230
230
  # Void a Payment
231
- # Void a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to cancel the payment.
231
+ # Void a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to cancel the payment.
232
232
  # @param void_payment_request
233
233
  # @param id The payment ID returned from a previous payment request.
234
234
  # @param [Hash] opts the optional parameters
@@ -239,7 +239,7 @@ module CyberSource
239
239
  end
240
240
 
241
241
  # Void a Payment
242
- # Void a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to cancel the payment.
242
+ # Void a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to cancel the payment.
243
243
  # @param void_payment_request
244
244
  # @param id The payment ID returned from a previous payment request.
245
245
  # @param [Hash] opts the optional parameters
@@ -17,17 +17,22 @@ module CyberSource
17
17
  # Payer name for the invoice.
18
18
  attr_accessor :name
19
19
 
20
+ # Your identifier for the customer. When a subscription or customer profile is being created, the maximum length for this field for most processors is 30. Otherwise, the maximum length is 100. #### Comercio Latino For recurring payments in Mexico, the value is the customer’s contract number. Note Before you request the authorization, you must inform the issuer of the customer contract numbers that will be used for recurring transactions. #### Worldpay VAP For a follow-on credit with Worldpay VAP, CyberSource checks the following locations, in the order given, for a customer account ID value and uses the first value it finds: 1. `customer_account_id` value in the follow-on credit request 2. Customer account ID value that was used for the capture that is being credited 3. Customer account ID value that was used for the original authorization If a customer account ID value cannot be found in any of these locations, then no value is used. For processor-specific information, see the `customer_account_id` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)
21
+ attr_accessor :merchant_customer_id
22
+
20
23
  # Attribute mapping from ruby-style variable name to JSON key.
21
24
  def self.attribute_map
22
25
  {
23
- :'name' => :'name'
26
+ :'name' => :'name',
27
+ :'merchant_customer_id' => :'merchantCustomerId'
24
28
  }
25
29
  end
26
30
 
27
31
  # Attribute type mapping.
28
32
  def self.swagger_types
29
33
  {
30
- :'name' => :'String'
34
+ :'name' => :'String',
35
+ :'merchant_customer_id' => :'String'
31
36
  }
32
37
  end
33
38
 
@@ -42,6 +47,10 @@ module CyberSource
42
47
  if attributes.has_key?(:'name')
43
48
  self.name = attributes[:'name']
44
49
  end
50
+
51
+ if attributes.has_key?(:'merchantCustomerId')
52
+ self.merchant_customer_id = attributes[:'merchantCustomerId']
53
+ end
45
54
  end
46
55
 
47
56
  # Show invalid properties with the reasons. Usually used together with valid?
@@ -63,12 +72,19 @@ module CyberSource
63
72
  @name = name
64
73
  end
65
74
 
75
+ # Custom attribute writer method with validation
76
+ # @param [Object] merchant_customer_id Value to be assigned
77
+ def merchant_customer_id=(merchant_customer_id)
78
+ @merchant_customer_id = merchant_customer_id
79
+ end
80
+
66
81
  # Checks equality by comparing each attribute.
67
82
  # @param [Object] Object to be compared
68
83
  def ==(o)
69
84
  return true if self.equal?(o)
70
85
  self.class == o.class &&
71
- name == o.name
86
+ name == o.name &&
87
+ merchant_customer_id == o.merchant_customer_id
72
88
  end
73
89
 
74
90
  # @see the `==` method
@@ -80,7 +96,7 @@ module CyberSource
80
96
  # Calculates hash code according to all attributes.
81
97
  # @return [Fixnum] Hash code
82
98
  def hash
83
- [name].hash
99
+ [name, merchant_customer_id].hash
84
100
  end
85
101
 
86
102
  # Builds the object from hash
@@ -21,11 +21,15 @@ module CyberSource
21
21
  # Customer's email address, including the full domain name. #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks. **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_email` request-level field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) #### Invoicing Email address for the customer for sending the invoice. If the invoice is in SENT status and email is updated, the old email customer payment link won't work and you must resend the invoice with the new payment link. #### Chase Paymentech Solutions Optional field. #### Credit Mutuel-CIC Optional field. #### OmniPay Direct Optional field. #### SIX Optional field. #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`. #### Worldpay VAP Optional field. #### All other processors Not used.
22
22
  attr_accessor :email
23
23
 
24
+ # Your identifier for the customer. When a subscription or customer profile is being created, the maximum length for this field for most processors is 30. Otherwise, the maximum length is 100. #### Comercio Latino For recurring payments in Mexico, the value is the customer’s contract number. Note Before you request the authorization, you must inform the issuer of the customer contract numbers that will be used for recurring transactions. #### Worldpay VAP For a follow-on credit with Worldpay VAP, CyberSource checks the following locations, in the order given, for a customer account ID value and uses the first value it finds: 1. `customer_account_id` value in the follow-on credit request 2. Customer account ID value that was used for the capture that is being credited 3. Customer account ID value that was used for the original authorization If a customer account ID value cannot be found in any of these locations, then no value is used. For processor-specific information, see the `customer_account_id` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)
25
+ attr_accessor :merchant_customer_id
26
+
24
27
  # Attribute mapping from ruby-style variable name to JSON key.
25
28
  def self.attribute_map
26
29
  {
27
30
  :'name' => :'name',
28
- :'email' => :'email'
31
+ :'email' => :'email',
32
+ :'merchant_customer_id' => :'merchantCustomerId'
29
33
  }
30
34
  end
31
35
 
@@ -33,7 +37,8 @@ module CyberSource
33
37
  def self.swagger_types
34
38
  {
35
39
  :'name' => :'String',
36
- :'email' => :'String'
40
+ :'email' => :'String',
41
+ :'merchant_customer_id' => :'String'
37
42
  }
38
43
  end
39
44
 
@@ -52,6 +57,10 @@ module CyberSource
52
57
  if attributes.has_key?(:'email')
53
58
  self.email = attributes[:'email']
54
59
  end
60
+
61
+ if attributes.has_key?(:'merchantCustomerId')
62
+ self.merchant_customer_id = attributes[:'merchantCustomerId']
63
+ end
55
64
  end
56
65
 
57
66
  # Show invalid properties with the reasons. Usually used together with valid?
@@ -79,13 +88,20 @@ module CyberSource
79
88
  @email = email
80
89
  end
81
90
 
91
+ # Custom attribute writer method with validation
92
+ # @param [Object] merchant_customer_id Value to be assigned
93
+ def merchant_customer_id=(merchant_customer_id)
94
+ @merchant_customer_id = merchant_customer_id
95
+ end
96
+
82
97
  # Checks equality by comparing each attribute.
83
98
  # @param [Object] Object to be compared
84
99
  def ==(o)
85
100
  return true if self.equal?(o)
86
101
  self.class == o.class &&
87
102
  name == o.name &&
88
- email == o.email
103
+ email == o.email &&
104
+ merchant_customer_id == o.merchant_customer_id
89
105
  end
90
106
 
91
107
  # @see the `==` method
@@ -97,7 +113,7 @@ module CyberSource
97
113
  # Calculates hash code according to all attributes.
98
114
  # @return [Fixnum] Hash code
99
115
  def hash
100
- [name, email].hash
116
+ [name, email, merchant_customer_id].hash
101
117
  end
102
118
 
103
119
  # Builds the object from hash
@@ -38,6 +38,8 @@ module CyberSource
38
38
 
39
39
  attr_accessor :issuer_information
40
40
 
41
+ attr_accessor :payment_account_information
42
+
41
43
  attr_accessor :payment_information
42
44
 
43
45
  attr_accessor :order_information
@@ -65,6 +67,7 @@ module CyberSource
65
67
  :'processing_information' => :'processingInformation',
66
68
  :'processor_information' => :'processorInformation',
67
69
  :'issuer_information' => :'issuerInformation',
70
+ :'payment_account_information' => :'paymentAccountInformation',
68
71
  :'payment_information' => :'paymentInformation',
69
72
  :'order_information' => :'orderInformation',
70
73
  :'point_of_sale_information' => :'pointOfSaleInformation',
@@ -88,6 +91,7 @@ module CyberSource
88
91
  :'processing_information' => :'PtsV2PaymentsPost201ResponseProcessingInformation',
89
92
  :'processor_information' => :'PtsV2PaymentsPost201ResponseProcessorInformation',
90
93
  :'issuer_information' => :'PtsV2PaymentsPost201ResponseIssuerInformation',
94
+ :'payment_account_information' => :'PtsV2PaymentsPost201ResponsePaymentAccountInformation',
91
95
  :'payment_information' => :'PtsV2PaymentsPost201ResponsePaymentInformation',
92
96
  :'order_information' => :'PtsV2PaymentsPost201ResponseOrderInformation',
93
97
  :'point_of_sale_information' => :'PtsV2PaymentsPost201ResponsePointOfSaleInformation',
@@ -146,6 +150,10 @@ module CyberSource
146
150
  self.issuer_information = attributes[:'issuerInformation']
147
151
  end
148
152
 
153
+ if attributes.has_key?(:'paymentAccountInformation')
154
+ self.payment_account_information = attributes[:'paymentAccountInformation']
155
+ end
156
+
149
157
  if attributes.has_key?(:'paymentInformation')
150
158
  self.payment_information = attributes[:'paymentInformation']
151
159
  end
@@ -215,6 +223,7 @@ module CyberSource
215
223
  processing_information == o.processing_information &&
216
224
  processor_information == o.processor_information &&
217
225
  issuer_information == o.issuer_information &&
226
+ payment_account_information == o.payment_account_information &&
218
227
  payment_information == o.payment_information &&
219
228
  order_information == o.order_information &&
220
229
  point_of_sale_information == o.point_of_sale_information &&
@@ -233,7 +242,7 @@ module CyberSource
233
242
  # Calculates hash code according to all attributes.
234
243
  # @return [Fixnum] Hash code
235
244
  def hash
236
- [_links, id, submit_time_utc, status, reconciliation_id, error_information, client_reference_information, processing_information, processor_information, issuer_information, payment_information, order_information, point_of_sale_information, installment_information, token_information, risk_information, consumer_authentication_information].hash
245
+ [_links, id, submit_time_utc, status, reconciliation_id, error_information, client_reference_information, processing_information, processor_information, issuer_information, payment_account_information, payment_information, order_information, point_of_sale_information, installment_information, token_information, risk_information, consumer_authentication_information].hash
237
246
  end
238
247
 
239
248
  # Builds the object from hash
@@ -0,0 +1,183 @@
1
+ =begin
2
+ #CyberSource Merged Spec
3
+
4
+ #All CyberSource API specs merged together. These are available at https://developer.cybersource.com/api/reference/api-reference.html
5
+
6
+ OpenAPI spec version: 0.0.1
7
+
8
+ Generated by: https://github.com/swagger-api/swagger-codegen.git
9
+ Swagger Codegen version: 2.2.3
10
+
11
+ =end
12
+
13
+ require 'date'
14
+
15
+ module CyberSource
16
+ class PtsV2PaymentsPost201ResponsePaymentAccountInformation
17
+ attr_accessor :card
18
+
19
+ # Attribute mapping from ruby-style variable name to JSON key.
20
+ def self.attribute_map
21
+ {
22
+ :'card' => :'card'
23
+ }
24
+ end
25
+
26
+ # Attribute type mapping.
27
+ def self.swagger_types
28
+ {
29
+ :'card' => :'PtsV2PaymentsPost201ResponsePaymentAccountInformationCard'
30
+ }
31
+ end
32
+
33
+ # Initializes the object
34
+ # @param [Hash] attributes Model attributes in the form of hash
35
+ def initialize(attributes = {})
36
+ return unless attributes.is_a?(Hash)
37
+
38
+ # convert string to symbol for hash key
39
+ attributes = attributes.each_with_object({}) { |(k, v), h| h[k.to_sym] = v }
40
+
41
+ if attributes.has_key?(:'card')
42
+ self.card = attributes[:'card']
43
+ end
44
+ end
45
+
46
+ # Show invalid properties with the reasons. Usually used together with valid?
47
+ # @return Array for valid properties with the reasons
48
+ def list_invalid_properties
49
+ invalid_properties = Array.new
50
+ invalid_properties
51
+ end
52
+
53
+ # Check to see if the all the properties in the model are valid
54
+ # @return true if the model is valid
55
+ def valid?
56
+ true
57
+ end
58
+
59
+ # Checks equality by comparing each attribute.
60
+ # @param [Object] Object to be compared
61
+ def ==(o)
62
+ return true if self.equal?(o)
63
+ self.class == o.class &&
64
+ card == o.card
65
+ end
66
+
67
+ # @see the `==` method
68
+ # @param [Object] Object to be compared
69
+ def eql?(o)
70
+ self == o
71
+ end
72
+
73
+ # Calculates hash code according to all attributes.
74
+ # @return [Fixnum] Hash code
75
+ def hash
76
+ [card].hash
77
+ end
78
+
79
+ # Builds the object from hash
80
+ # @param [Hash] attributes Model attributes in the form of hash
81
+ # @return [Object] Returns the model itself
82
+ def build_from_hash(attributes)
83
+ return nil unless attributes.is_a?(Hash)
84
+ self.class.swagger_types.each_pair do |key, type|
85
+ if type =~ /\AArray<(.*)>/i
86
+ # check to ensure the input is an array given that the the attribute
87
+ # is documented as an array but the input is not
88
+ if attributes[self.class.attribute_map[key]].is_a?(Array)
89
+ self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) })
90
+ end
91
+ elsif !attributes[self.class.attribute_map[key]].nil?
92
+ self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]]))
93
+ end # or else data not found in attributes(hash), not an issue as the data can be optional
94
+ end
95
+
96
+ self
97
+ end
98
+
99
+ # Deserializes the data based on type
100
+ # @param string type Data type
101
+ # @param string value Value to be deserialized
102
+ # @return [Object] Deserialized data
103
+ def _deserialize(type, value)
104
+ case type.to_sym
105
+ when :DateTime
106
+ DateTime.parse(value)
107
+ when :Date
108
+ Date.parse(value)
109
+ when :String
110
+ value.to_s
111
+ when :Integer
112
+ value.to_i
113
+ when :Float
114
+ value.to_f
115
+ when :BOOLEAN
116
+ if value.to_s =~ /\A(true|t|yes|y|1)\z/i
117
+ true
118
+ else
119
+ false
120
+ end
121
+ when :Object
122
+ # generic object (usually a Hash), return directly
123
+ value
124
+ when /\AArray<(?<inner_type>.+)>\z/
125
+ inner_type = Regexp.last_match[:inner_type]
126
+ value.map { |v| _deserialize(inner_type, v) }
127
+ when /\AHash<(?<k_type>.+?), (?<v_type>.+)>\z/
128
+ k_type = Regexp.last_match[:k_type]
129
+ v_type = Regexp.last_match[:v_type]
130
+ {}.tap do |hash|
131
+ value.each do |k, v|
132
+ hash[_deserialize(k_type, k)] = _deserialize(v_type, v)
133
+ end
134
+ end
135
+ else # model
136
+ temp_model = CyberSource.const_get(type).new
137
+ temp_model.build_from_hash(value)
138
+ end
139
+ end
140
+
141
+ # Returns the string representation of the object
142
+ # @return [String] String presentation of the object
143
+ def to_s
144
+ to_hash.to_s
145
+ end
146
+
147
+ # to_body is an alias to to_hash (backward compatibility)
148
+ # @return [Hash] Returns the object in the form of hash
149
+ def to_body
150
+ to_hash
151
+ end
152
+
153
+ # Returns the object in the form of hash
154
+ # @return [Hash] Returns the object in the form of hash
155
+ def to_hash
156
+ hash = {}
157
+ self.class.attribute_map.each_pair do |attr, param|
158
+ value = self.send(attr)
159
+ next if value.nil?
160
+ hash[param] = _to_hash(value)
161
+ end
162
+ hash
163
+ end
164
+
165
+ # Outputs non-array value in the form of hash
166
+ # For object, use to_hash. Otherwise, just return the value
167
+ # @param [Object] value Any valid value
168
+ # @return [Hash] Returns the value in the form of hash
169
+ def _to_hash(value)
170
+ if value.is_a?(Array)
171
+ value.compact.map { |v| _to_hash(v) }
172
+ elsif value.is_a?(Hash)
173
+ {}.tap do |hash|
174
+ value.each { |k, v| hash[k] = _to_hash(v) }
175
+ end
176
+ elsif value.respond_to? :to_hash
177
+ value.to_hash
178
+ else
179
+ value
180
+ end
181
+ end
182
+ end
183
+ end
@@ -13,7 +13,7 @@ Swagger Codegen version: 2.2.3
13
13
  require 'date'
14
14
 
15
15
  module CyberSource
16
- class PtsV2PaymentsPost201ResponsePaymentInformationCard
16
+ class PtsV2PaymentsPost201ResponsePaymentAccountInformationCard
17
17
  # Last four digits of the cardholder’s account number. 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. #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response. #### PIN debit This field is returned only for tokenized transactions. You can use this value on the receipt that you give to the cardholder. Returned by PIN debit credit and PIN debit purchase. This field is supported only by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX
18
18
  attr_accessor :suffix
19
19
 
@@ -67,7 +67,7 @@ module CyberSource
67
67
  # Attribute type mapping.
68
68
  def self.swagger_types
69
69
  {
70
- :'card' => :'PtsV2PaymentsPost201ResponsePaymentInformationCard',
70
+ :'card' => :'PtsV2PaymentsPost201ResponsePaymentAccountInformationCard',
71
71
  :'tokenized_card' => :'PtsV2PaymentsPost201ResponsePaymentInformationTokenizedCard',
72
72
  :'account_features' => :'PtsV2PaymentsPost201ResponsePaymentInformationAccountFeatures',
73
73
  :'bank' => :'PtsV2PaymentsPost201ResponsePaymentInformationBank',
@@ -16,7 +16,7 @@ module CyberSource
16
16
  class PtsV2PaymentsPost201ResponseProcessingInformation
17
17
  attr_accessor :bank_transfer_options
18
18
 
19
- # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
19
+ # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `027`: Click to Pay.
20
20
  attr_accessor :payment_solution
21
21
 
22
22
  # The possible values for the reply field are: - `true` : the airline data was included in the request to the processor. - `false` : the airline data was not included in the request to the processor. Returned by authorization, capture, or credit services.
@@ -81,6 +81,12 @@ module CyberSource
81
81
  @locality = locality
82
82
  end
83
83
 
84
+ # Custom attribute writer method with validation
85
+ # @param [Object] country Value to be assigned
86
+ def country=(country)
87
+ @country = country
88
+ end
89
+
84
90
  # Checks equality by comparing each attribute.
85
91
  # @param [Object] Object to be compared
86
92
  def ==(o)
@@ -20,7 +20,7 @@ module CyberSource
20
20
  # Value that identifies the processor/acquirer to use for the transaction. This value is supported only for **CyberSource through VisaNet**. Contact CyberSource Customer Support to get the value for this field.
21
21
  attr_accessor :processor_id
22
22
 
23
- # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
23
+ # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `027`: Click to Pay.
24
24
  attr_accessor :payment_solution
25
25
 
26
26
  # Please check with Cybersource customer support to see if your merchant account is configured correctly so you can include this field in your request. * For Payouts: max length for FDCCompass is String (22).
@@ -162,6 +162,12 @@ module CyberSource
162
162
  @locality = locality
163
163
  end
164
164
 
165
+ # Custom attribute writer method with validation
166
+ # @param [Object] country Value to be assigned
167
+ def country=(country)
168
+ @country = country
169
+ end
170
+
165
171
  # Custom attribute writer method with validation
166
172
  # @param [Object] postal_code Value to be assigned
167
173
  def postal_code=(postal_code)
@@ -17,13 +17,13 @@ module CyberSource
17
17
  # The encoded or encrypted value that a payment solution returns for an authorization request. For details about the valid values for a key, see [Creating an Online Authorization](https://developer.cybersource.com/api/developer-guides/dita-payments/CreatingOnlineAuth.html)
18
18
  attr_accessor :key_serial_number
19
19
 
20
- # The identifier for a payment solution, which is sending the encrypted payment data for decryption. Valid values: - Samsung Pay: `RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ=` **Note**: For other payment solutions, the value may be specific to the customer's mobile device. For example, the descriptor for a Bluefin payment encryption would be a device-generated descriptor. #### Used by **Authorization and Standalone Credits** Required for authorizations and standalone credits that use Bluefin PCI P2PE. #### Card Present processing Format of the encrypted payment data. The value for Bluefin PCI P2PE is `Ymx1ZWZpbg==`. Base64 format only. The value for Cybersource P2PE decryption is as follows: `RklEPUVNVi5QQVlNRU5ULkFQSQ==` if `paymentInformation.fluidData.encoding` is \"HEX\" `4649443D454D562E5041594D454E542E415049` if `paymentInformation.fluidData.encoding` is \"base64\"
20
+ # The identifier for a payment solution, which is sending the encrypted payment data for decryption. Valid values: Samsung Pay: RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ= Note: For other payment solutions, the value may be specific to the terminal or device initiatinf the payment. For example, the descriptor for a Bluefin payment encryption would be a device-generated descriptor. Used by Authorization and Standalone Credits. Required for authorizations and standalone credits. Card Present processing: Format of the encrypted payment data. The value for Bluefin PCI P2PE is `Ymx1ZWZpbg==`. paymentInformation.fluidData.encoding must be \"Base64\". The value for Cybersource P2PE decryption depends on the encoding method used and identified in encoding field. If paymentInformation.fluidData.encoding is `Base64`, the value is: `RklEPUVNVi5QQVlNRU5ULkFQSQ==` If paymentInformation.fluidData.encoding is `HEX`, the value is: `4649443D454D562E5041594D454E542E41504`
21
21
  attr_accessor :descriptor
22
22
 
23
- # Represents the encrypted payment data BLOB. The entry for this field is dependent on the payment solution a merchant uses. #### Used by **Authorization and Standalone Credits** Required for authorizations and standalone credits that use Bluefin PCI P2PE. #### Card Present processing This field represents the encrypted Bluefin PCI P2PE payment data. Obtain the encrypted payment data from a Bluefin-supported device.
23
+ # Represents the encrypted payment data BLOB. The entry for this field is dependent on the payment solution used by the merchant. Used by Authorization and Standalone Credits. Required for authorizations and standalone credits that use a Cybersource suppored Point-to-Point encryption method. Card Present processing This field represents the encrypted payment data generated by the payment terminal/device.
24
24
  attr_accessor :value
25
25
 
26
- # Encoding method used to encrypt the payment data. Valid value: Base64
26
+ # Encoding method used to encrypt the payment data. Valid values: `Base64`, `HEX`
27
27
  attr_accessor :encoding
28
28
 
29
29
  # Attribute mapping from ruby-style variable name to JSON key.
@@ -32,9 +32,6 @@ module CyberSource
32
32
  # POS terminal’s capability. Possible values: - `1`: Terminal has a magnetic stripe reader only. - `2`: Terminal has a magnetic stripe reader and manual entry capability. - `3`: Terminal has manual entry capability only. - `4`: Terminal can read chip cards. - `5`: Terminal can read contactless chip cards; cannot use contact to read chip cards. For an EMV transaction, the value of this field must be `4` or `5`. #### PIN debit Required for PIN debit purchase and PIN debit credit request. #### Used by **Authorization** Required for the following processors: - American Express Direct - Chase Paymentech Solutions - Credit Mutuel-CIC - FDC Nashville Global - FDMS Nashville - OmniPay Direct - SIX - Worldpay VAP Optional for the following processors: - CyberSource through VisaNet - GPN - GPX - JCN Gateway - RBS WorldPay Atlanta - TSYS Acquiring Solutions
33
33
  attr_accessor :terminal_capability
34
34
 
35
- # A one-digit code that identifies the capability of terminal to capture PINs. This code does not necessarily mean that a PIN was entered or is included in this message. For Payouts: This field is applicable for CtV. For details, see the `terminal_pin_capability` field description in [Card-Present Processing Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/Retail_SCMP_API/html/)
36
- attr_accessor :pin_entry_capability
37
-
38
35
  # Operating environment. Possible values for all card types except Mastercard: - `0`: No terminal used or unknown environment. - `1`: On merchant premises, attended. - `2`: On merchant premises, unattended. Examples: oil, kiosks, self-checkout, mobile telephone, personal digital assistant (PDA). - `3`: Off merchant premises, attended. Examples: portable POS devices at trade shows, at service calls, or in taxis. - `4`: Off merchant premises, unattended. Examples: vending machines, home computer, mobile telephone, PDA. - `5`: On premises of cardholder, unattended. - `9`: Unknown delivery mode. - `S`: Electronic delivery of product. Examples: music, software, or eTickets that are downloaded over the internet. - `T`: Physical delivery of product. Examples: music or software that is delivered by mail or by a courier. #### Possible values for Mastercard: - `2`: On merchant premises, unattended, or cardholder terminal. Examples: oil, kiosks, self-checkout, home computer, mobile telephone, personal digital assistant (PDA). Cardholder terminal is supported only for Mastercard transactions on CyberSource through VisaNet. - `4`: Off merchant premises, unattended, or cardholder terminal. Examples: vending machines, home computer, mobile telephone, PDA. Cardholder terminal is supported only for Mastercard transactions on CyberSource through VisaNet. This field is supported only for American Express Direct and CyberSource through VisaNet.
39
36
  attr_accessor :operating_environment
40
37
 
@@ -86,6 +83,12 @@ module CyberSource
86
83
  # Type of mPOS device. Possible values: - 0: Dongle - 1: Phone or tablet This optional field is supported only for Mastercard transactions on CyberSource through VisaNet. The value for this field corresponds to the following data in the TC 33 capture file: - Record: CP01 TCR6 - Position: 141 - Field: Mastercard mPOS Transaction The TC 33 Capture file contains information about the purchases and refunds that a merchant submits to CyberSource. CyberSource through VisaNet creates the TC 33 Capture file at the end of the day and sends it to the merchant’s acquirer, who uses this information to facilitate end-of-day clearing processing with payment networks.
87
84
  attr_accessor :is_dedicated_hardware_terminal
88
85
 
86
+ # This is the model name of the reader which is used to accept the payment. Possible values: - E3555 - P400 - A920
87
+ attr_accessor :terminal_model
88
+
89
+ # This is the manufacturer name of the reader which is used to accept the payment. Possible values: - PAX - Verifone - Ingenico
90
+ attr_accessor :terminal_make
91
+
89
92
  # Attribute mapping from ruby-style variable name to JSON key.
90
93
  def self.attribute_map
91
94
  {
@@ -95,7 +98,6 @@ module CyberSource
95
98
  :'cat_level' => :'catLevel',
96
99
  :'entry_mode' => :'entryMode',
97
100
  :'terminal_capability' => :'terminalCapability',
98
- :'pin_entry_capability' => :'pinEntryCapability',
99
101
  :'operating_environment' => :'operatingEnvironment',
100
102
  :'emv' => :'emv',
101
103
  :'amex_capn_data' => :'amexCapnData',
@@ -113,7 +115,9 @@ module CyberSource
113
115
  :'partner_sdk_version' => :'partnerSdkVersion',
114
116
  :'emv_application_identifier_and_dedicated_file_name' => :'emvApplicationIdentifierAndDedicatedFileName',
115
117
  :'terminal_compliance' => :'terminalCompliance',
116
- :'is_dedicated_hardware_terminal' => :'isDedicatedHardwareTerminal'
118
+ :'is_dedicated_hardware_terminal' => :'isDedicatedHardwareTerminal',
119
+ :'terminal_model' => :'terminalModel',
120
+ :'terminal_make' => :'terminalMake'
117
121
  }
118
122
  end
119
123
 
@@ -126,7 +130,6 @@ module CyberSource
126
130
  :'cat_level' => :'Integer',
127
131
  :'entry_mode' => :'String',
128
132
  :'terminal_capability' => :'Integer',
129
- :'pin_entry_capability' => :'Integer',
130
133
  :'operating_environment' => :'String',
131
134
  :'emv' => :'Ptsv2paymentsPointOfSaleInformationEmv',
132
135
  :'amex_capn_data' => :'String',
@@ -144,7 +147,9 @@ module CyberSource
144
147
  :'partner_sdk_version' => :'String',
145
148
  :'emv_application_identifier_and_dedicated_file_name' => :'String',
146
149
  :'terminal_compliance' => :'String',
147
- :'is_dedicated_hardware_terminal' => :'String'
150
+ :'is_dedicated_hardware_terminal' => :'String',
151
+ :'terminal_model' => :'String',
152
+ :'terminal_make' => :'String'
148
153
  }
149
154
  end
150
155
 
@@ -180,10 +185,6 @@ module CyberSource
180
185
  self.terminal_capability = attributes[:'terminalCapability']
181
186
  end
182
187
 
183
- if attributes.has_key?(:'pinEntryCapability')
184
- self.pin_entry_capability = attributes[:'pinEntryCapability']
185
- end
186
-
187
188
  if attributes.has_key?(:'operatingEnvironment')
188
189
  self.operating_environment = attributes[:'operatingEnvironment']
189
190
  end
@@ -259,6 +260,14 @@ module CyberSource
259
260
  if attributes.has_key?(:'isDedicatedHardwareTerminal')
260
261
  self.is_dedicated_hardware_terminal = attributes[:'isDedicatedHardwareTerminal']
261
262
  end
263
+
264
+ if attributes.has_key?(:'terminalModel')
265
+ self.terminal_model = attributes[:'terminalModel']
266
+ end
267
+
268
+ if attributes.has_key?(:'terminalMake')
269
+ self.terminal_make = attributes[:'terminalMake']
270
+ end
262
271
  end
263
272
 
264
273
  # Show invalid properties with the reasons. Usually used together with valid?
@@ -281,14 +290,6 @@ module CyberSource
281
290
  invalid_properties.push('invalid value for "terminal_capability", must be greater than or equal to 1.')
282
291
  end
283
292
 
284
- if !@pin_entry_capability.nil? && @pin_entry_capability > 1
285
- invalid_properties.push('invalid value for "pin_entry_capability", must be smaller than or equal to 1.')
286
- end
287
-
288
- if !@pin_entry_capability.nil? && @pin_entry_capability < 1
289
- invalid_properties.push('invalid value for "pin_entry_capability", must be greater than or equal to 1.')
290
- end
291
-
292
293
  if !@pin_block_encoding_format.nil? && @pin_block_encoding_format > 9
293
294
  invalid_properties.push('invalid value for "pin_block_encoding_format", must be smaller than or equal to 9.')
294
295
  end
@@ -303,8 +304,6 @@ module CyberSource
303
304
  return false if !@cat_level.nil? && @cat_level < 1
304
305
  return false if !@terminal_capability.nil? && @terminal_capability > 5
305
306
  return false if !@terminal_capability.nil? && @terminal_capability < 1
306
- return false if !@pin_entry_capability.nil? && @pin_entry_capability > 1
307
- return false if !@pin_entry_capability.nil? && @pin_entry_capability < 1
308
307
  return false if !@pin_block_encoding_format.nil? && @pin_block_encoding_format > 9
309
308
  true
310
309
  end
@@ -361,20 +360,6 @@ module CyberSource
361
360
  @terminal_capability = terminal_capability
362
361
  end
363
362
 
364
- # Custom attribute writer method with validation
365
- # @param [Object] pin_entry_capability Value to be assigned
366
- def pin_entry_capability=(pin_entry_capability)
367
- if !pin_entry_capability.nil? && pin_entry_capability > 1
368
- fail ArgumentError, 'invalid value for "pin_entry_capability", must be smaller than or equal to 1.'
369
- end
370
-
371
- if !pin_entry_capability.nil? && pin_entry_capability < 1
372
- fail ArgumentError, 'invalid value for "pin_entry_capability", must be greater than or equal to 1.'
373
- end
374
-
375
- @pin_entry_capability = pin_entry_capability
376
- end
377
-
378
363
  # Custom attribute writer method with validation
379
364
  # @param [Object] operating_environment Value to be assigned
380
365
  def operating_environment=(operating_environment)
@@ -457,6 +442,18 @@ module CyberSource
457
442
  @is_dedicated_hardware_terminal = is_dedicated_hardware_terminal
458
443
  end
459
444
 
445
+ # Custom attribute writer method with validation
446
+ # @param [Object] terminal_model Value to be assigned
447
+ def terminal_model=(terminal_model)
448
+ @terminal_model = terminal_model
449
+ end
450
+
451
+ # Custom attribute writer method with validation
452
+ # @param [Object] terminal_make Value to be assigned
453
+ def terminal_make=(terminal_make)
454
+ @terminal_make = terminal_make
455
+ end
456
+
460
457
  # Checks equality by comparing each attribute.
461
458
  # @param [Object] Object to be compared
462
459
  def ==(o)
@@ -468,7 +465,6 @@ module CyberSource
468
465
  cat_level == o.cat_level &&
469
466
  entry_mode == o.entry_mode &&
470
467
  terminal_capability == o.terminal_capability &&
471
- pin_entry_capability == o.pin_entry_capability &&
472
468
  operating_environment == o.operating_environment &&
473
469
  emv == o.emv &&
474
470
  amex_capn_data == o.amex_capn_data &&
@@ -486,7 +482,9 @@ module CyberSource
486
482
  partner_sdk_version == o.partner_sdk_version &&
487
483
  emv_application_identifier_and_dedicated_file_name == o.emv_application_identifier_and_dedicated_file_name &&
488
484
  terminal_compliance == o.terminal_compliance &&
489
- is_dedicated_hardware_terminal == o.is_dedicated_hardware_terminal
485
+ is_dedicated_hardware_terminal == o.is_dedicated_hardware_terminal &&
486
+ terminal_model == o.terminal_model &&
487
+ terminal_make == o.terminal_make
490
488
  end
491
489
 
492
490
  # @see the `==` method
@@ -498,7 +496,7 @@ module CyberSource
498
496
  # Calculates hash code according to all attributes.
499
497
  # @return [Fixnum] Hash code
500
498
  def hash
501
- [terminal_id, terminal_serial_number, lane_number, cat_level, entry_mode, terminal_capability, pin_entry_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].hash
499
+ [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
502
500
  end
503
501
 
504
502
  # Builds the object from hash
@@ -32,7 +32,7 @@ module CyberSource
32
32
  # Type of transaction. Some payment card companies use this information when determining discount rates. #### Used by **Authorization** Required payer authentication transactions; otherwise, optional. **Credit** Required for standalone credits on Chase Paymentech solutions; otherwise, optional. Only `internet`, `moto`, `install`, `recurring`, and `recurring_internet` are valid values. #### Ingenico ePayments When you omit this field for Ingenico ePayments, the processor uses the default transaction type they have on file for you instead of the default value (listed in Appendix I, \"Commerce Indicators,\" on page 441.) #### Payer Authentication Transactions For the possible values and requirements, see \"Payer Authentication,\" page 195. #### Other Types of Transactions See Appendix I, \"Commerce Indicators,\" on page 441. #### Card Present You must set this field to `retail`. This field is required for a card-present transaction. Note that this should ONLY be used when the cardholder and card are present at the time of the transaction. For all keyed transactions originated from a POS terminal where the cardholder and card are not present, commerceIndicator should be submitted as “moto\"
33
33
  attr_accessor :commerce_indicator
34
34
 
35
- # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
35
+ # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `027`: Click to Pay.
36
36
  attr_accessor :payment_solution
37
37
 
38
38
  # Please check with Cybersource customer support to see if your merchant account is configured correctly so you can include this field in your request. * For Payouts: max length for FDCCompass is String (22).
@@ -14,7 +14,7 @@ require 'date'
14
14
 
15
15
  module CyberSource
16
16
  class Ptsv2paymentsidcapturesProcessingInformation
17
- # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
17
+ # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `027`: Click to Pay.
18
18
  attr_accessor :payment_solution
19
19
 
20
20
  # Please check with Cybersource customer support to see if your merchant account is configured correctly so you can include this field in your request. * For Payouts: max length for FDCCompass is String (22).
@@ -14,7 +14,7 @@ require 'date'
14
14
 
15
15
  module CyberSource
16
16
  class Ptsv2paymentsidrefundsProcessingInformation
17
- # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
17
+ # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `027`: Click to Pay.
18
18
  attr_accessor :payment_solution
19
19
 
20
20
  # Please check with Cybersource customer support to see if your merchant account is configured correctly so you can include this field in your request. * For Payouts: max length for FDCCompass is String (22).
@@ -14,7 +14,7 @@ require 'date'
14
14
 
15
15
  module CyberSource
16
16
  class Ptsv2paymentsidreversalsProcessingInformation
17
- # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
17
+ # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `027`: Click to Pay.
18
18
  attr_accessor :payment_solution
19
19
 
20
20
  # Please check with Cybersource customer support to see if your merchant account is configured correctly so you can include this field in your request. * For Payouts: max length for FDCCompass is String (22).
@@ -108,6 +108,12 @@ module CyberSource
108
108
  @locality = locality
109
109
  end
110
110
 
111
+ # Custom attribute writer method with validation
112
+ # @param [Object] country Value to be assigned
113
+ def country=(country)
114
+ @country = country
115
+ end
116
+
111
117
  # Custom attribute writer method with validation
112
118
  # @param [Object] postal_code Value to be assigned
113
119
  def postal_code=(postal_code)
@@ -14,16 +14,16 @@ require 'date'
14
14
 
15
15
  module CyberSource
16
16
  class Riskv1authenticationsetupsPaymentInformationFluidData
17
- # Represents the encrypted payment data BLOB. The entry for this field is dependent on the payment solution a merchant uses. #### Used by **Authorization and Standalone Credits** Required for authorizations and standalone credits that use Bluefin PCI P2PE. #### Card Present processing This field represents the encrypted Bluefin PCI P2PE payment data. Obtain the encrypted payment data from a Bluefin-supported device.
17
+ # Represents the encrypted payment data BLOB. The entry for this field is dependent on the payment solution used by the merchant. Used by Authorization and Standalone Credits. Required for authorizations and standalone credits that use a Cybersource suppored Point-to-Point encryption method. Card Present processing This field represents the encrypted payment data generated by the payment terminal/device.
18
18
  attr_accessor :value
19
19
 
20
20
  # The encoded or encrypted value that a payment solution returns for an authorization request. For details about the valid values for a key, see [Creating an Online Authorization](https://developer.cybersource.com/api/developer-guides/dita-payments/CreatingOnlineAuth.html)
21
21
  attr_accessor :key_serial_number
22
22
 
23
- # The identifier for a payment solution, which is sending the encrypted payment data for decryption. Valid values: - Samsung Pay: `RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ=` **Note**: For other payment solutions, the value may be specific to the customer's mobile device. For example, the descriptor for a Bluefin payment encryption would be a device-generated descriptor. #### Used by **Authorization and Standalone Credits** Required for authorizations and standalone credits that use Bluefin PCI P2PE. #### Card Present processing Format of the encrypted payment data. The value for Bluefin PCI P2PE is `Ymx1ZWZpbg==`. Base64 format only. The value for Cybersource P2PE decryption is as follows: `RklEPUVNVi5QQVlNRU5ULkFQSQ==` if `paymentInformation.fluidData.encoding` is \"HEX\" `4649443D454D562E5041594D454E542E415049` if `paymentInformation.fluidData.encoding` is \"base64\"
23
+ # The identifier for a payment solution, which is sending the encrypted payment data for decryption. Valid values: Samsung Pay: RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ= Note: For other payment solutions, the value may be specific to the terminal or device initiatinf the payment. For example, the descriptor for a Bluefin payment encryption would be a device-generated descriptor. Used by Authorization and Standalone Credits. Required for authorizations and standalone credits. Card Present processing: Format of the encrypted payment data. The value for Bluefin PCI P2PE is `Ymx1ZWZpbg==`. paymentInformation.fluidData.encoding must be \"Base64\". The value for Cybersource P2PE decryption depends on the encoding method used and identified in encoding field. If paymentInformation.fluidData.encoding is `Base64`, the value is: `RklEPUVNVi5QQVlNRU5ULkFQSQ==` If paymentInformation.fluidData.encoding is `HEX`, the value is: `4649443D454D562E5041594D454E542E41504`
24
24
  attr_accessor :descriptor
25
25
 
26
- # Encoding method used to encrypt the payment data. Valid value: Base64
26
+ # Encoding method used to encrypt the payment data. Valid values: `Base64`, `HEX`
27
27
  attr_accessor :encoding
28
28
 
29
29
  # Attribute mapping from ruby-style variable name to JSON key.
@@ -14,7 +14,7 @@ require 'date'
14
14
 
15
15
  module CyberSource
16
16
  class Riskv1authenticationsetupsProcessingInformation
17
- # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
17
+ # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `027`: Click to Pay.
18
18
  attr_accessor :payment_solution
19
19
 
20
20
  # Identifier for the **Visa Checkout** order. Visa Checkout provides a unique order ID for every transaction in the Visa Checkout **callID** field.
@@ -26,9 +26,6 @@ module CyberSource
26
26
  # Field that contains the session ID that you send to Decision Manager to obtain the device fingerprint information. The string can contain uppercase and lowercase letters, digits, hyphen (-), and underscore (_). However, do not use the same uppercase and lowercase letters to indicate different session IDs. The session ID must be unique for each merchant ID. You can use any string that you are already generating, such as an order number or web session ID. The session ID must be unique for each page load, regardless of an individual’s web session ID. If a user navigates to a profiled page and is assigned a web session, navigates away from the profiled page, then navigates back to the profiled page, the generated session ID should be different and unique. You may use a web session ID, but it is preferable to use an application GUID (Globally Unique Identifier). This measure ensures that a unique ID is generated every time the page is loaded, even if it is the same user reloading the page.
27
27
  attr_accessor :fingerprint_session_id
28
28
 
29
- # Boolean that indicates whether request contains the device fingerprint information. Values: - `true`: Use raw fingerprintSessionId when looking up device details. - `false` (default): Use merchant id + fingerprintSessionId as the session id for Device detail collection.
30
- attr_accessor :use_raw_fingerprint_session_id
31
-
32
29
  # Email address set in the customer’s browser, which may differ from customer email.
33
30
  attr_accessor :http_browser_email
34
31
 
@@ -74,7 +71,6 @@ module CyberSource
74
71
  :'ip_address' => :'ipAddress',
75
72
  :'host_name' => :'hostName',
76
73
  :'fingerprint_session_id' => :'fingerprintSessionId',
77
- :'use_raw_fingerprint_session_id' => :'useRawFingerprintSessionId',
78
74
  :'http_browser_email' => :'httpBrowserEmail',
79
75
  :'user_agent' => :'userAgent',
80
76
  :'raw_data' => :'rawData',
@@ -98,7 +94,6 @@ module CyberSource
98
94
  :'ip_address' => :'String',
99
95
  :'host_name' => :'String',
100
96
  :'fingerprint_session_id' => :'String',
101
- :'use_raw_fingerprint_session_id' => :'BOOLEAN',
102
97
  :'http_browser_email' => :'String',
103
98
  :'user_agent' => :'String',
104
99
  :'raw_data' => :'Array<Ptsv2paymentsDeviceInformationRawData>',
@@ -139,10 +134,6 @@ module CyberSource
139
134
  self.fingerprint_session_id = attributes[:'fingerprintSessionId']
140
135
  end
141
136
 
142
- if attributes.has_key?(:'useRawFingerprintSessionId')
143
- self.use_raw_fingerprint_session_id = attributes[:'useRawFingerprintSessionId']
144
- end
145
-
146
137
  if attributes.has_key?(:'httpBrowserEmail')
147
138
  self.http_browser_email = attributes[:'httpBrowserEmail']
148
139
  end
@@ -286,7 +277,6 @@ module CyberSource
286
277
  ip_address == o.ip_address &&
287
278
  host_name == o.host_name &&
288
279
  fingerprint_session_id == o.fingerprint_session_id &&
289
- use_raw_fingerprint_session_id == o.use_raw_fingerprint_session_id &&
290
280
  http_browser_email == o.http_browser_email &&
291
281
  user_agent == o.user_agent &&
292
282
  raw_data == o.raw_data &&
@@ -311,7 +301,7 @@ module CyberSource
311
301
  # Calculates hash code according to all attributes.
312
302
  # @return [Fixnum] Hash code
313
303
  def hash
314
- [cookies_accepted, ip_address, host_name, fingerprint_session_id, use_raw_fingerprint_session_id, http_browser_email, user_agent, raw_data, http_accept_browser_value, http_accept_content, http_browser_language, http_browser_java_enabled, http_browser_java_script_enabled, http_browser_color_depth, http_browser_screen_height, http_browser_screen_width, http_browser_time_difference, user_agent_browser_value].hash
304
+ [cookies_accepted, ip_address, host_name, fingerprint_session_id, http_browser_email, user_agent, raw_data, http_accept_browser_value, http_accept_content, http_browser_language, http_browser_java_enabled, http_browser_java_script_enabled, http_browser_color_depth, http_browser_screen_height, http_browser_screen_width, http_browser_time_difference, user_agent_browser_value].hash
315
305
  end
316
306
 
317
307
  # Builds the object from hash
@@ -17,17 +17,21 @@ module CyberSource
17
17
  # 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).
18
18
  attr_accessor :auth_type
19
19
 
20
+ attr_accessor :initiator
21
+
20
22
  # Attribute mapping from ruby-style variable name to JSON key.
21
23
  def self.attribute_map
22
24
  {
23
- :'auth_type' => :'authType'
25
+ :'auth_type' => :'authType',
26
+ :'initiator' => :'initiator'
24
27
  }
25
28
  end
26
29
 
27
30
  # Attribute type mapping.
28
31
  def self.swagger_types
29
32
  {
30
- :'auth_type' => :'String'
33
+ :'auth_type' => :'String',
34
+ :'initiator' => :'Ptsv2paymentsProcessingInformationAuthorizationOptionsInitiator'
31
35
  }
32
36
  end
33
37
 
@@ -42,6 +46,10 @@ module CyberSource
42
46
  if attributes.has_key?(:'authType')
43
47
  self.auth_type = attributes[:'authType']
44
48
  end
49
+
50
+ if attributes.has_key?(:'initiator')
51
+ self.initiator = attributes[:'initiator']
52
+ end
45
53
  end
46
54
 
47
55
  # Show invalid properties with the reasons. Usually used together with valid?
@@ -68,7 +76,8 @@ module CyberSource
68
76
  def ==(o)
69
77
  return true if self.equal?(o)
70
78
  self.class == o.class &&
71
- auth_type == o.auth_type
79
+ auth_type == o.auth_type &&
80
+ initiator == o.initiator
72
81
  end
73
82
 
74
83
  # @see the `==` method
@@ -80,7 +89,7 @@ module CyberSource
80
89
  # Calculates hash code according to all attributes.
81
90
  # @return [Fixnum] Hash code
82
91
  def hash
83
- [auth_type].hash
92
+ [auth_type, initiator].hash
84
93
  end
85
94
 
86
95
  # Builds the object from hash
@@ -14,7 +14,7 @@ require 'date'
14
14
 
15
15
  module CyberSource
16
16
  class TssV2TransactionsPost201ResponseEmbeddedProcessingInformation
17
- # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.
17
+ # Type of digital payment solution for the transaction. Possible Values: - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/VCO_SCMP_API/html/) - `001`: Apple Pay. - `004`: Cybersource In-App Solution. - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct. For details, see \"Masterpass\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) - `006`: Android Pay. - `007`: Chase Pay. - `008`: Samsung Pay. - `012`: Google Pay. - `013`: Cybersource P2PE Decryption - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token. - `027`: Click to Pay.
18
18
  attr_accessor :payment_solution
19
19
 
20
20
  # Payouts transaction type. Required for OCT transactions. This field is a pass-through, which means that CyberSource does not verify the value or modify it in any way before sending it to the processor. **Note** When the request includes this field, this value overrides the information in your CyberSource account. For valid values, see the `invoiceHeader_businessApplicationID` field description in [Payouts Using the Simple Order API.](http://apps.cybersource.com/library/documentation/dev_guides/payouts_SO/Payouts_SO_API.pdf)
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: cybersource_rest_client
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.32
4
+ version: 0.0.33
5
5
  platform: ruby
6
6
  authors:
7
7
  - CyberSource
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2021-06-17 00:00:00.000000000 Z
11
+ date: 2021-07-23 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: typhoeus
@@ -517,12 +517,13 @@ files:
517
517
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_order_information_amount_details.rb
518
518
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_order_information_invoice_details.rb
519
519
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_order_information_reward_points_details.rb
520
+ - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_account_information.rb
521
+ - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_account_information_card.rb
520
522
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information.rb
521
523
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_account_features.rb
522
524
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_account_features_balances.rb
523
525
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_bank.rb
524
526
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_bank_account.rb
525
- - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_card.rb
526
527
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_instrument_identifier.rb
527
528
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_tokenized_card.rb
528
529
  - lib/cybersource_rest_client/models/pts_v2_payments_post201_response_point_of_sale_information.rb