You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CyberSource/__init__.py
+2-1
Original file line number
Diff line number
Diff line change
@@ -176,12 +176,13 @@
176
176
from .models.pts_v2_payments_post201_response_order_information_amount_detailsimportPtsV2PaymentsPost201ResponseOrderInformationAmountDetails
177
177
from .models.pts_v2_payments_post201_response_order_information_invoice_detailsimportPtsV2PaymentsPost201ResponseOrderInformationInvoiceDetails
178
178
from .models.pts_v2_payments_post201_response_order_information_reward_points_detailsimportPtsV2PaymentsPost201ResponseOrderInformationRewardPointsDetails
179
+
from .models.pts_v2_payments_post201_response_payment_account_informationimportPtsV2PaymentsPost201ResponsePaymentAccountInformation
180
+
from .models.pts_v2_payments_post201_response_payment_account_information_cardimportPtsV2PaymentsPost201ResponsePaymentAccountInformationCard
179
181
from .models.pts_v2_payments_post201_response_payment_informationimportPtsV2PaymentsPost201ResponsePaymentInformation
180
182
from .models.pts_v2_payments_post201_response_payment_information_account_featuresimportPtsV2PaymentsPost201ResponsePaymentInformationAccountFeatures
181
183
from .models.pts_v2_payments_post201_response_payment_information_account_features_balancesimportPtsV2PaymentsPost201ResponsePaymentInformationAccountFeaturesBalances
182
184
from .models.pts_v2_payments_post201_response_payment_information_bankimportPtsV2PaymentsPost201ResponsePaymentInformationBank
183
185
from .models.pts_v2_payments_post201_response_payment_information_bank_accountimportPtsV2PaymentsPost201ResponsePaymentInformationBankAccount
184
-
from .models.pts_v2_payments_post201_response_payment_information_cardimportPtsV2PaymentsPost201ResponsePaymentInformationCard
185
186
from .models.pts_v2_payments_post201_response_payment_information_instrument_identifierimportPtsV2PaymentsPost201ResponsePaymentInformationInstrumentIdentifier
186
187
from .models.pts_v2_payments_post201_response_payment_information_tokenized_cardimportPtsV2PaymentsPost201ResponsePaymentInformationTokenizedCard
187
188
from .models.pts_v2_payments_post201_response_point_of_sale_informationimportPtsV2PaymentsPost201ResponsePointOfSaleInformation
A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/api/developer-guides/dita-payments/GettingStarted.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation. Find more on [Authorization with Add-On Features page.](https://developer.cybersource.com/api/authorization-add-ons.html) Possible [RESPONSE CODES](https://developer.cybersource.com/api/reference/response-codes.html) . Processor specific [Testing Triggers](https://developer.cybersource.com/hello-world/testing-guide.html).
48
+
A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/api/developer-guides/dita-payments/GettingStarted.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation. Find more on [Authorization with Add-On Features page.](https://developer.cybersource.com/api/authorization-add-ons.html)
49
49
This method makes a synchronous HTTP request by default. To make an
50
50
asynchronous HTTP request, please define a `callback` function
A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/api/developer-guides/dita-payments/GettingStarted.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation. Find more on [Authorization with Add-On Features page.](https://developer.cybersource.com/api/authorization-add-ons.html) Possible [RESPONSE CODES](https://developer.cybersource.com/api/reference/response-codes.html) . Processor specific [Testing Triggers](https://developer.cybersource.com/hello-world/testing-guide.html).
74
+
A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/api/developer-guides/dita-payments/GettingStarted.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation. Find more on [Authorization with Add-On Features page.](https://developer.cybersource.com/api/authorization-add-ons.html)
75
75
This method makes a synchronous HTTP request by default. To make an
76
76
asynchronous HTTP request, please define a `callback` function
Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call Include the capture ID in the POST request to refund the captured amount.
48
+
Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to refund the captured amount.
49
49
This method makes a synchronous HTTP request by default. To make an
50
50
asynchronous HTTP request, please define a `callback` function
Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call Include the capture ID in the POST request to refund the captured amount.
75
+
Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to refund the captured amount.
76
76
This method makes a synchronous HTTP request by default. To make an
77
77
asynchronous HTTP request, please define a `callback` function
Refund a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to refund the payment amount.
161
+
Refund a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to refund the payment amount.
162
162
This method makes a synchronous HTTP request by default. To make an
163
163
asynchronous HTTP request, please define a `callback` function
Refund a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to refund the payment amount.
188
+
Refund a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to refund the payment amount.
189
189
This method makes a synchronous HTTP request by default. To make an
190
190
asynchronous HTTP request, please define a `callback` function
Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to cancel the capture.
154
+
Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to cancel the capture.
155
155
This method makes a synchronous HTTP request by default. To make an
156
156
asynchronous HTTP request, please define a `callback` function
Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to cancel the capture.
181
+
Refund a capture API is only used, if you have requested Capture independenlty using [/pts/v2/payments/{id}/captures](https://developer.cybersource.com/api-reference-assets/index.html#payments_capture) API call. Include the capture ID in the POST request to cancel the capture.
182
182
This method makes a synchronous HTTP request by default. To make an
183
183
asynchronous HTTP request, please define a `callback` function
Void a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to cancel the payment.
380
+
Void a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to cancel the payment.
381
381
This method makes a synchronous HTTP request by default. To make an
382
382
asynchronous HTTP request, please define a `callback` function
Void a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to cancel the payment.
407
+
Void a Payment API is only used, if you have requested Authorization and Capture together in [/pts/v2/payments](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments) API call. Include the payment ID in the POST request to cancel the payment.
408
408
This method makes a synchronous HTTP request by default. To make an
409
409
asynchronous HTTP request, please define a `callback` function
Copy file name to clipboardexpand all lines: CyberSource/models/__init__.py
+2-1
Original file line number
Diff line number
Diff line change
@@ -176,12 +176,13 @@
176
176
from .pts_v2_payments_post201_response_order_information_amount_detailsimportPtsV2PaymentsPost201ResponseOrderInformationAmountDetails
177
177
from .pts_v2_payments_post201_response_order_information_invoice_detailsimportPtsV2PaymentsPost201ResponseOrderInformationInvoiceDetails
178
178
from .pts_v2_payments_post201_response_order_information_reward_points_detailsimportPtsV2PaymentsPost201ResponseOrderInformationRewardPointsDetails
179
+
from .pts_v2_payments_post201_response_payment_account_informationimportPtsV2PaymentsPost201ResponsePaymentAccountInformation
180
+
from .pts_v2_payments_post201_response_payment_account_information_cardimportPtsV2PaymentsPost201ResponsePaymentAccountInformationCard
179
181
from .pts_v2_payments_post201_response_payment_informationimportPtsV2PaymentsPost201ResponsePaymentInformation
180
182
from .pts_v2_payments_post201_response_payment_information_account_featuresimportPtsV2PaymentsPost201ResponsePaymentInformationAccountFeatures
181
183
from .pts_v2_payments_post201_response_payment_information_account_features_balancesimportPtsV2PaymentsPost201ResponsePaymentInformationAccountFeaturesBalances
182
184
from .pts_v2_payments_post201_response_payment_information_bankimportPtsV2PaymentsPost201ResponsePaymentInformationBank
183
185
from .pts_v2_payments_post201_response_payment_information_bank_accountimportPtsV2PaymentsPost201ResponsePaymentInformationBankAccount
184
-
from .pts_v2_payments_post201_response_payment_information_cardimportPtsV2PaymentsPost201ResponsePaymentInformationCard
185
186
from .pts_v2_payments_post201_response_payment_information_instrument_identifierimportPtsV2PaymentsPost201ResponsePaymentInformationInstrumentIdentifier
186
187
from .pts_v2_payments_post201_response_payment_information_tokenized_cardimportPtsV2PaymentsPost201ResponsePaymentInformationTokenizedCard
187
188
from .pts_v2_payments_post201_response_point_of_sale_informationimportPtsV2PaymentsPost201ResponsePointOfSaleInformation
InvoicingV2InvoicesAllGet200ResponseCustomerInformation - a model defined in Swagger
44
46
"""
45
47
46
48
self._name=None
49
+
self._merchant_customer_id=None
47
50
48
51
ifnameisnotNone:
49
52
self.name=name
53
+
ifmerchant_customer_idisnotNone:
54
+
self.merchant_customer_id=merchant_customer_id
50
55
51
56
@property
52
57
defname(self):
@@ -71,6 +76,29 @@ def name(self, name):
71
76
72
77
self._name=name
73
78
79
+
@property
80
+
defmerchant_customer_id(self):
81
+
"""
82
+
Gets the merchant_customer_id of this InvoicingV2InvoicesAllGet200ResponseCustomerInformation.
83
+
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)
84
+
85
+
:return: The merchant_customer_id of this InvoicingV2InvoicesAllGet200ResponseCustomerInformation.
Sets the merchant_customer_id of this InvoicingV2InvoicesAllGet200ResponseCustomerInformation.
94
+
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)
95
+
96
+
:param merchant_customer_id: The merchant_customer_id of this InvoicingV2InvoicesAllGet200ResponseCustomerInformation.
0 commit comments