cybersource-rest-client 0.0.36 → 0.0.39

package/docs/TssV2TransactionsGet200ResponseRiskInformation.md

@@ -1,13 +1,13 @@
-# CyberSource.TssV2TransactionsGet200ResponseRiskInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**profile** | [**TssV2TransactionsGet200ResponseRiskInformationProfile**](TssV2TransactionsGet200ResponseRiskInformationProfile.md) |  | [optional] 
-**rules** | [**[TssV2TransactionsGet200ResponseRiskInformationRules]**](TssV2TransactionsGet200ResponseRiskInformationRules.md) |  | [optional] 
-**passiveProfile** | [**TssV2TransactionsGet200ResponseRiskInformationProfile**](TssV2TransactionsGet200ResponseRiskInformationProfile.md) |  | [optional] 
-**passiveRules** | [**[TssV2TransactionsGet200ResponseRiskInformationRules]**](TssV2TransactionsGet200ResponseRiskInformationRules.md) |  | [optional] 
-**score** | [**TssV2TransactionsGet200ResponseRiskInformationScore**](TssV2TransactionsGet200ResponseRiskInformationScore.md) |  | [optional] 
-**localTime** | **String** | Time that the transaction was submitted in local time. Generated by Cybersource. | [optional] 
-
-
+# CyberSource.TssV2TransactionsGet200ResponseRiskInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**profile** | [**TssV2TransactionsGet200ResponseRiskInformationProfile**](TssV2TransactionsGet200ResponseRiskInformationProfile.md) |  | [optional] 
+**rules** | [**[TssV2TransactionsGet200ResponseRiskInformationRules]**](TssV2TransactionsGet200ResponseRiskInformationRules.md) |  | [optional] 
+**passiveProfile** | [**TssV2TransactionsGet200ResponseRiskInformationProfile**](TssV2TransactionsGet200ResponseRiskInformationProfile.md) |  | [optional] 
+**passiveRules** | [**[TssV2TransactionsGet200ResponseRiskInformationRules]**](TssV2TransactionsGet200ResponseRiskInformationRules.md) |  | [optional] 
+**score** | [**TssV2TransactionsGet200ResponseRiskInformationScore**](TssV2TransactionsGet200ResponseRiskInformationScore.md) |  | [optional] 
+**localTime** | **String** | Time that the transaction was submitted in local time. Generated by Cybersource. | [optional] 
+
+

package/docs/TssV2TransactionsGet200ResponseRiskInformationProfile.md

@@ -1,9 +1,9 @@
-# CyberSource.TssV2TransactionsGet200ResponseRiskInformationProfile
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**name** | **String** | The name of the profile.  | [optional] 
-**decision** | **String** | Decision returned by the profile; this field contains one of these values: - ACCEPT - REJECT - REVIEW  | [optional] 
-
-
+# CyberSource.TssV2TransactionsGet200ResponseRiskInformationProfile
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**name** | **String** | The name of the profile.  | [optional] 
+**decision** | **String** | Decision returned by the profile; this field contains one of these values: - ACCEPT - REJECT - REVIEW  | [optional] 
+
+

package/docs/TssV2TransactionsGet200ResponseRiskInformationRules.md

@@ -1,9 +1,9 @@
-# CyberSource.TssV2TransactionsGet200ResponseRiskInformationRules
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**name** | **String** | Description of the rule as it appears in the Profile Editor. | [optional] 
-**decision** | **String** | Summarizes the result for the rule according to the setting that you chose in the Profile Editor. This field can contain one of the following values: - `IGNORE` - `REVIEW` - `REJECT` - `ACCEPT`  | [optional] 
-
-
+# CyberSource.TssV2TransactionsGet200ResponseRiskInformationRules
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**name** | **String** | Description of the rule as it appears in the Profile Editor. | [optional] 
+**decision** | **String** | Summarizes the result for the rule according to the setting that you chose in the Profile Editor. This field can contain one of the following values: - `IGNORE` - `REVIEW` - `REJECT` - `ACCEPT`  | [optional] 
+
+

package/docs/TssV2TransactionsGet200ResponseRiskInformationScore.md

@@ -1,9 +1,9 @@
-# CyberSource.TssV2TransactionsGet200ResponseRiskInformationScore
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**factorCodes** | **[String]** | Array of factor codes. | [optional] 
-**result** | **Number** | The description for this field is not available.  | [optional] 
-
-
+# CyberSource.TssV2TransactionsGet200ResponseRiskInformationScore
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**factorCodes** | **[String]** | Array of factor codes. | [optional] 
+**result** | **Number** | The description for this field is not available.  | [optional] 
+
+

package/docs/TssV2TransactionsGet200ResponseSenderInformation.md

@@ -1,8 +1,8 @@
-# CyberSource.TssV2TransactionsGet200ResponseSenderInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**referenceNumber** | **String** | Reference number generated by you that uniquely identifies the sender. | [optional] 
-
-
+# CyberSource.TssV2TransactionsGet200ResponseSenderInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**referenceNumber** | **String** | Reference number generated by you that uniquely identifies the sender. | [optional] 
+
+

package/docs/TssV2TransactionsGet200ResponseTokenInformation.md

@@ -1,11 +1,11 @@
-# CyberSource.TssV2TransactionsGet200ResponseTokenInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**customer** | [**PtsV2PaymentsPost201ResponseTokenInformationCustomer**](PtsV2PaymentsPost201ResponseTokenInformationCustomer.md) |  | [optional] 
-**paymentInstrument** | [**PtsV2PaymentsPost201ResponseTokenInformationPaymentInstrument**](PtsV2PaymentsPost201ResponseTokenInformationPaymentInstrument.md) |  | [optional] 
-**shippingAddress** | [**PtsV2PaymentsPost201ResponseTokenInformationShippingAddress**](PtsV2PaymentsPost201ResponseTokenInformationShippingAddress.md) |  | [optional] 
-**instrumentIdentifier** | [**TssV2TransactionsGet200ResponsePaymentInformationInstrumentIdentifier**](TssV2TransactionsGet200ResponsePaymentInformationInstrumentIdentifier.md) |  | [optional] 
-
-
+# CyberSource.TssV2TransactionsGet200ResponseTokenInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**customer** | [**PtsV2PaymentsPost201ResponseTokenInformationCustomer**](PtsV2PaymentsPost201ResponseTokenInformationCustomer.md) |  | [optional] 
+**paymentInstrument** | [**PtsV2PaymentsPost201ResponseTokenInformationPaymentInstrument**](PtsV2PaymentsPost201ResponseTokenInformationPaymentInstrument.md) |  | [optional] 
+**shippingAddress** | [**PtsV2PaymentsPost201ResponseTokenInformationShippingAddress**](PtsV2PaymentsPost201ResponseTokenInformationShippingAddress.md) |  | [optional] 
+**instrumentIdentifier** | [**TssV2TransactionsGet200ResponsePaymentInformationInstrumentIdentifier**](TssV2TransactionsGet200ResponsePaymentInformationInstrumentIdentifier.md) |  | [optional] 
+
+

package/docs/TssV2TransactionsPost201Response.md

@@ -1,21 +1,21 @@
-# CyberSource.TssV2TransactionsPost201Response
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**searchId** | **String** | An unique identification number assigned by CyberSource to identify each Search request. | [optional] 
-**save** | **Boolean** | Indicates whether or not you want to save this search request for future use. The options are:  * `true` * `false` (default value)  If set to `true`, this field returns `searchID` in the response. You can use this value to retrieve the details of the saved search.  | [optional] 
-**name** | **String** | Name of this search. When `save` is set to `true`, this search is saved with this name.  | [optional] 
-**timezone** | **String** | Merchant’s time zone in ISO standard, using the TZ database format. For example: `America/Chicago`  | [optional] 
-**query** | **String** | String that contains the filters and variables for which you want to search. For information about supported field-filters and operators, see the [Query Filters]( https://developer.cybersource.com/api/developer-guides/dita-txn-search-details-rest-api-dev-guide-102718/txn-search-intro/txn-filtering.html) section of the Transaction Search Developer Guide.  | [optional] 
-**offset** | **Number** | Controls the starting point within the collection of results, which defaults to 0. The first item in the collection is retrieved by setting a zero offset.  For example, if you have a collection of 15 items to be retrieved from a resource and you specify limit=5, you can retrieve the entire set of results in 3 successive requests by varying the offset value like this:  `offset=0` `offset=5` `offset=10`  **Note:** If an offset larger than the number of results is provided, this will result in no embedded object being returned.  | [optional] 
-**limit** | **Number** | Controls the maximum number of items that may be returned for a single request. The default is 20, the maximum is 2000.  | [optional] 
-**sort** | **String** | A comma separated list of the following form:  `submitTimeUtc:desc`  | [optional] 
-**count** | **Number** | Results for this page, this could be below the limit. | [optional] 
-**totalCount** | **Number** | Total number of results. | [optional] 
-**status** | **String** | The status of the submitted transaction. | [optional] 
-**submitTimeUtc** | **String** | Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC.  Returned by Cybersource for all services.  | [optional] 
-**embedded** | [**TssV2TransactionsPost201ResponseEmbedded**](TssV2TransactionsPost201ResponseEmbedded.md) |  | [optional] 
-**links** | [**PtsV2IncrementalAuthorizationPatch201ResponseLinks**](PtsV2IncrementalAuthorizationPatch201ResponseLinks.md) |  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201Response
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**searchId** | **String** | An unique identification number assigned by CyberSource to identify each Search request. | [optional] 
+**save** | **Boolean** | Indicates whether or not you want to save this search request for future use. The options are:  * `true` * `false` (default value)  If set to `true`, this field returns `searchID` in the response. You can use this value to retrieve the details of the saved search.  | [optional] 
+**name** | **String** | Name of this search. When `save` is set to `true`, this search is saved with this name.  | [optional] 
+**timezone** | **String** | Merchant’s time zone in ISO standard, using the TZ database format. For example: `America/Chicago`  | [optional] 
+**query** | **String** | String that contains the filters and variables for which you want to search. For information about supported field-filters and operators, see the [Query Filters]( https://developer.cybersource.com/api/developer-guides/dita-txn-search-details-rest-api-dev-guide-102718/txn-search-intro/txn-filtering.html) section of the Transaction Search Developer Guide.  | [optional] 
+**offset** | **Number** | Controls the starting point within the collection of results, which defaults to 0. The first item in the collection is retrieved by setting a zero offset.  For example, if you have a collection of 15 items to be retrieved from a resource and you specify limit=5, you can retrieve the entire set of results in 3 successive requests by varying the offset value like this:  `offset=0` `offset=5` `offset=10`  **Note:** If an offset larger than the number of results is provided, this will result in no embedded object being returned.  | [optional] 
+**limit** | **Number** | Controls the maximum number of items that may be returned for a single request. The default is 20, the maximum is 2000.  | [optional] 
+**sort** | **String** | A comma separated list of the following form:  `submitTimeUtc:desc`  | [optional] 
+**count** | **Number** | Results for this page, this could be below the limit. | [optional] 
+**totalCount** | **Number** | Total number of results. | [optional] 
+**status** | **String** | The status of the submitted transaction. | [optional] 
+**submitTimeUtc** | **String** | Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC.  Returned by Cybersource for all services.  | [optional] 
+**embedded** | [**TssV2TransactionsPost201ResponseEmbedded**](TssV2TransactionsPost201ResponseEmbedded.md) |  | [optional] 
+**links** | [**PtsV2IncrementalAuthorizationPatch201ResponseLinks**](PtsV2IncrementalAuthorizationPatch201ResponseLinks.md) |  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbedded.md

@@ -1,8 +1,8 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbedded
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**transactionSummaries** | [**[TssV2TransactionsPost201ResponseEmbeddedTransactionSummaries]**](TssV2TransactionsPost201ResponseEmbeddedTransactionSummaries.md) | transaction search summary | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbedded
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**transactionSummaries** | [**[TssV2TransactionsPost201ResponseEmbeddedTransactionSummaries]**](TssV2TransactionsPost201ResponseEmbeddedTransactionSummaries.md) | transaction search summary | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedApplicationInformation.md

@@ -1,12 +1,12 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedApplicationInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**reasonCode** | **String** | Indicates the reason why a request succeeded or failed and possible action to take if a request fails.  For details, see the appendix of reason codes in the documentation for the relevant payment method.  | [optional] 
-**rCode** | **String** | Indicates whether the service request was successful. Possible values:  - `-1`: An error occurred. - `0`: The request was declined. - `1`: The request was successful.  | [optional] 
-**rFlag** | **String** | One-word description of the result of the application.  | [optional] 
-**applications** | [**[TssV2TransactionsPost201ResponseEmbeddedApplicationInformationApplications]**](TssV2TransactionsPost201ResponseEmbeddedApplicationInformationApplications.md) |  | [optional] 
-**returnCode** | **Number** | The description for this field is not available. | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedApplicationInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**reasonCode** | **String** | Indicates the reason why a request succeeded or failed and possible action to take if a request fails.  For details, see the appendix of reason codes in the documentation for the relevant payment method.  | [optional] 
+**rCode** | **String** | Indicates whether the service request was successful. Possible values:  - `-1`: An error occurred. - `0`: The request was declined. - `1`: The request was successful.  | [optional] 
+**rFlag** | **String** | One-word description of the result of the application.  | [optional] 
+**applications** | [**[TssV2TransactionsPost201ResponseEmbeddedApplicationInformationApplications]**](TssV2TransactionsPost201ResponseEmbeddedApplicationInformationApplications.md) |  | [optional] 
+**returnCode** | **Number** | The description for this field is not available. | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedApplicationInformationApplications.md

@@ -1,14 +1,14 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedApplicationInformationApplications
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**name** | **String** | The name of the CyberSource transaction type (such as CC settlement or CC authorization) that the merchant wants to process in a transaction request. More than one transaction type can included in a transaction request. Each transaction type separately returns their own status, reasonCode, rCode, and rFlag messages.  | [optional] 
-**reasonCode** | **String** | 3-digit reason code that indicates why the customer profile payment succeeded or failed. | [optional] 
-**rCode** | **String** | Indicates whether the service request was successful. Possible values:  - `-1`: An error occurred. - `0`: The request was declined. - `1`: The request was successful.  | [optional] 
-**rFlag** | **String** | One-word description of the result of the application.  | [optional] 
-**reconciliationId** | **String** | Reference number that you use to reconcile your CyberSource reports with your processor reports.  | [optional] 
-**rMessage** | **String** | Message that explains the reply flag for the application.  | [optional] 
-**returnCode** | **Number** | The description for this field is not available. | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedApplicationInformationApplications
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**name** | **String** | The name of the CyberSource transaction type (such as CC settlement or CC authorization) that the merchant wants to process in a transaction request. More than one transaction type can included in a transaction request. Each transaction type separately returns their own status, reasonCode, rCode, and rFlag messages.  | [optional] 
+**reasonCode** | **String** | 3-digit reason code that indicates why the customer profile payment succeeded or failed. | [optional] 
+**rCode** | **String** | Indicates whether the service request was successful. Possible values:  - `-1`: An error occurred. - `0`: The request was declined. - `1`: The request was successful.  | [optional] 
+**rFlag** | **String** | One-word description of the result of the application.  | [optional] 
+**reconciliationId** | **String** | Reference number that you use to reconcile your CyberSource reports with your processor reports.  | [optional] 
+**rMessage** | **String** | Message that explains the reply flag for the application.  | [optional] 
+**returnCode** | **Number** | The description for this field is not available. | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedBuyerInformation.md

@@ -1,8 +1,8 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedBuyerInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**merchantCustomerId** | **String** | 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)  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedBuyerInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**merchantCustomerId** | **String** | 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)  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedClientReferenceInformation.md

@@ -1,11 +1,11 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedClientReferenceInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**code** | **String** | Merchant-generated order reference or tracking number. It is recommended that you send a unique value for each transaction so that you can perform meaningful searches for the transaction.  #### Used by **Authorization** Required field.  #### PIN Debit Requests for PIN debit reversals need to use the same merchant reference number that was used in the transaction that is being reversed.  Required field for all PIN Debit requests (purchase, credit, and reversal).  #### FDC Nashville Global Certain circumstances can cause the processor to truncate this value to 15 or 17 characters for Level II and Level III processing, which can cause a discrepancy between the value you submit and the value included in some processor reports.  | [optional] 
-**applicationName** | **String** | The name of the Connection Method client (such as Virtual Terminal or SOAP Toolkit API) that the merchant uses to send a transaction request to CyberSource.  | [optional] 
-**applicationUser** | **String** | The entity that is responsible for running the transaction and submitting the processing request to CyberSource. This could be a person, a system, or a connection method.  | [optional] 
-**partner** | [**TssV2TransactionsGet200ResponseClientReferenceInformationPartner**](TssV2TransactionsGet200ResponseClientReferenceInformationPartner.md) |  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedClientReferenceInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**code** | **String** | Merchant-generated order reference or tracking number. It is recommended that you send a unique value for each transaction so that you can perform meaningful searches for the transaction.  #### Used by **Authorization** Required field.  #### PIN Debit Requests for PIN debit reversals need to use the same merchant reference number that was used in the transaction that is being reversed.  Required field for all PIN Debit requests (purchase, credit, and reversal).  #### FDC Nashville Global Certain circumstances can cause the processor to truncate this value to 15 or 17 characters for Level II and Level III processing, which can cause a discrepancy between the value you submit and the value included in some processor reports.  | [optional] 
+**applicationName** | **String** | The name of the Connection Method client (such as Virtual Terminal or SOAP Toolkit API) that the merchant uses to send a transaction request to CyberSource.  | [optional] 
+**applicationUser** | **String** | The entity that is responsible for running the transaction and submitting the processing request to CyberSource. This could be a person, a system, or a connection method.  | [optional] 
+**partner** | [**TssV2TransactionsGet200ResponseClientReferenceInformationPartner**](TssV2TransactionsGet200ResponseClientReferenceInformationPartner.md) |  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedConsumerAuthenticationInformation.md

@@ -1,10 +1,10 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedConsumerAuthenticationInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**xid** | **String** | Transaction identifier.  For details, see `xid` request field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  | [optional] 
-**transactionId** | **String** | Payer auth Transaction identifier. | [optional] 
-**eciRaw** | **String** | Raw electronic commerce indicator (ECI).  For details, see `eci_raw` request field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedConsumerAuthenticationInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**xid** | **String** | Transaction identifier.  For details, see `xid` request field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  | [optional] 
+**transactionId** | **String** | Payer auth Transaction identifier. | [optional] 
+**eciRaw** | **String** | Raw electronic commerce indicator (ECI).  For details, see `eci_raw` request field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedLinks.md

@@ -1,8 +1,8 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedLinks
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**transactionDetail** | [**PtsV2PaymentsPost201ResponseLinksSelf**](PtsV2PaymentsPost201ResponseLinksSelf.md) |  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedLinks
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**transactionDetail** | [**PtsV2PaymentsPost201ResponseLinksSelf**](PtsV2PaymentsPost201ResponseLinksSelf.md) |  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedMerchantInformation.md

@@ -1,8 +1,8 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedMerchantInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**resellerId** | **String** | An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedMerchantInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**resellerId** | **String** | An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response.  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedOrderInformation.md

@@ -1,10 +1,10 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedOrderInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**billTo** | [**TssV2TransactionsPost201ResponseEmbeddedOrderInformationBillTo**](TssV2TransactionsPost201ResponseEmbeddedOrderInformationBillTo.md) |  | [optional] 
-**shipTo** | [**TssV2TransactionsPost201ResponseEmbeddedOrderInformationShipTo**](TssV2TransactionsPost201ResponseEmbeddedOrderInformationShipTo.md) |  | [optional] 
-**amountDetails** | [**Ptsv2paymentsidreversalsReversalInformationAmountDetails**](Ptsv2paymentsidreversalsReversalInformationAmountDetails.md) |  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedOrderInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**billTo** | [**TssV2TransactionsPost201ResponseEmbeddedOrderInformationBillTo**](TssV2TransactionsPost201ResponseEmbeddedOrderInformationBillTo.md) |  | [optional] 
+**shipTo** | [**TssV2TransactionsPost201ResponseEmbeddedOrderInformationShipTo**](TssV2TransactionsPost201ResponseEmbeddedOrderInformationShipTo.md) |  | [optional] 
+**amountDetails** | [**Ptsv2paymentsidreversalsReversalInformationAmountDetails**](Ptsv2paymentsidreversalsReversalInformationAmountDetails.md) |  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedOrderInformationBillTo.md

@@ -1,13 +1,13 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedOrderInformationBillTo
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**firstName** | **String** | Customer’s first name. This name must be the same as the name on the card.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### CyberSource Latin American Processing **Important** For an authorization request, CyberSource Latin American Processing concatenates `orderInformation.billTo.firstName` and `orderInformation.billTo.lastName`. If the concatenated value exceeds 30 characters, CyberSource Latin American Processing declines the authorization request.\\ **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.  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  #### For Payouts: This field may be sent only for FDC Compass.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### OmniPay Direct Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
-**lastName** | **String** | Customer’s last name. This name must be the same as the name on the card.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### CyberSource Latin American Processing **Important** For an authorization request, CyberSource Latin American Processing concatenates `orderInformation.billTo.firstName` and `orderInformation.billTo.lastName`. If the concatenated value exceeds 30 characters, CyberSource Latin American Processing declines the authorization request.\\ **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.  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  #### For Payouts: This field may be sent only for FDC Compass.  #### OmniPay Direct Optional field.  #### RBS WorldPay Atlanta Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
-**address1** | **String** | Payment card billing street address as it appears on the credit card issuer’s records.  #### Atos This field must not contain colons (:).  #### CyberSource through VisaNet **Important** When you populate orderInformation.billTo.address1 and orderInformation.billTo.address2, CyberSource through VisaNet concatenates the two values. If the concatenated value exceeds 40 characters, CyberSource through VisaNet truncates the value at 40 characters before sending it to Visa and the issuing bank. Truncating this value affects AVS results and therefore might also affect risk decisions and chargebacks. Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  #### FDMS Nashville When the street name is numeric, it must be sent in numeric format. For example, if the address is _One First Street_, it must be sent as _1 1st Street_.  Required if keyed; not used if swiped.  String (20)  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### All other processors: Optional. String (60)  #### For Payouts This field may be sent only for FDC Compass.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  | [optional] 
-**email** | **String** | Customer's email address, including the full domain name.  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  For processor-specific information, see the `customer_email` request-level field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)  #### Invoicing Email address for the customer for sending the invoice. If the invoice is in SENT status and email is updated, the old email customer payment link won't work and you must resend the invoice with the new payment link.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### OmniPay Direct Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
-**country** | **String** | Payment card billing country. Use the two-character [ISO Standard Country Codes](http://apps.cybersource.com/library/documentation/sbc/quickref/countries_alpha_list.pdf).  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### OmniPay Direct Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
-**phoneNumber** | **String** | Customer’s phone number.  It is recommended that you include the country code when the order is from outside the U.S.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  #### For Payouts: This field may be sent only for FDC Compass.  #### OmniPay Direct Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Optional field.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedOrderInformationBillTo
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**firstName** | **String** | Customer’s first name. This name must be the same as the name on the card.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### CyberSource Latin American Processing **Important** For an authorization request, CyberSource Latin American Processing concatenates `orderInformation.billTo.firstName` and `orderInformation.billTo.lastName`. If the concatenated value exceeds 30 characters, CyberSource Latin American Processing declines the authorization request.\\ **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.  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  #### For Payouts: This field may be sent only for FDC Compass.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### OmniPay Direct Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
+**lastName** | **String** | Customer’s last name. This name must be the same as the name on the card.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### CyberSource Latin American Processing **Important** For an authorization request, CyberSource Latin American Processing concatenates `orderInformation.billTo.firstName` and `orderInformation.billTo.lastName`. If the concatenated value exceeds 30 characters, CyberSource Latin American Processing declines the authorization request.\\ **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.  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  #### For Payouts: This field may be sent only for FDC Compass.  #### OmniPay Direct Optional field.  #### RBS WorldPay Atlanta Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
+**address1** | **String** | Payment card billing street address as it appears on the credit card issuer’s records.  #### Atos This field must not contain colons (:).  #### CyberSource through VisaNet **Important** When you populate orderInformation.billTo.address1 and orderInformation.billTo.address2, CyberSource through VisaNet concatenates the two values. If the concatenated value exceeds 40 characters, CyberSource through VisaNet truncates the value at 40 characters before sending it to Visa and the issuing bank. Truncating this value affects AVS results and therefore might also affect risk decisions and chargebacks. Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  #### FDMS Nashville When the street name is numeric, it must be sent in numeric format. For example, if the address is _One First Street_, it must be sent as _1 1st Street_.  Required if keyed; not used if swiped.  String (20)  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### All other processors: Optional. String (60)  #### For Payouts This field may be sent only for FDC Compass.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  | [optional] 
+**email** | **String** | Customer's email address, including the full domain name.  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  For processor-specific information, see the `customer_email` request-level field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html)  #### Invoicing Email address for the customer for sending the invoice. If the invoice is in SENT status and email is updated, the old email customer payment link won't work and you must resend the invoice with the new payment link.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### OmniPay Direct Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
+**country** | **String** | Payment card billing country. Use the two-character [ISO Standard Country Codes](http://apps.cybersource.com/library/documentation/sbc/quickref/countries_alpha_list.pdf).  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### OmniPay Direct Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Required when `processingInformation.billPaymentOptions.billPayment=true` and `pointOfSaleInformation.entryMode=keyed`.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
+**phoneNumber** | **String** | Customer’s phone number.  It is recommended that you include the country code when the order is from outside the U.S.  #### Chase Paymentech Solutions Optional field.  ####  Credit Mutuel-CIC Optional field.  #### CyberSource through VisaNet Credit card networks cannot process transactions that contain non-ASCII characters. CyberSource through VisaNet accepts and stores non-ASCII characters correctly and displays them correctly in reports. However, the limitations of the credit card networks prevent CyberSource through VisaNet from transmitting non-ASCII characters to the credit card networks. Therefore, CyberSource through VisaNet replaces non-ASCII characters with meaningless ASCII characters for transmission to the credit card networks.  #### For Payouts: This field may be sent only for FDC Compass.  #### OmniPay Direct Optional field.  #### SIX Optional field.  #### TSYS Acquiring Solutions Optional field.  #### Worldpay VAP Optional field.  #### All other processors Not used.  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedOrderInformationShipTo.md

@@ -1,12 +1,12 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedOrderInformationShipTo
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**firstName** | **String** | First name of the recipient.  #### Litle Maximum length: 25  #### All other processors Maximum length: 60  Optional field.  | [optional] 
-**lastName** | **String** | Last name of the recipient.  #### Litle Maximum length: 25  #### All other processors Maximum length: 60  Optional field.  | [optional] 
-**address1** | **String** | First line of the shipping address.  Required field for authorization if any shipping address information is included in the request; otherwise, optional.  #### Tax Calculation Optional field for U.S. and Canadian taxes. Not applicable to international and value added taxes. Billing address objects will be used to determine the cardholder’s location when shipTo objects are not present.  | [optional] 
-**country** | **String** | Country of the shipping address. Use the two-character [ISO Standard Country Codes.](http://apps.cybersource.com/library/documentation/sbc/quickref/countries_alpha_list.pdf)  Required field for authorization if any shipping address information is included in the request; otherwise, optional.  #### Tax Calculation Optional field for U.S., Canadian, international tax, and value added taxes. Billing address objects will be used to determine the cardholder’s location when shipTo objects are not present.  | [optional] 
-**phoneNumber** | **String** | Phone number associated with the shipping address. | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedOrderInformationShipTo
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**firstName** | **String** | First name of the recipient.  #### Litle Maximum length: 25  #### All other processors Maximum length: 60  Optional field.  | [optional] 
+**lastName** | **String** | Last name of the recipient.  #### Litle Maximum length: 25  #### All other processors Maximum length: 60  Optional field.  | [optional] 
+**address1** | **String** | First line of the shipping address.  Required field for authorization if any shipping address information is included in the request; otherwise, optional.  #### Tax Calculation Optional field for U.S. and Canadian taxes. Not applicable to international and value added taxes. Billing address objects will be used to determine the cardholder’s location when shipTo objects are not present.  | [optional] 
+**country** | **String** | Country of the shipping address. Use the two-character [ISO Standard Country Codes.](http://apps.cybersource.com/library/documentation/sbc/quickref/countries_alpha_list.pdf)  Required field for authorization if any shipping address information is included in the request; otherwise, optional.  #### Tax Calculation Optional field for U.S., Canadian, international tax, and value added taxes. Billing address objects will be used to determine the cardholder’s location when shipTo objects are not present.  | [optional] 
+**phoneNumber** | **String** | Phone number associated with the shipping address. | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedPaymentInformation.md

@@ -1,10 +1,11 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedPaymentInformation
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**paymentType** | [**TssV2TransactionsPost201ResponseEmbeddedPaymentInformationPaymentType**](TssV2TransactionsPost201ResponseEmbeddedPaymentInformationPaymentType.md) |  | [optional] 
-**customer** | [**Riskv1authenticationsetupsPaymentInformationCustomer**](Riskv1authenticationsetupsPaymentInformationCustomer.md) |  | [optional] 
-**card** | [**TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCard**](TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCard.md) |  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedPaymentInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**paymentType** | [**TssV2TransactionsPost201ResponseEmbeddedPaymentInformationPaymentType**](TssV2TransactionsPost201ResponseEmbeddedPaymentInformationPaymentType.md) |  | [optional] 
+**customer** | [**TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCustomer**](TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCustomer.md) |  | [optional] 
+**card** | [**TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCard**](TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCard.md) |  | [optional] 
+**bank** | [**TssV2TransactionsPost201ResponseEmbeddedPaymentInformationBank**](TssV2TransactionsPost201ResponseEmbeddedPaymentInformationBank.md) |  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedPaymentInformationBank.md

@@ -0,0 +1,8 @@
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedPaymentInformationBank
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**account** | [**TssV2TransactionsPost201ResponseEmbeddedPaymentInformationBankAccount**](TssV2TransactionsPost201ResponseEmbeddedPaymentInformationBankAccount.md) |  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedPaymentInformationBankAccount.md

@@ -0,0 +1,9 @@
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedPaymentInformationBankAccount
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**suffix** | **String** | Last four digits of the customer’s payment account number.  | [optional] 
+**prefix** | **String** | Bank Identification Number (BIN). This is the initial four to six numbers on a credit card account number.  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCard.md

@@ -1,10 +1,10 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCard
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**suffix** | **String** | Last four digits of the cardholder’s account number. This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details.  You must contact customer support to have your account enabled to receive these fields in the credit reply message.  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  #### PIN debit This field is returned only for tokenized transactions. You can use this value on the receipt that you give to the cardholder.  Returned by PIN debit credit and PIN debit purchase.  This field is supported only by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX  | [optional] 
-**prefix** | **String** | Bank Identification Number (BIN). This is the initial four to six numbers on a credit card account number.  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  | [optional] 
-**type** | **String** | Three-digit value that indicates the card type.  **IMPORTANT** It is strongly recommended that you include the card type field in request messages even if it is optional for your processor and card type. Omitting the card type can cause the transaction to be processed with the wrong card type.  Possible values: - `001`: Visa. For card-present transactions on all processors except SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type value `001` for Visa Electron. - `002`: Mastercard, Eurocard[^1], which is a European regional brand of Mastercard. - `003`: American Express - `004`: Discover - `005`: Diners Club - `006`: Carte Blanche[^1] - `007`: JCB[^1] - `014`: Enroute[^1] - `021`: JAL[^1] - `024`: Maestro (UK Domestic)[^1] - `031`: Delta[^1]: Use this value only for Ingenico ePayments. For other processors, use `001` for all Visa card types. - `033`: Visa Electron[^1]. Use this value only for Ingenico ePayments and SIX. For other processors, use `001` for all Visa card types. - `034`: Dankort[^1] - `036`: Cartes Bancaires[^1,4] - `037`: Carta Si[^1] - `039`: Encoded account number[^1] - `040`: UATP[^1] - `042`: Maestro (International)[^1] - `050`: Hipercard[^2,3] - `051`: Aura - `054`: Elo[^3] - `062`: China UnionPay  [^1]: For this card type, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in your request for an authorization or a stand-alone credit. [^2]: For this card type on Cielo 3.0, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. This card type is not supported on Cielo 1.5. [^3]: For this card type on Getnet and Rede, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. [^4]: For this card type, you must include the `paymentInformation.card.type` in your request for any payer authentication services.  #### Used by **Authorization** Required for Carte Blanche and JCB. Optional for all other card types.  #### Card Present reply This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details. You must contact customer support to have your account enabled to receive these fields in the credit reply message.  Returned by the Credit service.  This reply field is only supported by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International  | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCard
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**suffix** | **String** | Last four digits of the cardholder’s account number. This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details.  You must contact customer support to have your account enabled to receive these fields in the credit reply message.  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  #### PIN debit This field is returned only for tokenized transactions. You can use this value on the receipt that you give to the cardholder.  Returned by PIN debit credit and PIN debit purchase.  This field is supported only by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX  | [optional] 
+**prefix** | **String** | Bank Identification Number (BIN). This is the initial four to six numbers on a credit card account number.  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  | [optional] 
+**type** | **String** | Three-digit value that indicates the card type.  **IMPORTANT** It is strongly recommended that you include the card type field in request messages even if it is optional for your processor and card type. Omitting the card type can cause the transaction to be processed with the wrong card type.  Possible values: - `001`: Visa. For card-present transactions on all processors except SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type value `001` for Visa Electron. - `002`: Mastercard, Eurocard[^1], which is a European regional brand of Mastercard. - `003`: American Express - `004`: Discover - `005`: Diners Club - `006`: Carte Blanche[^1] - `007`: JCB[^1] - `014`: Enroute[^1] - `021`: JAL[^1] - `024`: Maestro (UK Domestic)[^1] - `031`: Delta[^1]: Use this value only for Ingenico ePayments. For other processors, use `001` for all Visa card types. - `033`: Visa Electron[^1]. Use this value only for Ingenico ePayments and SIX. For other processors, use `001` for all Visa card types. - `034`: Dankort[^1] - `036`: Cartes Bancaires[^1,4] - `037`: Carta Si[^1] - `039`: Encoded account number[^1] - `040`: UATP[^1] - `042`: Maestro (International)[^1] - `050`: Hipercard[^2,3] - `051`: Aura - `054`: Elo[^3] - `062`: China UnionPay  [^1]: For this card type, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in your request for an authorization or a stand-alone credit. [^2]: For this card type on Cielo 3.0, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. This card type is not supported on Cielo 1.5. [^3]: For this card type on Getnet and Rede, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. [^4]: For this card type, you must include the `paymentInformation.card.type` in your request for any payer authentication services.  #### Used by **Authorization** Required for Carte Blanche and JCB. Optional for all other card types.  #### Card Present reply This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details. You must contact customer support to have your account enabled to receive these fields in the credit reply message.  Returned by the Credit service.  This reply field is only supported by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response.  #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCustomer.md

@@ -0,0 +1,8 @@
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedPaymentInformationCustomer
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**customerId** | **String** | Unique identifier for the customer's card and billing information.  When you use Payment Tokenization or Recurring Billing and you include this value in your request, many of the fields that are normally required for an authorization or credit become optional.  **NOTE** When you use Payment Tokenization or Recurring Billing, the value for the Customer ID is actually the Cybersource payment token for a customer. This token stores information such as the consumer’s card number so it can be applied towards bill payments, recurring payments, or one-time payments. By using this token in a payment API request, the merchant doesn't need to pass in data such as the card number or expiration date in the request itself.  For details, see the `subscription_id` field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/)  | [optional] 
+
+

package/docs/TssV2TransactionsPost201ResponseEmbeddedPaymentInformationPaymentType.md

@@ -1,9 +1,9 @@
-# CyberSource.TssV2TransactionsPost201ResponseEmbeddedPaymentInformationPaymentType
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**type** | **String** | Indicates the payment type used in this payment transaction. Example: credit card, check | [optional] 
-**method** | **String** | Indicates the payment method used in this payment transaction. | [optional] 
-
-
+# CyberSource.TssV2TransactionsPost201ResponseEmbeddedPaymentInformationPaymentType
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** | Indicates the payment type used in this payment transaction. Example: credit card, check | [optional] 
+**method** | **String** | Indicates the payment method used in this payment transaction. | [optional] 
+
+