cybersource-rest-client 0.0.36 → 0.0.39

package/src/model/Riskv1authenticationresultsPaymentInformationTokenizedCard.js

@@ -1,118 +1,118 @@
-/**
- * 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.Riskv1authenticationresultsPaymentInformationTokenizedCard = factory(root.CyberSource.ApiClient);
-  }
-}(this, function(ApiClient) {
-  'use strict';
-
-
-
-
-  /**
-   * The Riskv1authenticationresultsPaymentInformationTokenizedCard model module.
-   * @module model/Riskv1authenticationresultsPaymentInformationTokenizedCard
-   * @version 0.0.1
-   */
-
-  /**
-   * Constructs a new <code>Riskv1authenticationresultsPaymentInformationTokenizedCard</code>.
-   * @alias module:model/Riskv1authenticationresultsPaymentInformationTokenizedCard
-   * @class
-   */
-  var exports = function() {
-    var _this = this;
-
-
-
-
-
-
-  };
-
-  /**
-   * Constructs a <code>Riskv1authenticationresultsPaymentInformationTokenizedCard</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/Riskv1authenticationresultsPaymentInformationTokenizedCard} obj Optional instance to populate.
-   * @return {module:model/Riskv1authenticationresultsPaymentInformationTokenizedCard} The populated <code>Riskv1authenticationresultsPaymentInformationTokenizedCard</code> instance.
-   */
-  exports.constructFromObject = function(data, obj) {
-    if (data) {
-      obj = obj || new exports();
-
-      if (data.hasOwnProperty('transactionType')) {
-        obj['transactionType'] = ApiClient.convertToType(data['transactionType'], 'String');
-      }
-      if (data.hasOwnProperty('type')) {
-        obj['type'] = ApiClient.convertToType(data['type'], '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('number')) {
-        obj['number'] = ApiClient.convertToType(data['number'], 'String');
-      }
-    }
-    return obj;
-  }
-
-  /**
-   * Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
-   * @member {String} transactionType
-   */
-  exports.prototype['transactionType'] = 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;
-  /**
-   * One of two possible meanings: - The two-digit month in which a token expires. - The two-digit month in which a card expires. Format: `MM` Possible values: `01` through `12`  **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below.  #### 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 (`card_type=039`), if there is no expiration date on the card, use `12`.\\ **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Samsung Pay and Apple Pay Month in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction.  For processor-specific information, see the `customer_cc_expmo` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
-   * @member {String} expirationMonth
-   */
-  exports.prototype['expirationMonth'] = undefined;
-  /**
-   * One of two possible meanings: - The four-digit year in which a token expires. - The four-digit year in which a card expires. Format: `YYYY` Possible values: `1900` through `3000` Data type: Non-negative integer  **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below.  #### 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 (`card_ type=039`), if there is no expiration date on the card, use `2021`.  #### FDC Nashville Global and FDMS South You can send in 2 digits or 4 digits. When you send in 2 digits, they must be the last 2 digits of the year.  #### Samsung Pay and Apple Pay Year in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  For processor-specific information, see the `customer_cc_expyr` or `token_expiration_year` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
-   * @member {String} expirationYear
-   */
-  exports.prototype['expirationYear'] = undefined;
-  /**
-   * Customer’s payment network token value. 
-   * @member {String} number
-   */
-  exports.prototype['number'] = 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.Riskv1authenticationresultsPaymentInformationTokenizedCard = factory(root.CyberSource.ApiClient);
+  }
+}(this, function(ApiClient) {
+  'use strict';
+
+
+
+
+  /**
+   * The Riskv1authenticationresultsPaymentInformationTokenizedCard model module.
+   * @module model/Riskv1authenticationresultsPaymentInformationTokenizedCard
+   * @version 0.0.1
+   */
+
+  /**
+   * Constructs a new <code>Riskv1authenticationresultsPaymentInformationTokenizedCard</code>.
+   * @alias module:model/Riskv1authenticationresultsPaymentInformationTokenizedCard
+   * @class
+   */
+  var exports = function() {
+    var _this = this;
+
+
+
+
+
+
+  };
+
+  /**
+   * Constructs a <code>Riskv1authenticationresultsPaymentInformationTokenizedCard</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/Riskv1authenticationresultsPaymentInformationTokenizedCard} obj Optional instance to populate.
+   * @return {module:model/Riskv1authenticationresultsPaymentInformationTokenizedCard} The populated <code>Riskv1authenticationresultsPaymentInformationTokenizedCard</code> instance.
+   */
+  exports.constructFromObject = function(data, obj) {
+    if (data) {
+      obj = obj || new exports();
+
+      if (data.hasOwnProperty('transactionType')) {
+        obj['transactionType'] = ApiClient.convertToType(data['transactionType'], 'String');
+      }
+      if (data.hasOwnProperty('type')) {
+        obj['type'] = ApiClient.convertToType(data['type'], '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('number')) {
+        obj['number'] = ApiClient.convertToType(data['number'], 'String');
+      }
+    }
+    return obj;
+  }
+
+  /**
+   * Type of transaction that provided the token data. This value does not specify the token service provider; it specifies the entity that provided you with information about the token.  Possible value: - `2`: Near-field communication (NFC) transaction. The customer’s mobile device provided the token data for a contactless EMV transaction. For recurring transactions, use this value if the original transaction was a contactless EMV transaction.  #### Visa Platform Connect - `1`: For Rupay and In App tokenization. Example: InApp apple pay. - `3`: Card/Credential On File Tokenization.  **NOTE** No CyberSource through VisaNet acquirers support EMV at this time.  Required field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. 
+   * @member {String} transactionType
+   */
+  exports.prototype['transactionType'] = 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;
+  /**
+   * One of two possible meanings: - The two-digit month in which a token expires. - The two-digit month in which a card expires. Format: `MM` Possible values: `01` through `12`  **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below.  #### 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 (`card_type=039`), if there is no expiration date on the card, use `12`.\\ **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  #### Samsung Pay and Apple Pay Month in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction.  For processor-specific information, see the `customer_cc_expmo` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
+   * @member {String} expirationMonth
+   */
+  exports.prototype['expirationMonth'] = undefined;
+  /**
+   * One of two possible meanings: - The four-digit year in which a token expires. - The four-digit year in which a card expires. Format: `YYYY` Possible values: `1900` through `3000` Data type: Non-negative integer  **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below.  #### 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 (`card_ type=039`), if there is no expiration date on the card, use `2021`.  #### FDC Nashville Global and FDMS South You can send in 2 digits or 4 digits. When you send in 2 digits, they must be the last 2 digits of the year.  #### Samsung Pay and Apple Pay Year in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction.  **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting.  For processor-specific information, see the `customer_cc_expyr` or `token_expiration_year` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
+   * @member {String} expirationYear
+   */
+  exports.prototype['expirationYear'] = undefined;
+  /**
+   * Customer’s payment network token value. 
+   * @member {String} number
+   */
+  exports.prototype['number'] = undefined;
+
+
+
+  return exports;
+}));
+
+

package/src/model/Riskv1authenticationsBuyerInformation.js

@@ -1,101 +1,101 @@
-/**
- * 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', 'model/Ptsv2paymentsBuyerInformationPersonalIdentification'], factory);
-  } else if (typeof module === 'object' && module.exports) {
-    // CommonJS-like environments that support module.exports, like Node.
-    module.exports = factory(require('../ApiClient'), require('./Ptsv2paymentsBuyerInformationPersonalIdentification'));
-  } else {
-    // Browser globals (root is window)
-    if (!root.CyberSource) {
-      root.CyberSource = {};
-    }
-    root.CyberSource.Riskv1authenticationsBuyerInformation = factory(root.CyberSource.ApiClient, root.CyberSource.Ptsv2paymentsBuyerInformationPersonalIdentification);
-  }
-}(this, function(ApiClient, Ptsv2paymentsBuyerInformationPersonalIdentification) {
-  'use strict';
-
-
-
-
-  /**
-   * The Riskv1authenticationsBuyerInformation model module.
-   * @module model/Riskv1authenticationsBuyerInformation
-   * @version 0.0.1
-   */
-
-  /**
-   * Constructs a new <code>Riskv1authenticationsBuyerInformation</code>.
-   * @alias module:model/Riskv1authenticationsBuyerInformation
-   * @class
-   * @param mobilePhone {Number} Cardholder’s mobile phone number. **Important** Required for Visa Secure transactions in Brazil. Do not use this request field for any other types of transactions. 
-   */
-  var exports = function(mobilePhone) {
-    var _this = this;
-
-
-
-    _this['mobilePhone'] = mobilePhone;
-  };
-
-  /**
-   * Constructs a <code>Riskv1authenticationsBuyerInformation</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/Riskv1authenticationsBuyerInformation} obj Optional instance to populate.
-   * @return {module:model/Riskv1authenticationsBuyerInformation} The populated <code>Riskv1authenticationsBuyerInformation</code> instance.
-   */
-  exports.constructFromObject = function(data, obj) {
-    if (data) {
-      obj = obj || new exports();
-
-      if (data.hasOwnProperty('merchantCustomerId')) {
-        obj['merchantCustomerId'] = ApiClient.convertToType(data['merchantCustomerId'], 'String');
-      }
-      if (data.hasOwnProperty('personalIdentification')) {
-        obj['personalIdentification'] = ApiClient.convertToType(data['personalIdentification'], [Ptsv2paymentsBuyerInformationPersonalIdentification]);
-      }
-      if (data.hasOwnProperty('mobilePhone')) {
-        obj['mobilePhone'] = ApiClient.convertToType(data['mobilePhone'], 'Number');
-      }
-    }
-    return obj;
-  }
-
-  /**
-   * Your identifier for the customer.  When a subscription or customer profile is being created, the maximum length for this field for most processors is 30. Otherwise, the maximum length is 100.  #### Comercio Latino For recurring payments in Mexico, the value is the customer’s contract number. Note Before you request the authorization, you must inform the issuer of the customer contract numbers that will be used for recurring transactions.  #### Worldpay VAP For a follow-on credit with Worldpay VAP, CyberSource checks the following locations, in the order given, for a customer account ID value and uses the first value it finds: 1. `customer_account_id` value in the follow-on credit request 2. Customer account ID value that was used for the capture that is being credited 3. Customer account ID value that was used for the original authorization If a customer account ID value cannot be found in any of these locations, then no value is used.  For processor-specific information, see the `customer_account_id` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
-   * @member {String} merchantCustomerId
-   */
-  exports.prototype['merchantCustomerId'] = undefined;
-  /**
-   * This array contains detailed information about the buyer's form of persoanl identification.
-   * @member {Array.<module:model/Ptsv2paymentsBuyerInformationPersonalIdentification>} personalIdentification
-   */
-  exports.prototype['personalIdentification'] = undefined;
-  /**
-   * Cardholder’s mobile phone number. **Important** Required for Visa Secure transactions in Brazil. Do not use this request field for any other types of transactions. 
-   * @member {Number} mobilePhone
-   */
-  exports.prototype['mobilePhone'] = 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', 'model/Ptsv2paymentsBuyerInformationPersonalIdentification'], factory);
+  } else if (typeof module === 'object' && module.exports) {
+    // CommonJS-like environments that support module.exports, like Node.
+    module.exports = factory(require('../ApiClient'), require('./Ptsv2paymentsBuyerInformationPersonalIdentification'));
+  } else {
+    // Browser globals (root is window)
+    if (!root.CyberSource) {
+      root.CyberSource = {};
+    }
+    root.CyberSource.Riskv1authenticationsBuyerInformation = factory(root.CyberSource.ApiClient, root.CyberSource.Ptsv2paymentsBuyerInformationPersonalIdentification);
+  }
+}(this, function(ApiClient, Ptsv2paymentsBuyerInformationPersonalIdentification) {
+  'use strict';
+
+
+
+
+  /**
+   * The Riskv1authenticationsBuyerInformation model module.
+   * @module model/Riskv1authenticationsBuyerInformation
+   * @version 0.0.1
+   */
+
+  /**
+   * Constructs a new <code>Riskv1authenticationsBuyerInformation</code>.
+   * @alias module:model/Riskv1authenticationsBuyerInformation
+   * @class
+   * @param mobilePhone {Number} Cardholder’s mobile phone number. **Important** Required for Visa Secure transactions in Brazil. Do not use this request field for any other types of transactions. 
+   */
+  var exports = function(mobilePhone) {
+    var _this = this;
+
+
+
+    _this['mobilePhone'] = mobilePhone;
+  };
+
+  /**
+   * Constructs a <code>Riskv1authenticationsBuyerInformation</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/Riskv1authenticationsBuyerInformation} obj Optional instance to populate.
+   * @return {module:model/Riskv1authenticationsBuyerInformation} The populated <code>Riskv1authenticationsBuyerInformation</code> instance.
+   */
+  exports.constructFromObject = function(data, obj) {
+    if (data) {
+      obj = obj || new exports();
+
+      if (data.hasOwnProperty('merchantCustomerId')) {
+        obj['merchantCustomerId'] = ApiClient.convertToType(data['merchantCustomerId'], 'String');
+      }
+      if (data.hasOwnProperty('personalIdentification')) {
+        obj['personalIdentification'] = ApiClient.convertToType(data['personalIdentification'], [Ptsv2paymentsBuyerInformationPersonalIdentification]);
+      }
+      if (data.hasOwnProperty('mobilePhone')) {
+        obj['mobilePhone'] = ApiClient.convertToType(data['mobilePhone'], 'Number');
+      }
+    }
+    return obj;
+  }
+
+  /**
+   * Your identifier for the customer.  When a subscription or customer profile is being created, the maximum length for this field for most processors is 30. Otherwise, the maximum length is 100.  #### Comercio Latino For recurring payments in Mexico, the value is the customer’s contract number. Note Before you request the authorization, you must inform the issuer of the customer contract numbers that will be used for recurring transactions.  #### Worldpay VAP For a follow-on credit with Worldpay VAP, CyberSource checks the following locations, in the order given, for a customer account ID value and uses the first value it finds: 1. `customer_account_id` value in the follow-on credit request 2. Customer account ID value that was used for the capture that is being credited 3. Customer account ID value that was used for the original authorization If a customer account ID value cannot be found in any of these locations, then no value is used.  For processor-specific information, see the `customer_account_id` field description in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) 
+   * @member {String} merchantCustomerId
+   */
+  exports.prototype['merchantCustomerId'] = undefined;
+  /**
+   * This array contains detailed information about the buyer's form of persoanl identification.
+   * @member {Array.<module:model/Ptsv2paymentsBuyerInformationPersonalIdentification>} personalIdentification
+   */
+  exports.prototype['personalIdentification'] = undefined;
+  /**
+   * Cardholder’s mobile phone number. **Important** Required for Visa Secure transactions in Brazil. Do not use this request field for any other types of transactions. 
+   * @member {Number} mobilePhone
+   */
+  exports.prototype['mobilePhone'] = undefined;
+
+
+
+  return exports;
+}));
+
+