cybersource-rest-client 0.0.36 → 0.0.39

package/src/model/TssV2TransactionsGet200ResponsePaymentInformationCard.js

@@ -1,163 +1,163 @@
-/**
- * CyberSource Merged Spec
- * All CyberSource API specs merged together. These are available at https://developer.cybersource.com/api/reference/api-reference.html
- *
- * OpenAPI spec version: 0.0.1
- *
- * NOTE: This class is auto generated by the swagger code generator program.
- * https://github.com/swagger-api/swagger-codegen.git
- *
- * Swagger Codegen version: 2.3.0
- *
- * Do not edit the class manually.
- *
- */
-
-(function(root, factory) {
-  if (typeof define === 'function' && define.amd) {
-    // AMD. Register as an anonymous module.
-    define(['ApiClient'], factory);
-  } else if (typeof module === 'object' && module.exports) {
-    // CommonJS-like environments that support module.exports, like Node.
-    module.exports = factory(require('../ApiClient'));
-  } else {
-    // Browser globals (root is window)
-    if (!root.CyberSource) {
-      root.CyberSource = {};
-    }
-    root.CyberSource.TssV2TransactionsGet200ResponsePaymentInformationCard = factory(root.CyberSource.ApiClient);
-  }
-}(this, function(ApiClient) {
-  'use strict';
-
-
-
-
-  /**
-   * The TssV2TransactionsGet200ResponsePaymentInformationCard model module.
-   * @module model/TssV2TransactionsGet200ResponsePaymentInformationCard
-   * @version 0.0.1
-   */
-
-  /**
-   * Constructs a new <code>TssV2TransactionsGet200ResponsePaymentInformationCard</code>.
-   * @alias module:model/TssV2TransactionsGet200ResponsePaymentInformationCard
-   * @class
-   */
-  var exports = function() {
-    var _this = this;
-
-
-
-
-
-
-
-
-
-
-
-  };
-
-  /**
-   * Constructs a <code>TssV2TransactionsGet200ResponsePaymentInformationCard</code> from a plain JavaScript object, optionally creating a new instance.
-   * Copies all relevant properties from <code>data</code> to <code>obj</code> if supplied or a new instance if not.
-   * @param {Object} data The plain JavaScript object bearing properties of interest.
-   * @param {module:model/TssV2TransactionsGet200ResponsePaymentInformationCard} obj Optional instance to populate.
-   * @return {module:model/TssV2TransactionsGet200ResponsePaymentInformationCard} The populated <code>TssV2TransactionsGet200ResponsePaymentInformationCard</code> instance.
-   */
-  exports.constructFromObject = function(data, obj) {
-    if (data) {
-      obj = obj || new exports();
-
-      if (data.hasOwnProperty('suffix')) {
-        obj['suffix'] = ApiClient.convertToType(data['suffix'], 'String');
-      }
-      if (data.hasOwnProperty('prefix')) {
-        obj['prefix'] = ApiClient.convertToType(data['prefix'], 'String');
-      }
-      if (data.hasOwnProperty('expirationMonth')) {
-        obj['expirationMonth'] = ApiClient.convertToType(data['expirationMonth'], 'String');
-      }
-      if (data.hasOwnProperty('expirationYear')) {
-        obj['expirationYear'] = ApiClient.convertToType(data['expirationYear'], 'String');
-      }
-      if (data.hasOwnProperty('startMonth')) {
-        obj['startMonth'] = ApiClient.convertToType(data['startMonth'], 'String');
-      }
-      if (data.hasOwnProperty('startYear')) {
-        obj['startYear'] = ApiClient.convertToType(data['startYear'], 'String');
-      }
-      if (data.hasOwnProperty('issueNumber')) {
-        obj['issueNumber'] = ApiClient.convertToType(data['issueNumber'], 'String');
-      }
-      if (data.hasOwnProperty('type')) {
-        obj['type'] = ApiClient.convertToType(data['type'], 'String');
-      }
-      if (data.hasOwnProperty('accountEncoderId')) {
-        obj['accountEncoderId'] = ApiClient.convertToType(data['accountEncoderId'], 'String');
-      }
-      if (data.hasOwnProperty('useAs')) {
-        obj['useAs'] = ApiClient.convertToType(data['useAs'], 'String');
-      }
-    }
-    return obj;
-  }
-
-  /**
-   * 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 
-   * @member {String} suffix
-   */
-  exports.prototype['suffix'] = undefined;
-  /**
-   * 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. 
-   * @member {String} prefix
-   */
-  exports.prototype['prefix'] = undefined;
-  /**
-   * Two-digit month in which the payment card expires.  Format: `MM`.  Valid values: `01` through `12`. Leading 0 is required.  #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`01` through `12`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request.  #### Encoded Account Numbers For encoded account numbers (_type_=039), if there is no expiration date on the card, use `12`.  #### FDMS Nashville Required field.  #### All other processors Required if `pointOfSaleInformation.entryMode=keyed`. However, this field is optional if your account is configured for relaxed requirements for address data and expiration date. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response. 
-   * @member {String} expirationMonth
-   */
-  exports.prototype['expirationMonth'] = undefined;
-  /**
-   * Four-digit year in which the payment card expires.  Format: `YYYY`.  #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`1900` through `3000`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request.  #### Encoded Account Numbers For encoded account numbers (**_type_**`=039`), if there is no expiration date on the card, use `2021`.  #### FDMS Nashville Required field.  #### FDC Nashville Global and FDMS South You can send in 2 digits or 4 digits. If you send in 2 digits, they must be the last 2 digits of the year.  #### All other processors Required if `pointOfSaleInformation.entryMode=keyed`. However, this field is optional if your account is configured for relaxed requirements for address data and expiration date. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response. 
-   * @member {String} expirationYear
-   */
-  exports.prototype['expirationYear'] = undefined;
-  /**
-   * Month of the start of the Maestro (UK Domestic) card validity period. Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card. `Format: MM`. Possible values: 01 through 12.  **Note** The start date is not required for Maestro (UK Domestic) transactions. 
-   * @member {String} startMonth
-   */
-  exports.prototype['startMonth'] = undefined;
-  /**
-   * Year of the start of the Maestro (UK Domestic) card validity period. Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card. `Format: YYYY`.  **Note** The start date is not required for Maestro (UK Domestic) transactions. 
-   * @member {String} startYear
-   */
-  exports.prototype['startYear'] = undefined;
-  /**
-   * Number of times a Maestro (UK Domestic) card has been issued to the account holder. The card might or might not have an issue number. The number can consist of one or two digits, and the first digit might be a zero. When you include this value in your request, include exactly what is printed on the card. A value of 2 is different than a value of 02. Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card.  **Note** The issue number is not required for Maestro (UK Domestic) transactions. 
-   * @member {String} issueNumber
-   */
-  exports.prototype['issueNumber'] = undefined;
-  /**
-   * 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 
-   * @member {String} type
-   */
-  exports.prototype['type'] = undefined;
-  /**
-   * Identifier for the issuing bank that provided the customer’s encoded account number. Contact your processor for the bank’s ID. 
-   * @member {String} accountEncoderId
-   */
-  exports.prototype['accountEncoderId'] = undefined;
-  /**
-   * Flag that specifies the type of account associated with the card. The cardholder provides this information during the payment process.  #### Cielo and Comercio Latino  Possible values:   - CREDIT: Credit card  - DEBIT: Debit card  This field is required for:  - Debit transactions on Cielo and Comercio Latino.  - Transactions with Brazilian-issued cards on CyberSource through VisaNet.  **Note** The value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP07 TCR0 - Position: 51 - Field: Combination Card Transaction Identifier  This field is supported only for Mastercard transactions in Brazil on CyberSource through VisaNet. 
-   * @member {String} useAs
-   */
-  exports.prototype['useAs'] = undefined;
-
-
-
-  return exports;
-}));
-
-
+/**
+ * CyberSource Merged Spec
+ * All CyberSource API specs merged together. These are available at https://developer.cybersource.com/api/reference/api-reference.html
+ *
+ * OpenAPI spec version: 0.0.1
+ *
+ * NOTE: This class is auto generated by the swagger code generator program.
+ * https://github.com/swagger-api/swagger-codegen.git
+ *
+ * Swagger Codegen version: 2.3.0
+ *
+ * Do not edit the class manually.
+ *
+ */
+
+(function(root, factory) {
+  if (typeof define === 'function' && define.amd) {
+    // AMD. Register as an anonymous module.
+    define(['ApiClient'], factory);
+  } else if (typeof module === 'object' && module.exports) {
+    // CommonJS-like environments that support module.exports, like Node.
+    module.exports = factory(require('../ApiClient'));
+  } else {
+    // Browser globals (root is window)
+    if (!root.CyberSource) {
+      root.CyberSource = {};
+    }
+    root.CyberSource.TssV2TransactionsGet200ResponsePaymentInformationCard = factory(root.CyberSource.ApiClient);
+  }
+}(this, function(ApiClient) {
+  'use strict';
+
+
+
+
+  /**
+   * The TssV2TransactionsGet200ResponsePaymentInformationCard model module.
+   * @module model/TssV2TransactionsGet200ResponsePaymentInformationCard
+   * @version 0.0.1
+   */
+
+  /**
+   * Constructs a new <code>TssV2TransactionsGet200ResponsePaymentInformationCard</code>.
+   * @alias module:model/TssV2TransactionsGet200ResponsePaymentInformationCard
+   * @class
+   */
+  var exports = function() {
+    var _this = this;
+
+
+
+
+
+
+
+
+
+
+
+  };
+
+  /**
+   * Constructs a <code>TssV2TransactionsGet200ResponsePaymentInformationCard</code> from a plain JavaScript object, optionally creating a new instance.
+   * Copies all relevant properties from <code>data</code> to <code>obj</code> if supplied or a new instance if not.
+   * @param {Object} data The plain JavaScript object bearing properties of interest.
+   * @param {module:model/TssV2TransactionsGet200ResponsePaymentInformationCard} obj Optional instance to populate.
+   * @return {module:model/TssV2TransactionsGet200ResponsePaymentInformationCard} The populated <code>TssV2TransactionsGet200ResponsePaymentInformationCard</code> instance.
+   */
+  exports.constructFromObject = function(data, obj) {
+    if (data) {
+      obj = obj || new exports();
+
+      if (data.hasOwnProperty('suffix')) {
+        obj['suffix'] = ApiClient.convertToType(data['suffix'], 'String');
+      }
+      if (data.hasOwnProperty('prefix')) {
+        obj['prefix'] = ApiClient.convertToType(data['prefix'], 'String');
+      }
+      if (data.hasOwnProperty('expirationMonth')) {
+        obj['expirationMonth'] = ApiClient.convertToType(data['expirationMonth'], 'String');
+      }
+      if (data.hasOwnProperty('expirationYear')) {
+        obj['expirationYear'] = ApiClient.convertToType(data['expirationYear'], 'String');
+      }
+      if (data.hasOwnProperty('startMonth')) {
+        obj['startMonth'] = ApiClient.convertToType(data['startMonth'], 'String');
+      }
+      if (data.hasOwnProperty('startYear')) {
+        obj['startYear'] = ApiClient.convertToType(data['startYear'], 'String');
+      }
+      if (data.hasOwnProperty('issueNumber')) {
+        obj['issueNumber'] = ApiClient.convertToType(data['issueNumber'], 'String');
+      }
+      if (data.hasOwnProperty('type')) {
+        obj['type'] = ApiClient.convertToType(data['type'], 'String');
+      }
+      if (data.hasOwnProperty('accountEncoderId')) {
+        obj['accountEncoderId'] = ApiClient.convertToType(data['accountEncoderId'], 'String');
+      }
+      if (data.hasOwnProperty('useAs')) {
+        obj['useAs'] = ApiClient.convertToType(data['useAs'], 'String');
+      }
+    }
+    return obj;
+  }
+
+  /**
+   * 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 
+   * @member {String} suffix
+   */
+  exports.prototype['suffix'] = undefined;
+  /**
+   * 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. 
+   * @member {String} prefix
+   */
+  exports.prototype['prefix'] = undefined;
+  /**
+   * Two-digit month in which the payment card expires.  Format: `MM`.  Valid values: `01` through `12`. Leading 0 is required.  #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`01` through `12`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request.  #### Encoded Account Numbers For encoded account numbers (_type_=039), if there is no expiration date on the card, use `12`.  #### FDMS Nashville Required field.  #### All other processors Required if `pointOfSaleInformation.entryMode=keyed`. However, this field is optional if your account is configured for relaxed requirements for address data and expiration date. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response. 
+   * @member {String} expirationMonth
+   */
+  exports.prototype['expirationMonth'] = undefined;
+  /**
+   * Four-digit year in which the payment card expires.  Format: `YYYY`.  #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`1900` through `3000`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request.  #### Encoded Account Numbers For encoded account numbers (**_type_**`=039`), if there is no expiration date on the card, use `2021`.  #### FDMS Nashville Required field.  #### FDC Nashville Global and FDMS South You can send in 2 digits or 4 digits. If you send in 2 digits, they must be the last 2 digits of the year.  #### All other processors Required if `pointOfSaleInformation.entryMode=keyed`. However, this field is optional if your account is configured for relaxed requirements for address data and expiration date. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response. 
+   * @member {String} expirationYear
+   */
+  exports.prototype['expirationYear'] = undefined;
+  /**
+   * Month of the start of the Maestro (UK Domestic) card validity period. Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card. `Format: MM`. Possible values: 01 through 12.  **Note** The start date is not required for Maestro (UK Domestic) transactions. 
+   * @member {String} startMonth
+   */
+  exports.prototype['startMonth'] = undefined;
+  /**
+   * Year of the start of the Maestro (UK Domestic) card validity period. Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card. `Format: YYYY`.  **Note** The start date is not required for Maestro (UK Domestic) transactions. 
+   * @member {String} startYear
+   */
+  exports.prototype['startYear'] = undefined;
+  /**
+   * Number of times a Maestro (UK Domestic) card has been issued to the account holder. The card might or might not have an issue number. The number can consist of one or two digits, and the first digit might be a zero. When you include this value in your request, include exactly what is printed on the card. A value of 2 is different than a value of 02. Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card.  **Note** The issue number is not required for Maestro (UK Domestic) transactions. 
+   * @member {String} issueNumber
+   */
+  exports.prototype['issueNumber'] = undefined;
+  /**
+   * 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 
+   * @member {String} type
+   */
+  exports.prototype['type'] = undefined;
+  /**
+   * Identifier for the issuing bank that provided the customer’s encoded account number. Contact your processor for the bank’s ID. 
+   * @member {String} accountEncoderId
+   */
+  exports.prototype['accountEncoderId'] = undefined;
+  /**
+   * Flag that specifies the type of account associated with the card. The cardholder provides this information during the payment process.  #### Cielo and Comercio Latino  Possible values:   - CREDIT: Credit card  - DEBIT: Debit card  This field is required for:  - Debit transactions on Cielo and Comercio Latino.  - Transactions with Brazilian-issued cards on CyberSource through VisaNet.  **Note** The value for this field corresponds to the following data in the TC 33 capture file5: - Record: CP07 TCR0 - Position: 51 - Field: Combination Card Transaction Identifier  This field is supported only for Mastercard transactions in Brazil on CyberSource through VisaNet. 
+   * @member {String} useAs
+   */
+  exports.prototype['useAs'] = undefined;
+
+
+
+  return exports;
+}));
+
+

package/src/model/TssV2TransactionsGet200ResponsePaymentInformationCustomer.js

@@ -1,91 +1,91 @@
-/**
- * CyberSource Merged Spec
- * All CyberSource API specs merged together. These are available at https://developer.cybersource.com/api/reference/api-reference.html
- *
- * OpenAPI spec version: 0.0.1
- *
- * NOTE: This class is auto generated by the swagger code generator program.
- * https://github.com/swagger-api/swagger-codegen.git
- *
- * Swagger Codegen version: 2.3.0
- *
- * Do not edit the class manually.
- *
- */
-
-(function(root, factory) {
-  if (typeof define === 'function' && define.amd) {
-    // AMD. Register as an anonymous module.
-    define(['ApiClient'], factory);
-  } else if (typeof module === 'object' && module.exports) {
-    // CommonJS-like environments that support module.exports, like Node.
-    module.exports = factory(require('../ApiClient'));
-  } else {
-    // Browser globals (root is window)
-    if (!root.CyberSource) {
-      root.CyberSource = {};
-    }
-    root.CyberSource.TssV2TransactionsGet200ResponsePaymentInformationCustomer = factory(root.CyberSource.ApiClient);
-  }
-}(this, function(ApiClient) {
-  'use strict';
-
-
-
-
-  /**
-   * The TssV2TransactionsGet200ResponsePaymentInformationCustomer model module.
-   * @module model/TssV2TransactionsGet200ResponsePaymentInformationCustomer
-   * @version 0.0.1
-   */
-
-  /**
-   * Constructs a new <code>TssV2TransactionsGet200ResponsePaymentInformationCustomer</code>.
-   * @alias module:model/TssV2TransactionsGet200ResponsePaymentInformationCustomer
-   * @class
-   */
-  var exports = function() {
-    var _this = this;
-
-
-
-  };
-
-  /**
-   * Constructs a <code>TssV2TransactionsGet200ResponsePaymentInformationCustomer</code> from a plain JavaScript object, optionally creating a new instance.
-   * Copies all relevant properties from <code>data</code> to <code>obj</code> if supplied or a new instance if not.
-   * @param {Object} data The plain JavaScript object bearing properties of interest.
-   * @param {module:model/TssV2TransactionsGet200ResponsePaymentInformationCustomer} obj Optional instance to populate.
-   * @return {module:model/TssV2TransactionsGet200ResponsePaymentInformationCustomer} The populated <code>TssV2TransactionsGet200ResponsePaymentInformationCustomer</code> instance.
-   */
-  exports.constructFromObject = function(data, obj) {
-    if (data) {
-      obj = obj || new exports();
-
-      if (data.hasOwnProperty('customerId')) {
-        obj['customerId'] = ApiClient.convertToType(data['customerId'], 'String');
-      }
-      if (data.hasOwnProperty('id')) {
-        obj['id'] = ApiClient.convertToType(data['id'], 'String');
-      }
-    }
-    return obj;
-  }
-
-  /**
-   * Unique identifier for the legacy Secure Storage token used in the transaction. When you include this value in your request, many of the fields that are normally required for an authorization or credit become optional. 
-   * @member {String} customerId
-   */
-  exports.prototype['customerId'] = undefined;
-  /**
-   * Unique identifier for the Customer token that was created as part of a bundled TOKEN_CREATE action. 
-   * @member {String} id
-   */
-  exports.prototype['id'] = undefined;
-
-
-
-  return exports;
-}));
-
-
+/**
+ * CyberSource Merged Spec
+ * All CyberSource API specs merged together. These are available at https://developer.cybersource.com/api/reference/api-reference.html
+ *
+ * OpenAPI spec version: 0.0.1
+ *
+ * NOTE: This class is auto generated by the swagger code generator program.
+ * https://github.com/swagger-api/swagger-codegen.git
+ *
+ * Swagger Codegen version: 2.3.0
+ *
+ * Do not edit the class manually.
+ *
+ */
+
+(function(root, factory) {
+  if (typeof define === 'function' && define.amd) {
+    // AMD. Register as an anonymous module.
+    define(['ApiClient'], factory);
+  } else if (typeof module === 'object' && module.exports) {
+    // CommonJS-like environments that support module.exports, like Node.
+    module.exports = factory(require('../ApiClient'));
+  } else {
+    // Browser globals (root is window)
+    if (!root.CyberSource) {
+      root.CyberSource = {};
+    }
+    root.CyberSource.TssV2TransactionsGet200ResponsePaymentInformationCustomer = factory(root.CyberSource.ApiClient);
+  }
+}(this, function(ApiClient) {
+  'use strict';
+
+
+
+
+  /**
+   * The TssV2TransactionsGet200ResponsePaymentInformationCustomer model module.
+   * @module model/TssV2TransactionsGet200ResponsePaymentInformationCustomer
+   * @version 0.0.1
+   */
+
+  /**
+   * Constructs a new <code>TssV2TransactionsGet200ResponsePaymentInformationCustomer</code>.
+   * @alias module:model/TssV2TransactionsGet200ResponsePaymentInformationCustomer
+   * @class
+   */
+  var exports = function() {
+    var _this = this;
+
+
+
+  };
+
+  /**
+   * Constructs a <code>TssV2TransactionsGet200ResponsePaymentInformationCustomer</code> from a plain JavaScript object, optionally creating a new instance.
+   * Copies all relevant properties from <code>data</code> to <code>obj</code> if supplied or a new instance if not.
+   * @param {Object} data The plain JavaScript object bearing properties of interest.
+   * @param {module:model/TssV2TransactionsGet200ResponsePaymentInformationCustomer} obj Optional instance to populate.
+   * @return {module:model/TssV2TransactionsGet200ResponsePaymentInformationCustomer} The populated <code>TssV2TransactionsGet200ResponsePaymentInformationCustomer</code> instance.
+   */
+  exports.constructFromObject = function(data, obj) {
+    if (data) {
+      obj = obj || new exports();
+
+      if (data.hasOwnProperty('customerId')) {
+        obj['customerId'] = ApiClient.convertToType(data['customerId'], 'String');
+      }
+      if (data.hasOwnProperty('id')) {
+        obj['id'] = ApiClient.convertToType(data['id'], 'String');
+      }
+    }
+    return obj;
+  }
+
+  /**
+   * 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/) 
+   * @member {String} customerId
+   */
+  exports.prototype['customerId'] = undefined;
+  /**
+   * Unique identifier for the Customer token that was created as part of a bundled TOKEN_CREATE action. 
+   * @member {String} id
+   */
+  exports.prototype['id'] = undefined;
+
+
+
+  return exports;
+}));
+
+