@vality/swag-payments 0.1.3-e658db3.0 → 0.1.3-fd6802c.0

package/lib/model/contactInfo.d.ts

@@ -1,52 +0,0 @@
-/**
- * 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.
- */
-/**
- * Contact details
- */
-export interface ContactInfo {
-    /**
-     * Email address
-     */
-    email?: string;
-    /**
-     * Mobile phone number with international prefix according to [E.164](https://en.wikipedia.org/wiki/E.164).
-     */
-    phoneNumber?: string;
-    /**
-     * First name
-     */
-    firstName?: string;
-    /**
-     * Last name
-     */
-    lastName?: string;
-    /**
-     * Alpha-3 country code by standard [ISO 3166-1](https://en.wikipedia.org/wiki/ISO_3166-1)
-     */
-    country?: string;
-    /**
-     * State
-     */
-    state?: string;
-    /**
-     * City
-     */
-    city?: string;
-    /**
-     * Address
-     */
-    address?: string;
-    /**
-     * Postal code
-     */
-    postalCode?: string;
-}

package/lib/model/contract.d.ts

@@ -1,54 +0,0 @@
-/**
- * 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 { LegalAgreement } from './legalAgreement';
-import { Contractor } from './contractor';
-import { ReportingPreferences } from './reportingPreferences';
-/**
- * Contract details
- */
-export interface Contract {
-    /**
-     * Contract ID
-     */
-    id: string;
-    /**
-     * Date and time of contract creation
-     */
-    createdAt: string;
-    /**
-     * Contract status
-     */
-    status: Contract.StatusEnum;
-    /**
-     * Contract effective date and time
-     */
-    validSince?: string;
-    /**
-     * Contract expiration date and time
-     */
-    validUntil?: string;
-    /**
-     * Contract termination date and time
-     */
-    terminatedAt?: string;
-    contractor: Contractor;
-    legalAgreement?: LegalAgreement;
-    paymentInstitutionID: number;
-    reportingPreferences?: ReportingPreferences;
-}
-export declare namespace Contract {
-    type StatusEnum = 'active' | 'terminated';
-    const StatusEnum: {
-        Active: StatusEnum;
-        Terminated: StatusEnum;
-    };
-}

package/lib/model/contractAdjustment.d.ts

@@ -1,32 +0,0 @@
-/**
- * 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.
- */
-/**
- * Data of contract adjustment
- */
-export interface ContractAdjustment {
-    /**
-     * Contract adjustment identifier
-     */
-    id: string;
-    /**
-     * Date and time of contract adjustment creation
-     */
-    createdAt: string;
-    /**
-     * Contract adjustment effective date and time
-     */
-    validSince?: string;
-    /**
-     * Contract adjustment expiration date and time
-     */
-    validUntil?: string;
-}

package/lib/model/contractor.d.ts

@@ -1,28 +0,0 @@
-/**
- * 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.
- */
-/**
- * Contractor data
- */
-export interface Contractor {
-    /**
-     * Contractor type
-     */
-    contractorType: Contractor.ContractorTypeEnum;
-}
-export declare namespace Contractor {
-    type ContractorTypeEnum = 'LegalEntity' | 'PrivateEntity' | 'RegisteredUser';
-    const ContractorTypeEnum: {
-        LegalEntity: ContractorTypeEnum;
-        PrivateEntity: ContractorTypeEnum;
-        RegisteredUser: ContractorTypeEnum;
-    };
-}

package/lib/model/costAmountRange.d.ts

@@ -1,21 +0,0 @@
-/**
- * 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

@@ -1,22 +0,0 @@
-/**
- * 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/createBinding400Response.d.ts

@@ -1,34 +0,0 @@
-/**
- * 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/createCustomer400Response.d.ts

@@ -1,34 +0,0 @@
-/**
- * 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/createInvoice400Response.d.ts

@@ -1,38 +0,0 @@
-/**
- * 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/createInvoiceTemplate400Response.d.ts

@@ -1,34 +0,0 @@
-/**
- * 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/createInvoiceWithTemplate400Response.d.ts

@@ -1,31 +0,0 @@
-/**
- * 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/createPayment400Response.d.ts

@@ -1,38 +0,0 @@
-/**
- * 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/createPayout400Response.d.ts

@@ -1,32 +0,0 @@
-/**
- * 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/createRefund400Response.d.ts

@@ -1,41 +0,0 @@
-/**
- * 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/createWebhook400Response.d.ts

@@ -1,31 +0,0 @@
-/**
- * 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/createWebhook429Response.d.ts

@@ -1,17 +0,0 @@
-/**
- * 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/cryptoCurrencyTransferRequest.d.ts

@@ -1,26 +0,0 @@
-/**
- * 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 './userInteraction';
-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/cryptoCurrencyTransferRequestAllOf.d.ts

@@ -1,25 +0,0 @@
-/**
- * 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;
-}