@vality/swag-payments 0.1.0

package/lib/model/invoice-template-single-line.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 { InvoiceTemplateDetails } from './invoice-template-details';
+import { InvoiceTemplateLineCost } from './invoice-template-line-cost';
+import { InvoiceLineTaxMode } from './invoice-line-tax-mode';
+export interface InvoiceTemplateSingleLine extends InvoiceTemplateDetails {
+    /**
+     * Name of the offered goods or services
+     */
+    product: string;
+    price: InvoiceTemplateLineCost;
+    taxMode?: InvoiceLineTaxMode;
+}

package/lib/model/invoice-template-update-params.d.ts

@@ -0,0 +1,29 @@
+/**
+ * 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 { InvoiceTemplateDetails } from './invoice-template-details';
+import { LifetimeInterval } from './lifetime-interval';
+export interface InvoiceTemplateUpdateParams {
+    /**
+     * Template name
+     */
+    name?: string;
+    /**
+     * Description of the goods or services offered
+     */
+    description?: string;
+    lifetime?: LifetimeInterval;
+    details?: InvoiceTemplateDetails;
+    /**
+     * Metadata that will be associated with the invoice created by the template, in case other metadata is not specified in the invoice creation request.
+     */
+    metadata?: object;
+}

package/lib/model/invoice-template.d.ts

@@ -0,0 +1,45 @@
+/**
+ * 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 { InvoiceTemplateDetails } from './invoice-template-details';
+import { LifetimeInterval } from './lifetime-interval';
+export interface InvoiceTemplate {
+    /**
+     * Invoice template ID
+     */
+    id: string;
+    /**
+     * External invoice template identifier
+     */
+    externalID?: string;
+    /**
+     * Shop ID
+     */
+    shopID: string;
+    /**
+     * Template name
+     */
+    name?: string;
+    /**
+     * Description of the goods or services offered
+     */
+    description?: string;
+    /**
+     * Template creation date
+     */
+    createdAt?: string;
+    lifetime: LifetimeInterval;
+    details: InvoiceTemplateDetails;
+    /**
+     * Metadata that will be associated with the invoice created by the template, in case other metadata is not specified in the invoice creation request.
+     */
+    metadata?: object;
+}

package/lib/model/invoice.d.ts

@@ -0,0 +1,88 @@
+/**
+ * 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 { InvoiceLine } from './invoice-line';
+import { AllocationTransaction } from './allocation-transaction';
+import { InvoiceClientInfo } from './invoice-client-info';
+import { InvoiceBankAccount } from './invoice-bank-account';
+export interface Invoice {
+    /**
+     * Invoice ID
+     */
+    id: string;
+    /**
+     * Shop ID
+     */
+    shopID: string;
+    /**
+     * External invoice identifier
+     */
+    externalID?: string;
+    /**
+     * Created at
+     */
+    createdAt: string;
+    /**
+     * Expiration date and time
+     */
+    dueDate: string;
+    /**
+     * The price of the goods or services offered, in minor monetary units, e.g. cents if U.S. dollars are specified as the currency
+     */
+    amount: number;
+    /**
+     * Currency character code according to [ISO 4217](http://www.iso.org/iso/home/standards/currency_codes.htm).
+     */
+    currency: string;
+    /**
+     * Name of the offered goods or services
+     */
+    product: string;
+    /**
+     * Description of the goods or services offered
+     */
+    description?: string;
+    /**
+     * Invoice template identifier (for invoices created from an invoice template).
+     */
+    invoiceTemplateID?: string;
+    /**
+     * Products and services cart
+     */
+    cart?: Array<InvoiceLine>;
+    /**
+     * Allocation of cash
+     */
+    allocation?: Array<AllocationTransaction>;
+    bankAccount?: InvoiceBankAccount;
+    /**
+     * Invoice metadata
+     */
+    metadata: object;
+    clientInfo?: InvoiceClientInfo;
+    /**
+     * Invoice status
+     */
+    status: Invoice.StatusEnum;
+    /**
+     * Reason for invoice cancellation or redemption
+     */
+    reason?: string;
+}
+export declare namespace Invoice {
+    type StatusEnum = 'unpaid' | 'cancelled' | 'paid' | 'fulfilled';
+    const StatusEnum: {
+        Unpaid: StatusEnum;
+        Cancelled: StatusEnum;
+        Paid: StatusEnum;
+        Fulfilled: StatusEnum;
+    };
+}

package/lib/model/invoices-topic-all-of.d.ts

@@ -0,0 +1,39 @@
+/**
+ * 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 InvoicesTopicAllOf {
+    /**
+     * Shop ID
+     */
+    shopID: string;
+    /**
+     * List of invoice event types to be notified about
+     */
+    eventTypes: Array<InvoicesTopicAllOf.EventTypesEnum>;
+}
+export declare namespace InvoicesTopicAllOf {
+    type EventTypesEnum = 'InvoiceCreated' | 'InvoicePaid' | 'InvoiceCancelled' | 'InvoiceFulfilled' | 'PaymentStarted' | 'PaymentProcessed' | 'PaymentCaptured' | 'PaymentCancelled' | 'PaymentRefunded' | 'PaymentFailed' | 'PaymentRefundCreated' | 'PaymentRefundSucceeded' | 'PaymentRefundFailed';
+    const EventTypesEnum: {
+        InvoiceCreated: EventTypesEnum;
+        InvoicePaid: EventTypesEnum;
+        InvoiceCancelled: EventTypesEnum;
+        InvoiceFulfilled: EventTypesEnum;
+        PaymentStarted: EventTypesEnum;
+        PaymentProcessed: EventTypesEnum;
+        PaymentCaptured: EventTypesEnum;
+        PaymentCancelled: EventTypesEnum;
+        PaymentRefunded: EventTypesEnum;
+        PaymentFailed: EventTypesEnum;
+        PaymentRefundCreated: EventTypesEnum;
+        PaymentRefundSucceeded: EventTypesEnum;
+        PaymentRefundFailed: EventTypesEnum;
+    };
+}

package/lib/model/invoices-topic.d.ts

@@ -0,0 +1,43 @@
+/**
+ * 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 { WebhookScope } from './webhook-scope';
+/**
+ * Scope that includes invoice events within a specific shop
+ */
+export interface InvoicesTopic extends WebhookScope {
+    /**
+     * Shop ID
+     */
+    shopID: string;
+    /**
+     * List of invoice event types to be notified about
+     */
+    eventTypes: Array<InvoicesTopic.EventTypesEnum>;
+}
+export declare namespace InvoicesTopic {
+    type EventTypesEnum = 'InvoiceCreated' | 'InvoicePaid' | 'InvoiceCancelled' | 'InvoiceFulfilled' | 'PaymentStarted' | 'PaymentProcessed' | 'PaymentCaptured' | 'PaymentCancelled' | 'PaymentRefunded' | 'PaymentFailed' | 'PaymentRefundCreated' | 'PaymentRefundSucceeded' | 'PaymentRefundFailed';
+    const EventTypesEnum: {
+        InvoiceCreated: EventTypesEnum;
+        InvoicePaid: EventTypesEnum;
+        InvoiceCancelled: EventTypesEnum;
+        InvoiceFulfilled: EventTypesEnum;
+        PaymentStarted: EventTypesEnum;
+        PaymentProcessed: EventTypesEnum;
+        PaymentCaptured: EventTypesEnum;
+        PaymentCancelled: EventTypesEnum;
+        PaymentRefunded: EventTypesEnum;
+        PaymentFailed: EventTypesEnum;
+        PaymentRefundCreated: EventTypesEnum;
+        PaymentRefundSucceeded: EventTypesEnum;
+        PaymentRefundFailed: EventTypesEnum;
+    };
+}

package/lib/model/legal-agreement.d.ts

@@ -0,0 +1,28 @@
+/**
+ * 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.
+ */
+/**
+ * Legal agreement details
+ */
+export interface LegalAgreement {
+    /**
+     * Legal agreement Identifier, e.g. contract number
+     */
+    id: string;
+    /**
+     * Date and time of conclusion of the legal agreement
+     */
+    signedAt: string;
+    /**
+     * Date and time of termination of the legal agreement
+     */
+    validUntil?: string;
+}

package/lib/model/legal-entity-all-of.d.ts

@@ -0,0 +1,24 @@
+/**
+ * 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 LegalEntityAllOf {
+    /**
+     * Legal entity type
+     */
+    entityType: LegalEntityAllOf.EntityTypeEnum;
+}
+export declare namespace LegalEntityAllOf {
+    type EntityTypeEnum = 'RussianLegalEntity' | 'InternationalLegalEntity';
+    const EntityTypeEnum: {
+        RussianLegalEntity: EntityTypeEnum;
+        InternationalLegalEntity: EntityTypeEnum;
+    };
+}

package/lib/model/legal-entity.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 { Contractor } from './contractor';
+import { LegalEntityAllOf } from './legal-entity-all-of';
+/**
+ * Legal entity
+ */
+export interface LegalEntity extends Contractor, LegalEntityAllOf {
+}
+export declare namespace LegalEntity {
+}

package/lib/model/lifetime-interval.d.ts

@@ -0,0 +1,19 @@
+/**
+ * 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.
+ */
+/**
+ * The life time of an invoice from the time it was created.
+ */
+export interface LifetimeInterval {
+    days: number;
+    months: number;
+    years: number;
+}

package/lib/model/logic-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 payment process
+ */
+export interface LogicError {
+    code: string;
+    message: string;
+}

package/lib/model/mobile-commerce-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 MobileCommerceAllOf {
+    /**
+     * List of mobile operators
+     */
+    operators: Array<string>;
+}

package/lib/model/mobile-commerce-data-all-of.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.
+ */
+import { MobileCommercePhone } from './mobile-commerce-phone';
+/**
+ * Mobile commerce
+ */
+export interface MobileCommerceDataAllOf {
+    mobilePhone: MobileCommercePhone;
+}

package/lib/model/mobile-commerce-data.d.ts

@@ -0,0 +1,6 @@
+import { PaymentTool } from './payment-tool';
+import { MobileCommerceDataAllOf } from './mobile-commerce-data-all-of';
+export interface MobileCommerceData extends PaymentTool, MobileCommerceDataAllOf {
+}
+export declare namespace MobileCommerceData {
+}

package/lib/model/mobile-commerce-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 MobileCommerceDetails {
+    /**
+     * Masked cell phone number
+     */
+    phoneNumber: string;
+}

package/lib/model/mobile-commerce-phone.d.ts

@@ -0,0 +1,24 @@
+/**
+ * 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.
+ */
+/**
+ * Telephone number, according to ITU-T recommendation [E.164](https://en.wikipedia.org/wiki/E.164)
+ */
+export interface MobileCommercePhone {
+    /**
+     * Country code (1-3 digits)
+     */
+    cc: string;
+    /**
+     * Phone number
+     */
+    ctn: string;
+}

package/lib/model/mobile-commerce.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 MobileCommerce extends PaymentMethod {
+    /**
+     * List of mobile operators
+     */
+    operators: Array<string>;
+}
+export declare namespace MobileCommerce {
+}