cybersource-rest-client 0.0.62 → 0.0.64

package/MLE.md

@@ -0,0 +1,98 @@
+[![Generic badge](https://img.shields.io/badge/MLE-NEW-GREEN.svg)](https://shields.io/)
+
+# Message Level Encryption (MLE) Feature
+
+This feature provides an implementation of Message Level Encryption (MLE) for APIs provided by CyberSource, integrated within our SDK. This feature ensures secure communication by encrypting messages at the application level before they are sent over the network.
+
+## Configuration
+
+### Global MLE Configuration
+
+In the `merchantConfig` object, set the `useMLEGlobally` variable to enable or disable MLE for all supported APIs for the Rest SDK.
+
+- **Variable**: `useMLEGlobally`
+- **Type**: `boolean`
+- **Default**: `false`
+- **Description**: Enables MLE globally for all APIs when set to `true`. If set to `true`, it will enable MLE for all API calls that support MLE by CyberSource, unless overridden by `mapToControlMLEonAPI`.
+
+### API-level MLE Control
+
+Optionally, you can control the MLE feature at the API level using the `mapToControlMLEonAPI` variable in the `merchantConfig` object.
+
+- **Variable**: `mapToControlMLEonAPI`
+- **Type**: `Map<string, boolean>`
+- **Description**: Overrides the global MLE setting for specific APIs. The key is the function name of the API in the SDK, and the value is a boolean indicating whether MLE should be enabled (`true`) or disabled (`false`) for that specific API call.
+
+### MLE Key Alias
+
+Another optional parameter for MLE is `mleKeyAlias`, which specifies the key alias used to retrieve the MLE certificate from the JWT P12 file.
+
+- **Variable**: `mleKeyAlias`
+- **Type**: `string`
+- **Default**: `CyberSource_SJC_US`
+- **Description**: By default, CyberSource uses the `CyberSource_SJC_US` public certificate to encrypt the payload. However, users can override this default value by setting their own key alias.
+
+## Notes
+- If `useMLEGlobally` is set to true, it will enable MLE for all API calls that support MLE by CyberSource, unless overridden by mapToControlMLEonAPI.
+- If `mapToControlMLEonAPI` is not provided or does not contain a specific API function name, the global useMLEGlobally setting will be applied.
+- The `mleKeyAlias` parameter is optional and defaults to CyberSource_SJC_US if not specified by the user. Users can override this default value by setting their own key alias.
+
+## Example Configuration
+
+```json
+{
+  "merchantConfig": {
+    "useMLEGlobally": true //globally MLE will be enabled for all MLE supported APIs
+  }
+}
+```
+Or 
+
+```json
+{
+  "merchantConfig": {
+    "useMLEGlobally": true, //globally MLE will be enabled for all MLE supported APIs
+    "mapToControlMLEonAPI": {
+      "apiFunctionName1": false, //if want to disable the particular api from list of MLE supported APIs
+      "apiFunctionName2": true //if want to enable MLE on API which is not in the list of supported MLE APIs for used version of Rest SDK
+    },
+    "mleKeyAlias": "Custom_Key_Alias" //optional if any custom value provided by Cybs
+  }
+}
+```
+Or
+
+```json
+{
+  "merchantConfig": {
+    "useMLEGlobally": false, //globally MLE will be disabled for all APIs
+    "mapToControlMLEonAPI": {
+      "apiFunctionName1": true, //if want to enable MLE for API1
+      "apiFunctionName2": true //if want to enable MLE for API2
+    },
+    "mleKeyAlias": "Custom_Key_Alias" //optional if any custom value provided by Cybs
+  }
+}
+```
+
+In the above examples:
+- MLE is enabled/disabled globally (`useMLEGlobally` is true/false).
+- `apiFunctionName1` will have MLE disabled/enabled based on value provided.
+- `apiFunctionName2` will have MLE enabled.
+- `mleKeyAlias` is set to `Custom_Key_Alias`, overriding the default value.
+
+Please refer given link for sample codes with MLE:
+https://github.com/CyberSource/cybersource-rest-samples-node/tree/master/Samples/MLEFeature
+
+## Additional Information
+
+### API Support
+- MLE is initially designed to support a few APIs.
+- It can be extended to support more APIs in the future based on requirements and updates.
+### Authentication Type
+- MLE is only supported with `JWT (JSON Web Token)` authentication type within the SDK.
+### Using the SDK
+To use the MLE feature in the SDK, configure the `merchantConfig` object as shown above and pass it to the SDK initialization.
+
+## Contact
+For any issues or further assistance, please open an issue on the GitHub repository or contact our support team.

package/README.md

@@ -71,6 +71,13 @@ More information about this new logging framework can be found in this file : [L
 
 ## Features
 
+### Message Level Encryption (MLE) Feature
+[![Generic badge](https://img.shields.io/badge/MLE-NEW-GREEN.svg)](https://shields.io/)
+
+This feature provides an implementation of Message Level Encryption (MLE) for APIs provided by CyberSource, integrated within our SDK. This feature ensures secure communication by encrypting messages at the application level before they are sent over the network.
+
+More information about this new MLE feature can be found in this file : [MLE.md](MLE.md)
+
 ### MetaKey Support
 
 A Meta Key is a single key that can be used by one, some, or all merchants (or accounts, if created by a Portfolio user) in the portfolio.

package/docs/CommerceSolutionsProductsTokenManagementConfigurationInformationConfigurations.md

@@ -4,5 +4,6 @@
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **parentProfileId** | **String** | Specify the Vault ID to which transacting MID needs to be assigned.Provide Vault ID as seen on EBC Vault management page. If not provided , transacting MID will be assigned to the existing default Vault at merchant's level. If there are no Vaults at merchant level , a new Vault will be created and transacting MID will be assigned to it. | [optional] 
+**vault** | [**CommerceSolutionsProductsTokenManagementConfigurationInformationConfigurationsVault**](CommerceSolutionsProductsTokenManagementConfigurationInformationConfigurationsVault.md) |  | [optional] 
 
 

package/docs/CommerceSolutionsProductsTokenManagementConfigurationInformationConfigurationsVault.md

@@ -0,0 +1,14 @@
+# CyberSource.CommerceSolutionsProductsTokenManagementConfigurationInformationConfigurationsVault
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**defaultTokenType** | **String** | Default token type to be used. Possible Values:   - 'CUSTOMER'  - 'PAYMENT_INSTRUMENT'  - 'INSTRUMENT_IDENTIFIER'  | [optional] 
+**location** | **String** | Location where the vault will be stored.  Use 'IDC' (the Indian Data Centre) when merchant is storing token data in India  or 'GDC' (the Global Data Centre) for all other cases.  Possible Values:    - 'IDC'   - 'GDC'  | [optional] 
+**tokenFormats** | [**TmsTokenFormats**](TmsTokenFormats.md) |  | [optional] 
+**tokenPermissions** | [**TokenPermissions**](TokenPermissions.md) |  | [optional] 
+**sensitivePrivileges** | [**TmsSensitivePrivileges**](TmsSensitivePrivileges.md) |  | [optional] 
+**nullify** | [**TmsNullify**](TmsNullify.md) |  | [optional] 
+**networkTokenServices** | [**TmsNetworkTokenServices**](TmsNetworkTokenServices.md) |  | [optional] 
+
+

package/docs/CreatePaymentRequest.md

@@ -29,6 +29,7 @@ Name | Type | Description | Notes
 **riskInformation** | [**Ptsv2paymentsRiskInformation**](Ptsv2paymentsRiskInformation.md) |  | [optional] 
 **acquirerInformation** | [**Ptsv2paymentsAcquirerInformation**](Ptsv2paymentsAcquirerInformation.md) |  | [optional] 
 **recurringPaymentInformation** | [**Ptsv2paymentsRecurringPaymentInformation**](Ptsv2paymentsRecurringPaymentInformation.md) |  | [optional] 
+**unscheduledPaymentInformation** | [**Ptsv2paymentsUnscheduledPaymentInformation**](Ptsv2paymentsUnscheduledPaymentInformation.md) |  | [optional] 
 **hostedPaymentInformation** | [**Ptsv2paymentsHostedPaymentInformation**](Ptsv2paymentsHostedPaymentInformation.md) |  | [optional] 
 **watchlistScreeningInformation** | [**Ptsv2paymentsWatchlistScreeningInformation**](Ptsv2paymentsWatchlistScreeningInformation.md) |  | [optional] 
 

package/docs/ECheckConfigCommonInternalOnlyProcessors.md

@@ -7,8 +7,8 @@ Name | Type | Description | Notes
 **terminalId** | **String** | *NEW* The 'Terminal Id' aka TID, is an identifier used for with your payments processor. Depending on the processor and payment acceptance type this may also be the default Terminal ID used for Card Present and Virtual Terminal transactions. Applicable for VPC processors.  | [optional] 
 **enable15anTransactionReferenceNumber** | **Boolean** | *NEW* This ensures the transaction reference # contains an identifier that can be viewed in CYBS | [optional] [default to true]
 **portalSupportedPaytypes** | **String** | *NEW* This is used by the EBC2 application | [optional] [default to 'CHECK']
-**settlementMethod** | **Object** | *NEW* | [optional] 
-**verificationLevel** | **Object** | *NEW* | [optional] 
+**settlementMethod** | **String** | *NEW*  Possible values: - BEST_GUESS | [optional] [default to 'BEST_GUESS']
+**verificationLevel** | **String** | *NEW*  Possible values: - VALIDATION | [optional] [default to 'VALIDATION']
 **setCompletedState** | **Boolean** | *Moved* When set to Yes we will automatically update transactions to a completed status X-number of days after the transaction comes through; if no failure notification is received. When set to No means we will not update transaction status in this manner. For BAMS/Bank of America merchants, they should be set to No unless we are explicitly asked to set a merchant to YES. | [optional] [default to false]
 
 

package/docs/ECheckConfigCommonProcessors.md

@@ -7,7 +7,7 @@ Name | Type | Description | Notes
 **companyId** | **String** | *EXISTING* company ID assigned to merchant by Acquiring bank. This field is alphanumeric | [optional] 
 **batchGroup** | **String** | *EXISTING* Capture requests are grouped into a batch bound for your payment processor. The batch time can be identified by reading the last 2-digits as military time. E.g., <processor>_16 = your processing cutoff is 4PM PST. Please note if you are in a different location you may then need to convert time zone as well. | [optional] 
 **enableAccuityForAvs** | **Boolean** | *NEW* Accuity is the original validation service that checks the account/routing number for formatting issues. Used by WF and set to \"Yes\" unless told otherwise | [optional] [default to true]
-**accuityCheckType** | **Object** | *NEW* | [optional] 
+**accuityCheckType** | **String** | *NEW*  Possible values: - ALWAYS | [optional] [default to 'ALWAYS']
 **setCompletedState** | **Boolean** | *Moved* When set to Yes we will automatically update transactions to a completed status X-number of days after the transaction comes through; if no failure notification is received. When set to No means we will not update transaction status in this manner. For BAMS/Bank of America merchants, they should be set to No unless we are explicitly asked to set a merchant to YES. | [optional] [default to false]
 
 

package/docs/ECheckConfigFeaturesAccountValidationServiceInternalOnlyProcessors.md

@@ -3,6 +3,6 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**avsVersion** | **Object** | *NEW* | [optional] 
+**avsVersion** | **String** | *NEW*  Possible values: - 2 | [optional] [default to '2']
 
 

package/docs/ECheckConfigFeaturesAccountValidationServiceProcessors.md

@@ -6,11 +6,11 @@ Name | Type | Description | Notes
 **avsAccountOwnershipService** | **Boolean** | *NEW* Determined in WF eTicket if account has opted into the Account Ownership Service. | [optional] 
 **avsAccountStatusService** | **Boolean** | *NEW* Determined in WF eTicket if account has opted into the Account Status Service. | [optional] 
 **avsSignedAgreement** | **Boolean** | *NEW* Taken from Addendum Agreement Column in boarding form. | [optional] 
-**avsCalculatedResponseBehavior** | **Object** | *NEW* | [optional] 
+**avsCalculatedResponseBehavior** | **String** | *NEW*  Possible values: - continue | [optional] [default to 'continue']
 **avsAdditionalId** | **String** | *NEW* Also known as the Additional ID. Taken from the boarding form. | [optional] 
 **enableAvs** | **Boolean** | *NEW* | [optional] [default to true]
 **avsEntityId** | **String** | *NEW* Also known as the AVS Gateway Entity ID. | [optional] 
-**avsResultMode** | **Object** | *NEW* | [optional] 
+**avsResultMode** | **String** | *NEW*  Possible values: - FULL_RESPONSE - LOGIC_BOX | [optional] 
 **enableAvsTokenCreation** | **Boolean** | *NEW* Applicable if the merchant wants to run AVS on token creation requests only. | [optional] [default to false]
 
 

package/docs/GenerateCaptureContextRequest.md

@@ -3,9 +3,9 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**targetOrigins** | **[String]** | The [target origin](https://developer.mozilla.org/en-US/docs/Glossary/Origin) of the website on which you will be launching Microform is defined by the scheme (protocol), hostname (domain) and port number (if used).    You must use https://hostname (unless you use http://localhost) Wildcards are NOT supported.  Ensure that subdomains are included. Any valid top-level domain is supported (e.g. .com, .co.uk, .gov.br etc)  Examples:   - https://example.com   - https://subdomain.example.com   - https://example.com:8080<br><br>  If you are embedding within multiple nested iframes you need to specify the origins of all the browser contexts used, for example:    targetOrigins: [     \"https://example.com\",     \"https://basket.example.com\",     \"https://ecom.example.com\"   ]  | [optional] 
-**allowedCardNetworks** | **[String]** | The list of card networks you want to use for this Microform transaction.  Microform currently supports the following card networks: - VISA - MAESTRO - MASTERCARD - AMEX - DISCOVER - DINERSCLUB - JCB - CUP - CARTESBANCAIRES - CARNET  | [optional] 
 **clientVersion** | **String** | Specify the version of Microform that you want to use.  | [optional] 
-**checkoutApiInitialization** | [**Microformv2sessionsCheckoutApiInitialization**](Microformv2sessionsCheckoutApiInitialization.md) |  | [optional] 
+**targetOrigins** | **[String]** | The [target origin](https://developer.mozilla.org/en-US/docs/Glossary/Origin) of the website on which you will be launching Microform is defined by the scheme (protocol), hostname (domain) and port number (if used).    You must use https://hostname (unless you use http://localhost) Wildcards are NOT supported.  Ensure that subdomains are included. Any valid top-level domain is supported (e.g. .com, .co.uk, .gov.br etc)  Examples:   - https://example.com   - https://subdomain.example.com   - https://example.com:8080<br><br>  If you are embedding within multiple nested iframes you need to specify the origins of all the browser contexts used, for example:    targetOrigins: [     \"https://example.com\",     \"https://basket.example.com\",     \"https://ecom.example.com\"   ]  | [optional] 
+**allowedCardNetworks** | **[String]** | The list of card networks you want to use for this Microform transaction.  Microform currently supports the following card networks: - VISA - MASTERCARD - AMEX - CARNET - CARTESBANCAIRES - CUP - DINERSCLUB - DISCOVER - EFTPOS - ELO - JCB - JCREW - MADA - MAESTRO - MEEZA  **Important:**    - When integrating Microform (Accept Card) at least one card network should be specified in the allowedCardNetworks field in the capture context request.   - When integrating Microform (Accept Check) the allowedCardNetworks field is not required in the capture context request.   - When integrating both Microform (Accept Card) and Microform (Accept Check) at least one card network should be specified in the allowedCardNetworks field in the capture context request.  | [optional] 
+**allowedPaymentTypes** | **[String]** | The payment types that are allowed for the merchant.    Possible values when launching Microform: - CARD - CHECK <br><br>  | [optional] 
 
 

package/docs/GenerateUnifiedCheckoutCaptureContextRequest.md

@@ -3,14 +3,13 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**targetOrigins** | **[String]** | The [target origin](https://developer.mozilla.org/en-US/docs/Glossary/Origin) of the website on which you will be launching Unified Checkout is defined by the scheme (protocol), hostname (domain) and port number (if used).    You must use https://hostname (unless you use http://localhost) Wildcards are NOT supported.  Ensure that subdomains are included. Any valid top-level domain is supported (e.g. .com, .co.uk, .gov.br etc)  Examples:   - https://example.com   - https://subdomain.example.com   - https://example.com:8080<br><br>  If you are embedding within multiple nested iframes you need to specify the origins of all the browser contexts used, for example:    targetOrigins: [     \"https://example.com\",     \"https://basket.example.com\",     \"https://ecom.example.com\"   ]  | [optional] 
 **clientVersion** | **String** | Specify the version of Unified Checkout that you want to use. | [optional] 
-**allowedCardNetworks** | **[String]** | The list of card networks you want to use for this Unified Checkout transaction.  Unified Checkout currently supports the following card networks:   - VISA   - MASTERCARD   - AMEX   - DISCOVER   - DINERSCLUB   - JCB  | [optional] 
-**allowedPaymentTypes** | **[String]** | The payment types that are allowed for the merchant.    Possible values when launching Unified Checkout:   - PANENTRY                 - GOOGLEPAY   - SRC   - CHECK <br><br>  Possible values when launching Unified Checkout with Checkout API: - PANENTRY               - SRC <br><br>  Possible values when launching Click To Pay Drop-In UI: - CLICKTOPAY <br><br>  **Important:**    - SRC and CLICKTOPAY are only available for Visa, Mastercard and AMEX.  | [optional] 
+**targetOrigins** | **[String]** | The [target origin](https://developer.mozilla.org/en-US/docs/Glossary/Origin) of the website on which you will be launching Unified Checkout is defined by the scheme (protocol), hostname (domain) and port number (if used).    You must use https://hostname (unless you use http://localhost) Wildcards are NOT supported.  Ensure that subdomains are included. Any valid top-level domain is supported (e.g. .com, .co.uk, .gov.br etc)  Examples:   - https://example.com   - https://subdomain.example.com   - https://example.com:8080<br><br>  If you are embedding within multiple nested iframes you need to specify the origins of all the browser contexts used, for example:    targetOrigins: [     \"https://example.com\",     \"https://basket.example.com\",     \"https://ecom.example.com\"   ]  | [optional] 
+**allowedCardNetworks** | **[String]** | The list of card networks you want to use for this Unified Checkout transaction.  Unified Checkout currently supports the following card networks:     - VISA     - MASTERCARD     - AMEX     - CARNET     - CARTESBANCAIRES     - CUP     - DINERSCLUB     - DISCOVER     - EFTPOS     - ELO     - JCB     - JCREW     - MADA     - MAESTRO     - MEEZA  | [optional] 
+**allowedPaymentTypes** | **[String]** | The payment types that are allowed for the merchant.    Possible values when launching Unified Checkout:   - APPLEPAY   - CHECK   - CLICKTOPAY   - GOOGLEPAY   - PANENTRY                 - PAZE <br><br>  Possible values when launching Click To Pay Drop-In UI: - CLICKTOPAY <br><br>  **Important:**    - CLICKTOPAY only available for Visa, Mastercard and AMEX for saved cards.   - Visa and Mastercard will look to tokenize using network tokenization for all Click to Pay requests.  Click to Pay uses Click to Pay token requester IDs and not the merchant's existing token requester.   - Apple Pay, Google Pay, Check, and Paze can be used independently without requiring PAN entry in the allowedPaymentTypes field.  | [optional] 
 **country** | **String** | Country the purchase is originating from (e.g. country of the merchant).  Use the two-character ISO Standard  | [optional] 
 **locale** | **String** | Localization of the User experience conforming to the ISO 639-1 language standards and two-character ISO Standard Country Code.  Please refer to list of [supported locales through Unified Checkout](https://developer.cybersource.com/docs/cybs/en-us/unified-checkout/developer/all/rest/unified-checkout/uc-appendix-languages.html)  | [optional] 
 **captureMandate** | [**Upv1capturecontextsCaptureMandate**](Upv1capturecontextsCaptureMandate.md) |  | [optional] 
 **orderInformation** | [**Upv1capturecontextsOrderInformation**](Upv1capturecontextsOrderInformation.md) |  | [optional] 
-**checkoutApiInitialization** | [**Upv1capturecontextsCheckoutApiInitialization**](Upv1capturecontextsCheckoutApiInitialization.md) |  | [optional] 
 
 

package/docs/InlineResponse2011.md

@@ -6,8 +6,8 @@ Name | Type | Description | Notes
 **id** | **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] 
 **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] 
 **status** | **String** | The status of the submitted transaction.  Possible values:  - COMPLETED  - MULTIPLE  - NO MATCH  | [optional] 
-**paymentAccountInformation** | [**InlineResponse2011PaymentAccountInformation**](InlineResponse2011PaymentAccountInformation.md) |  | [optional] 
-**issuerInformation** | [**InlineResponse2011IssuerInformation**](InlineResponse2011IssuerInformation.md) |  | [optional] 
+**paymentAccountInformation** | [**TmsBinLookupPaymentAccountInformation**](TmsBinLookupPaymentAccountInformation.md) |  | [optional] 
+**issuerInformation** | [**TmsBinLookupIssuerInformation**](TmsBinLookupIssuerInformation.md) |  | [optional] 
 **payoutInformation** | [**InlineResponse2011PayoutInformation**](InlineResponse2011PayoutInformation.md) |  | [optional] 
 
 

package/docs/InstrumentIdentifierApi.md

@@ -79,7 +79,8 @@ var apiInstance = new CyberSource.InstrumentIdentifierApi();
 var instrumentIdentifierId = "instrumentIdentifierId_example"; // String | The Id of an Instrument Identifier.
 
 var opts = { 
-  'profileId': "profileId_example" // String | The Id of a profile containing user specific TMS configuration.
+  'profileId': "profileId_example", // String | The Id of a profile containing user specific TMS configuration.
+  'retrieveBinDetails': true // Boolean | Retrieve the Bin Details of PAN or network token
 };
 
 var callback = function(error, data, response) {
@@ -98,6 +99,7 @@ Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
  **instrumentIdentifierId** | **String**| The Id of an Instrument Identifier. | 
  **profileId** | **String**| The Id of a profile containing user specific TMS configuration. | [optional] 
+ **retrieveBinDetails** | **Boolean**| Retrieve the Bin Details of PAN or network token | [optional] 
 
 ### Return type
 
@@ -130,6 +132,7 @@ var instrumentIdentifierId = "instrumentIdentifierId_example"; // String | The I
 
 var opts = { 
   'profileId': "profileId_example", // String | The Id of a profile containing user specific TMS configuration.
+  'retrieveBinDetails': true, // Boolean | Retrieve the Bin Details of PAN or network token
   'offset': 0, // Number | Starting record in zero-based dataset that should be returned as the first object in the array. Default is 0.
   'limit': 20 // Number | The maximum number that can be returned in the array starting from the offset record in zero-based dataset. Default is 20, maximum is 100.
 };
@@ -150,6 +153,7 @@ Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
  **instrumentIdentifierId** | **String**| The Id of an Instrument Identifier. | 
  **profileId** | **String**| The Id of a profile containing user specific TMS configuration. | [optional] 
+ **retrieveBinDetails** | **Boolean**| Retrieve the Bin Details of PAN or network token | [optional] 
  **offset** | **Number**| Starting record in zero-based dataset that should be returned as the first object in the array. Default is 0. | [optional] [default to 0]
  **limit** | **Number**| The maximum number that can be returned in the array starting from the offset record in zero-based dataset. Default is 20, maximum is 100. | [optional] [default to 20]
 
@@ -186,6 +190,7 @@ var patchInstrumentIdentifierRequest = new CyberSource.PatchInstrumentIdentifier
 
 var opts = { 
   'profileId': "profileId_example", // String | The Id of a profile containing user specific TMS configuration.
+  'retrieveBinDetails': true, // Boolean | Retrieve the Bin Details of PAN or network token
   'ifMatch': "ifMatch_example" // String | Contains an ETag value from a GET request to make the request conditional.
 };
 
@@ -206,6 +211,7 @@ Name | Type | Description  | Notes
  **instrumentIdentifierId** | **String**| The Id of an Instrument Identifier. | 
  **patchInstrumentIdentifierRequest** | [**PatchInstrumentIdentifierRequest**](PatchInstrumentIdentifierRequest.md)| Specify the previous transaction Id to update. | 
  **profileId** | **String**| The Id of a profile containing user specific TMS configuration. | [optional] 
+ **retrieveBinDetails** | **Boolean**| Retrieve the Bin Details of PAN or network token | [optional] 
  **ifMatch** | **String**| Contains an ETag value from a GET request to make the request conditional. | [optional] 
 
 ### Return type
@@ -238,7 +244,8 @@ var apiInstance = new CyberSource.InstrumentIdentifierApi();
 var postInstrumentIdentifierRequest = new CyberSource.PostInstrumentIdentifierRequest(); // PostInstrumentIdentifierRequest | Specify either a Card, Bank Account or Enrollable Card
 
 var opts = { 
-  'profileId': "profileId_example" // String | The Id of a profile containing user specific TMS configuration.
+  'profileId': "profileId_example", // String | The Id of a profile containing user specific TMS configuration.
+  'retrieveBinDetails': true // Boolean | Retrieve the Bin Details of PAN or network token
 };
 
 var callback = function(error, data, response) {
@@ -257,6 +264,7 @@ Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
  **postInstrumentIdentifierRequest** | [**PostInstrumentIdentifierRequest**](PostInstrumentIdentifierRequest.md)| Specify either a Card, Bank Account or Enrollable Card | 
  **profileId** | **String**| The Id of a profile containing user specific TMS configuration. | [optional] 
+ **retrieveBinDetails** | **Boolean**| Retrieve the Bin Details of PAN or network token | [optional] 
 
 ### Return type
 

package/docs/OctCreatePaymentRequest.md

@@ -10,5 +10,6 @@ Name | Type | Description | Notes
 **senderInformation** | [**Ptsv2payoutsSenderInformation**](Ptsv2payoutsSenderInformation.md) |  | [optional] 
 **processingInformation** | [**Ptsv2payoutsProcessingInformation**](Ptsv2payoutsProcessingInformation.md) |  | [optional] 
 **paymentInformation** | [**Ptsv2payoutsPaymentInformation**](Ptsv2payoutsPaymentInformation.md) |  | [optional] 
+**aggregatorInformation** | [**Ptsv2payoutsAggregatorInformation**](Ptsv2payoutsAggregatorInformation.md) |  | [optional] 
 
 

package/docs/PatchInstrumentIdentifierRequest.md

@@ -16,5 +16,6 @@ Name | Type | Description | Notes
 **processingInformation** | [**TmsEmbeddedInstrumentIdentifierProcessingInformation**](TmsEmbeddedInstrumentIdentifierProcessingInformation.md) |  | [optional] 
 **billTo** | [**TmsEmbeddedInstrumentIdentifierBillTo**](TmsEmbeddedInstrumentIdentifierBillTo.md) |  | [optional] 
 **metadata** | [**TmsEmbeddedInstrumentIdentifierMetadata**](TmsEmbeddedInstrumentIdentifierMetadata.md) |  | [optional] 
+**embedded** | [**TmsEmbeddedInstrumentIdentifierEmbedded**](TmsEmbeddedInstrumentIdentifierEmbedded.md) |  | [optional] 
 
 

package/docs/PaymentInstrumentApi.md

@@ -77,7 +77,8 @@ var apiInstance = new CyberSource.PaymentInstrumentApi();
 var paymentInstrumentId = "paymentInstrumentId_example"; // String | The Id of a payment instrument.
 
 var opts = { 
-  'profileId': "profileId_example" // String | The Id of a profile containing user specific TMS configuration.
+  'profileId': "profileId_example", // String | The Id of a profile containing user specific TMS configuration.
+  'retrieveBinDetails': true // Boolean | Retrieve the Bin Details of PAN or network token
 };
 
 var callback = function(error, data, response) {
@@ -96,6 +97,7 @@ Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
  **paymentInstrumentId** | **String**| The Id of a payment instrument. | 
  **profileId** | **String**| The Id of a profile containing user specific TMS configuration. | [optional] 
+ **retrieveBinDetails** | **Boolean**| Retrieve the Bin Details of PAN or network token | [optional] 
 
 ### Return type
 
@@ -130,6 +132,7 @@ var patchPaymentInstrumentRequest = new CyberSource.PatchPaymentInstrumentReques
 
 var opts = { 
   'profileId': "profileId_example", // String | The Id of a profile containing user specific TMS configuration.
+  'retrieveBinDetails': true, // Boolean | Retrieve the Bin Details of PAN or network token
   'ifMatch': "ifMatch_example" // String | Contains an ETag value from a GET request to make the request conditional.
 };
 
@@ -150,6 +153,7 @@ Name | Type | Description  | Notes
  **paymentInstrumentId** | **String**| The Id of a payment instrument. | 
  **patchPaymentInstrumentRequest** | [**PatchPaymentInstrumentRequest**](PatchPaymentInstrumentRequest.md)|  | 
  **profileId** | **String**| The Id of a profile containing user specific TMS configuration. | [optional] 
+ **retrieveBinDetails** | **Boolean**| Retrieve the Bin Details of PAN or network token | [optional] 
  **ifMatch** | **String**| Contains an ETag value from a GET request to make the request conditional. | [optional] 
 
 ### Return type
@@ -182,7 +186,8 @@ var apiInstance = new CyberSource.PaymentInstrumentApi();
 var postPaymentInstrumentRequest = new CyberSource.PostPaymentInstrumentRequest(); // PostPaymentInstrumentRequest | 
 
 var opts = { 
-  'profileId': "profileId_example" // String | The Id of a profile containing user specific TMS configuration.
+  'profileId': "profileId_example", // String | The Id of a profile containing user specific TMS configuration.
+  'retrieveBinDetails': true // Boolean | Retrieve the Bin Details of PAN or network token
 };
 
 var callback = function(error, data, response) {
@@ -201,6 +206,7 @@ Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
  **postPaymentInstrumentRequest** | [**PostPaymentInstrumentRequest**](PostPaymentInstrumentRequest.md)|  | 
  **profileId** | **String**| The Id of a profile containing user specific TMS configuration. | [optional] 
+ **retrieveBinDetails** | **Boolean**| Retrieve the Bin Details of PAN or network token | [optional] 
 
 ### Return type
 

package/docs/PostInstrumentIdentifierEnrollmentRequest.md

@@ -16,5 +16,6 @@ Name | Type | Description | Notes
 **processingInformation** | [**TmsEmbeddedInstrumentIdentifierProcessingInformation**](TmsEmbeddedInstrumentIdentifierProcessingInformation.md) |  | [optional] 
 **billTo** | [**TmsEmbeddedInstrumentIdentifierBillTo**](TmsEmbeddedInstrumentIdentifierBillTo.md) |  | [optional] 
 **metadata** | [**TmsEmbeddedInstrumentIdentifierMetadata**](TmsEmbeddedInstrumentIdentifierMetadata.md) |  | [optional] 
+**embedded** | [**TmsEmbeddedInstrumentIdentifierEmbedded**](TmsEmbeddedInstrumentIdentifierEmbedded.md) |  | [optional] 
 
 

package/docs/PostInstrumentIdentifierRequest.md

@@ -16,5 +16,6 @@ Name | Type | Description | Notes
 **processingInformation** | [**TmsEmbeddedInstrumentIdentifierProcessingInformation**](TmsEmbeddedInstrumentIdentifierProcessingInformation.md) |  | [optional] 
 **billTo** | [**TmsEmbeddedInstrumentIdentifierBillTo**](TmsEmbeddedInstrumentIdentifierBillTo.md) |  | [optional] 
 **metadata** | [**TmsEmbeddedInstrumentIdentifierMetadata**](TmsEmbeddedInstrumentIdentifierMetadata.md) |  | [optional] 
+**embedded** | [**TmsEmbeddedInstrumentIdentifierEmbedded**](TmsEmbeddedInstrumentIdentifierEmbedded.md) |  | [optional] 
 
 

package/docs/PostPaymentCredentialsRequest.md

@@ -3,6 +3,6 @@
 ## Properties
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**paymentCredentialType** | **String** | The type of payment credentials to be returned. By default, payment credentials include network token and cryptogram or dynamic CVV. If \"NETWORK_TOKEN\" is supplied then only network token will be returned and cryptogram or dynamic CVV will be excluded.   Possible Values:   - NETWORK_TOKEN  | [optional] 
+**paymentCredentialType** | **String** | The type of payment credentials to be returned. By default, payment credentials include network token and cryptogram or dynamic CVV. If \"NETWORK_TOKEN\" is supplied then only network token card number will be returned and no cryptogram or dynamic CVV will be requested. If \"SECURITY_CODE\" is supplied then dynamic CVV will be requested and returned with the network token card number. Dynamic CVV is only supported for Amex and SCOF. If \"CRYPTOGRAM\" is supplied then cryptogram will be requested and returned with the network token card number. Cryptogram is NOT supported for Amex.  Possible Values:   - NETWORK_TOKEN   - SECURITY_CODE   - CRYPTOGRAM  | [optional] 
 
 

package/docs/PtsV2IncrementalAuthorizationPatch201ResponseProcessorInformation.md

@@ -10,6 +10,7 @@ Name | Type | Description | Notes
 **systemTraceAuditNumber** | **String** | This field is returned only for **American Express Direct** and **CyberSource through VisaNet**. Returned by authorization and incremental authorization services.  #### American Express Direct  System trace audit number (STAN). This value identifies the transaction and is useful when investigating a chargeback dispute.  #### CyberSource through VisaNet  System trace number that must be printed on the customer's receipt.  | [optional] 
 **responseDetails** | **String** | This field might contain information about a decline. This field is supported only for **CyberSource through VisaNet**.  | [optional] 
 **merchantAdvice** | [**PtsV2PaymentsPost201ResponseProcessorInformationMerchantAdvice**](PtsV2PaymentsPost201ResponseProcessorInformationMerchantAdvice.md) |  | [optional] 
+**merchantRiskPrediction** | **String** | Mastercard is introducing the Merchant Risk Predict Service in the middle East/Africa Region. A newly launched service comprised of seven independent artificial intelligence (AI)-powered scores intended to augment existing merchant risk management practices.  | [optional] 
 **sellerProtection** | [**PtsV2PaymentsPost201ResponseProcessorInformationSellerProtection**](PtsV2PaymentsPost201ResponseProcessorInformationSellerProtection.md) |  | [optional] 
 
 

package/docs/PtsV2PaymentsPost201ResponseConsumerAuthenticationInformation.md

@@ -40,6 +40,7 @@ Name | Type | Description | Notes
 **whiteListStatusSource** | **String** | This data element will be populated by the system setting Whitelist Status. Possible Values: 01 - 3DS/ Server/ 02 – DS/03 - ACS  | [optional] 
 **xid** | **String** | Transaction identifier generated by CyberSource for successful enrollment or validation checks. Use this value, which is in base64, to match an outgoing PAReq with an incoming PARes. CyberSource forwards the XID with the card authorization service to these payment processors in these cases: - Barclays - Streamline (when the **ecommerceIndicator**`=spa`)  | [optional] 
 **directoryServerTransactionId** | **String** | The Directory Server Transaction ID is generated by the Mastercard Directory Server during the authentication transaction and passed back to the merchant with the authentication results. For Cybersource Through Visanet Gateway: The value for this field corresponds to the following data in the TC 33 capture file3: Record: CP01 TCR7, Position: 114-149, Field: MC AVV Verification—Directory Server Transaction ID  | [optional] 
+**dataQualityIndicator** | **String** | The field is used to indicate that a transaction does not meet the Visa Secure authentication data quality requirements. | [optional] 
 **authenticationResult** | **String** | Raw authentication data that comes from the cardissuing bank. Primary authentication field that indicates if authentication was successful and if liability shift occurred. You should examine first the result of this field. This field contains one of these values: - `-1`: Invalid PARes. - `0`: Successful validation. - `1`: Cardholder is not participating, but the attempt to authenticate was recorded. - `6`: Issuer unable to perform authentication. - `9`: Cardholder did not complete authentication.  | [optional] 
 **authenticationStatusMsg** | **String** | Message that explains the authenticationResult reply field.  | [optional] 
 **indicator** | **String** | Indicator used to differentiate Internet transactions from other types. The authentication failed if this field is not returned. For Visa, if your payment processor is Streamline, Barclays, AIBMS, or FDC Germany, you receive the value vbv_failure instead of internet when eci is 07. The value of this field is passed automatically to the authorization service if you request the services together. This field contains one of these values: - `aesk`: American Express SafeKey authentication verified successfully. - `aesk_attempted`: Card not enrolled in American Express SafeKey, but the attempt to authenticate was recorded. - `dipb`: Discover ProtectBuy authentication verified successfully. - `dipb_attempted`: Card not enrolled in Discover ProtectBuy, but the attempt to authenticate was recorded. - `internet`: Authentication was not verified successfully. - `js`: J/Secure authentication verified successfully. - `js_attempted`: Card not enrolled in J/Secure, but the attempt to authenticate was recorded. - `moto`: Mail or telephone order. - `pb_attempted`: Card not enrolled in Diners Club ProtectBuy, but the attempt to authenticate was recorded. - `recurring`: Recurring transaction. - `spa`: Mastercard Identity Check authentication verified successfully. - `spa_failure`: Mastercard Identity Check failed authentication. - `vbv`: Visa Secure authentication verified successfully. - `vbv_attempted`: Card not enrolled in Visa Secure, but the attempt to authenticate was recorded. - `vbv_failure`: Visa Secure authentication unavailable.  | [optional] 

package/docs/PtsV2PaymentsPost201ResponseEmbeddedActions.md

@@ -8,5 +8,7 @@ Name | Type | Description | Notes
 **CONSUMER_AUTHENTICATION** | [**PtsV2PaymentsPost201ResponseEmbeddedActionsCONSUMERAUTHENTICATION**](PtsV2PaymentsPost201ResponseEmbeddedActionsCONSUMERAUTHENTICATION.md) |  | [optional] 
 **VALIDATE_CONSUMER_AUTHENTICATION** | [**PtsV2PaymentsPost201ResponseEmbeddedActionsCONSUMERAUTHENTICATION**](PtsV2PaymentsPost201ResponseEmbeddedActionsCONSUMERAUTHENTICATION.md) |  | [optional] 
 **WATCHLIST_SCREENING** | [**PtsV2PaymentsPost201ResponseEmbeddedActionsWATCHLISTSCREENING**](PtsV2PaymentsPost201ResponseEmbeddedActionsWATCHLISTSCREENING.md) |  | [optional] 
+**TOKEN_CREATE** | [**PtsV2PaymentsPost201ResponseEmbeddedActionsTOKENCREATE**](PtsV2PaymentsPost201ResponseEmbeddedActionsTOKENCREATE.md) |  | [optional] 
+**TOKEN_UPDATE** | [**PtsV2PaymentsPost201ResponseEmbeddedActionsTOKENUPDATE**](PtsV2PaymentsPost201ResponseEmbeddedActionsTOKENUPDATE.md) |  | [optional] 
 
 

package/docs/PtsV2PaymentsPost201ResponseEmbeddedActionsTOKENCREATE.md

@@ -0,0 +1,10 @@
+# CyberSource.PtsV2PaymentsPost201ResponseEmbeddedActionsTOKENCREATE
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**status** | **String** | The status of the token create.  Possible value is:   - SUCCESS   - SERVER_ERROR   - INVALID_REQUEST  | [optional] 
+**reason** | **String** | The reason of the status.  Possible values:  - INVALID_DATA  - SYSTEM_ERROR  - MISSING_FIELD  | [optional] 
+**message** | **String** | The detail message related to the status and reason listed above. | [optional] 
+
+

package/docs/PtsV2PaymentsPost201ResponseEmbeddedActionsTOKENUPDATE.md

@@ -0,0 +1,10 @@
+# CyberSource.PtsV2PaymentsPost201ResponseEmbeddedActionsTOKENUPDATE
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**status** | **String** | The status of the token update.  Possible value is:   - SUCCESS   - SERVER_ERROR   - INVALID_REQUEST  | [optional] 
+**reason** | **String** | The reason of the status. Possible values:  - INVALID_DATA  - SYSTEM_ERROR  - MISSING_FIELD  | [optional] 
+**message** | **String** | The detail message related to the status and reason listed above. | [optional] 
+
+

package/docs/PtsV2PaymentsPost201ResponsePaymentInformationAccountFeatures.md

@@ -21,5 +21,6 @@ Name | Type | Description | Notes
 **signatureDebit** | **String** | Indicates whether the card is a signature debit card.  This information enables you to alter the way an order is processed. For example, you might not want to reauthorize a transaction for a signature debit card, or you might want to perform reversals promptly for a signature debit card. This field is supported for Visa, Mastercard, and Maestro (International) on Chase Paymentech Solutions. Possible values:   - `Y`: Yes  - `N`: No  - `X`: Not applicable / Unknown  | [optional] 
 **prepaid** | **String** | Indicates whether the card is a prepaid card. This information enables you to determine when a gift card or prepaid card is presented for use when establishing a new recurring, installment, or deferred billing relationship.  This field is supported for Visa, Mastercard, Discover, Diners Club, and JCB on Chase Paymentech Solutions. Possible values:   - `Y`: Yes  - `N`: No  - `X`: Not applicable / Unknown  | [optional] 
 **regulated** | **String** | Indicates whether the card is regulated according to the Durbin Amendment. If the card is regulated, the card issuer is subject to price caps and interchange rules. This field is supported for Visa, Mastercard, Discover, Diners Club, and JCB on Chase Paymentech Solutions. Possible values:   - `Y`: Yes  - `N`: No  - `X`: Not applicable / Unknown  | [optional] 
+**accountHolderType** | **String** | This is the account owner information, valid values are: - `01` : primary account holder - `02` : secondary account holder This is returned in the response of an account verification transaction by the Issuer.   | [optional] 
 
 

package/docs/PtsV2PaymentsPost201ResponseProcessingInformation.md

@@ -7,5 +7,7 @@ Name | Type | Description | Notes
 **paymentSolution** | **String** | Type of digital payment solution for the transaction. Possible Values:   - `visacheckout`: Visa Checkout. This value is required for Visa Checkout transactions. For details, see `payment_solution` field description in [Visa Checkout Using the REST API.](https://developer.cybersource.com/content/dam/docs/cybs/en-us/apifields/reference/all/rest/api-fields.pdf)  - `001`: Apple Pay.  - `004`: Cybersource In-App Solution.  - `005`: Masterpass. This value is required for Masterpass transactions on OmniPay Direct.   - `006`: Android Pay.  - `007`: Chase Pay.  - `008`: Samsung Pay.  - `012`: Google Pay.  - `013`: Cybersource P2PE Decryption  - `014`: Mastercard credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.  - `015`: Visa credential on file (COF) payment network token. Returned in authorizations that use a payment network token associated with a TMS token.  - `027`: Click to Pay.  | [optional] 
 **enhancedDataEnabled** | **Boolean** | The possible values for the reply field are: - `true` : the airline data was included in the request to the processor. - `false` : the airline data was not included in the request to the processor.  Returned by authorization, capture, or credit services.  | [optional] 
 **captureOptions** | [**PtsV2PaymentsPost201ResponseProcessingInformationCaptureOptions**](PtsV2PaymentsPost201ResponseProcessingInformationCaptureOptions.md) |  | [optional] 
+**authorizationOptions** | [**PtsV2PaymentsPost201ResponseProcessingInformationAuthorizationOptions**](PtsV2PaymentsPost201ResponseProcessingInformationAuthorizationOptions.md) |  | [optional] 
+**purchaseOptions** | [**PtsV2PaymentsPost201ResponseProcessingInformationPurchaseOptions**](PtsV2PaymentsPost201ResponseProcessingInformationPurchaseOptions.md) |  | [optional] 
 
 

package/docs/PtsV2PaymentsPost201ResponseProcessingInformationAuthorizationOptions.md

@@ -0,0 +1,8 @@
+# CyberSource.PtsV2PaymentsPost201ResponseProcessingInformationAuthorizationOptions
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**serviceType** | **String** | Field is used for back-to-back funding transaction and can be defined as a payment flow that automatically transfers funds through a real-time  funding or a live-load. This type of transaction can also be connected to a purchase.  In back-to-back funding of general purpose card that is used to make a purchase, two separate accounts are involved:  - account one is used to make the purchase - account two is used to automatically fund or reimburse account one  Possible values: - 0B = back to back funding transaction - 00 = normal transaction - 01 = originator hold - 02 = Visa deferred OCT hold, default interval - 03 = Visa deferred OCT hold, user-defined interval - 09 = Cancel pending deferred OCT request - 0I = Visa Direct custom program 1 - 0Q = uery the status of the deferred OCT - A0 = Alias Directory 2  | [optional] 
+
+

package/docs/PtsV2PaymentsPost201ResponseProcessingInformationPurchaseOptions.md

@@ -0,0 +1,11 @@
+# CyberSource.PtsV2PaymentsPost201ResponseProcessingInformationPurchaseOptions
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**eligibilityIndicator** | **String** | This field contains installment data defined by MasterCard. Possible values:   - Y = eligible   - N = not eligile  | [optional] 
+**type** | **String** | Data mapped received in response from MasterCard. Possible values: - 01 = Meal Voucher - Employee Nutrition Program - 02 = Food Voucher - Employee Nutrition Program - 03 = Culture Voucher - Worker's Culture Program - 04 = Meal Voucher - Consolidation of Labor Laws - 05 = Food Voucher - Consolidation of Labor Laws  | [optional] 
+**benefitAmount** | **String** | Workplace benefit amount. | [optional] 
+**benefitType** | **String** | Workplace benefit type. Possible values: - 70 = employee benefit - 4T = transportation / transit - 52 = general benefit - 53 = meal voucher - 54 = fuel - 55 = ecological / sustainability - 58 = philanthropy / patronage / consumption - 59 = gift - 5S = sport / culture - 5T = book / education  | [optional] 
+
+

package/docs/PtsV2PaymentsPost201ResponseProcessorInformation.md

@@ -47,5 +47,6 @@ Name | Type | Description | Notes
 **expirationTimeUtc** | **String** | The date and time when the authorized payment expires, in Internet date and time format.  | [optional] 
 **orderId** | **String** | The id of the order  | [optional] 
 **orderStatus** | **String** | The order status.  Possible values: - `CREATED` - `VOIDED` - `COMPLETED` - `PAYER_ACTION_REQUIRED`  | [optional] 
+**merchantRiskPrediction** | **String** | Mastercard is introducing the Merchant Risk Predict Service in the middle East/Africa Region. A newly launched service comprised of seven independent artificial intelligence (AI)-powered scores intended to augment existing merchant risk management practices.  | [optional] 
 
 

package/docs/PtsV2PaymentsReversalsPost201ResponseProcessorInformation.md

@@ -5,6 +5,7 @@ Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **transactionId** | **String** | Processor transaction ID.  This value identifies the transaction on a host system. This value is supported only for Moneris. It contains this information:   - Terminal used to process the transaction  - Shift during which the transaction took place  - Batch number  - Transaction number within the batch  You must store this value. If you give the customer a receipt, display this value on the receipt.  Example For the value 66012345001069003:   - Terminal ID = 66012345  - Shift number = 001  - Batch number = 069  - Transaction number = 003  | [optional] 
 **responseCode** | **String** | For most processors, this is the error message sent directly from the bank. Returned only when the processor returns this value.  **Important** Do not use this field to evaluate the result of the authorization.  #### PIN debit Response value that is returned by the processor or bank. **Important** Do not use this field to evaluate the results of the transaction request.  Returned by PIN debit credit, PIN debit purchase, and PIN debit reversal.  #### AIBMS If this value is `08`, you can accept the transaction if the customer provides you with identification.  #### Atos This value is the response code sent from Atos and it might also include the response code from the bank. Format: `aa,bb` with the two values separated by a comma and where: - `aa` is the two-digit error message from Atos. - `bb` is the optional two-digit error message from the bank.  #### Comercio Latino This value is the status code and the error or response code received from the processor separated by a colon. Format: [status code]:E[error code] or [status code]:R[response code] Example `2:R06`  #### JCN Gateway Processor-defined detail error code. The associated response category code is in the `processorInformation.responseCategoryCode` field. String (3)  #### paypalgateway Processor generated ID for the itemized detail.  | [optional] 
+**networkTransactionId** | **String** | Same value as `processorInformation.transactionId` | [optional] 
 **responseCategoryCode** | **String** | Processor-defined response category code. The associated detail error code is in the `processorInformation.responseCode` or `issuerInformation.responseCode` field of the service you requested.  This field is supported only for:   - Japanese issuers  - Domestic transactions in Japan  - Comercio Latino—processor transaction ID required for troubleshooting  #### Maximum length for processors   - Comercio Latino: 36  - All other processors: 3  | [optional] 
 **forwardedAcquirerCode** | **String** | Name of the Japanese acquirer that processed the transaction. Returned only for JCN Gateway. Please contact the CyberSource Japan Support Group for more information.  | [optional] 
 **masterCardServiceCode** | **String** | Mastercard service that was used for the transaction. Mastercard provides this value to CyberSource.  Possible value:  - 53: Mastercard card-on-file token service  #### CyberSource through VisaNet The value for this field corresponds to the following data in the TC 33 capture file: - Record: CP01 TCR6 - Position: 133-134 - Field: Mastercard Merchant on-behalf service. **Note** This field is returned only for CyberSource through VisaNet.  | [optional] 

package/docs/PtsV2PayoutsPost201Response.md

@@ -16,5 +16,6 @@ Name | Type | Description | Notes
 **recipientInformation** | [**PtsV2PayoutsPost201ResponseRecipientInformation**](PtsV2PayoutsPost201ResponseRecipientInformation.md) |  | [optional] 
 **issuerInformation** | [**PtsV2PayoutsPost201ResponseIssuerInformation**](PtsV2PayoutsPost201ResponseIssuerInformation.md) |  | [optional] 
 **tokenInformation** | [**PtsV2PaymentsPost201ResponseTokenInformation**](PtsV2PaymentsPost201ResponseTokenInformation.md) |  | [optional] 
+**processingInformation** | [**PtsV2PayoutsPost201ResponseProcessingInformation**](PtsV2PayoutsPost201ResponseProcessingInformation.md) |  | [optional] 
 
 

package/docs/PtsV2PayoutsPost201ResponseProcessingInformation.md

@@ -0,0 +1,8 @@
+# CyberSource.PtsV2PayoutsPost201ResponseProcessingInformation
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**purchaseOptions** | [**Ptsv2payoutsProcessingInformationPurchaseOptions**](Ptsv2payoutsProcessingInformationPurchaseOptions.md) |  | [optional] 
+
+

package/docs/Ptsv2billingagreementsInstallmentInformation.md

@@ -9,7 +9,7 @@ Name | Type | Description | Notes
 **lastInstallmentDate** | **String** | End date of the SI transactions. Cannot be later than card expiry date. Ideally this can be set to expiry date. Required in case the authentication is initiated for SI registration.  | [optional] 
 **maxAmount** | **String** | Maximum Amount for which SI can be initiated. Required in case the authentication is initiated for SI registration.  | [optional] 
 **minAmount** | **String** | Minimum Amount for which SI can be initiated. Required in case the authentication is initiated for SI registration.  | [optional] 
-**paymentType** | **String** | Payment plan for the installments.  Possible values: - 0 (default): Regular installment. This value is not allowed for airline transactions. - 1: Installment payment with down payment. - 2: Installment payment without down payment. This value is supported only for airline transactions. - 3: Installment payment; down payment and boarding fee will follow. This value is supported only for airline transactions. - 4: Down payment only; regular installment payment will follow. - 5: Boarding fee only. This value is supported only for airline transactions.  This field is supported only for installment payments with Visa on CyberSource through VisaNet in Brazil.  The value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP07 TCR1 - Position: 9 - Field: Merchant Installment Supporting Information  | [optional] 
+**paymentType** | **String** | Payment plan for the installments. This field is supported only for installment payments on Visa Platform Connect, RuPay and SPG-KSA seamless flow.  Possible values for a standing-instruction (SI) merchant-initiated transaction (MIT) with Diners Club or Mastercard in India or with an India-issued card: - 1: SI with a fixed amount. - 2: SI with a maximum amount. - 3: Other kind of SI.  Possible values for a type of Installment transaction for on-soil transaction in Kingdom of Saudi Arabia - 1: Registration or first transaction. - 2: Subsequent transaction.  Possible values for other kinds of installment payments: - 0 (default): Regular installment. This value is not allowed for airline transactions. - 1: Installment payment with down payment. - 2: Installment payment without down payment. This value is supported only for airline transactions. - 3: Installment payment; down payment and boarding fee will follow. This value is supported only for airline transactions. - 4: Down payment only; regular installment payment will follow. - 5: Boarding fee only. This value is supported only for airline transactions. - 6: SI de-registration on RuPay for the payer authentication seamless flow.  | [optional] 
 **preferredDay** | **String** | Preferred date for initiating the SI transaction every month. This field need not be sent in case the SI has to be initiated as and when required, e.g., topping up the wallet, etc.  | [optional] 
 **sequence** | **Number** | 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.  #### Chase Paymentech Solutions and FDC Compass This field is optional because this value is required in the merchant descriptors.  #### 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.  | [optional] 
 

package/docs/Ptsv2paymentsAggregatorInformation.md

@@ -6,5 +6,10 @@ Name | Type | Description | Notes
 **aggregatorId** | **String** | Value that identifies you as a payment aggregator. Get this value from the processor.  #### CyberSource through VisaNet The value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP01 TCR6 - Position: 95-105 - Field: Payment Facilitator ID  This field is supported for Visa, Mastercard and Discover Transactions.  **FDC Compass**\\ This value must consist of uppercase characters.  | [optional] 
 **name** | **String** | Your payment aggregator business name.  **American Express Direct**\\ The maximum length of the aggregator name depends on the length of the sub-merchant name. The combined length for both values must not exceed 36 characters.\\  #### CyberSource through VisaNet With American Express, the maximum length of the aggregator name depends on the length of the sub-merchant 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.  | [optional] 
 **subMerchant** | [**Ptsv2paymentsAggregatorInformationSubMerchant**](Ptsv2paymentsAggregatorInformationSubMerchant.md) |  | [optional] 
+**streetAddress** | **String** | Acquirer street name. | [optional] 
+**city** | **String** | Acquirer city. | [optional] 
+**state** | **String** | Acquirer state. | [optional] 
+**postalCode** | **String** | Acquirer postal code. | [optional] 
+**country** | **String** | Acquirer country. | [optional]