Update services + models (#1255)

* [create-pull-request] automated change

* Fix test automation/services (#1259)

* fix ut

* Revert breaking change

* fix import

* fix import #2

* fix import #3

---------

Co-authored-by: jilling <jilling.kingma@adyen.com>

---------

Co-authored-by: Alexandros Moraitis <amoraitis@outlook.com>
Co-authored-by: jilling <jilling.kingma@adyen.com>

Author: 3 people

src/services/transfers/transactionsApi.ts

@@ -30,10 +30,10 @@ export class TransactionsApi extends Service {
     * @summary Get all transactions
     * @param createdSince {@link Date } Only include transactions that have been created on or after this point in time. The value must be in ISO 8601 format. For example, **2021-05-30T15:07:40Z**.
     * @param createdUntil {@link Date } Only include transactions that have been created on or before this point in time. The value must be in ISO 8601 format. For example, **2021-05-30T15:07:40Z**.
-    * @param balancePlatform {@link string } Unique identifier of the [balance platform](https://docs.adyen.com/api-explorer/#/balanceplatform/latest/get/balancePlatforms/{id}__queryParam_id).
-    * @param paymentInstrumentId {@link string } Unique identifier of the [payment instrument](https://docs.adyen.com/api-explorer/balanceplatform/latest/get/paymentInstruments/_id_).
-    * @param accountHolderId {@link string } Unique identifier of the [account holder](https://docs.adyen.com/api-explorer/#/balanceplatform/latest/get/accountHolders/{id}__queryParam_id).
-    * @param balanceAccountId {@link string } Unique identifier of the [balance account](https://docs.adyen.com/api-explorer/#/balanceplatform/latest/get/balanceAccounts/{id}__queryParam_id).
+    * @param balancePlatform {@link string } The unique identifier of the [balance platform](https://docs.adyen.com/api-explorer/#/balanceplatform/latest/get/balancePlatforms/{id}__queryParam_id).  Required if you don\'t provide a `balanceAccountId` or `accountHolderId`.
+    * @param paymentInstrumentId {@link string } The unique identifier of the [payment instrument](https://docs.adyen.com/api-explorer/balanceplatform/latest/get/paymentInstruments/_id_).  To use this parameter, you must also provide a `balanceAccountId`, `accountHolderId`, or `balancePlatform`.  The `paymentInstrumentId` must be related to the `balanceAccountId` or `accountHolderId` that you provide.
+    * @param accountHolderId {@link string } The unique identifier of the [account holder](https://docs.adyen.com/api-explorer/#/balanceplatform/latest/get/accountHolders/{id}__queryParam_id).  Required if you don\'t provide a `balanceAccountId` or `balancePlatform`.  If you provide a `balanceAccountId`, the `accountHolderId` must be related to the `balanceAccountId`.
+    * @param balanceAccountId {@link string } The unique identifier of the [balance account](https://docs.adyen.com/api-explorer/#/balanceplatform/latest/get/balanceAccounts/{id}__queryParam_id).  Required if you don\'t provide an `accountHolderId` or `balancePlatform`.  If you provide an `accountHolderId`, the `balanceAccountId` must be related to the `accountHolderId`.
     * @param cursor {@link string } The `cursor` returned in the links of the previous response.
     * @param limit {@link number } The number of items returned per page, maximum of 100 items. By default, the response returns 10 items per page.
     * @param requestOptions {@link IRequest.Options}

src/services/transfers/transfersApi.ts

@@ -28,6 +28,7 @@ export class TransfersApi extends Service {
 
     /**
     * @summary Transfer funds
+    * @param wWWAuthenticate {@link string } Header for authenticating through SCA
     * @param transferInfo {@link TransferInfo } 
     * @param requestOptions {@link IRequest.Options}
     * @return {@link Transfer }

src/typings/checkout/afterpayDetails.ts

@@ -86,6 +86,7 @@ export namespace AfterpayDetails {
     export enum TypeEnum {
         AfterpayDefault = 'afterpay_default',
         Afterpaytouch = 'afterpaytouch',
-        AfterpayB2b = 'afterpay_b2b'
+        AfterpayB2b = 'afterpay_b2b',
+        Clearpay = 'clearpay'
     }
 }

src/typings/checkout/balanceCheckRequest.ts

@@ -55,7 +55,7 @@ export class BalanceCheckRequest {
     'fraudOffset'?: number;
     'installments'?: Installments;
     /**
-    * This field allows merchants to use dynamic shopper statement in local character sets. The local shopper statement field can be supplied in markets where localized merchant descriptors are used. Currently, Adyen only supports this in the Japanese market .The available character sets at the moment are: * Processing in Japan: **ja-Kana** The character set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special characters. Merchants can use half-width or full-width characters. An example request would be: > {   \"shopperStatement\" : \"ADYEN - SELLER-A\",   \"localizedShopperStatement\" : {     \"ja-Kana\" : \"ADYEN - セラーA\"   } } We recommend merchants to always supply the field localizedShopperStatement in addition to the field shopperStatement.It is issuer dependent whether the localized shopper statement field is supported. In the case of non-domestic transactions (e.g. US-issued cards processed in JP) the field `shopperStatement` is used to modify the statement of the shopper. Adyen handles the complexity of ensuring the correct descriptors are assigned. Please note, this field can be used for only Visa and Mastercard transactions.
+    * The `localizedShopperStatement` field lets you use dynamic values for your shopper statement in a local character set. If not supplied, left empty, or for cross-border transactions, **shopperStatement** is used.  Adyen currently supports the ja-Kana character set for Visa and Mastercard payments in Japan using Japanese cards. This character set supports:  * UTF-8 based Katakana, capital letters, numbers and special characters.  * Half-width or full-width characters.
     */
     'localizedShopperStatement'?: { [key: string]: string; };
     /**

src/typings/checkout/donationPaymentRequest.ts

@@ -163,7 +163,7 @@ export class DonationPaymentRequest {
     */
     'lineItems'?: Array<LineItem>;
     /**
-    * This field allows merchants to use dynamic shopper statement in local character sets. The local shopper statement field can be supplied in markets where localized merchant descriptors are used. Currently, Adyen only supports this in the Japanese market .The available character sets at the moment are: * Processing in Japan: **ja-Kana** The character set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special characters. Merchants should send the Katakana shopperStatement in full-width characters.  An example request would be: > {   \"shopperStatement\" : \"ADYEN - SELLER-A\",   \"localizedShopperStatement\" : {     \"ja-Kana\" : \"ADYEN - セラーA\"   } } We recommend merchants to always supply the field localizedShopperStatement in addition to the field shopperStatement.It is issuer dependent whether the localized shopper statement field is supported. In the case of non-domestic transactions (e.g. US-issued cards processed in JP) the field `shopperStatement` is used to modify the statement of the shopper. Adyen handles the complexity of ensuring the correct descriptors are assigned.
+    * The `localizedShopperStatement` field lets you use dynamic values for your shopper statement in a local character set. If not supplied, left empty, or for cross-border transactions, **shopperStatement** is used.  Adyen currently supports the ja-Kana character set for Visa and Mastercard payments in Japan using Japanese cards. This character set supports:  * UTF-8 based Katakana, capital letters, numbers and special characters.  * Half-width or full-width characters.
     */
     'localizedShopperStatement'?: { [key: string]: string; };
     'mandate'?: Mandate;

src/typings/checkout/paymentDetails.ts

@@ -95,7 +95,6 @@ export namespace PaymentDetails {
         Knet = 'knet',
         Omannet = 'omannet',
         GopayWallet = 'gopay_wallet',
-        Poli = 'poli',
         KcpNaverpay = 'kcp_naverpay',
         OnlinebankingIn = 'onlinebanking_IN',
         Fawry = 'fawry',

src/typings/checkout/paymentRequest.ts

@@ -151,7 +151,7 @@ export class PaymentRequest {
     */
     'lineItems'?: Array<LineItem>;
     /**
-    * This field allows merchants to use dynamic shopper statement in local character sets. The local shopper statement field can be supplied in markets where localized merchant descriptors are used. Currently, Adyen only supports this in the Japanese market .The available character sets at the moment are: * Processing in Japan: **ja-Kana** The character set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special characters. Merchants should send the Katakana shopperStatement in full-width characters.  An example request would be: > {   \"shopperStatement\" : \"ADYEN - SELLER-A\",   \"localizedShopperStatement\" : {     \"ja-Kana\" : \"ADYEN - セラーA\"   } } We recommend merchants to always supply the field localizedShopperStatement in addition to the field shopperStatement.It is issuer dependent whether the localized shopper statement field is supported. In the case of non-domestic transactions (e.g. US-issued cards processed in JP) the field `shopperStatement` is used to modify the statement of the shopper. Adyen handles the complexity of ensuring the correct descriptors are assigned.
+    * The `localizedShopperStatement` field lets you use dynamic values for your shopper statement in a local character set. If not supplied, left empty, or for cross-border transactions, **shopperStatement** is used.  Adyen currently supports the ja-Kana character set for Visa and Mastercard payments in Japan using Japanese cards. This character set supports:  * UTF-8 based Katakana, capital letters, numbers and special characters.  * Half-width or full-width characters.
     */
     'localizedShopperStatement'?: { [key: string]: string; };
     'mandate'?: Mandate;

src/typings/checkout/paymentSetupRequest.ts

@@ -96,7 +96,7 @@ export class PaymentSetupRequest {
     */
     'lineItems'?: Array<LineItem>;
     /**
-    * This field allows merchants to use dynamic shopper statement in local character sets. The local shopper statement field can be supplied in markets where localized merchant descriptors are used. Currently, Adyen only supports this in the Japanese market .The available character sets at the moment are: * Processing in Japan: **ja-Kana** The character set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special characters. Merchants can use half-width or full-width characters. An example request would be: > {   \"shopperStatement\" : \"ADYEN - SELLER-A\",   \"localizedShopperStatement\" : {     \"ja-Kana\" : \"ADYEN - セラーA\"   } } We recommend merchants to always supply the field localizedShopperStatement in addition to the field shopperStatement.It is issuer dependent whether the localized shopper statement field is supported. In the case of non-domestic transactions (e.g. US-issued cards processed in JP) the field `shopperStatement` is used to modify the statement of the shopper. Adyen handles the complexity of ensuring the correct descriptors are assigned. Please note, this field can be used for only Visa and Mastercard transactions.
+    * The `localizedShopperStatement` field lets you use dynamic values for your shopper statement in a local character set. If not supplied, left empty, or for cross-border transactions, **shopperStatement** is used.  Adyen currently supports the ja-Kana character set for Visa and Mastercard payments in Japan using Japanese cards. This character set supports:  * UTF-8 based Katakana, capital letters, numbers and special characters.  * Half-width or full-width characters.
     */
     'localizedShopperStatement'?: { [key: string]: string; };
     'mandate'?: Mandate;

src/typings/checkout/threeDSRequestData.ts

@@ -71,7 +71,7 @@ export namespace ThreeDSRequestData {
         Preferred = 'preferred'
     }
     export enum ThreeDSVersionEnum {
-        _10 = 'V_2_1_0',
-        _20 = 'V_2_2_0'
+        _10 = '2.1.0',
+        _20 = '2.2.0'
     }
 }

src/typings/legalEntityManagement/acceptTermsOfServiceResponse.ts

@@ -22,7 +22,7 @@ export class AcceptTermsOfServiceResponse {
     */
     'ipAddress'?: string;
     /**
-    * The language used for the Terms of Service document, specified by the two letter [ISO 639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) language code. For example, **nl** for Dutch.
+    * The language used for the Terms of Service document, specified by the two-letter [ISO 639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) language code. Possible value: **en** for English.
     */
     'language'?: string;
     /**