cybersource-rest-client 0.0.40 → 0.0.42

package/.idea/cybersource-rest-client-node.iml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<module type="JAVA_MODULE" version="4">
+  <component name="NewModuleRootManager" inherit-compiler-output="true">
+    <exclude-output />
+    <content url="file://$MODULE_DIR$" />
+    <orderEntry type="inheritedJdk" />
+    <orderEntry type="sourceFolder" forTests="false" />
+  </component>
+</module>

package/.idea/jsLibraryMappings.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="JavaScriptLibraryMappings">
+    <file url="file://$PROJECT_DIR$" libraries="{Node.js Core}" />
+  </component>
+</project>

package/.idea/libraries/swagger_codegen_cli_2_3_0.xml

@@ -0,0 +1,9 @@
+<component name="libraryTable">
+  <library name="swagger-codegen-cli-2.3.0">
+    <CLASSES>
+      <root url="jar://$PROJECT_DIR$/generator/swagger-codegen-cli-2.3.0.jar!/" />
+    </CLASSES>
+    <JAVADOC />
+    <SOURCES />
+  </library>
+</component>

package/.idea/misc.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="ProjectRootManager">
+    <output url="file://$PROJECT_DIR$/out" />
+  </component>
+</project>

package/.idea/modules.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="ProjectModuleManager">
+    <modules>
+      <module fileurl="file://$PROJECT_DIR$/.idea/cybersource-rest-client-node.iml" filepath="$PROJECT_DIR$/.idea/cybersource-rest-client-node.iml" />
+    </modules>
+  </component>
+</project>

package/.idea/vcs.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="VcsDirectoryMappings">
+    <mapping directory="" vcs="Git" />
+  </component>
+</project>

package/Logging.md

@@ -1,65 +1,65 @@
-[![Generic badge](https://img.shields.io/badge/LOGGING-NEW-GREEN.svg)](https://shields.io/)
-
-# Logging in CyberSource REST Client SDK (Node.js)
-
-Since v0.0.35, a new logging framework has been introduced in the SDK. This new logging framework makes use of Winston, and standardizes the logging so that it can be integrated with the logging in the client application. The decision to use Winston for building this logging framework has been taken based on benchmark studies that have been made on various logging platforms supported for Node.js.
-
-[One such study](https://www.loggly.com/blog/benchmarking-popular-node-js-logging-libraries/) performed benchmarking of five logging frameworks on the market — Log4js, Winston, Bunyan, winston-syslog, and bunyan-syslog. In this study,
-
-> _Winston performed best when logging to the console. Winston and Bunyan both performed best in their own ways when logging to the file system._
-
-## Winston Configuration
-
-In order to leverage the new logging framework, the following configuration settings may be added to the merchant configuration as part of **`LogConfiguration`**:
-
-* enableLog
-* logDirectory
-* logFileName
-* logFileMaxSize
-* loggingLevel
-* maxLogFiles
-* enableMasking
-
-In our [sample Configuration.js](https://github.com/CyberSource/cybersource-rest-samples-node/blob/master/Data/Configuration.js) file, the following lines
-
-```javascript
-    'enableLog': EnableLog,
-    'logFilename': LogFileName,
-    'logDirectory': LogDirectory,
-    'logFileMaxSize': LogfileMaxSize
-```
-
-have to be replaced by the following lines
-
-```javascript
-    'logConfiguration': {
-        'enableLog': EnableLog,
-        'logFileName': LogFileName,
-        'logDirectory': LogDirectory,
-        'logFileMaxSize': LogfileMaxSize,
-        'loggingLevel': LogLevel,
-        'enableMasking': EnableMasking
-    }
-```
-
-where, `EnableLog`, `LogFileName`, `LogDirectory`, `LogfileMaxSize`, `LogLevel`, and `EnableMasking` are variables to be provided.
-
-### Important Notes
-
-The variable `enableMasking` needs to be set to `true` if sensitive data in the request/response should be hidden/masked.
-
-Sensitive data fields are listed below:
-
-  * Card Security Code
-  * Card Number
-  * Any field with `number` in the name
-  * Card Expiration Month
-  * Card Expiration Year
-  * Account
-  * Routing Number
-  * Email
-  * First Name & Last Name
-  * Phone Number
-  * Type
-  * Token
-  * Signature
+[![Generic badge](https://img.shields.io/badge/LOGGING-NEW-GREEN.svg)](https://shields.io/)
+
+# Logging in CyberSource REST Client SDK (Node.js)
+
+Since v0.0.35, a new logging framework has been introduced in the SDK. This new logging framework makes use of Winston, and standardizes the logging so that it can be integrated with the logging in the client application. The decision to use Winston for building this logging framework has been taken based on benchmark studies that have been made on various logging platforms supported for Node.js.
+
+[One such study](https://www.loggly.com/blog/benchmarking-popular-node-js-logging-libraries/) performed benchmarking of five logging frameworks on the market — Log4js, Winston, Bunyan, winston-syslog, and bunyan-syslog. In this study,
+
+> _Winston performed best when logging to the console. Winston and Bunyan both performed best in their own ways when logging to the file system._
+
+## Winston Configuration
+
+In order to leverage the new logging framework, the following configuration settings may be added to the merchant configuration as part of **`LogConfiguration`**:
+
+* enableLog
+* logDirectory
+* logFileName
+* logFileMaxSize
+* loggingLevel
+* maxLogFiles
+* enableMasking
+
+In our [sample Configuration.js](https://github.com/CyberSource/cybersource-rest-samples-node/blob/master/Data/Configuration.js) file, the following lines
+
+```javascript
+    'enableLog': EnableLog,
+    'logFilename': LogFileName,
+    'logDirectory': LogDirectory,
+    'logFileMaxSize': LogfileMaxSize
+```
+
+have to be replaced by the following lines
+
+```javascript
+    'logConfiguration': {
+        'enableLog': EnableLog,
+        'logFileName': LogFileName,
+        'logDirectory': LogDirectory,
+        'logFileMaxSize': LogfileMaxSize,
+        'loggingLevel': LogLevel,
+        'enableMasking': EnableMasking
+    }
+```
+
+where, `EnableLog`, `LogFileName`, `LogDirectory`, `LogfileMaxSize`, `LogLevel`, and `EnableMasking` are variables to be provided.
+
+### Important Notes
+
+The variable `enableMasking` needs to be set to `true` if sensitive data in the request/response should be hidden/masked.
+
+Sensitive data fields are listed below:
+
+  * Card Security Code
+  * Card Number
+  * Any field with `number` in the name
+  * Card Expiration Month
+  * Card Expiration Year
+  * Account
+  * Routing Number
+  * Email
+  * First Name & Last Name
+  * Phone Number
+  * Type
+  * Token
+  * Signature

package/README.md

@@ -1,69 +1,69 @@
-# Node.JS Client SDK for the CyberSource REST API
-
-The CyberSource Node client provides convenient access to the [CyberSource REST API](https://developer.cybersource.com/api/reference/api-reference.html) from your Node application.
-
-## Requirements
-
-* Node.js version 6.17.1 or higher
-* A CyberSource account (see _Registration & Configuration_ section below)
-
-## Installation
-
-```shell
-    npm install cybersource-rest-client
-```
-
-## Registration & Configuration
-
-Use of this SDK and the CyberSource APIs requires having an account on our system. You can find details of getting a test account and creating your keys [here](https://developer.cybersource.com/api/developer-guides/dita-gettingstarted/registration.html)
-
-Remember this SDK is for use in server-side Node applications that access the CyberSource REST API and credentials should always be securely stored and accessed appropriately. 
-
-## SDK Usage Examples and Sample Code
-
-To get started using this SDK, it's highly recommended to download our sample code repository:
-
-* [Cybersource Node.js Sample Code Repository (on GitHub)](https://github.com/CyberSource/cybersource-rest-samples-node)
-
-In that respository, we have comprehensive sample code for all common uses of our API:
-
-Additionally, you can find details and examples of how our API is structured in our API Reference Guide:
-
-* [Developer Center API Reference](https://developer.cybersource.com/api/reference/api-reference.html)
-
-The API Reference Guide provides examples of what information is needed for a particular request and how that information would be formatted. Using those examples, you can easily determine what methods would be necessary to include that information in a request using this SDK.
-
-## 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.
-
-The Portfolio or Parent Account owns the key and is considered the transaction submitter when a Meta Key is used, while the merchant owns the transaction.
-
-MIDs continue to be able to create keys for themselves, even if a Meta Key is generated.
-
-Further information on MetaKey can be found in [New Business Center User Guide](https://developer.cybersource.com/library/documentation/dev_guides/Business_Center/New_Business_Center_User_Guide.pdf).
-
-### Switching between the sandbox environment and the production environment
-
-Cybersource maintains a complete sandbox environment for testing and development purposes. This sandbox environment is an exact duplicate of our production environment with the transaction authorization and settlement process simulated. By default, this SDK is configured to communicate with the sandbox environment. To switch to the production environment, set the `runEnvironment` in the SDK Configuration.  See our sample at <https://github.com/CyberSource/cybersource-rest-samples-node/blob/master/Data/Configuration.js>.
-
-```javascript
-    // For TESTING use
-    const RunEnvironment = "apitest.cybersource.com";
-    // For PRODUCTION use
-    const RunEnvironment = "api.cybersource.com";
-```
-
-API credentials are different for each environment, so be sure to switch to the appropriate credentials when switching environments.
-
-### Logging
-
-[![Generic badge](https://img.shields.io/badge/LOGGING-NEW-GREEN.svg)](https://shields.io/)
-
-Since v0.0.35, a new logging framework has been introduced in the SDK. This new logging framework makes use of Winston, and standardizes the logging so that it can be integrated with the logging in the client application.
-
-More information about this new logging framework can be found in this file : [Logging.md](Logging.md)
-
-## License
-
-This repository is distributed under a proprietary license. See the provided [`LICENSE.txt`](/LICENSE.txt) file.
+# Node.JS Client SDK for the CyberSource REST API
+
+The CyberSource Node client provides convenient access to the [CyberSource REST API](https://developer.cybersource.com/api/reference/api-reference.html) from your Node application.
+
+## Requirements
+
+* Node.js version 6.17.1 or higher
+* A CyberSource account (see _Registration & Configuration_ section below)
+
+## Installation
+
+```shell
+    npm install cybersource-rest-client
+```
+
+## Registration & Configuration
+
+Use of this SDK and the CyberSource APIs requires having an account on our system. You can find details of getting a test account and creating your keys [here](https://developer.cybersource.com/api/developer-guides/dita-gettingstarted/registration.html)
+
+Remember this SDK is for use in server-side Node applications that access the CyberSource REST API and credentials should always be securely stored and accessed appropriately. 
+
+## SDK Usage Examples and Sample Code
+
+To get started using this SDK, it's highly recommended to download our sample code repository:
+
+* [Cybersource Node.js Sample Code Repository (on GitHub)](https://github.com/CyberSource/cybersource-rest-samples-node)
+
+In that respository, we have comprehensive sample code for all common uses of our API:
+
+Additionally, you can find details and examples of how our API is structured in our API Reference Guide:
+
+* [Developer Center API Reference](https://developer.cybersource.com/api/reference/api-reference.html)
+
+The API Reference Guide provides examples of what information is needed for a particular request and how that information would be formatted. Using those examples, you can easily determine what methods would be necessary to include that information in a request using this SDK.
+
+## 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.
+
+The Portfolio or Parent Account owns the key and is considered the transaction submitter when a Meta Key is used, while the merchant owns the transaction.
+
+MIDs continue to be able to create keys for themselves, even if a Meta Key is generated.
+
+Further information on MetaKey can be found in [New Business Center User Guide](https://developer.cybersource.com/library/documentation/dev_guides/Business_Center/New_Business_Center_User_Guide.pdf).
+
+### Switching between the sandbox environment and the production environment
+
+Cybersource maintains a complete sandbox environment for testing and development purposes. This sandbox environment is an exact duplicate of our production environment with the transaction authorization and settlement process simulated. By default, this SDK is configured to communicate with the sandbox environment. To switch to the production environment, set the `runEnvironment` in the SDK Configuration.  See our sample at <https://github.com/CyberSource/cybersource-rest-samples-node/blob/master/Data/Configuration.js>.
+
+```javascript
+    // For TESTING use
+    const RunEnvironment = "apitest.cybersource.com";
+    // For PRODUCTION use
+    const RunEnvironment = "api.cybersource.com";
+```
+
+API credentials are different for each environment, so be sure to switch to the appropriate credentials when switching environments.
+
+### Logging
+
+[![Generic badge](https://img.shields.io/badge/LOGGING-NEW-GREEN.svg)](https://shields.io/)
+
+Since v0.0.35, a new logging framework has been introduced in the SDK. This new logging framework makes use of Winston, and standardizes the logging so that it can be integrated with the logging in the client application.
+
+More information about this new logging framework can be found in this file : [Logging.md](Logging.md)
+
+## License
+
+This repository is distributed under a proprietary license. See the provided [`LICENSE.txt`](/LICENSE.txt) file.

package/docs/AccessTokenResponse.md

@@ -1,14 +1,14 @@
-# CyberSource.AccessTokenResponse
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**accessToken** | **String** | Created JWT token. | [optional] 
-**tokenType** | **String** | Bearer. | [optional] 
-**refreshToken** | **String** | Newly created JWT token for initial request or if refresh token expired, else the same refresh token as in the request. | [optional] 
-**expiresIn** | **Number** | Number of seconds left till the access token gets expired. | [optional] 
-**scope** | **String** | List of permissions for APIs. | [optional] 
-**refreshTokenExpiresIn** | **Number** | Number of seconds left till the refresh token gets expired. | [optional] 
-**clientStatus** | **String** | Successful response can be returned only if client status is active. | [optional] 
-
-
+# CyberSource.AccessTokenResponse
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**accessToken** | **String** | Created JWT token. | [optional] 
+**tokenType** | **String** | Bearer. | [optional] 
+**refreshToken** | **String** | Newly created JWT token for initial request or if refresh token expired, else the same refresh token as in the request. | [optional] 
+**expiresIn** | **Number** | Number of seconds left till the access token gets expired. | [optional] 
+**scope** | **String** | List of permissions for APIs. | [optional] 
+**refreshTokenExpiresIn** | **Number** | Number of seconds left till the refresh token gets expired. | [optional] 
+**clientStatus** | **String** | Successful response can be returned only if client status is active. | [optional] 
+
+

package/docs/AddNegativeListRequest.md

@@ -1,13 +1,13 @@
-# CyberSource.AddNegativeListRequest
-
-## Properties
-Name | Type | Description | Notes
------------- | ------------- | ------------- | -------------
-**orderInformation** | [**Riskv1liststypeentriesOrderInformation**](Riskv1liststypeentriesOrderInformation.md) |  | [optional] 
-**paymentInformation** | [**Riskv1liststypeentriesPaymentInformation**](Riskv1liststypeentriesPaymentInformation.md) |  | [optional] 
-**clientReferenceInformation** | [**Riskv1liststypeentriesClientReferenceInformation**](Riskv1liststypeentriesClientReferenceInformation.md) |  | [optional] 
-**deviceInformation** | [**Riskv1liststypeentriesDeviceInformation**](Riskv1liststypeentriesDeviceInformation.md) |  | [optional] 
-**riskInformation** | [**Riskv1liststypeentriesRiskInformation**](Riskv1liststypeentriesRiskInformation.md) |  | [optional] 
-**buyerInformation** | [**Riskv1liststypeentriesBuyerInformation**](Riskv1liststypeentriesBuyerInformation.md) |  | [optional] 
-
-
+# CyberSource.AddNegativeListRequest
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**orderInformation** | [**Riskv1liststypeentriesOrderInformation**](Riskv1liststypeentriesOrderInformation.md) |  | [optional] 
+**paymentInformation** | [**Riskv1liststypeentriesPaymentInformation**](Riskv1liststypeentriesPaymentInformation.md) |  | [optional] 
+**clientReferenceInformation** | [**Riskv1liststypeentriesClientReferenceInformation**](Riskv1liststypeentriesClientReferenceInformation.md) |  | [optional] 
+**deviceInformation** | [**Riskv1liststypeentriesDeviceInformation**](Riskv1liststypeentriesDeviceInformation.md) |  | [optional] 
+**riskInformation** | [**Riskv1liststypeentriesRiskInformation**](Riskv1liststypeentriesRiskInformation.md) |  | [optional] 
+**buyerInformation** | [**Riskv1liststypeentriesBuyerInformation**](Riskv1liststypeentriesBuyerInformation.md) |  | [optional] 
+
+