cybersource_rest_client 0.0.33 → 0.0.34
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/cybersource_rest_client/models/inline_response_400_2.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicing_v2_invoice_settings_get200_response.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_all_get200_response.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_all_get200_response_invoices.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_all_get400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_all_get404_response.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_all_get502_response.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_get200_response.rb +2 -2
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_post201_response.rb +2 -2
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_post202_response.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_asym_deletes_post200_response.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_asym_get200_response.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_asym_post201_response.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_sym_deletes_post200_response.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_sym_get200_response.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_sym_post201_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v1_transaction_batches_get200_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v1_transaction_batches_get400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v1_transaction_batches_get500_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_credits_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_incremental_authorization_patch201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_incremental_authorization_patch201_response_error_information.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_incremental_authorization_patch201_response_processor_information.rb +6 -0
- data/lib/cybersource_rest_client/models/pts_v2_incremental_authorization_patch400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_captures_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_payments_captures_post400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_error_information.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_processor_information.rb +9 -13
- data/lib/cybersource_rest_client/models/pts_v2_payments_post400_response.rb +2 -2
- data/lib/cybersource_rest_client/models/pts_v2_payments_post502_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_refund_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_payments_refund_post400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_reversals_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_payments_reversals_post400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_voids_post201_response.rb +2 -2
- data/lib/cybersource_rest_client/models/pts_v2_payments_voids_post400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payouts_post201_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payouts_post201_response_error_information.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payouts_post201_response_order_information_amount_details.rb +2 -2
- data/lib/cybersource_rest_client/models/pts_v2_payouts_post400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2credits_processing_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_order_information_amount_details.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_fluid_data.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2payments_point_of_sale_information.rb +2 -0
- data/lib/cybersource_rest_client/models/ptsv2payments_processing_information.rb +1 -1
- data/lib/cybersource_rest_client/models/risk_v1_address_verifications_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/risk_v1_authentication_results_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/risk_v1_authentication_setups_post201_response.rb +2 -2
- data/lib/cybersource_rest_client/models/risk_v1_authentications_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/risk_v1_authentications_post400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/risk_v1_authentications_post400_response_1.rb +1 -1
- data/lib/cybersource_rest_client/models/risk_v1_decisions_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/risk_v1_decisions_post400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/risk_v1_decisions_post400_response_1.rb +1 -1
- data/lib/cybersource_rest_client/models/risk_v1_export_compliance_inquiries_post201_response.rb +3 -3
- data/lib/cybersource_rest_client/models/risk_v1_update_post201_response.rb +2 -2
- data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_fluid_data.rb +2 -2
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response.rb +3 -3
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_consumer_authentication_information.rb +13 -4
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_consumer_authentication_information_strong_authentication.rb +254 -0
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_order_information_amount_details.rb +2 -2
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processing_information.rb +2 -2
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processor_information.rb +8 -12
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_risk_information.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_merchant_information.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_order_information_bill_to.rb +17 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_processing_information.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_processor_information.rb +6 -0
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_transaction_summaries.rb +2 -2
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/vas_v2_payments_post201_response.rb +2 -2
- data/lib/cybersource_rest_client/models/vas_v2_payments_post400_response.rb +1 -1
- data/lib/cybersource_rest_client/models/vas_v2_tax_void200_response.rb +2 -2
- data/lib/cybersource_rest_client/models/vas_v2_tax_voids_post400_response.rb +1 -1
- data/lib/cybersource_rest_client.rb +1 -0
- metadata +3 -2
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class PtsV2PaymentsPost502Response
|
17
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
17
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
18
18
|
attr_accessor :submit_time_utc
|
19
19
|
|
20
20
|
# The status of the submitted transaction. Possible values: - SERVER_ERROR
|
@@ -16,16 +16,16 @@ module CyberSource
|
|
16
16
|
class PtsV2PaymentsRefundPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
22
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
23
23
|
attr_accessor :submit_time_utc
|
24
24
|
|
25
25
|
# The status of the submitted transaction. Possible values: - PENDING
|
26
26
|
attr_accessor :status
|
27
27
|
|
28
|
-
# Reference number for the transaction.
|
28
|
+
# Reference number for the transaction. Depending on how your Cybersource account is configured, this value could either be provided in the API request or generated by CyberSource. The actual value used in the request to the processor is provided back to you by Cybersource in the response.
|
29
29
|
attr_accessor :reconciliation_id
|
30
30
|
|
31
31
|
attr_accessor :client_reference_information
|
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class PtsV2PaymentsRefundPost400Response
|
17
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
17
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
18
18
|
attr_accessor :submit_time_utc
|
19
19
|
|
20
20
|
# The status of the submitted transaction. Possible values: - INVALID_REQUEST
|
@@ -16,16 +16,16 @@ module CyberSource
|
|
16
16
|
class PtsV2PaymentsReversalsPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
22
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
23
23
|
attr_accessor :submit_time_utc
|
24
24
|
|
25
25
|
# The status of the submitted transaction. Possible values: - REVERSED
|
26
26
|
attr_accessor :status
|
27
27
|
|
28
|
-
# Reference number for the transaction.
|
28
|
+
# Reference number for the transaction. Depending on how your Cybersource account is configured, this value could either be provided in the API request or generated by CyberSource. The actual value used in the request to the processor is provided back to you by Cybersource in the response.
|
29
29
|
attr_accessor :reconciliation_id
|
30
30
|
|
31
31
|
attr_accessor :client_reference_information
|
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class PtsV2PaymentsReversalsPost400Response
|
17
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
17
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
18
18
|
attr_accessor :submit_time_utc
|
19
19
|
|
20
20
|
# The status of the submitted transaction. Possible values: - INVALID_REQUEST
|
@@ -16,10 +16,10 @@ module CyberSource
|
|
16
16
|
class PtsV2PaymentsVoidsPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
22
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
23
23
|
attr_accessor :submit_time_utc
|
24
24
|
|
25
25
|
# The status of the submitted transaction. Possible values: - VOIDED
|
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class PtsV2PaymentsVoidsPost400Response
|
17
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
17
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
18
18
|
attr_accessor :submit_time_utc
|
19
19
|
|
20
20
|
# The status of the submitted transaction. Possible values: - INVALID_REQUEST
|
@@ -16,7 +16,7 @@ module CyberSource
|
|
16
16
|
class PtsV2PayoutsPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
22
|
# Time of request in UTC. `Format: YYYY-MM-DDThh:mm:ssZ` Example 2016-08-11T22:47:57Z equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The T separates the date and the time. The Z indicates UTC.
|
data/lib/cybersource_rest_client/models/pts_v2_payouts_post201_response_error_information.rb
CHANGED
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class PtsV2PayoutsPost201ResponseErrorInformation
|
17
|
-
# The reason of the status. Possible values: - EXPIRED_CARD - PROCESSOR_DECLINED - STOLEN_LOST_CARD - UNAUTHORIZED_CARD - CVN_NOT_MATCH - INVALID_CVN - BLACKLISTED_CUSTOMER - INVALID_ACCOUNT - GENERAL_DECLINE - RISK_CONTROL_DECLINE - PROCESSOR_RISK_CONTROL_DECLINE
|
17
|
+
# The reason of the status. Possible values: - EXPIRED_CARD - PROCESSOR_DECLINED - STOLEN_LOST_CARD - UNAUTHORIZED_CARD - CVN_NOT_MATCH - INVALID_CVN - BLACKLISTED_CUSTOMER - INVALID_ACCOUNT - GENERAL_DECLINE - RISK_CONTROL_DECLINE - PROCESSOR_RISK_CONTROL_DECLINE - DEBIT_CARD_USAGE_EXCEEDED_LIMIT
|
18
18
|
attr_accessor :reason
|
19
19
|
|
20
20
|
# The detail message related to the status and reason listed above.
|
@@ -20,10 +20,10 @@ module CyberSource
|
|
20
20
|
# Currency used for the order. Use the three-character [ISO Standard Currency Codes.](http://apps.cybersource.com/library/documentation/sbc/quickref/currencies.pdf) #### Used by **Authorization** Required field. **Authorization Reversal** For an authorization reversal (`reversalInformation`) or a capture (`processingOptions.capture` is set to `true`), you must use the same currency that you used in your payment authorization request. #### PIN Debit Currency for the amount you requested for the PIN debit purchase. This value is returned for partial authorizations. The issuing bank can approve a partial amount if the balance on the debit card is less than the requested transaction amount. For the possible values, see the [ISO Standard Currency Codes](https://developer.cybersource.com/library/documentation/sbc/quickref/currencies.pdf). Returned by PIN debit purchase. For PIN debit reversal requests, you must use the same currency that was used for the PIN debit purchase or PIN debit credit that you are reversing. For the possible values, see the [ISO Standard Currency Codes](https://developer.cybersource.com/library/documentation/sbc/quickref/currencies.pdf). Required field for PIN Debit purchase and PIN Debit credit requests. Optional field for PIN Debit reversal requests. #### GPX This field is optional for reversing an authorization or credit. #### DCC for First Data Your local currency. For details, see the `currency` field description in [Dynamic Currency Conversion For First Data Using the SCMP API](http://apps.cybersource.com/library/documentation/dev_guides/DCC_FirstData_SCMP/DCC_FirstData_SCMP_API.pdf). #### Tax Calculation Required for international tax and value added tax only. Optional for U.S. and Canadian taxes. Your local currency.
|
21
21
|
attr_accessor :currency
|
22
22
|
|
23
|
-
# This is a multicurrency field. It contains the transaction amount (field 4), converted to the Currency used to bill the cardholder’s account.
|
23
|
+
# This is a multicurrency field. It contains the transaction amount (field 4), converted to the Currency used to bill the cardholder’s account. This field is returned for OCT transactions.
|
24
24
|
attr_accessor :settlement_amount
|
25
25
|
|
26
|
-
# This is a multicurrency-only field. It contains a 3-digit numeric code that identifies the currency used by the issuer to bill the cardholder's account.
|
26
|
+
# This is a multicurrency-only field. It contains a 3-digit numeric code that identifies the currency used by the issuer to bill the cardholder's account. This field is returned for OCT transactions.
|
27
27
|
attr_accessor :settlement_currency
|
28
28
|
|
29
29
|
# Attribute mapping from ruby-style variable name to JSON key.
|
@@ -20,7 +20,7 @@ module CyberSource
|
|
20
20
|
# The status of the submitted transaction.
|
21
21
|
attr_accessor :status
|
22
22
|
|
23
|
-
# The reason of the status. Possible values: - MISSING_FIELD - INVALID_DATA - DUPLICATE_REQUEST - INVALID_CARD - INVALID_MERCHANT_CONFIGURATION - INVALID_AMOUNT
|
23
|
+
# The reason of the status. Possible values: - MISSING_FIELD - INVALID_DATA - DUPLICATE_REQUEST - INVALID_CARD - INVALID_MERCHANT_CONFIGURATION - INVALID_AMOUNT
|
24
24
|
attr_accessor :reason
|
25
25
|
|
26
26
|
# The detail message related to the status and reason listed above.
|
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class Ptsv2creditsProcessingInformation
|
17
|
-
# 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.
|
17
|
+
# 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. The list of valid values in this field depends on your processor. See Appendix I, \"Commerce Indicators,\" on page 441 of the Cybersource Credit Card Guide. #### 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. #### 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\"
|
18
18
|
attr_accessor :commerce_indicator
|
19
19
|
|
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.
|
@@ -61,10 +61,10 @@ module CyberSource
|
|
61
61
|
|
62
62
|
attr_accessor :surcharge
|
63
63
|
|
64
|
-
# This is a multicurrency field. It contains the transaction amount (field 4), converted to the Currency used to bill the cardholder’s account.
|
64
|
+
# This is a multicurrency field. It contains the transaction amount (field 4), converted to the Currency used to bill the cardholder’s account. This field is returned for OCT transactions.
|
65
65
|
attr_accessor :settlement_amount
|
66
66
|
|
67
|
-
# This is a multicurrency-only field. It contains a 3-digit numeric code that identifies the currency used by the issuer to bill the cardholder's account.
|
67
|
+
# This is a multicurrency-only field. It contains a 3-digit numeric code that identifies the currency used by the issuer to bill the cardholder's account. This field is returned for OCT transactions.
|
68
68
|
attr_accessor :settlement_currency
|
69
69
|
|
70
70
|
attr_accessor :amex_additional_amounts
|
@@ -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 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
|
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
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 values: `Base64`, `HEX`
|
26
|
+
# Encoding method used to encrypt the payment data. Valid values: `Base64`, `HEX` If no value is provided, `Base64` is taken as the default value. And the `Base64` descriptor is used for paymentInformation.fluidData.encoding
|
27
27
|
attr_accessor :encoding
|
28
28
|
|
29
29
|
# Attribute mapping from ruby-style variable name to JSON key.
|
@@ -46,8 +46,10 @@ module CyberSource
|
|
46
46
|
# When connectivity is unavailable, the client software that is installed on the POS terminal can store a transaction in its memory and send it for authorization when connectivity is restored. This value is provided by the client software that is installed on the POS terminal. This value is not forwarded to the processor. Instead, the value is forwarded to the reporting functionality. Possible values: - `Y`: Transaction was stored and then forwarded. - `N` (default): Transaction was not stored and then forwarded. For authorizations and credits, this field is supported only on these processors: - American Express Direct - FDC Nashville Global - OmniPay Direct - SIX Optional field.
|
47
47
|
attr_accessor :store_and_forward_indicator
|
48
48
|
|
49
|
+
# Complete list of cardholder verification methods (CVMs) supported by the terminal. Optional field. Possible values: - `PIN` - `Signature` **EXAMPLE**: [\"PIN\",\"Signature\"] **NOTE**: You can submit one of the values or both of the above in a request. For authorizations and credits, this field is only supported on these processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX
|
49
50
|
attr_accessor :cardholder_verification_method
|
50
51
|
|
52
|
+
# Complete list of card input methods supported by the terminal. Possible values: - `Keyed`: Terminal can accept card data that is entered manually. - `Swiped`: Terminal can accept card data from a magnetic stripe reader. - `Contact`: Terminal can accept card data in EMV contact mode (\"dipping a card\"). - `Contactless`: Terminal can accept card data in EMV contactless mode (\"tapping a card\"). - `BarCode`: Terminal can read bar codes. - `QRcode`: Terminal can read or scan QR codes. - `OCR`: Terminal can perform optical character recognition (OCT) on the card. **EXAMPLE**: [\"Keyed\",\"Swiped\",\"Contact\",\"Contactless\"] #### Used by **Authorization and Credit** Optional. This field is supported only by client software that is installed on your POS terminals for the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX
|
51
53
|
attr_accessor :terminal_input_capability
|
52
54
|
|
53
55
|
# Indicates whether the terminal can capture the card. Possible values: - `1`: Terminal can capture card. - `0`: Terminal cannot capture card. For authorizations and credits, this field is supported only by these processors: - American Express Direct - Credit Mutuel-CIC - OmniPay Direct Optional field.
|
@@ -29,7 +29,7 @@ module CyberSource
|
|
29
29
|
# 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)
|
30
30
|
attr_accessor :business_application_id
|
31
31
|
|
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.
|
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. The list of valid values in this field depends on your processor. See Appendix I, \"Commerce Indicators,\" on page 441 of the Cybersource Credit Card Guide. #### 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. #### 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
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.
|
@@ -16,13 +16,13 @@ module CyberSource
|
|
16
16
|
class RiskV1AddressVerificationsPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
22
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
23
23
|
attr_accessor :submit_time_utc
|
24
24
|
|
25
|
-
# Time that the transaction was submitted in local time.
|
25
|
+
# Time that the transaction was submitted in local time. Generated by Cybersource.
|
26
26
|
attr_accessor :submit_time_local
|
27
27
|
|
28
28
|
# The status for the call can be: - COMPLETED - INVALID_REQUEST - DECLINED
|
@@ -16,13 +16,13 @@ module CyberSource
|
|
16
16
|
class RiskV1AuthenticationResultsPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
22
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
23
23
|
attr_accessor :submit_time_utc
|
24
24
|
|
25
|
-
# Time that the transaction was submitted in local time.
|
25
|
+
# Time that the transaction was submitted in local time. Generated by Cybersource.
|
26
26
|
attr_accessor :submit_time_local
|
27
27
|
|
28
28
|
# The status for payerAuthentication 201 enroll and validate calls. Possible values are: - `AUTHENTICATION_SUCCESSFUL` - `PENDING_AUTHENTICATION` - `INVALID_REQUEST` - `AUTHENTICATION_FAILED`
|
@@ -16,10 +16,10 @@ module CyberSource
|
|
16
16
|
class RiskV1AuthenticationSetupsPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
22
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
23
23
|
attr_accessor :submit_time_utc
|
24
24
|
|
25
25
|
# The status for payerAuthentication 201 setup calls. Possible value is: - COMPLETED - FAILED
|
@@ -16,13 +16,13 @@ module CyberSource
|
|
16
16
|
class RiskV1AuthenticationsPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
22
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
23
23
|
attr_accessor :submit_time_utc
|
24
24
|
|
25
|
-
# Time that the transaction was submitted in local time.
|
25
|
+
# Time that the transaction was submitted in local time. Generated by Cybersource.
|
26
26
|
attr_accessor :submit_time_local
|
27
27
|
|
28
28
|
# The status for payerAuthentication 201 enroll and validate calls. Possible values are: - `AUTHENTICATION_SUCCESSFUL` - `PENDING_AUTHENTICATION` - `INVALID_REQUEST` - `AUTHENTICATION_FAILED`
|
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class RiskV1AuthenticationsPost400Response
|
17
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
17
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
18
18
|
attr_accessor :submit_time_utc
|
19
19
|
|
20
20
|
# The status for payerAuthentication 400 setup calls. Possible values are: - INVALID_REQUEST
|
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class RiskV1AuthenticationsPost400Response1
|
17
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
17
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
18
18
|
attr_accessor :submit_time_utc
|
19
19
|
|
20
20
|
# The status for payerAuthentication 201 enroll and validate calls. Value is: - `INVALID_REQUEST`
|
@@ -16,13 +16,13 @@ module CyberSource
|
|
16
16
|
class RiskV1DecisionsPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
22
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
23
23
|
attr_accessor :submit_time_utc
|
24
24
|
|
25
|
-
# Time that the transaction was submitted in local time.
|
25
|
+
# Time that the transaction was submitted in local time. Generated by Cybersource.
|
26
26
|
attr_accessor :submit_time_local
|
27
27
|
|
28
28
|
# The status of the submitted transaction. Possible values: - `ACCEPTED` - `REJECTED` - `PENDING_REVIEW` - `DECLINED` - `PENDING_AUTHENTICATION` - `INVALID_REQUEST` - `AUTHENTICATION_FAILED` - `CHALLENGE`
|
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class RiskV1DecisionsPost400Response
|
17
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
17
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
18
18
|
attr_accessor :submit_time_utc
|
19
19
|
|
20
20
|
# The status of the submitted transaction. Possible values: - `INVALID_REQUEST` - `DECLINED`
|
@@ -14,7 +14,7 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class RiskV1DecisionsPost400Response1
|
17
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
17
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
18
18
|
attr_accessor :submit_time_utc
|
19
19
|
|
20
20
|
# The status of the submitted transaction. Possible values: - INVALID_REQUEST
|
data/lib/cybersource_rest_client/models/risk_v1_export_compliance_inquiries_post201_response.rb
CHANGED
@@ -16,13 +16,13 @@ module CyberSource
|
|
16
16
|
class RiskV1ExportComplianceInquiriesPost201Response
|
17
17
|
attr_accessor :_links
|
18
18
|
|
19
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
19
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
20
20
|
attr_accessor :id
|
21
21
|
|
22
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
22
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
23
23
|
attr_accessor :submit_time_utc
|
24
24
|
|
25
|
-
# Time that the transaction was submitted in local time.
|
25
|
+
# Time that the transaction was submitted in local time. Generated by Cybersource.
|
26
26
|
attr_accessor :submit_time_local
|
27
27
|
|
28
28
|
# The status for the call can be: - COMPLETED - INVALID_REQUEST - DECLINED
|
@@ -18,13 +18,13 @@ module CyberSource
|
|
18
18
|
|
19
19
|
attr_accessor :client_reference_informaton
|
20
20
|
|
21
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
21
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
22
22
|
attr_accessor :id
|
23
23
|
|
24
24
|
# The status for risk update 201 calls. Possible values are: - INVALID_REQUEST - COMPLETED
|
25
25
|
attr_accessor :status
|
26
26
|
|
27
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
27
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
28
28
|
attr_accessor :submit_time_utc
|
29
29
|
|
30
30
|
# Attribute mapping from ruby-style variable name to JSON key.
|
data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_fluid_data.rb
CHANGED
@@ -20,10 +20,10 @@ module CyberSource
|
|
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 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
|
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 values: `Base64`, `HEX`
|
26
|
+
# Encoding method used to encrypt the payment data. Valid values: `Base64`, `HEX` If no value is provided, `Base64` is taken as the default value. And the `Base64` descriptor is used for paymentInformation.fluidData.encoding
|
27
27
|
attr_accessor :encoding
|
28
28
|
|
29
29
|
# Attribute mapping from ruby-style variable name to JSON key.
|
@@ -14,13 +14,13 @@ require 'date'
|
|
14
14
|
|
15
15
|
module CyberSource
|
16
16
|
class TssV2TransactionsGet200Response
|
17
|
-
# An unique identification number to identify the submitted request. It is also appended to the endpoint of the resource.
|
17
|
+
# An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.
|
18
18
|
attr_accessor :id
|
19
19
|
|
20
20
|
# Contains the transaction identifier for the first transaction in the series of transactions. For example, you might send an authorization request for a payment, followed by a capture request for that payment, and then a refund request for that captured payment. Each of those requests, if successful, creates a resource that is assigned an identifier, which is returned in the response. The rootId identifies the first ID in the series, which in this case would be the ID of the original authorization.
|
21
21
|
attr_accessor :root_id
|
22
22
|
|
23
|
-
# Reference number for the transaction.
|
23
|
+
# Reference number for the transaction. Depending on how your Cybersource account is configured, this value could either be provided in the API request or generated by CyberSource. The actual value used in the request to the processor is provided back to you by Cybersource in the response.
|
24
24
|
attr_accessor :reconciliation_id
|
25
25
|
|
26
26
|
# Your CyberSource merchant ID.
|
@@ -29,7 +29,7 @@ module CyberSource
|
|
29
29
|
# The status of the submitted transaction.
|
30
30
|
attr_accessor :status
|
31
31
|
|
32
|
-
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by
|
32
|
+
# Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services.
|
33
33
|
attr_accessor :submit_time_utc
|
34
34
|
|
35
35
|
attr_accessor :application_information
|
@@ -26,13 +26,16 @@ module CyberSource
|
|
26
26
|
# Payer auth Transaction identifier.
|
27
27
|
attr_accessor :transaction_id
|
28
28
|
|
29
|
+
attr_accessor :strong_authentication
|
30
|
+
|
29
31
|
# Attribute mapping from ruby-style variable name to JSON key.
|
30
32
|
def self.attribute_map
|
31
33
|
{
|
32
34
|
:'eci_raw' => :'eciRaw',
|
33
35
|
:'cavv' => :'cavv',
|
34
36
|
:'xid' => :'xid',
|
35
|
-
:'transaction_id' => :'transactionId'
|
37
|
+
:'transaction_id' => :'transactionId',
|
38
|
+
:'strong_authentication' => :'strongAuthentication'
|
36
39
|
}
|
37
40
|
end
|
38
41
|
|
@@ -42,7 +45,8 @@ module CyberSource
|
|
42
45
|
:'eci_raw' => :'String',
|
43
46
|
:'cavv' => :'String',
|
44
47
|
:'xid' => :'String',
|
45
|
-
:'transaction_id' => :'String'
|
48
|
+
:'transaction_id' => :'String',
|
49
|
+
:'strong_authentication' => :'TssV2TransactionsGet200ResponseConsumerAuthenticationInformationStrongAuthentication'
|
46
50
|
}
|
47
51
|
end
|
48
52
|
|
@@ -69,6 +73,10 @@ module CyberSource
|
|
69
73
|
if attributes.has_key?(:'transactionId')
|
70
74
|
self.transaction_id = attributes[:'transactionId']
|
71
75
|
end
|
76
|
+
|
77
|
+
if attributes.has_key?(:'strongAuthentication')
|
78
|
+
self.strong_authentication = attributes[:'strongAuthentication']
|
79
|
+
end
|
72
80
|
end
|
73
81
|
|
74
82
|
# Show invalid properties with the reasons. Usually used together with valid?
|
@@ -110,7 +118,8 @@ module CyberSource
|
|
110
118
|
eci_raw == o.eci_raw &&
|
111
119
|
cavv == o.cavv &&
|
112
120
|
xid == o.xid &&
|
113
|
-
transaction_id == o.transaction_id
|
121
|
+
transaction_id == o.transaction_id &&
|
122
|
+
strong_authentication == o.strong_authentication
|
114
123
|
end
|
115
124
|
|
116
125
|
# @see the `==` method
|
@@ -122,7 +131,7 @@ module CyberSource
|
|
122
131
|
# Calculates hash code according to all attributes.
|
123
132
|
# @return [Fixnum] Hash code
|
124
133
|
def hash
|
125
|
-
[eci_raw, cavv, xid, transaction_id].hash
|
134
|
+
[eci_raw, cavv, xid, transaction_id, strong_authentication].hash
|
126
135
|
end
|
127
136
|
|
128
137
|
# Builds the object from hash
|