cybersource_rest_client 0.0.56 → 0.0.58
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/AuthenticationSDK/core/Authorization.rb +1 -1
- data/lib/cybersource_rest_client/api/asymmetric_key_management_api.rb +8 -0
- data/lib/cybersource_rest_client/api/batches_api.rb +14 -26
- data/lib/cybersource_rest_client/api/billing_agreements_api.rb +6 -0
- data/lib/cybersource_rest_client/api/capture_api.rb +2 -0
- data/lib/cybersource_rest_client/api/chargeback_details_api.rb +2 -8
- data/lib/cybersource_rest_client/api/chargeback_summaries_api.rb +2 -8
- data/lib/cybersource_rest_client/api/conversion_details_api.rb +2 -8
- data/lib/cybersource_rest_client/api/create_new_webhooks_api.rb +21 -37
- data/lib/cybersource_rest_client/api/credit_api.rb +2 -0
- data/lib/cybersource_rest_client/api/customer_api.rb +8 -64
- data/lib/cybersource_rest_client/api/customer_payment_instrument_api.rb +10 -124
- data/lib/cybersource_rest_client/api/customer_shipping_address_api.rb +10 -124
- data/lib/cybersource_rest_client/api/decision_manager_api.rb +10 -0
- data/lib/cybersource_rest_client/api/download_dtd_api.rb +2 -0
- data/lib/cybersource_rest_client/api/download_xsd_api.rb +2 -0
- data/lib/cybersource_rest_client/api/emv_tag_details_api.rb +4 -0
- data/lib/cybersource_rest_client/api/instrument_identifier_api.rb +12 -108
- data/lib/cybersource_rest_client/api/interchange_clearing_level_details_api.rb +2 -8
- data/lib/cybersource_rest_client/api/invoice_settings_api.rb +4 -0
- data/lib/cybersource_rest_client/api/invoices_api.rb +12 -0
- data/lib/cybersource_rest_client/api/keymanagement_api.rb +2 -0
- data/lib/cybersource_rest_client/api/keymanagementpassword_api.rb +2 -0
- data/lib/cybersource_rest_client/api/keymanagementpgp_api.rb +2 -0
- data/lib/cybersource_rest_client/api/keymanagementscmp_api.rb +2 -0
- data/lib/cybersource_rest_client/api/manage_webhooks_api.rb +77 -93
- data/lib/cybersource_rest_client/api/merchant_boarding_api.rb +2 -2
- data/lib/cybersource_rest_client/api/microform_integration_api.rb +2 -0
- data/lib/cybersource_rest_client/api/net_fundings_api.rb +2 -8
- data/lib/cybersource_rest_client/api/notification_of_changes_api.rb +2 -0
- data/lib/cybersource_rest_client/api/payer_authentication_api.rb +6 -0
- data/lib/cybersource_rest_client/api/payment_batch_summaries_api.rb +2 -16
- data/lib/cybersource_rest_client/api/payment_instrument_api.rb +8 -64
- data/lib/cybersource_rest_client/api/payments_api.rb +6 -0
- data/lib/cybersource_rest_client/api/payouts_api.rb +2 -0
- data/lib/cybersource_rest_client/api/plans_api.rb +16 -0
- data/lib/cybersource_rest_client/api/purchase_and_refund_details_api.rb +2 -16
- data/lib/cybersource_rest_client/api/push_funds_api.rb +2 -0
- data/lib/cybersource_rest_client/api/refund_api.rb +4 -0
- data/lib/cybersource_rest_client/api/report_definitions_api.rb +4 -16
- data/lib/cybersource_rest_client/api/report_downloads_api.rb +2 -8
- data/lib/cybersource_rest_client/api/report_subscriptions_api.rb +12 -58
- data/lib/cybersource_rest_client/api/reports_api.rb +8 -26
- data/lib/cybersource_rest_client/api/retrieval_details_api.rb +2 -8
- data/lib/cybersource_rest_client/api/retrieval_summaries_api.rb +2 -8
- data/lib/cybersource_rest_client/api/reversal_api.rb +4 -0
- data/lib/cybersource_rest_client/api/search_transactions_api.rb +4 -0
- data/lib/cybersource_rest_client/api/secure_file_share_api.rb +4 -16
- data/lib/cybersource_rest_client/api/subscriptions_api.rb +16 -0
- data/lib/cybersource_rest_client/api/symmetric_key_management_api.rb +8 -0
- data/lib/cybersource_rest_client/api/taxes_api.rb +4 -0
- data/lib/cybersource_rest_client/api/token_api.rb +13 -23
- data/lib/cybersource_rest_client/api/transaction_batches_api.rb +6 -0
- data/lib/cybersource_rest_client/api/transaction_details_api.rb +2 -0
- data/lib/cybersource_rest_client/api/transient_token_data_api.rb +2 -0
- data/lib/cybersource_rest_client/api/unified_checkout_capture_context_api.rb +2 -0
- data/lib/cybersource_rest_client/api/user_management_api.rb +2 -0
- data/lib/cybersource_rest_client/api/user_management_search_api.rb +2 -0
- data/lib/cybersource_rest_client/api/verification_api.rb +4 -0
- data/lib/cybersource_rest_client/api/void_api.rb +10 -0
- data/lib/cybersource_rest_client/models/boardingv1registrations_product_information_selected_products.rb +1 -1
- data/lib/cybersource_rest_client/models/check_payer_auth_enrollment_request.rb +1 -1
- data/lib/cybersource_rest_client/models/commerce_solutions_products_account_updater.rb +1 -1
- data/lib/cybersource_rest_client/models/commerce_solutions_products_bin_lookup.rb +1 -1
- data/lib/cybersource_rest_client/models/commerce_solutions_products_token_management.rb +1 -1
- data/lib/cybersource_rest_client/models/create_bundled_decision_manager_case_request.rb +1 -1
- data/lib/cybersource_rest_client/models/create_search_request.rb +1 -1
- data/lib/cybersource_rest_client/models/{create_webhook.rb → create_webhook_request.rb} +1 -1
- data/lib/cybersource_rest_client/models/get_all_subscriptions_response_order_information_bill_to.rb +2 -2
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_all_get200_response_customer_information.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicing_v2_invoices_all_get404_response.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicingv2invoices_customer_information.rb +1 -1
- data/lib/cybersource_rest_client/models/invoicingv2invoices_customer_information_company.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_asym_deletes_post200_response_key_information.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_asym_get200_response_key_information.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_asym_post201_response_key_information.rb +1 -1
- data/lib/cybersource_rest_client/models/kms_v2_keys_sym_post201_response_key_information.rb +1 -1
- data/lib/cybersource_rest_client/models/kmsv2keysasym_key_information.rb +1 -1
- data/lib/cybersource_rest_client/models/kmsv2keyssym_key_information.rb +1 -1
- data/lib/cybersource_rest_client/models/kmsv2keyssymdeletes_key_information.rb +1 -1
- data/lib/cybersource_rest_client/models/kmsv2keyssymverifi_key_information.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_card_processing_config_card_not_present.rb +4 -4
- data/lib/cybersource_rest_client/models/payment_products_card_processing_config_card_not_present_installment.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_card_processing_config_card_not_present_payouts.rb +2 -2
- data/lib/cybersource_rest_client/models/payment_products_card_processing_config_card_not_present_processors.rb +2 -2
- data/lib/cybersource_rest_client/models/payment_products_card_processing_config_card_present_processors.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_card_processing_config_common_merchant_descriptor_info.rb +2 -2
- data/lib/cybersource_rest_client/models/payment_products_card_processing_config_features_card_not_present_payouts_currencies.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_e_check_config_account_validation_service.rb +3 -3
- data/lib/cybersource_rest_client/models/payment_products_e_check_config_account_validation_service_internal_only.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_e_check_config_account_validation_service_processors.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_payer_authentication_config_card_types_j_cbj_secure.rb +2 -2
- data/lib/cybersource_rest_client/models/payment_products_payer_authentication_config_card_types_verified.rb +2 -2
- data/lib/cybersource_rest_client/models/payment_products_payer_authentication_config_card_types_verified_currencies.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_secure_acceptance_config_notifications_customer_notifications.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_secure_acceptance_config_notifications_merchant_notifications.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_secure_acceptance_config_payment_types_card_types.rb +5 -5
- data/lib/cybersource_rest_client/models/payment_products_secure_acceptance_config_payment_types_card_types_discover.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_virtual_terminal_config_card_not_present_global_payment_info.rb +4 -4
- data/lib/cybersource_rest_client/models/payment_products_virtual_terminal_config_card_not_present_global_payment_info_basic_info.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_virtual_terminal_config_card_not_present_merchant_defined_data_fields.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_virtual_terminal_config_card_not_present_payment_info.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_virtual_terminal_config_card_not_present_receipt_info.rb +4 -4
- data/lib/cybersource_rest_client/models/payment_products_virtual_terminal_config_card_not_present_receipt_info_email_receipt.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_virtual_terminal_config_card_not_present_receipt_info_header.rb +1 -1
- data/lib/cybersource_rest_client/models/payment_products_virtual_terminal_config_card_not_present_receipt_info_order_info.rb +1 -1
- data/lib/cybersource_rest_client/models/{payment_products.rb → payments_products.rb} +18 -18
- data/lib/cybersource_rest_client/models/{payment_products_currency_conversion.rb → payments_products_card_present_connect.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_currency_conversion_configuration_information.rb → payments_products_card_present_connect_configuration_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_card_present_connect_configuration_information_configurations.rb → payments_products_card_present_connect_configuration_information_configurations.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_card_present_connect_subscription_information.rb → payments_products_card_present_connect_subscription_information.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_card_processing.rb → payments_products_card_processing.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_virtual_terminal_configuration_information.rb → payments_products_card_processing_configuration_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information_configurations.rb → payments_products_card_processing_configuration_information_configurations.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information_configurations_common.rb → payments_products_card_processing_configuration_information_configurations_common.rb} +4 -4
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information_configurations_common_acquirer.rb → payments_products_card_processing_configuration_information_configurations_common_acquirer.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information_configurations_common_currencies.rb → payments_products_card_processing_configuration_information_configurations_common_currencies.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information_configurations_common_currencies_1.rb → payments_products_card_processing_configuration_information_configurations_common_currencies_1.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information_configurations_common_payment_types.rb → payments_products_card_processing_configuration_information_configurations_common_payment_types.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information_configurations_common_processors.rb → payments_products_card_processing_configuration_information_configurations_common_processors.rb} +10 -10
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information_configurations_features.rb → payments_products_card_processing_configuration_information_configurations_features.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information_configurations_features_card_present.rb → payments_products_card_processing_configuration_information_configurations_features_card_present.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_subscription_information.rb → payments_products_card_processing_subscription_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_subscription_information_features.rb → payments_products_card_processing_subscription_information_features.rb} +1 -1
- data/lib/cybersource_rest_client/models/payments_products_currency_conversion.rb +200 -0
- data/lib/cybersource_rest_client/models/{payment_products_payer_authentication_configuration_information.rb → payments_products_currency_conversion_configuration_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_currency_conversion_configuration_information_configurations.rb → payments_products_currency_conversion_configuration_information_configurations.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_currency_conversion_configuration_information_configurations_processors.rb → payments_products_currency_conversion_configuration_information_configurations_processors.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_cybs_ready_terminal.rb → payments_products_cybs_ready_terminal.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_differential_fee.rb → payments_products_differential_fee.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_differential_fee_subscription_information.rb → payments_products_differential_fee_subscription_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_differential_fee_subscription_information_features.rb → payments_products_differential_fee_subscription_information_features.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_digital_payments.rb → payments_products_digital_payments.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_digital_payments_subscription_information.rb → payments_products_digital_payments_subscription_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_payouts.rb → payments_products_e_check.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_e_check_configuration_information_configurations_common_internal_only_processors.rb → payments_products_e_check_config_common_internal_only_processors.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_e_check_configuration_information.rb → payments_products_e_check_configuration_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_e_check_configuration_information_configurations.rb → payments_products_e_check_configuration_information_configurations.rb} +4 -4
- data/lib/cybersource_rest_client/models/{payment_products_e_check_configuration_information_configurations_common.rb → payments_products_e_check_configuration_information_configurations_common.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_e_check_configuration_information_configurations_common_internal_only.rb → payments_products_e_check_configuration_information_configurations_common_internal_only.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_e_check_configuration_information_configurations_common_processors.rb → payments_products_e_check_configuration_information_configurations_common_processors.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_e_check_configuration_information_configurations_features.rb → payments_products_e_check_configuration_information_configurations_features.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_e_check_configuration_information_configurations_underwriting.rb → payments_products_e_check_configuration_information_configurations_underwriting.rb} +4 -4
- data/lib/cybersource_rest_client/models/{payment_products_e_check_subscription_information.rb → payments_products_e_check_subscription_information.rb} +1 -1
- data/lib/cybersource_rest_client/models/payments_products_payer_authentication.rb +200 -0
- data/lib/cybersource_rest_client/models/{payment_products_card_present_connect_configuration_information.rb → payments_products_payer_authentication_configuration_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_payer_authentication_configuration_information_configurations.rb → payments_products_payer_authentication_configuration_information_configurations.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_payer_authentication_configuration_information_configurations_card_types.rb → payments_products_payer_authentication_configuration_information_configurations_card_types.rb} +9 -9
- data/lib/cybersource_rest_client/models/{payment_products_payer_authentication_configuration_information_configurations_card_types_cb.rb → payments_products_payer_authentication_configuration_information_configurations_card_types_cb.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_payer_authentication_subscription_information.rb → payments_products_payer_authentication_subscription_information.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_e_check.rb → payments_products_payouts.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_payouts_configuration_information.rb → payments_products_payouts_configuration_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_payouts_configuration_information_configurations.rb → payments_products_payouts_configuration_information_configurations.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_payouts_configuration_information_configurations_processor_account.rb → payments_products_payouts_configuration_information_configurations_processor_account.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_payouts_configuration_information_configurations_pullfunds.rb → payments_products_payouts_configuration_information_configurations_pullfunds.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_payouts_configuration_information_configurations_pushfunds.rb → payments_products_payouts_configuration_information_configurations_pushfunds.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_card_present_connect.rb → payments_products_secure_acceptance.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_card_processing_configuration_information.rb → payments_products_secure_acceptance_configuration_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_secure_acceptance_configuration_information_configurations.rb → payments_products_secure_acceptance_configuration_information_configurations.rb} +7 -7
- data/lib/cybersource_rest_client/models/{payment_products_secure_acceptance_configuration_information_configurations_checkout.rb → payments_products_secure_acceptance_configuration_information_configurations_checkout.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_secure_acceptance_configuration_information_configurations_contact_information.rb → payments_products_secure_acceptance_configuration_information_configurations_contact_information.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_secure_acceptance_configuration_information_configurations_notifications.rb → payments_products_secure_acceptance_configuration_information_configurations_notifications.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_secure_acceptance_configuration_information_configurations_payment_methods.rb → payments_products_secure_acceptance_configuration_information_configurations_payment_methods.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_secure_acceptance_configuration_information_configurations_payment_types.rb → payments_products_secure_acceptance_configuration_information_configurations_payment_types.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_secure_acceptance_configuration_information_configurations_service.rb → payments_products_secure_acceptance_configuration_information_configurations_service.rb} +1 -1
- data/lib/cybersource_rest_client/models/{payment_products_tax.rb → payments_products_tax.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_secure_acceptance.rb → payments_products_virtual_terminal.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_secure_acceptance_configuration_information.rb → payments_products_virtual_terminal_configuration_information.rb} +2 -2
- data/lib/cybersource_rest_client/models/{payment_products_virtual_terminal_configuration_information_configurations.rb → payments_products_virtual_terminal_configuration_information_configurations.rb} +3 -3
- data/lib/cybersource_rest_client/models/{payment_products_virtual_terminal_configuration_information_configurations_card_not_present.rb → payments_products_virtual_terminal_configuration_information_configurations_card_not_present.rb} +3 -3
- data/lib/cybersource_rest_client/models/post_payment_credentials_request.rb +191 -0
- data/lib/cybersource_rest_client/models/pts_v2_credits_post201_response_credit_amount_details.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_incremental_authorization_patch201_response_processor_information.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_captures_post201_response.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_captures_post201_response_processor_information.rb +16 -5
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_1_order_information_bill_to.rb +4 -4
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_1_order_information_ship_to.rb +6 -6
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_1_payment_information_payment_type_method.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_buyer_information.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_consumer_authentication_information.rb +4 -4
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_embedded_actions_capture.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_installment_information.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_issuer_information.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_account_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_payment_information_tokenized_card.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_point_of_sale_information_emv.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_processor_information.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_processor_information_electronic_verification_results.rb +18 -18
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_risk_information_info_codes.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_risk_information_score.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_post201_response_watchlist_screening_information.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payments_refund_post201_response_refund_amount_details.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payouts_post201_response_merchant_information_merchant_descriptor.rb +3 -3
- data/lib/cybersource_rest_client/models/pts_v2_payouts_post201_response_order_information_amount_details.rb +1 -1
- data/lib/cybersource_rest_client/models/pts_v2_payouts_post201_response_processor_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_aggregator_information_sub_merchant.rb +8 -8
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_merchant_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_merchant_information_merchant_descriptor.rb +4 -4
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_point_of_service_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_processing_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_recipient_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_recipient_information_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_sender_information.rb +4 -4
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_sender_information_account.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv1pushfundstransfer_sender_information_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2billingagreements_device_information.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2billingagreements_installment_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2billingagreements_merchant_information.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2billingagreements_merchant_information_merchant_descriptor.rb +3 -3
- data/lib/cybersource_rest_client/models/ptsv2billingagreements_order_information_bill_to.rb +5 -5
- data/lib/cybersource_rest_client/models/ptsv2billingagreements_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2billingagreements_payment_information_tokenized_card.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2credits_installment_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2credits_processing_information.rb +3 -3
- data/lib/cybersource_rest_client/models/ptsv2credits_processing_information_bank_transfer_options.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_acquirer_information.rb +22 -5
- data/lib/cybersource_rest_client/models/ptsv2payments_aggregator_information_sub_merchant.rb +9 -9
- data/lib/cybersource_rest_client/models/ptsv2payments_buyer_information.rb +5 -5
- data/lib/cybersource_rest_client/models/ptsv2payments_buyer_information_personal_identification.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_client_reference_information_partner.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_consumer_authentication_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_device_information.rb +5 -5
- data/lib/cybersource_rest_client/models/ptsv2payments_installment_information.rb +3 -3
- data/lib/cybersource_rest_client/models/ptsv2payments_merchant_information.rb +4 -4
- data/lib/cybersource_rest_client/models/ptsv2payments_merchant_information_merchant_descriptor.rb +5 -5
- data/lib/cybersource_rest_client/models/ptsv2payments_merchant_information_service_fee_descriptor.rb +3 -3
- data/lib/cybersource_rest_client/models/ptsv2payments_merchant_information_service_location.rb +4 -4
- data/lib/cybersource_rest_client/models/ptsv2payments_order_information_amount_details.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2payments_order_information_bill_to.rb +9 -9
- data/lib/cybersource_rest_client/models/ptsv2payments_order_information_bill_to_company.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_order_information_invoice_details.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_order_information_invoice_details_transaction_advice_addendum.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_order_information_line_items.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_order_information_ship_to.rb +7 -7
- data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_bank.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_bank_account.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_card.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_customer.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_payment_type_method.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_payment_information_tokenized_card.rb +3 -3
- data/lib/cybersource_rest_client/models/ptsv2payments_point_of_sale_information.rb +4 -4
- data/lib/cybersource_rest_client/models/ptsv2payments_point_of_sale_information_emv.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2payments_processing_information.rb +6 -6
- data/lib/cybersource_rest_client/models/ptsv2payments_processing_information_authorization_options.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_processing_information_authorization_options_initiator.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_processing_information_bank_transfer_options.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2payments_recipient_information.rb +5 -5
- data/lib/cybersource_rest_client/models/ptsv2payments_risk_information_buyer_history_customer_account.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_travel_information_auto_rental.rb +4 -4
- data/lib/cybersource_rest_client/models/ptsv2payments_travel_information_transit_airline.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_travel_information_transit_airline_ancillary_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_travel_information_transit_airline_legs.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_watchlist_screening_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payments_watchlist_screening_information_weights.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2paymentsid_client_reference_information_partner.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_aggregator_information_sub_merchant.rb +8 -8
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_buyer_information.rb +3 -3
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_device_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_installment_information.rb +3 -3
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_merchant_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_order_information_amount_details.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_order_information_bill_to.rb +6 -6
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_order_information_invoice_details.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_order_information_ship_to.rb +3 -3
- data/lib/cybersource_rest_client/models/ptsv2paymentsidcaptures_point_of_sale_information_emv.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2paymentsidrefunds_merchant_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2paymentsidrefunds_order_information_line_items.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2paymentsidrefunds_payment_information_bank.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2paymentsidrefunds_payment_information_card.rb +2 -2
- data/lib/cybersource_rest_client/models/ptsv2paymentsidreversals_point_of_sale_information_emv.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payouts_merchant_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payouts_merchant_information_merchant_descriptor.rb +5 -5
- data/lib/cybersource_rest_client/models/ptsv2payouts_order_information_bill_to.rb +4 -4
- data/lib/cybersource_rest_client/models/ptsv2payouts_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payouts_processing_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payouts_recipient_information.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2payouts_sender_information.rb +5 -5
- data/lib/cybersource_rest_client/models/ptsv2payouts_sender_information_account.rb +1 -1
- data/lib/cybersource_rest_client/models/ptsv2refreshpaymentstatusid_payment_information_customer.rb +1 -1
- data/lib/cybersource_rest_client/models/push_funds201_response_order_information_amount_details.rb +1 -1
- data/lib/cybersource_rest_client/models/push_funds201_response_processor_information.rb +1 -1
- data/lib/cybersource_rest_client/models/{replay_webhooks.rb → replay_webhooks_request.rb} +1 -1
- data/lib/cybersource_rest_client/models/risk_products_decision_manager.rb +1 -1
- data/lib/cybersource_rest_client/models/risk_products_fraud_management_essentials.rb +1 -1
- data/lib/cybersource_rest_client/models/risk_v1_decisions_post201_response_consumer_authentication_information.rb +4 -4
- data/lib/cybersource_rest_client/models/risk_v1_decisions_post201_response_payment_information.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1addressverifications_buyer_information.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1addressverifications_order_information_bill_to.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1addressverifications_order_information_line_items.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1addressverifications_order_information_ship_to.rb +7 -7
- data/lib/cybersource_rest_client/models/riskv1authenticationresults_order_information.rb +5 -17
- data/lib/cybersource_rest_client/models/riskv1authenticationresults_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1authenticationresults_payment_information_tokenized_card.rb +2 -2
- data/lib/cybersource_rest_client/models/riskv1authentications_buyer_information.rb +2 -2
- data/lib/cybersource_rest_client/models/riskv1authentications_device_information.rb +2 -2
- data/lib/cybersource_rest_client/models/riskv1authentications_order_information_bill_to.rb +4 -4
- data/lib/cybersource_rest_client/models/riskv1authentications_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1authentications_payment_information_tokenized_card.rb +2 -2
- data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1authenticationsetups_payment_information_tokenized_card.rb +2 -2
- data/lib/cybersource_rest_client/models/riskv1decisions_acquirer_information.rb +248 -0
- data/lib/cybersource_rest_client/models/riskv1decisions_buyer_information.rb +2 -2
- data/lib/cybersource_rest_client/models/riskv1decisions_consumer_authentication_information.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1decisions_device_information.rb +6 -6
- data/lib/cybersource_rest_client/models/riskv1decisions_merchant_information.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1decisions_merchant_information_merchant_descriptor.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1decisions_order_information_bill_to.rb +4 -4
- data/lib/cybersource_rest_client/models/riskv1decisions_order_information_line_items.rb +2 -2
- data/lib/cybersource_rest_client/models/riskv1decisions_order_information_ship_to.rb +7 -7
- data/lib/cybersource_rest_client/models/riskv1decisions_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1decisions_payment_information_tokenized_card.rb +2 -2
- data/lib/cybersource_rest_client/models/riskv1exportcomplianceinquiries_export_compliance_information.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1exportcomplianceinquiries_order_information_bill_to.rb +3 -3
- data/lib/cybersource_rest_client/models/riskv1exportcomplianceinquiries_order_information_line_items.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1exportcomplianceinquiries_order_information_ship_to.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1liststypeentries_order_information_bill_to.rb +4 -4
- data/lib/cybersource_rest_client/models/riskv1liststypeentries_order_information_ship_to.rb +6 -6
- data/lib/cybersource_rest_client/models/riskv1liststypeentries_payment_information_bank.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1liststypeentries_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/riskv1liststypeentries_risk_information_marking_details.rb +2 -2
- data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument__embedded_instrument_identifier_bill_to.rb +1 -1
- data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument__embedded_instrument_identifier_card.rb +1 -1
- data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_bill_to.rb +5 -5
- data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_buyer_information.rb +1 -1
- data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_buyer_information_issued_by.rb +1 -1
- data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_card_tokenized_information.rb +2 -2
- data/lib/cybersource_rest_client/models/tmsv2customers__embedded_default_payment_instrument_merchant_information_merchant_descriptor.rb +1 -1
- data/lib/cybersource_rest_client/models/tmsv2customers__embedded_tokenized_card.rb +24 -2
- data/lib/cybersource_rest_client/models/tmsv2customers__embedded_tokenized_card_card.rb +3 -3
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_buyer_information.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_device_information.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_merchant_information_merchant_descriptor.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_order_information_amount_details.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_order_information_bill_to.rb +7 -7
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_order_information_ship_to.rb +6 -6
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_payment_information_bank.rb +3 -3
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_payment_information_bank_account.rb +3 -3
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_payment_information_card.rb +2 -2
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_payment_information_customer.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_point_of_sale_information.rb +1 -1
- 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_processing_information_authorization_options_initiator.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processor_information.rb +2 -2
- data/lib/cybersource_rest_client/models/tss_v2_transactions_get200_response_processor_information_electronic_verification_results.rb +10 -10
- 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_buyer_information.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_order_information_bill_to.rb +4 -4
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_order_information_ship_to.rb +2 -2
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_payment_information_bank_account.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_payment_information_card.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_point_of_sale_information_partner.rb +1 -1
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_processing_information.rb +2 -2
- data/lib/cybersource_rest_client/models/tss_v2_transactions_post201_response__embedded_risk_information_providers_fingerprint.rb +1 -1
- data/lib/cybersource_rest_client/models/tssv2transactionsemv_tag_details_emv_details_list.rb +1 -1
- data/lib/cybersource_rest_client/models/{update_webhook.rb → update_webhook_request.rb} +1 -1
- data/lib/cybersource_rest_client/models/upv1capturecontexts_order_information_bill_to.rb +7 -7
- data/lib/cybersource_rest_client/models/upv1capturecontexts_order_information_bill_to_company.rb +3 -3
- data/lib/cybersource_rest_client/models/value_added_services_products.rb +2 -2
- data/lib/cybersource_rest_client/models/vas_v2_payments_post201_response_tax_information.rb +1 -1
- data/lib/cybersource_rest_client/models/vasv2tax_buyer_information.rb +1 -1
- data/lib/cybersource_rest_client/models/vasv2tax_order_information_line_items.rb +2 -2
- data/lib/cybersource_rest_client/models/vasv2tax_order_information_ship_to.rb +7 -7
- data/lib/cybersource_rest_client/models/vasv2tax_tax_information.rb +1 -1
- data/lib/cybersource_rest_client.rb +69 -68
- metadata +98 -97
- data/lib/cybersource_rest_client/models/payment_products_payer_authentication.rb +0 -200
- data/lib/cybersource_rest_client/models/payment_products_virtual_terminal.rb +0 -200
- data/lib/cybersource_rest_client/models/riskv1authenticationresults_order_information_line_items.rb +0 -240
|
@@ -14,7 +14,7 @@ require 'date'
|
|
|
14
14
|
|
|
15
15
|
module CyberSource
|
|
16
16
|
class Ptsv2creditsInstallmentInformation
|
|
17
|
-
# #### American Express Direct, Cielo, and CyberSource Latin American Processing Flag that indicates the type of funding for the installment plan associated with the payment. Possible values: - `1`: Merchant-funded installment plan - `2`: Issuer-funded installment plan If you do not include this field in the request, CyberSource uses the value in your CyberSource account. To change the value in your CyberSource account, contact CyberSource Customer Service. For details, see `installment_plan_type` field description in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### CyberSource through VisaNet and American Express Defined code that indicates the type of installment plan for this transaction. Contact American Express for: - Information about the kinds of installment plans that American Express provides - Values for this field For installment payments with American Express in Brazil, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP07 TCR3 - Position: 5-6 - Field: Plan Type * 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
|
|
17
|
+
# #### American Express Direct, Cielo, and CyberSource Latin American Processing Flag that indicates the type of funding for the installment plan associated with the payment. Possible values: - `1`: Merchant-funded installment plan - `2`: Issuer-funded installment plan If you do not include this field in the request, CyberSource uses the value in your CyberSource account. To change the value in your CyberSource account, contact CyberSource Customer Service. For details, see `installment_plan_type` field description in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### CyberSource through VisaNet and American Express Defined code that indicates the type of installment plan for this transaction. Contact American Express for: - Information about the kinds of installment plans that American Express provides - Values for this field For installment payments with American Express in Brazil, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP07 TCR3 - Position: 5-6 - Field: Plan Type * 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 card companies. #### CyberSource through VisaNet with Visa or Mastercard Flag indicating the type of funding for the installment plan associated with the payment. Possible values: - 1 or 01: Merchant-funded installment plan - 2 or 02: Issuer-funded installment plan - 43: Crediario installment plan—only with Visa in Brazil For details, see \"Installment Payments on CyberSource through VisaNet\" in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) For installment payments with Visa in Brazil, the value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP07 TCR1 - Position: 5-6 - Field: Installment Type For all other kinds of installment payments, the value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP01 TCR5 - Position: 39-40 - Field: Installment Plan Type (Issuer or Merchant)
|
|
18
18
|
attr_accessor :plan_type
|
|
19
19
|
|
|
20
20
|
# 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 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. 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
|
|
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.
|
|
@@ -41,13 +41,13 @@ module CyberSource
|
|
|
41
41
|
# Indicates that the transaction includes industry-specific data. Possible Values: - `airline` - `restaurant` - `lodging` - `auto_rental` - `transit` - `healthcare_medical` - `healthcare_transit` - `transit` #### Card Present, Airlines and Auto Rental You must set this field to `airline` in order for airline data to be sent to the processor. For example, if this field is not set to `airline` or is not included in the request, no airline data is sent to the processor. You must set this field to `restaurant` in order for restaurant data to be sent to the processor. When this field is not set to `restaurant` or is not included in the request, no restaurant data is sent to the processor. You must set this field to `auto_rental` in order for auto rental data to be sent to the processor. For example, if this field is not set to `auto_rental` or is not included in the request, no auto rental data is sent to the processor. Restaurant data is supported only on CyberSource through VisaNet.
|
|
42
42
|
attr_accessor :industry_data_type
|
|
43
43
|
|
|
44
|
-
# This field carries the wallet type in authorization requests and credit requests. Possible value are: - `101`: Masterpass remote payment. The customer created the wallet by manually interacting with a customer-controlled device such as a computer, tablet, or phone. This value is supported only for Masterpass transactions on Chase Paymentech Solutions and CyberSource through VisaNet. - `102`: Masterpass remote near field communication (NFC) payment. The customer created the wallet by tapping a PayPass card or customer-controlled device at a contactless card reader. This value is supported only for card-present Masterpass transactions on CyberSource through VisaNet. - `103`: Masterpass Apple Pay payment. The payment was made with a combination of Masterpass and Apple Pay. This value is supported only for Masterpass Apple Pay transactions on CyberSource through VisaNet. - `216`: Masterpass Google Pay payment. The payment was made with a combination of Masterpass and Google Pay. This value is supported only for Masterpass Google Pay transactions on CyberSource through VisaNet. - `217`: Masterpass Samsung Pay payment. The payment was made with a combination of Masterpass and Samsung Pay. This value is supported only for Masterpass Samsung Pay transactions on CyberSource through VisaNet. - `SDW`: Staged digital wallet. An issuer or operator created the wallet. This value is supported only for Masterpass transactions on Chase Paymentech Solutions. - `VCIND`: Visa Checkout payment. This value is supported only on CyberSource through VisaNet, FDC Compass, FDC Nashville Global, FDI Australia, and TSYS Acquiring Solutions. See Getting Started with Visa Checkout. For Visa Checkout transactions, the way CyberSource processes the value for this field depends on the processor. See the Visa Checkout section below. For all other values, this field is a passthrough; therefore, CyberSource does not verify the value or modify it in any way before sending it to the processor. Masterpass (101, 102, 103, 216, and 217): The Masterpass platform generates the wallet type value and passes it to you along with the customer
|
|
44
|
+
# This field carries the wallet type in authorization requests and credit requests. Possible value are: - `101`: Masterpass remote payment. The customer created the wallet by manually interacting with a customer-controlled device such as a computer, tablet, or phone. This value is supported only for Masterpass transactions on Chase Paymentech Solutions and CyberSource through VisaNet. - `102`: Masterpass remote near field communication (NFC) payment. The customer created the wallet by tapping a PayPass card or customer-controlled device at a contactless card reader. This value is supported only for card-present Masterpass transactions on CyberSource through VisaNet. - `103`: Masterpass Apple Pay payment. The payment was made with a combination of Masterpass and Apple Pay. This value is supported only for Masterpass Apple Pay transactions on CyberSource through VisaNet. - `216`: Masterpass Google Pay payment. The payment was made with a combination of Masterpass and Google Pay. This value is supported only for Masterpass Google Pay transactions on CyberSource through VisaNet. - `217`: Masterpass Samsung Pay payment. The payment was made with a combination of Masterpass and Samsung Pay. This value is supported only for Masterpass Samsung Pay transactions on CyberSource through VisaNet. - `SDW`: Staged digital wallet. An issuer or operator created the wallet. This value is supported only for Masterpass transactions on Chase Paymentech Solutions. - `VCIND`: Visa Checkout payment. This value is supported only on CyberSource through VisaNet, FDC Compass, FDC Nashville Global, FDI Australia, and TSYS Acquiring Solutions. See Getting Started with Visa Checkout. For Visa Checkout transactions, the way CyberSource processes the value for this field depends on the processor. See the Visa Checkout section below. For all other values, this field is a passthrough; therefore, CyberSource does not verify the value or modify it in any way before sending it to the processor. Masterpass (101, 102, 103, 216, and 217): The Masterpass platform generates the wallet type value and passes it to you along with the customer's checkout information. Visa Checkout: This field is optional for Visa Checkout authorizations on FDI Australia. For all other processors, this field is required for Visa Checkout authorizations. For Visa Checkout transactions on the following processors, CyberSource sends the value that the processor expects for this field:FDC Compass,FDC Nashville Global,FDI Australia,TSYS Acquiring Solutions For all other processors, this field is a passthrough; therefore, CyberSource does not verify the value or modify it in any way before sending it to the processor. For incremental authorizations, this field is supported only for Mastercard and the supported values are 101 and 102. Payment card companies can introduce new values without notice. Your order management system should be able to process new values without problems. CyberSource through VisaNet When the value for this field is 101, 102, 103, 216, or 217, it corresponds to the following data in the TC 33 capture file5: Record: CP01 TCR6, Position: 88-90, Field: Mastercard Wallet Identifier. When the value for this field is VCIND, it corresponds to the following data in the TC 33 capture file5: Record: CP01 TCR8, Position: 72-76, Field: Agent Unique ID.
|
|
45
45
|
attr_accessor :wallet_type
|
|
46
46
|
|
|
47
47
|
# Supplementary domestic transaction information provided by the acquirer for National Net Settlement Service (NNSS) transactions. NNSS is a settlement service that Visa provides. For transactions on CyberSource through VisaNet in countries that subscribe to NNSS: VisaNet clears transactions; VisaNet transfers funds to the acquirer after deducting processing fees and interchange fees. VisaNet settles transactions in the local pricing currency through a local financial institution. This field is supported only on CyberSource through VisaNet for domestic data in Colombia
|
|
48
48
|
attr_accessor :national_net_domestic_data
|
|
49
49
|
|
|
50
|
-
# On PIN Debit Gateways: This U.S.-only field is optionally used by participants (merchants and acquirers) to specify the network access priority. VisaNet checks to determine if there are issuer routing preferences for any of the networks specified by the sharing group code. If an issuer preference exists for one of the specified debit networks, VisaNet makes a routing selection based on the issuer
|
|
50
|
+
# On PIN Debit Gateways: This U.S.-only field is optionally used by participants (merchants and acquirers) to specify the network access priority. VisaNet checks to determine if there are issuer routing preferences for any of the networks specified by the sharing group code. If an issuer preference exists for one of the specified debit networks, VisaNet makes a routing selection based on the issuer's preference. If an issuer preference exists for more than one of the specified debit networks, or if no issuer preference exists, VisaNet makes a selection based on the acquirer's routing priorities. #### PIN debit Priority order of the networks through which he transaction will be routed. Set this value to a series of one-character network codes in your preferred order. This is a list of the network codes: | Network | Code | | --- | --- | | Accel | E | | AFFN | U | | Alaska Option | 3 | | CU24 | C | | Interlink | G | | Maestro | 8 | | NETS | P | | NYCE | F | | Pulse | H | | Shazam | 7 | | Star | M | | Visa | V | For example, if the Star network is your first preference and Pulse is your second preference, set this field to a value of `MH`. When you do not include this value in your PIN debit request, the list of network codes from your account is used. **Note** This field is supported only for businesses located in the U.S. Optional field for PIN debit credit or PIN debit purchase.
|
|
51
51
|
attr_accessor :network_routing_order
|
|
52
52
|
|
|
53
53
|
attr_accessor :recurring_options
|
data/lib/cybersource_rest_client/models/ptsv2credits_processing_information_bank_transfer_options.rb
CHANGED
|
@@ -14,7 +14,7 @@ require 'date'
|
|
|
14
14
|
|
|
15
15
|
module CyberSource
|
|
16
16
|
class Ptsv2creditsProcessingInformationBankTransferOptions
|
|
17
|
-
# Payment related information. This information is included on the customer
|
|
17
|
+
# Payment related information. This information is included on the customer's statement.
|
|
18
18
|
attr_accessor :customer_memo
|
|
19
19
|
|
|
20
20
|
# Specifies the authorization method for the transaction. #### TeleCheck Accepts only the following values: - `ARC`: account receivable conversion - `CCD`: corporate cash disbursement - `POP`: point of purchase conversion - `PPD`: prearranged payment and deposit entry - `TEL`: telephone-initiated entry - `WEB`: internet-initiated entry For details, see `ecp_sec_code` field description in the [Electronic Check Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/EChecks_SCMP_API/html/)
|
|
@@ -26,13 +26,17 @@ module CyberSource
|
|
|
26
26
|
# Username for the visa directory server that is created when your acquirer sets up your account. This ID might be the same as your merchant ID. the username can be 15 or 23 characters.
|
|
27
27
|
attr_accessor :merchant_id
|
|
28
28
|
|
|
29
|
+
# Acquirer assigned merchant id. Check if your processor supports this field.
|
|
30
|
+
attr_accessor :acquirer_merchant_id
|
|
31
|
+
|
|
29
32
|
# Attribute mapping from ruby-style variable name to JSON key.
|
|
30
33
|
def self.attribute_map
|
|
31
34
|
{
|
|
32
35
|
:'acquirer_bin' => :'acquirerBin',
|
|
33
36
|
:'country' => :'country',
|
|
34
37
|
:'password' => :'password',
|
|
35
|
-
:'merchant_id' => :'merchantId'
|
|
38
|
+
:'merchant_id' => :'merchantId',
|
|
39
|
+
:'acquirer_merchant_id' => :'acquirerMerchantId'
|
|
36
40
|
}
|
|
37
41
|
end
|
|
38
42
|
|
|
@@ -42,7 +46,8 @@ module CyberSource
|
|
|
42
46
|
:'acquirer_bin' => :'acquirer_bin',
|
|
43
47
|
:'country' => :'country',
|
|
44
48
|
:'password' => :'password',
|
|
45
|
-
:'merchant_id' => :'merchant_id'
|
|
49
|
+
:'merchant_id' => :'merchant_id',
|
|
50
|
+
:'acquirer_merchant_id' => :'acquirer_merchant_id'
|
|
46
51
|
}
|
|
47
52
|
end
|
|
48
53
|
|
|
@@ -52,7 +57,8 @@ module CyberSource
|
|
|
52
57
|
:'acquirer_bin' => :'String',
|
|
53
58
|
:'country' => :'String',
|
|
54
59
|
:'password' => :'String',
|
|
55
|
-
:'merchant_id' => :'String'
|
|
60
|
+
:'merchant_id' => :'String',
|
|
61
|
+
:'acquirer_merchant_id' => :'String'
|
|
56
62
|
}
|
|
57
63
|
end
|
|
58
64
|
|
|
@@ -79,6 +85,10 @@ module CyberSource
|
|
|
79
85
|
if attributes.has_key?(:'merchantId')
|
|
80
86
|
self.merchant_id = attributes[:'merchantId']
|
|
81
87
|
end
|
|
88
|
+
|
|
89
|
+
if attributes.has_key?(:'acquirerMerchantId')
|
|
90
|
+
self.acquirer_merchant_id = attributes[:'acquirerMerchantId']
|
|
91
|
+
end
|
|
82
92
|
end
|
|
83
93
|
|
|
84
94
|
# Show invalid properties with the reasons. Usually used together with valid?
|
|
@@ -118,6 +128,12 @@ module CyberSource
|
|
|
118
128
|
@merchant_id = merchant_id
|
|
119
129
|
end
|
|
120
130
|
|
|
131
|
+
# Custom attribute writer method with validation
|
|
132
|
+
# @param [Object] acquirer_merchant_id Value to be assigned
|
|
133
|
+
def acquirer_merchant_id=(acquirer_merchant_id)
|
|
134
|
+
@acquirer_merchant_id = acquirer_merchant_id
|
|
135
|
+
end
|
|
136
|
+
|
|
121
137
|
# Checks equality by comparing each attribute.
|
|
122
138
|
# @param [Object] Object to be compared
|
|
123
139
|
def ==(o)
|
|
@@ -126,7 +142,8 @@ module CyberSource
|
|
|
126
142
|
acquirer_bin == o.acquirer_bin &&
|
|
127
143
|
country == o.country &&
|
|
128
144
|
password == o.password &&
|
|
129
|
-
merchant_id == o.merchant_id
|
|
145
|
+
merchant_id == o.merchant_id &&
|
|
146
|
+
acquirer_merchant_id == o.acquirer_merchant_id
|
|
130
147
|
end
|
|
131
148
|
|
|
132
149
|
# @see the `==` method
|
|
@@ -138,7 +155,7 @@ module CyberSource
|
|
|
138
155
|
# Calculates hash code according to all attributes.
|
|
139
156
|
# @return [Fixnum] Hash code
|
|
140
157
|
def hash
|
|
141
|
-
[acquirer_bin, country, password, merchant_id].hash
|
|
158
|
+
[acquirer_bin, country, password, merchant_id, acquirer_merchant_id].hash
|
|
142
159
|
end
|
|
143
160
|
|
|
144
161
|
# Builds the object from hash
|
data/lib/cybersource_rest_client/models/ptsv2payments_aggregator_information_sub_merchant.rb
CHANGED
|
@@ -20,31 +20,31 @@ module CyberSource
|
|
|
20
20
|
# The ID you assigned to your sub-merchant. CyberSource through VisaNet: For American Express transaction, the value for this field corresponds to the following data in the TC 33 capture file: - Record: CP01 TCRB - Position: 65-84 - Field: American Express Seller ID For Mastercard transactions, the value for this field corresponds to the following data in the TC 33 capture file: - Record: CP01 TCR6 - Position: 117-131 - Field: Mastercard Sub-Merchant ID FDC Compass: This value must consist of uppercase characters. American Express Direct: String (20) CyberSource through VisaNet with American Express: String (20) CyberSource through VisaNet with Mastercard: String (15) FDC Compass: String (20) FDC Nashville Global: String (14)
|
|
21
21
|
attr_accessor :id
|
|
22
22
|
|
|
23
|
-
# Sub-merchant
|
|
23
|
+
# Sub-merchant's business name. #### American Express Direct The maximum length of the sub-merchant name depends on the length of the aggregator name. The combined length for both values must not exceed 36 characters. #### CyberSource through VisaNet With American Express, the maximum length of the sub-merchant name depends on the length of the aggregator name. The combined length for both values must not exceed 36 characters. The value for this field does not map to the TC 33 capture file5. #### FDC Compass This value must consist of uppercase characters. #### FDC Nashville Global With Mastercard, the maximum length of the sub-merchant name depends on the length of the aggregator name: - If aggregator name length is 1 through 3, maximum sub-merchant name length is 21. - If aggregator name length is 4 through 7, maximum sub-merchant name length is 17. - If aggregator name length is 8 through 12, maximum sub-merchant name length is 12.
|
|
24
24
|
attr_accessor :name
|
|
25
25
|
|
|
26
|
-
# First line of the sub-merchant
|
|
26
|
+
# First line of the sub-merchant's street address. For processor-specific details, see `submerchant_street` field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### CyberSource through VisaNet The value for this field does not map to the TC 33 capture file5. #### FDC Compass This value must consist of uppercase characters.
|
|
27
27
|
attr_accessor :address1
|
|
28
28
|
|
|
29
|
-
# Sub-merchant
|
|
29
|
+
# Sub-merchant's city. For processor-specific details, see `submerchant_city` request field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### CyberSource through VisaNet The value for this field does not map to the TC 33 capture file5. #### FDC Compass This value must consist of uppercase characters.
|
|
30
30
|
attr_accessor :locality
|
|
31
31
|
|
|
32
|
-
# Sub-merchant
|
|
32
|
+
# Sub-merchant's state or province. For possible values and also aggregator support, see `submerchant_state` request field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### CyberSource through VisaNet The value for this field does not map to the TC 33 capture file5. #### FDC Compass This value must consist of uppercase characters.
|
|
33
33
|
attr_accessor :administrative_area
|
|
34
34
|
|
|
35
|
-
# Sub-merchant
|
|
35
|
+
# Sub-merchant's region. **Example**\\ `NE` indicates that the sub-merchant is in the northeast region. For processor-specific details, see `submerchant_region` request field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)
|
|
36
36
|
attr_accessor :region
|
|
37
37
|
|
|
38
|
-
# Partial postal code for the sub-merchant
|
|
38
|
+
# Partial postal code for the sub-merchant's address. For processor-specific details, see `submerchant_postal_code` request field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### CyberSource through VisaNet The value for this field does not map to the TC 33 capture file5. #### FDC Compass This value must consist of uppercase characters.
|
|
39
39
|
attr_accessor :postal_code
|
|
40
40
|
|
|
41
|
-
# Sub-merchant
|
|
41
|
+
# Sub-merchant's country. Use the [ISO Standard Country Codes](https://developer.cybersource.com/library/documentation/sbc/quickref/countries_alpha_list.pdf). #### CyberSource through VisaNet The value for this field does not map to the TC 33 capture file. #### FDC Compass This value must consist of uppercase characters. For details, see the `submerchant_country` request-level field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)
|
|
42
42
|
attr_accessor :country
|
|
43
43
|
|
|
44
|
-
# Sub-merchant
|
|
44
|
+
# Sub-merchant's email address. **Maximum length for processors** - American Express Direct: 40 - CyberSource through VisaNet: 40 - FDC Compass: 40 - FDC Nashville Global: 19 #### CyberSource through VisaNet With American Express, the value for this field corresponds to the following data in the TC 33 capture file: - Record: CP01 TCRB - Position: 25-64 - Field: American Express Seller E-mail Address **Note** 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 card companies.
|
|
45
45
|
attr_accessor :email
|
|
46
46
|
|
|
47
|
-
# Sub-merchant
|
|
47
|
+
# Sub-merchant's telephone number. **Maximum length for procesors** - American Express Direct: 20 - CyberSource through VisaNet: 20 - FDC Compass: 13 - FDC Nashville Global: 10 #### CyberSource through VisaNet With American Express, the value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP01 TCRB - Position: 5-24 - Field: American Express Seller Telephone Number **FDC Compass**\\ This value must consist of uppercase characters. Use one of these recommended formats:\\ `NNN-NNN-NNNN`\\ `NNN-AAAAAAA`
|
|
48
48
|
attr_accessor :phone_number
|
|
49
49
|
|
|
50
50
|
# Attribute mapping from ruby-style variable name to JSON key.
|
|
@@ -14,16 +14,16 @@ require 'date'
|
|
|
14
14
|
|
|
15
15
|
module CyberSource
|
|
16
16
|
class Ptsv2paymentsBuyerInformation
|
|
17
|
-
# 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
|
|
17
|
+
# 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)
|
|
18
18
|
attr_accessor :merchant_customer_id
|
|
19
19
|
|
|
20
|
-
# Recipient
|
|
20
|
+
# Recipient's date of birth. **Format**: `YYYYMMDD`. This field is a `pass-through`, which means that CyberSource ensures that the value is eight numeric characters but otherwise does not verify the value or modify it in any way before sending it to the processor. If the field is not required for the transaction, CyberSource does not forward it to the processor. For more details, see `recipient_date_of_birth` field description in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)
|
|
21
21
|
attr_accessor :date_of_birth
|
|
22
22
|
|
|
23
|
-
# Customer
|
|
23
|
+
# Customer's government-assigned tax identification number. #### Tax Calculation Optional for international and value added taxes only. Not applicable to U.S. and Canadian taxes. For processor-specific information, see the purchaser_vat_registration_number field in [Level II and Level III Processing Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/Level_2_3_SCMP_API/html)
|
|
24
24
|
attr_accessor :vat_registration_number
|
|
25
25
|
|
|
26
|
-
# Company
|
|
26
|
+
# Company's tax identifier. This is only used for eCheck service. ** TeleCheck ** Contact your TeleCheck representative to find out whether this field is required or optional. ** All Other Processors ** Not used.
|
|
27
27
|
attr_accessor :company_tax_id
|
|
28
28
|
|
|
29
29
|
attr_accessor :personal_identification
|
|
@@ -37,7 +37,7 @@ module CyberSource
|
|
|
37
37
|
# language setting of the user
|
|
38
38
|
attr_accessor :language
|
|
39
39
|
|
|
40
|
-
# Cardholder
|
|
40
|
+
# Cardholder's mobile phone number. **Important** Required for Visa Secure transactions in Brazil. Do not use this request field for any other types of transactions.
|
|
41
41
|
attr_accessor :mobile_phone
|
|
42
42
|
|
|
43
43
|
# Attribute mapping from ruby-style variable name to JSON key.
|
data/lib/cybersource_rest_client/models/ptsv2payments_buyer_information_personal_identification.rb
CHANGED
|
@@ -20,7 +20,7 @@ module CyberSource
|
|
|
20
20
|
# The value of the identification type. This field is supported only on the following processors. #### ComercioLatino Set this field to the Cadastro de Pessoas Fisicas (CPF). #### CyberSource Latin American Processing Supported for Redecard in Brazil. Set this field to the Cadastro de Pessoas Fisicas (CPF), which is required for AVS for Redecard in Brazil. **Note** CyberSource Latin American Processing is the name of a specific processing connection that CyberSource supports. In the CyberSource API documentation, CyberSource Latin American Processing does not refer to the general topic of processing in Latin America. The information in this field description is for the specific processing connection called CyberSource Latin American Processing. It is not for any other Latin American processors that CyberSource supports. For processor-specific information, see the `personal_id` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) If `type = PASSPORT`, this is the cardholder's passport number. Recommended for Discover ProtectBuy.
|
|
21
21
|
attr_accessor :id
|
|
22
22
|
|
|
23
|
-
# The government agency that issued the driver's license or passport. If **type**` = DRIVER_LICENSE`, this is the State or province where the customer
|
|
23
|
+
# The government agency that issued the driver's license or passport. If **type**` = DRIVER_LICENSE`, this is the State or province where the customer's driver's license was issued. If **type**` = PASSPORT`, this is the Issuing country for the cardholder's passport. Recommended for Discover ProtectBuy. Use the two-character [State, Province, and Territory Codes for the United States and Canada](https://developer.cybersource.com/library/documentation/sbc/quickref/states_and_provinces.pdf). #### TeleCheck Contact your TeleCheck representative to find out whether this field is required or optional. #### All Other Processors Not used. For details about the country that issued the passport, see `customer_passport_country` field description in [CyberSource Payer Authentication Using the SCMP API] (https://apps.cybersource.com/library/documentation/dev_guides/Payer_Authentication_SCMP_API/html/) For details about the state or province that issued the passport, see `driver_license_state` field description in [Electronic Check Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/EChecks_SCMP_API/html/)
|
|
24
24
|
attr_accessor :issued_by
|
|
25
25
|
|
|
26
26
|
# Verification results received from Issuer or Card Network for verification transactions. Response Only Field.
|
data/lib/cybersource_rest_client/models/ptsv2payments_client_reference_information_partner.rb
CHANGED
|
@@ -14,7 +14,7 @@ require 'date'
|
|
|
14
14
|
|
|
15
15
|
module CyberSource
|
|
16
16
|
class Ptsv2paymentsClientReferenceInformationPartner
|
|
17
|
-
# Value that links the previous transaction to the current follow-on request. This value is assigned by the client software that is installed on the POS terminal, which makes it available to the terminal
|
|
17
|
+
# Value that links the previous transaction to the current follow-on request. This value is assigned by the client software that is installed on the POS terminal, which makes it available to the terminal's software and to CyberSource. Therefore, you can use this value to reconcile transactions between CyberSource and the terminal's software. CyberSource does not forward this value to the processor. Instead, the value is forwarded to the CyberSource reporting functionality. This field is supported only on these processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX Optional field.
|
|
18
18
|
attr_accessor :original_transaction_id
|
|
19
19
|
|
|
20
20
|
# Identifier for the developer that helped integrate a partner solution to CyberSource. Send this value in all requests that are sent through the partner solutions built by that developer. CyberSource assigns the ID to the developer. **Note** When you see a developer ID of 999 in reports, the developer ID that was submitted is incorrect.
|
data/lib/cybersource_rest_client/models/ptsv2payments_consumer_authentication_information.rb
CHANGED
|
@@ -148,7 +148,7 @@ module CyberSource
|
|
|
148
148
|
# Specifies the product code, which designates the type of transaction. Specify one of the following values for this field: - AIR: Airline purchase Important Required for American Express SafeKey (U.S.). - `ACC`: Accommodation Rental - `ACF`: Account funding - `CHA`: Check acceptance - `DIG`: Digital Goods - `DSP`: Cash Dispensing - `GAS`: Fuel - `GEN`: General Retail - `LUX`: Luxury Retail - `PAL`: Prepaid activation and load - `PHY`: Goods or services purchase - `QCT`: Quasi-cash transaction - `REN`: Car Rental - `RES`: Restaurant - `SVC`: Services - `TBD`: Other - `TRA`: Travel **Important** Required for Visa Secure transactions in Brazil. Do not use this request field for any other types of transactions.
|
|
149
149
|
attr_accessor :product_code
|
|
150
150
|
|
|
151
|
-
# The URL of the merchant
|
|
151
|
+
# The URL of the merchant's return page. CyberSource adds this return URL to the step-up JWT and returns it in the response of the Payer Authentication enrollment call. The merchant's return URL page serves as a listening URL. Once the bank session completes, the merchant receives a POST to their URL. This response contains the completed bank session's transactionId. The merchant's return page should capture the transaction ID and send it in the Payer Authentication validation call.
|
|
152
152
|
attr_accessor :return_url
|
|
153
153
|
|
|
154
154
|
# Cardinal's directory server assigned 3DS Requestor ID value
|
|
@@ -20,10 +20,10 @@ module CyberSource
|
|
|
20
20
|
# IP address of the customer. #### Used by **Authorization, Capture, and Credit** Optional field.
|
|
21
21
|
attr_accessor :ip_address
|
|
22
22
|
|
|
23
|
-
# Customer
|
|
23
|
+
# Customer's browser as identified from the HTTP header data. For example, `Mozilla` is the value that identifies the Netscape browser.
|
|
24
24
|
attr_accessor :user_agent
|
|
25
25
|
|
|
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
|
|
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
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.
|
|
@@ -37,13 +37,13 @@ module CyberSource
|
|
|
37
37
|
|
|
38
38
|
attr_accessor :raw_data
|
|
39
39
|
|
|
40
|
-
# Value of the Accept header sent by the customer
|
|
40
|
+
# Value of the Accept header sent by the customer's web browser. **Note** If the customer's browser provides a value, you must include it in your request.
|
|
41
41
|
attr_accessor :http_accept_browser_value
|
|
42
42
|
|
|
43
43
|
# The exact content of the HTTP accept header.
|
|
44
44
|
attr_accessor :http_accept_content
|
|
45
45
|
|
|
46
|
-
# Email address set in the customer
|
|
46
|
+
# Email address set in the customer's browser, which may differ from customer email.
|
|
47
47
|
attr_accessor :http_browser_email
|
|
48
48
|
|
|
49
49
|
# Value represents the browser language as defined in IETF BCP47. Example:en-US, refer https://en.wikipedia.org/wiki/IETF_language_tag for more details.
|
|
@@ -67,7 +67,7 @@ module CyberSource
|
|
|
67
67
|
# Time difference between UTC time and the cardholder browser local time, in minutes, Example:300
|
|
68
68
|
attr_accessor :http_browser_time_difference
|
|
69
69
|
|
|
70
|
-
# Value of the User-Agent header sent by the customer
|
|
70
|
+
# Value of the User-Agent header sent by the customer's web browser. Note If the customer's browser provides a value, you must include it in your request.
|
|
71
71
|
attr_accessor :user_agent_browser_value
|
|
72
72
|
|
|
73
73
|
# Attribute mapping from ruby-style variable name to JSON key.
|
|
@@ -20,16 +20,16 @@ module CyberSource
|
|
|
20
20
|
# Frequency of the installment payments. When you do not include this field in a request for a Crediario installment payment, CyberSource sends a space character to the processor. For details, see `installment_frequency` field description in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) This field is supported only for CyberSource through VisaNet. Possible values: - `B`: Biweekly - `M`: Monthly - `W`: Weekly For Crediario installment payments, the value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP01 TCR9 - Position: 41 - Field: Installment Frequency For details, see \"Installment Payments\" in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)
|
|
21
21
|
attr_accessor :frequency
|
|
22
22
|
|
|
23
|
-
# #### American Express Direct, Cielo, and CyberSource Latin American Processing Flag that indicates the type of funding for the installment plan associated with the payment. Possible values: - `1`: Merchant-funded installment plan - `2`: Issuer-funded installment plan If you do not include this field in the request, CyberSource uses the value in your CyberSource account. To change the value in your CyberSource account, contact CyberSource Customer Service. For details, see `installment_plan_type` field description in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### CyberSource through VisaNet and American Express Defined code that indicates the type of installment plan for this transaction. Contact American Express for: - Information about the kinds of installment plans that American Express provides - Values for this field For installment payments with American Express in Brazil, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP07 TCR3 - Position: 5-6 - Field: Plan Type * 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
|
|
23
|
+
# #### American Express Direct, Cielo, and CyberSource Latin American Processing Flag that indicates the type of funding for the installment plan associated with the payment. Possible values: - `1`: Merchant-funded installment plan - `2`: Issuer-funded installment plan If you do not include this field in the request, CyberSource uses the value in your CyberSource account. To change the value in your CyberSource account, contact CyberSource Customer Service. For details, see `installment_plan_type` field description in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### CyberSource through VisaNet and American Express Defined code that indicates the type of installment plan for this transaction. Contact American Express for: - Information about the kinds of installment plans that American Express provides - Values for this field For installment payments with American Express in Brazil, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP07 TCR3 - Position: 5-6 - Field: Plan Type * 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 card companies. #### CyberSource through VisaNet with Visa or Mastercard Flag indicating the type of funding for the installment plan associated with the payment. Possible values: - 1 or 01: Merchant-funded installment plan - 2 or 02: Issuer-funded installment plan - 43: Crediario installment plan—only with Visa in Brazil For details, see \"Installment Payments on CyberSource through VisaNet\" in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) For installment payments with Visa in Brazil, the value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP07 TCR1 - Position: 5-6 - Field: Installment Type For all other kinds of installment payments, the value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP01 TCR5 - Position: 39-40 - Field: Installment Plan Type (Issuer or Merchant)
|
|
24
24
|
attr_accessor :plan_type
|
|
25
25
|
|
|
26
|
-
# Installment number when making payments in installments. Used along with `totalCount` to track which payment is being processed. For example, the second of 5 payments would be passed to CyberSource as `sequence` = 2 and `totalCount` = 5. For details, see \"Installment Payments\" in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### Chase Paymentech Solutions and FDC Compass This field is optional because this value is required in the merchant descriptors. For details, see \"Chase Paymentech Solutions Merchant Descriptors\" and \"FDC Compass Merchant Descriptors\" in the [Merchant Descriptors Using the SCMP API] (https://apps.cybersource.com/library/documentation/dev_guides/Merchant_Descriptors_SCMP_API/html/) #### CyberSource through VisaNet When you do not include this field in a request for a Crediario installment payment, CyberSource sends a value of 0 to the processor. For Crediario installment payments, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP01 TCR9 - Position: 38-40 - Field: Installment Payment Number * 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
|
|
26
|
+
# Installment number when making payments in installments. Used along with `totalCount` to track which payment is being processed. For example, the second of 5 payments would be passed to CyberSource as `sequence` = 2 and `totalCount` = 5. For details, see \"Installment Payments\" in the [Credit Card Services Using the SCMP API Guide](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### Chase Paymentech Solutions and FDC Compass This field is optional because this value is required in the merchant descriptors. For details, see \"Chase Paymentech Solutions Merchant Descriptors\" and \"FDC Compass Merchant Descriptors\" in the [Merchant Descriptors Using the SCMP API] (https://apps.cybersource.com/library/documentation/dev_guides/Merchant_Descriptors_SCMP_API/html/) #### CyberSource through VisaNet When you do not include this field in a request for a Crediario installment payment, CyberSource sends a value of 0 to the processor. For Crediario installment payments, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP01 TCR9 - Position: 38-40 - Field: Installment Payment Number * 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 card companies.
|
|
27
27
|
attr_accessor :sequence
|
|
28
28
|
|
|
29
29
|
# Total amount of the loan that is being paid in installments. This field is supported only for CyberSource through VisaNet. For details, see \"Installment Payments\" in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)
|
|
30
30
|
attr_accessor :total_amount
|
|
31
31
|
|
|
32
|
-
# Total number of installments when making payments in installments. For details, see \"Installment Payments\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### Chase Paymentech Solutions and FDC Compass This field is optional because this value is required in the merchant descriptors. For details, see \"Chase Paymentech Solutions Merchant Descriptors\" and \"FDC Compass Merchant Descriptors\" in the [Merchant Descriptors Using the SCMP API.] (https://apps.cybersource.com/library/documentation/dev_guides/Merchant_Descriptors_SCMP_API/html/) #### American Express Direct, Cielo, and Comercio Latino This value is the total number of installments you approved. #### CyberSource Latin American Processing in Brazil This value is the total number of installments that you approved. The default is 1. #### All Other Processors This value is used along with _sequence_ to track which payment is being processed. For example, the second of 5 payments would be passed to CyberSource as _sequence_ = 2 and _totalCount_ = 5. #### CyberSource through VisaNet For Crediario installment payments, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP01 TCR9 - Position: 23-25 - Field: Number of Installments For installment payments with American Express in Brazil, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP07 TCR3 - Position: 7-8 - Field: Number of Installments For installment payments with Visa in Brazil, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP07 TCR1 - Position: 7-8 - Field: Number of Installments For all other kinds of installment payments, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP01 TCR5 - Position: 20-22 - Field: Installment Total Count **Note** 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
|
|
32
|
+
# Total number of installments when making payments in installments. For details, see \"Installment Payments\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) #### Chase Paymentech Solutions and FDC Compass This field is optional because this value is required in the merchant descriptors. For details, see \"Chase Paymentech Solutions Merchant Descriptors\" and \"FDC Compass Merchant Descriptors\" in the [Merchant Descriptors Using the SCMP API.] (https://apps.cybersource.com/library/documentation/dev_guides/Merchant_Descriptors_SCMP_API/html/) #### American Express Direct, Cielo, and Comercio Latino This value is the total number of installments you approved. #### CyberSource Latin American Processing in Brazil This value is the total number of installments that you approved. The default is 1. #### All Other Processors This value is used along with _sequence_ to track which payment is being processed. For example, the second of 5 payments would be passed to CyberSource as _sequence_ = 2 and _totalCount_ = 5. #### CyberSource through VisaNet For Crediario installment payments, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP01 TCR9 - Position: 23-25 - Field: Number of Installments For installment payments with American Express in Brazil, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP07 TCR3 - Position: 7-8 - Field: Number of Installments For installment payments with Visa in Brazil, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP07 TCR1 - Position: 7-8 - Field: Number of Installments For all other kinds of installment payments, the value for this field corresponds to the following data in the TC 33 capture file*: - Record: CP01 TCR5 - Position: 20-22 - Field: Installment Total Count **Note** 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 card companies.
|
|
33
33
|
attr_accessor :total_count
|
|
34
34
|
|
|
35
35
|
# Date of the first installment payment. Format: YYMMDD. When you do not include this field, CyberSource sends a string of six zeros (000000) to the processor. For details, see \"Installment Payments on CyberSource through VisaNet\" in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) This field is supported only for Crediario installment payments in Brazil on CyberSource through VisaNet. The value for this field corresponds to the following data in the TC 33 capture file: - Record: CP01 TCR9 - Position: 42-47 - Field: Date of First Installment
|
|
@@ -19,13 +19,13 @@ module CyberSource
|
|
|
19
19
|
# This field will contain either the merchant url or the reverse domain as per the requirement for DSRP Format 3. This might vary transaction to transaction and might not be static. Merchant needs to have access to send this value for all DSRP program.
|
|
20
20
|
attr_accessor :domain_name
|
|
21
21
|
|
|
22
|
-
# Company ID assigned to an independent sales organization. Get this value from Mastercard. #### CyberSource through VisaNet The value for this field corresponds to the following data in the TC 33 capture file: - Record: CP01 TCR6 - Position: 106-116 - Field: Mastercard Independent Sales Organization ID **Note** 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
|
|
22
|
+
# Company ID assigned to an independent sales organization. Get this value from Mastercard. #### CyberSource through VisaNet The value for this field corresponds to the following data in the TC 33 capture file: - Record: CP01 TCR6 - Position: 106-116 - Field: Mastercard Independent Sales Organization ID **Note** 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 card companies. For processor-specific information, see the `sales_organization_ID` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)
|
|
23
23
|
attr_accessor :sales_organization_id
|
|
24
24
|
|
|
25
|
-
# The value for this field is a four-digit number that the payment card industry uses to classify merchants into market segments. A payment card company assigned one or more of these values to your business when you started accepting the payment card company
|
|
25
|
+
# The value for this field is a four-digit number that the payment card industry uses to classify merchants into market segments. A payment card company assigned one or more of these values to your business when you started accepting the payment card company's cards. When you do not include this field in your request, CyberSource uses the value in your CyberSource account. For processor-specific information, see the `merchant_category_code` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) #### CyberSource through VisaNet The value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP01 TCR4 - Position: 150-153 - Field: Merchant Category Code
|
|
26
26
|
attr_accessor :category_code
|
|
27
27
|
|
|
28
|
-
# Merchant category code for domestic transactions. The value for this field is a four-digit number that the payment card industry uses to classify merchants into market segments. A payment card company assigned one or more of these values to your business when you started accepting the payment card company
|
|
28
|
+
# Merchant category code for domestic transactions. The value for this field is a four-digit number that the payment card industry uses to classify merchants into market segments. A payment card company assigned one or more of these values to your business when you started accepting the payment card company's cards. Including this field in a request for a domestic transaction might reduce interchange fees. When you include this field in a request: - Do not include the `merchant_category_code` field. - The value for this field overrides the value in your CyberSource account. This field is supported only for: - Domestic transactions with Mastercard in Spain. Domestic means that you and the cardholder are in the same country. - Merchants enrolled in the OmniPay Direct interchange program. - First Data Merchant Solutions (Europe) on OmniPay Direct.
|
|
29
29
|
attr_accessor :category_code_domestic
|
|
30
30
|
|
|
31
31
|
# Your Cadastro Nacional da Pessoa Jurídica (CNPJ) number. This field is supported only for BNDES transactions on CyberSource through VisaNet. The value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP07 TCR6 - Position: 40-59 - Field: BNDES Reference Field 1 For details, see `bill_merchant_tax_id` field description in the [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)
|
|
@@ -59,7 +59,7 @@ module CyberSource
|
|
|
59
59
|
|
|
60
60
|
attr_accessor :service_location
|
|
61
61
|
|
|
62
|
-
# Use this field only if you are requesting payment with Payer Authentication service together. Your company
|
|
62
|
+
# Use this field only if you are requesting payment with Payer Authentication service together. Your company's name as you want it to appear to the customer in the issuing bank's authentication form. This value overrides the value specified by your merchant bank.
|
|
63
63
|
attr_accessor :merchant_name
|
|
64
64
|
|
|
65
65
|
# Attribute mapping from ruby-style variable name to JSON key.
|
data/lib/cybersource_rest_client/models/ptsv2payments_merchant_information_merchant_descriptor.rb
CHANGED
|
@@ -14,7 +14,7 @@ require 'date'
|
|
|
14
14
|
|
|
15
15
|
module CyberSource
|
|
16
16
|
class Ptsv2paymentsMerchantInformationMerchantDescriptor
|
|
17
|
-
# Your merchant name. **Note** For Paymentech processor using Cybersource Payouts, the maximum data length is 22. #### PIN debit Your business name. This name is displayed on the cardholder
|
|
17
|
+
# Your merchant name. **Note** For Paymentech processor using Cybersource Payouts, the maximum data length is 22. #### PIN debit Your business name. This name is displayed on the cardholder's statement. When you include more than one consecutive space, extra spaces are removed. When you do not include this value in your PIN debit request, the merchant name from your account is used. **Important** This value must consist of English characters. Optional field for PIN debit credit or PIN debit purchase requests. #### Airline processing Your merchant name. This name is displayed on the cardholder's statement. When you include more than one consecutive space, extra spaces are removed. **Note** Some airline fee programs may require the original ticket number (ticket identifier) or the ancillary service description in positions 13 through 23 of this field. **Important** This value must consist of English characters. Required for captures and credits.
|
|
18
18
|
attr_accessor :name
|
|
19
19
|
|
|
20
20
|
# An alternate name for the merchant. For the descriptions, used-by information, data types, and lengths for these fields, see the `merchant_descriptor_alternate` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)-->
|
|
@@ -26,16 +26,16 @@ module CyberSource
|
|
|
26
26
|
# First line of merchant's address. For the descriptions, used-by information, data types, and lengths for these fields, see `merchant_descriptor_street` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)
|
|
27
27
|
attr_accessor :address1
|
|
28
28
|
|
|
29
|
-
# Merchant's City. #### PIN debit City for your business location. This value might be displayed on the cardholder
|
|
29
|
+
# Merchant's City. #### PIN debit City for your business location. This value might be displayed on the cardholder's statement. When you do not include this value in your PIN debit request, the merchant name from your account is used. **Important** This value must consist of English characters. Optional field for PIN debit credit or PIN debit purchase requests.
|
|
30
30
|
attr_accessor :locality
|
|
31
31
|
|
|
32
|
-
# Merchant's country. #### PIN debit Country code for your business location. Use the [ISO Standard Country Codes](https://developer.cybersource.com/library/documentation/sbc/quickref/countries_alpha_list.pdf) This value might be displayed on the cardholder
|
|
32
|
+
# Merchant's country. #### PIN debit Country code for your business location. Use the [ISO Standard Country Codes](https://developer.cybersource.com/library/documentation/sbc/quickref/countries_alpha_list.pdf) This value might be displayed on the cardholder's statement. When you do not include this value in your PIN debit request, the merchant name from your account is used. **Important** This value must consist of English characters. **Note** If your business is located in the U.S. or Canada and you include this field in a request, you must also include `merchantInformation.merchantDescriptor.administrativeArea`. Optional field for PIN debit credit or PIN debit purchase.
|
|
33
33
|
attr_accessor :country
|
|
34
34
|
|
|
35
|
-
# Merchant's postal code. #### PIN debit Postal code for your business location. This value might be displayed on the cardholder
|
|
35
|
+
# Merchant's postal code. #### PIN debit Postal code for your business location. This value might be displayed on the cardholder's statement. If your business is domiciled in the U.S., you can use a 5-digit or 9-digit postal code. A 9-digit postal code must follow this format: [5 digits][dash][4 digits] Example: `12345-6789` If your business is domiciled in Canada, you can use a 6-digit or 9-digit postal code. A 6-digit postal code must follow this format: [alpha][numeric][alpha][space] [numeric][alpha][numeric] Example: `A1B 2C3` When you do not include this value in your PIN debit request, the merchant name from your account is used. **Important** This value must consist of English characters. **Note** This field is supported only for businesses located in the U.S. or Canada. **Important** Mastercard requires a postal code for any country that uses postal codes. You can provide the postal code in your account or you can include this field in your request. Optional field for PIN debit credit or PIN debit purchase.
|
|
36
36
|
attr_accessor :postal_code
|
|
37
37
|
|
|
38
|
-
# The state where the merchant is located. #### PIN debit State code or region code for your business. Use the Use the [State, Province, and Territory Codes for the United States and Canada](https://developer.cybersource.com/library/documentation/sbc/quickref/states_and_provinces.pdf) This value might be displayed on the cardholder
|
|
38
|
+
# The state where the merchant is located. #### PIN debit State code or region code for your business. Use the Use the [State, Province, and Territory Codes for the United States and Canada](https://developer.cybersource.com/library/documentation/sbc/quickref/states_and_provinces.pdf) This value might be displayed on the cardholder's statement. When you do not include this value in your PIN debit request, the merchant name from your account is used. **Important** This value must consist of English characters. **Note** This field is supported only for businesses located in the U.S. or Canada. Optional field for PIN debit credit or PIN debit purchase.
|
|
39
39
|
attr_accessor :administrative_area
|
|
40
40
|
|
|
41
41
|
# Merchant phone as contact information for CNP transactions
|
data/lib/cybersource_rest_client/models/ptsv2payments_merchant_information_service_fee_descriptor.rb
CHANGED
|
@@ -14,13 +14,13 @@ require 'date'
|
|
|
14
14
|
|
|
15
15
|
module CyberSource
|
|
16
16
|
class Ptsv2paymentsMerchantInformationServiceFeeDescriptor
|
|
17
|
-
# Name of the service provider that is collecting the service fee. The service provider name must consist of 3, 7, or 12 characters followed by an asterisk (*). This value must also include the words
|
|
17
|
+
# Name of the service provider that is collecting the service fee. The service provider name must consist of 3, 7, or 12 characters followed by an asterisk (*). This value must also include the words \"Service Fee.\" When you include more than one consecutive space, extra spaces are removed. Use one of the following formats for this value: - <3-character name>*Service Fee - <7-character name>*Service Fee - <12-character name>*Service Fee When payments are made in installments, this value must also include installment information such as \"1 of 5\" or \"3 of 7.\" For installment payments, use one of the following formats for this value: - <3-character name>*Service Fee*<N> of <M> - <7-character name>*Service Fee*<N> of <M> - <12-character name>*Service Fee*<N> of <M> where <N> is the payment number and <M> is the total number of payments. When you do not include this value in your request, CyberSource uses the value that is in your CyberSource account. This value might be displayed on the cardholder's statement.
|
|
18
18
|
attr_accessor :name
|
|
19
19
|
|
|
20
|
-
# Contact information for the service provider that is collecting the service fee. when you include more than one consecutive space, extra spaces are removed. When you do not include this value in your request, CyberSource uses the value that is in your CyberSource account. This value might be displayed on the cardholder
|
|
20
|
+
# Contact information for the service provider that is collecting the service fee. when you include more than one consecutive space, extra spaces are removed. When you do not include this value in your request, CyberSource uses the value that is in your CyberSource account. This value might be displayed on the cardholder's statement.
|
|
21
21
|
attr_accessor :contact
|
|
22
22
|
|
|
23
|
-
# State or territory in which the service provider is located. When you do not include this value in your request, CyberSource uses the value that is in your CyberSource account. This value might be displayed on the cardholder
|
|
23
|
+
# State or territory in which the service provider is located. When you do not include this value in your request, CyberSource uses the value that is in your CyberSource account. This value might be displayed on the cardholder's statement.
|
|
24
24
|
attr_accessor :state
|
|
25
25
|
|
|
26
26
|
# Attribute mapping from ruby-style variable name to JSON key.
|
data/lib/cybersource_rest_client/models/ptsv2payments_merchant_information_service_location.rb
CHANGED
|
@@ -14,16 +14,16 @@ require 'date'
|
|
|
14
14
|
|
|
15
15
|
module CyberSource
|
|
16
16
|
class Ptsv2paymentsMerchantInformationServiceLocation
|
|
17
|
-
# #### Visa Platform Connect Merchant
|
|
17
|
+
# #### Visa Platform Connect Merchant's service location city name. When merchant provides services from a location other than the location identified as merchant location.
|
|
18
18
|
attr_accessor :locality
|
|
19
19
|
|
|
20
|
-
# #### Visa Platform Connect Merchant
|
|
20
|
+
# #### Visa Platform Connect Merchant's service location country subdivision code. When merchant provides services from a location other than the location identified as merchant location.
|
|
21
21
|
attr_accessor :country_subdivision_code
|
|
22
22
|
|
|
23
|
-
# #### Visa Platform Connect Merchant
|
|
23
|
+
# #### Visa Platform Connect Merchant's service location country code. When merchant provides services from a location other than the location identified as merchant location.
|
|
24
24
|
attr_accessor :country_code
|
|
25
25
|
|
|
26
|
-
# #### Visa Platform Connect Merchant
|
|
26
|
+
# #### Visa Platform Connect Merchant's service location postal code. When merchant provides services from a location other than the location identified as merchant location.
|
|
27
27
|
attr_accessor :postal_code
|
|
28
28
|
|
|
29
29
|
# Attribute mapping from ruby-style variable name to JSON key.
|
|
@@ -64,7 +64,7 @@ module CyberSource
|
|
|
64
64
|
|
|
65
65
|
attr_accessor :surcharge
|
|
66
66
|
|
|
67
|
-
# This is a multicurrency field. It contains the transaction amount (field 4), converted to the Currency used to bill the cardholder
|
|
67
|
+
# 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.
|
|
68
68
|
attr_accessor :settlement_amount
|
|
69
69
|
|
|
70
70
|
# 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.
|
|
@@ -83,7 +83,7 @@ module CyberSource
|
|
|
83
83
|
# Your local pricing currency code. For the possible values, see the [ISO Standard Currency Codes.](http://apps.cybersource.com/library/documentation/sbc/quickref/currencies.pdf)
|
|
84
84
|
attr_accessor :original_currency
|
|
85
85
|
|
|
86
|
-
# Cashback amount in the acquirer
|
|
86
|
+
# Cashback amount in the acquirer's currency. If a cashback amount is included in the request, it must be included in the `orderInformation.amountDetails.totalAmount` value. This field is supported only on CyberSource through VisaNet. #### Used by **Authorization** Optional. **Authorization Reversal** Optional. #### PIN debit Optional field for PIN debit purchase, PIN debit credit or PIN debit reversal.
|
|
87
87
|
attr_accessor :cashback_amount
|
|
88
88
|
|
|
89
89
|
attr_accessor :currency_conversion
|