@vality/swag-payments 0.1.0

package/lib/model/cost-amount-range.d.ts

@@ -0,0 +1,21 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CostAmountRange {
+    /**
+     * An upper (inclusive) limit on the value of goods or services.
+     */
+    upperBound: number;
+    /**
+     * A lower (inclusive) limit on the value of goods or services.
+     */
+    lowerBound: number;
+}

package/lib/model/country.d.ts

@@ -0,0 +1,22 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ * Country
+ */
+export interface Country {
+    /**
+     * Alpha-3 country code by standard [ISO 3166-1](https://en.wikipedia.org/wiki/ISO_3166-1)
+     */
+    id: string;
+    name: string;
+    tradeBlocs?: Array<string>;
+}

package/lib/model/create-binding400-response.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreateBinding400Response {
+    /**
+     * [Error code](#tag/Error-Codes)
+     */
+    code: CreateBinding400Response.CodeEnum;
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}
+export declare namespace CreateBinding400Response {
+    type CodeEnum = 'invalidPaymentResource' | 'operationNotPermitted' | 'invalidPartyStatus' | 'invalidShopStatus' | 'invalidPaymentToolToken' | 'invalidPaymentSession' | 'invalidRequest' | 'invalidDeadline';
+    const CodeEnum: {
+        InvalidPaymentResource: CodeEnum;
+        OperationNotPermitted: CodeEnum;
+        InvalidPartyStatus: CodeEnum;
+        InvalidShopStatus: CodeEnum;
+        InvalidPaymentToolToken: CodeEnum;
+        InvalidPaymentSession: CodeEnum;
+        InvalidRequest: CodeEnum;
+        InvalidDeadline: CodeEnum;
+    };
+}

package/lib/model/create-customer400-response.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreateCustomer400Response {
+    /**
+     * [Error code](#tag/Error-Codes)
+     */
+    code: CreateCustomer400Response.CodeEnum;
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}
+export declare namespace CreateCustomer400Response {
+    type CodeEnum = 'operationNotPermitted' | 'invalidPartyID' | 'invalidShopID' | 'invalidPartyStatus' | 'invalidShopStatus' | 'invalidRequest' | 'invalidDeadline' | 'ambiguousPartyID';
+    const CodeEnum: {
+        OperationNotPermitted: CodeEnum;
+        InvalidPartyId: CodeEnum;
+        InvalidShopId: CodeEnum;
+        InvalidPartyStatus: CodeEnum;
+        InvalidShopStatus: CodeEnum;
+        InvalidRequest: CodeEnum;
+        InvalidDeadline: CodeEnum;
+        AmbiguousPartyId: CodeEnum;
+    };
+}

package/lib/model/create-invoice-template400-response.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreateInvoiceTemplate400Response {
+    /**
+     * [Error code](#tag/Error-Codes)
+     */
+    code: CreateInvoiceTemplate400Response.CodeEnum;
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}
+export declare namespace CreateInvoiceTemplate400Response {
+    type CodeEnum = 'invalidPartyID' | 'invalidRequest' | 'invalidDeadline' | 'invalidShopID' | 'invalidPartyStatus' | 'invalidShopStatus' | 'invalidInvoiceCart' | 'ambiguousPartyID';
+    const CodeEnum: {
+        InvalidPartyId: CodeEnum;
+        InvalidRequest: CodeEnum;
+        InvalidDeadline: CodeEnum;
+        InvalidShopId: CodeEnum;
+        InvalidPartyStatus: CodeEnum;
+        InvalidShopStatus: CodeEnum;
+        InvalidInvoiceCart: CodeEnum;
+        AmbiguousPartyId: CodeEnum;
+    };
+}

package/lib/model/create-invoice-with-template400-response.d.ts

@@ -0,0 +1,31 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreateInvoiceWithTemplate400Response {
+    /**
+     * [Error code](#tag/Error-Codes)
+     */
+    code: CreateInvoiceWithTemplate400Response.CodeEnum;
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}
+export declare namespace CreateInvoiceWithTemplate400Response {
+    type CodeEnum = 'invalidPartyStatus' | 'invalidShopStatus' | 'invalidRequest' | 'invalidDeadline' | 'invoiceTermsViolated';
+    const CodeEnum: {
+        InvalidPartyStatus: CodeEnum;
+        InvalidShopStatus: CodeEnum;
+        InvalidRequest: CodeEnum;
+        InvalidDeadline: CodeEnum;
+        InvoiceTermsViolated: CodeEnum;
+    };
+}

package/lib/model/create-invoice400-response.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreateInvoice400Response {
+    /**
+     * [Error code](#tag/Error-Codes)
+     */
+    code: CreateInvoice400Response.CodeEnum;
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}
+export declare namespace CreateInvoice400Response {
+    type CodeEnum = 'invalidPartyID' | 'invalidShopID' | 'invalidRequest' | 'invalidDeadline' | 'invalidPartyStatus' | 'invalidShopStatus' | 'invalidInvoiceCart' | 'invalidAllocation' | 'allocationNotPermitted' | 'invalidInvoiceCost' | 'invoiceTermsViolated' | 'ambiguousPartyID';
+    const CodeEnum: {
+        InvalidPartyId: CodeEnum;
+        InvalidShopId: CodeEnum;
+        InvalidRequest: CodeEnum;
+        InvalidDeadline: CodeEnum;
+        InvalidPartyStatus: CodeEnum;
+        InvalidShopStatus: CodeEnum;
+        InvalidInvoiceCart: CodeEnum;
+        InvalidAllocation: CodeEnum;
+        AllocationNotPermitted: CodeEnum;
+        InvalidInvoiceCost: CodeEnum;
+        InvoiceTermsViolated: CodeEnum;
+        AmbiguousPartyId: CodeEnum;
+    };
+}

package/lib/model/create-payment400-response.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreatePayment400Response {
+    /**
+     * [Error code](#tag/Error-Codes)
+     */
+    code: CreatePayment400Response.CodeEnum;
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}
+export declare namespace CreatePayment400Response {
+    type CodeEnum = 'invalidInvoiceStatus' | 'invoicePaymentPending' | 'invalidRequest' | 'invalidDeadline' | 'invalidPartyStatus' | 'invalidShopStatus' | 'invalidContractStatus' | 'invalidPaymentToolToken' | 'invalidPaymentSession' | 'invalidProcessingDeadline' | 'invalidRecurrentParent' | 'operationNotPermitted';
+    const CodeEnum: {
+        InvalidInvoiceStatus: CodeEnum;
+        InvoicePaymentPending: CodeEnum;
+        InvalidRequest: CodeEnum;
+        InvalidDeadline: CodeEnum;
+        InvalidPartyStatus: CodeEnum;
+        InvalidShopStatus: CodeEnum;
+        InvalidContractStatus: CodeEnum;
+        InvalidPaymentToolToken: CodeEnum;
+        InvalidPaymentSession: CodeEnum;
+        InvalidProcessingDeadline: CodeEnum;
+        InvalidRecurrentParent: CodeEnum;
+        OperationNotPermitted: CodeEnum;
+    };
+}

package/lib/model/create-payout400-response.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreatePayout400Response {
+    /**
+     * [Error code](#tag/Error-Codes)
+     */
+    code: CreatePayout400Response.CodeEnum;
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}
+export declare namespace CreatePayout400Response {
+    type CodeEnum = 'invalidPartyID' | 'invalidPayoutTool' | 'invalidCash' | 'invalidRequest' | 'invalidDeadline' | 'ambiguousPartyID';
+    const CodeEnum: {
+        InvalidPartyId: CodeEnum;
+        InvalidPayoutTool: CodeEnum;
+        InvalidCash: CodeEnum;
+        InvalidRequest: CodeEnum;
+        InvalidDeadline: CodeEnum;
+        AmbiguousPartyId: CodeEnum;
+    };
+}

package/lib/model/create-refund400-response.d.ts

@@ -0,0 +1,41 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreateRefund400Response {
+    /**
+     * [Error code](#tag/Error-Codes)
+     */
+    code: CreateRefund400Response.CodeEnum;
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}
+export declare namespace CreateRefund400Response {
+    type CodeEnum = 'invalidPartyStatus' | 'invalidShopStatus' | 'invalidContractStatus' | 'invalidInvoiceCart' | 'invalidAllocation' | 'allocationNotPermitted' | 'operationNotPermitted' | 'invalidPaymentStatus' | 'insufficentAccountBalance' | 'invoicePaymentAmountExceeded' | 'inconsistentRefundCurrency' | 'invalidRequest' | 'invalidDeadline' | 'chargebackInProgress' | 'refundCartConflict';
+    const CodeEnum: {
+        InvalidPartyStatus: CodeEnum;
+        InvalidShopStatus: CodeEnum;
+        InvalidContractStatus: CodeEnum;
+        InvalidInvoiceCart: CodeEnum;
+        InvalidAllocation: CodeEnum;
+        AllocationNotPermitted: CodeEnum;
+        OperationNotPermitted: CodeEnum;
+        InvalidPaymentStatus: CodeEnum;
+        InsufficentAccountBalance: CodeEnum;
+        InvoicePaymentAmountExceeded: CodeEnum;
+        InconsistentRefundCurrency: CodeEnum;
+        InvalidRequest: CodeEnum;
+        InvalidDeadline: CodeEnum;
+        ChargebackInProgress: CodeEnum;
+        RefundCartConflict: CodeEnum;
+    };
+}

package/lib/model/create-webhook400-response.d.ts

@@ -0,0 +1,31 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreateWebhook400Response {
+    /**
+     * [Error code](#tag/Error-Codes)
+     */
+    code: CreateWebhook400Response.CodeEnum;
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}
+export declare namespace CreateWebhook400Response {
+    type CodeEnum = 'invalidPartyID' | 'invalidShopID' | 'invalidRequest' | 'invalidDeadline' | 'ambiguousPartyID';
+    const CodeEnum: {
+        InvalidPartyId: CodeEnum;
+        InvalidShopId: CodeEnum;
+        InvalidRequest: CodeEnum;
+        InvalidDeadline: CodeEnum;
+        AmbiguousPartyId: CodeEnum;
+    };
+}

package/lib/model/create-webhook429-response.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CreateWebhook429Response {
+    /**
+     * Human-readable description of the error
+     */
+    message: string;
+}

package/lib/model/crypto-currency-transfer-request-all-of.d.ts

@@ -0,0 +1,25 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CryptoCurrencyTransferRequestAllOf {
+    /**
+     * Cryptocurrency wallet address
+     */
+    cryptoAddress: string;
+    /**
+     * Cryptocurrency symbolic code
+     */
+    symbolicCode: string;
+    /**
+     * Amount of cash in cryptocurrency
+     */
+    cryptoAmount: string;
+}

package/lib/model/crypto-currency-transfer-request.d.ts

@@ -0,0 +1,26 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import { UserInteraction } from './user-interaction';
+export interface CryptoCurrencyTransferRequest extends UserInteraction {
+    /**
+     * Cryptocurrency wallet address
+     */
+    cryptoAddress: string;
+    /**
+     * Cryptocurrency symbolic code
+     */
+    symbolicCode: string;
+    /**
+     * Amount of cash in cryptocurrency
+     */
+    cryptoAmount: string;
+}

package/lib/model/crypto-wallet-all-of.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CryptoWalletAllOf {
+    /**
+     * List of cryptocurrencies
+     */
+    cryptoCurrencies: Array<string>;
+}

package/lib/model/crypto-wallet-data.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import { PaymentTool } from './payment-tool';
+export interface CryptoWalletData extends PaymentTool {
+    /**
+     * Cryptocurrency payment method. The list of cryptocurrencies available for making payments can be found out by calling the corresponding [operation](#operation/getInvoicePaymentMethods) after creating an invoice.
+     */
+    cryptoCurrency: string;
+}
+export declare namespace CryptoWalletData {
+}

package/lib/model/crypto-wallet-details.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export interface CryptoWalletDetails {
+    /**
+     * Cryptocurrency payment method. The list of cryptocurrencies available for making payments can be found out by calling the corresponding [operation](#operation/getInvoicePaymentMethods) after creating an invoice.
+     */
+    cryptoCurrency: string;
+}

package/lib/model/crypto-wallet.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import { PaymentMethod } from './payment-method';
+export interface CryptoWallet extends PaymentMethod {
+    /**
+     * List of cryptocurrencies
+     */
+    cryptoCurrencies: Array<string>;
+}
+export declare namespace CryptoWallet {
+}

package/lib/model/customer-and-token.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import { Customer } from './customer';
+import { AccessToken } from './access-token';
+export interface CustomerAndToken {
+    customer: Customer;
+    customerAccessToken: AccessToken;
+}

package/lib/model/customer-binding-error.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ * Description of the error that occurred during the binding process
+ */
+export interface CustomerBindingError {
+    code: string;
+    message: string;
+}

package/lib/model/customer-binding-interaction-completed-all-of.d.ts

@@ -0,0 +1,22 @@
+/**
+ * Vality Payments API
+ * ## Description API is designed for the merchants who accept payments via user interface such as a website or a mobile app and it is the only interaction point with the system for goods and services payment transactions. ## Interaction details Whenever an API is accessed, its unique ID must be passed in the header X-Request-ID of the corresponding request: ```  X-Request-ID: 37d735d4-0f42-4f05-89fa-eaa478fb5aa9 ``` ### Content type and coding The system accepts and returns data in JSON format and UTF-8 coding: ```   Content-Type: application/json; charset=utf-8 ``` ### Date formats The system accepts and returns timestamp values in the format date-time, described in [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339): ```   2017-01-01T00:00:00Z   2017-01-01T00:00:01+00:00 ``` ### Maximum request processing time Whenever an API is accessed, the time cutoff parameters, that define maximum request processing time of the transaction completion, can be passed in the header `X-Request-Deadline` of the corresponding request: ```  X-Request-Deadline: 10s ``` The system stops processing the request upon the specified time. It is recommended to specify a value that is not more than one minute and not less than three seconds. `X-Request-Deadline` can be:  * specified in the format `date-time` according to [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339); * specified in relative values: in milliseconds (`150000ms`), in seconds (`540s`) or in minutes (`3.5m`).
+ *
+ * The version of the OpenAPI document: 2.0.1
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import { UserInteraction } from './user-interaction';
+/**
+ * Notification on completion of the last requested interaction with the customer within the bindings
+ */
+export interface CustomerBindingInteractionCompletedAllOf {
+    /**
+     * Customer binding identifier
+     */
+    customerBindingID: string;
+    userInteraction?: UserInteraction;
+}