@vality/swag-payments 0.1.0

package/lib/model/models.d.ts

@@ -0,0 +1,261 @@
+export * from './access-token';
+export * from './allocation-body-amount';
+export * from './allocation-body-amount-all-of';
+export * from './allocation-body-total';
+export * from './allocation-body-total-all-of';
+export * from './allocation-fee';
+export * from './allocation-fee-fixed';
+export * from './allocation-fee-fixed-all-of';
+export * from './allocation-fee-share';
+export * from './allocation-fee-share-all-of';
+export * from './allocation-fee-target';
+export * from './allocation-target';
+export * from './allocation-target-shop';
+export * from './allocation-target-shop-all-of';
+export * from './allocation-transaction';
+export * from './apple-pay';
+export * from './apple-pay-all-of';
+export * from './articles-of-association';
+export * from './bank-account';
+export * from './bank-card';
+export * from './bank-card-all-of';
+export * from './bank-card-all-of-token-provider-data';
+export * from './bank-card-details';
+export * from './bank-card-token-provider-data';
+export * from './bank-card-tokenization-method';
+export * from './browser-get-request';
+export * from './browser-get-request-all-of';
+export * from './browser-post-request';
+export * from './browser-post-request-all-of';
+export * from './browser-request';
+export * from './cancel-payment400-response';
+export * from './capture-params';
+export * from './capture-params-all-of';
+export * from './capture-payment400-response';
+export * from './card-data';
+export * from './card-data-all-of';
+export * from './category';
+export * from './chargeback';
+export * from './client-info';
+export * from './contact-info';
+export * from './contract';
+export * from './contract-adjustment';
+export * from './contractor';
+export * from './cost-amount-range';
+export * from './country';
+export * from './create-binding400-response';
+export * from './create-customer400-response';
+export * from './create-invoice400-response';
+export * from './create-invoice-template400-response';
+export * from './create-invoice-with-template400-response';
+export * from './create-payment400-response';
+export * from './create-payout400-response';
+export * from './create-refund400-response';
+export * from './create-webhook400-response';
+export * from './create-webhook429-response';
+export * from './crypto-currency-transfer-request';
+export * from './crypto-currency-transfer-request-all-of';
+export * from './crypto-wallet';
+export * from './crypto-wallet-all-of';
+export * from './crypto-wallet-data';
+export * from './crypto-wallet-details';
+export * from './customer';
+export * from './customer-and-token';
+export * from './customer-binding';
+export * from './customer-binding-error';
+export * from './customer-binding-interaction-completed';
+export * from './customer-binding-interaction-completed-all-of';
+export * from './customer-binding-interaction-requested';
+export * from './customer-binding-interaction-requested-all-of';
+export * from './customer-binding-params';
+export * from './customer-binding-started';
+export * from './customer-binding-started-all-of';
+export * from './customer-binding-status';
+export * from './customer-binding-status-changed';
+export * from './customer-binding-status-changed-all-of';
+export * from './customer-change';
+export * from './customer-event';
+export * from './customer-params';
+export * from './customer-payer';
+export * from './customer-payer-all-of';
+export * from './customers-topic';
+export * from './customers-topic-all-of';
+export * from './decimal';
+export * from './default-logic-error';
+export * from './delete-customer400-response';
+export * from './digital-wallet';
+export * from './digital-wallet-all-of';
+export * from './digital-wallet-data';
+export * from './digital-wallet-data-all-of';
+export * from './digital-wallet-details';
+export * from './external-id-conflict-error';
+export * from './fulfill-invoice400-response';
+export * from './general-error';
+export * from './google-pay';
+export * from './google-pay-all-of';
+export * from './international-bank-account';
+export * from './international-bank-details';
+export * from './international-correspondent-bank-account';
+export * from './international-legal-entity';
+export * from './international-legal-entity-all-of';
+export * from './invoice';
+export * from './invoice-and-token';
+export * from './invoice-bank-account';
+export * from './invoice-change';
+export * from './invoice-client-info';
+export * from './invoice-created';
+export * from './invoice-created-all-of';
+export * from './invoice-event';
+export * from './invoice-line';
+export * from './invoice-line-tax-mode';
+export * from './invoice-line-tax-vat';
+export * from './invoice-line-tax-vat-all-of';
+export * from './invoice-params';
+export * from './invoice-params-with-template';
+export * from './invoice-russian-bank-account';
+export * from './invoice-russian-bank-account-all-of';
+export * from './invoice-status';
+export * from './invoice-status-changed';
+export * from './invoice-template';
+export * from './invoice-template-and-token';
+export * from './invoice-template-create-params';
+export * from './invoice-template-details';
+export * from './invoice-template-line-cost';
+export * from './invoice-template-line-cost-fixed';
+export * from './invoice-template-line-cost-fixed-all-of';
+export * from './invoice-template-line-cost-range';
+export * from './invoice-template-line-cost-range-all-of';
+export * from './invoice-template-line-cost-unlim';
+export * from './invoice-template-multi-line';
+export * from './invoice-template-multi-line-all-of';
+export * from './invoice-template-single-line';
+export * from './invoice-template-single-line-all-of';
+export * from './invoice-template-update-params';
+export * from './invoices-topic';
+export * from './invoices-topic-all-of';
+export * from './legal-agreement';
+export * from './legal-entity';
+export * from './legal-entity-all-of';
+export * from './lifetime-interval';
+export * from './logic-error';
+export * from './mobile-commerce';
+export * from './mobile-commerce-all-of';
+export * from './mobile-commerce-data';
+export * from './mobile-commerce-data-all-of';
+export * from './mobile-commerce-details';
+export * from './mobile-commerce-phone';
+export * from './party';
+export * from './payer';
+export * from './payer-session-info';
+export * from './payment';
+export * from './payment-error';
+export * from './payment-flow';
+export * from './payment-flow-hold';
+export * from './payment-flow-hold-all-of';
+export * from './payment-flow-instant';
+export * from './payment-institution';
+export * from './payment-interaction-completed';
+export * from './payment-interaction-completed-all-of';
+export * from './payment-interaction-requested';
+export * from './payment-interaction-requested-all-of';
+export * from './payment-method';
+export * from './payment-params';
+export * from './payment-recurrent-parent';
+export * from './payment-resource';
+export * from './payment-resource-client-info';
+export * from './payment-resource-params';
+export * from './payment-resource-payer';
+export * from './payment-resource-payer-all-of';
+export * from './payment-resource-result';
+export * from './payment-search-result';
+export * from './payment-search-result-all-of';
+export * from './payment-started';
+export * from './payment-started-all-of';
+export * from './payment-status';
+export * from './payment-status-changed';
+export * from './payment-status-changed-all-of';
+export * from './payment-terminal';
+export * from './payment-terminal-all-of';
+export * from './payment-terminal-data';
+export * from './payment-terminal-data-all-of';
+export * from './payment-terminal-details';
+export * from './payment-terminal-receipt';
+export * from './payment-terminal-receipt-all-of';
+export * from './payment-terms';
+export * from './payment-tool';
+export * from './payment-tool-details';
+export * from './payment-tool-details-bank-card';
+export * from './payment-tool-details-crypto-wallet';
+export * from './payment-tool-details-digital-wallet';
+export * from './payment-tool-details-mobile-commerce';
+export * from './payment-tool-details-payment-terminal';
+export * from './payout';
+export * from './payout-params';
+export * from './payout-tool';
+export * from './payout-tool-all-of';
+export * from './payout-tool-details';
+export * from './payout-tool-details-bank-account';
+export * from './payout-tool-details-international-bank-account';
+export * from './payout-tool-details-payment-institution-account';
+export * from './payout-tool-details-wallet-info';
+export * from './payout-tool-details-wallet-info-all-of';
+export * from './payout-tool-params';
+export * from './power-of-attorney';
+export * from './private-entity';
+export * from './private-entity-all-of';
+export * from './qr-code-display-request';
+export * from './qr-code-display-request-all-of';
+export * from './realm-mode';
+export * from './reason';
+export * from './recurrent-payer';
+export * from './recurrent-payer-all-of';
+export * from './redirect';
+export * from './redirect-all-of';
+export * from './refund';
+export * from './refund-error';
+export * from './refund-params';
+export * from './refund-search-result';
+export * from './refund-search-result-all-of';
+export * from './refund-started';
+export * from './refund-started-all-of';
+export * from './refund-status';
+export * from './refund-status-changed';
+export * from './refund-status-changed-all-of';
+export * from './registered-user';
+export * from './registered-user-all-of';
+export * from './report-link';
+export * from './report-params';
+export * from './reporting-preferences';
+export * from './representative';
+export * from './representative-document';
+export * from './rescind-invoice400-response';
+export * from './russian-legal-entity';
+export * from './russian-legal-entity-all-of';
+export * from './russian-private-entity';
+export * from './russian-private-entity-all-of';
+export * from './samsung-pay';
+export * from './samsung-pay-all-of';
+export * from './schedule';
+export * from './search-invoices200-response';
+export * from './search-payments200-response';
+export * from './search-payouts200-response';
+export * from './search-refunds200-response';
+export * from './service-acceptance-act-preferences';
+export * from './service-provider';
+export * from './shop';
+export * from './shop-details';
+export * from './shop-location';
+export * from './shop-location-url';
+export * from './shop-location-url-all-of';
+export * from './sub-error';
+export * from './tokenized-card-data';
+export * from './tokenized-card-data-all-of';
+export * from './trade-bloc';
+export * from './transaction-info';
+export * from './update-invoice-template400-response';
+export * from './user-interaction';
+export * from './user-interaction-form-inner';
+export * from './webhook';
+export * from './webhook-scope';
+export * from './yandex-pay';
+export * from './yandex-pay-all-of';

package/lib/model/party.d.ts

@@ -0,0 +1,16 @@
+/**
+ * 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 Party {
+    id: string;
+    isBlocked: boolean;
+    isSuspended: boolean;
+}

package/lib/model/payer-session-info.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.
+ */
+/**
+ * Payer\'s current session data
+ */
+export interface PayerSessionInfo {
+    /**
+     * URL of the resource to which the payer should be redirected upon completion of interaction with it in the browser, for example, preauthorization of payment using 3D Secure 2.0 protocol, if such interaction is required.
+     */
+    redirectUrl?: string;
+}

package/lib/model/payer.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.
+ */
+import { PayerSessionInfo } from './payer-session-info';
+export interface Payer {
+    /**
+     * Payment tool type
+     */
+    payerType: string;
+    sessionInfo?: PayerSessionInfo;
+}

package/lib/model/payment-error.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 { SubError } from './sub-error';
+/**
+ * [Error](#tag/Error-Codes) occurred during the payment process
+ */
+export interface PaymentError {
+    /**
+     * Basic error code
+     */
+    code: string;
+    subError?: SubError;
+}

package/lib/model/payment-flow-hold-all-of.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.
+ */
+export interface PaymentFlowHoldAllOf {
+    /**
+     * Cash withholding management policy
+     */
+    onHoldExpiration: PaymentFlowHoldAllOf.OnHoldExpirationEnum;
+    /**
+     * Date and time of withholding of funds
+     */
+    readonly heldUntil?: string;
+}
+export declare namespace PaymentFlowHoldAllOf {
+    type OnHoldExpirationEnum = 'cancel' | 'capture';
+    const OnHoldExpirationEnum: {
+        Cancel: OnHoldExpirationEnum;
+        Capture: OnHoldExpirationEnum;
+    };
+}

package/lib/model/payment-flow-hold.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 { PaymentFlow } from './payment-flow';
+export interface PaymentFlowHold extends PaymentFlow {
+    /**
+     * Cash withholding management policy
+     */
+    onHoldExpiration: PaymentFlowHold.OnHoldExpirationEnum;
+    /**
+     * Date and time of withholding of funds
+     */
+    readonly heldUntil?: string;
+}
+export declare namespace PaymentFlowHold {
+    type OnHoldExpirationEnum = 'cancel' | 'capture';
+    const OnHoldExpirationEnum: {
+        Cancel: OnHoldExpirationEnum;
+        Capture: OnHoldExpirationEnum;
+    };
+}

package/lib/model/payment-flow-instant.d.ts

@@ -0,0 +1,16 @@
+/**
+ * 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 { PaymentFlow } from './payment-flow';
+export interface PaymentFlowInstant extends PaymentFlow {
+}
+export declare namespace PaymentFlowInstant {
+}

package/lib/model/payment-flow.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 PaymentFlow {
+    /**
+     * Payment flow type
+     */
+    type: PaymentFlow.TypeEnum;
+}
+export declare namespace PaymentFlow {
+    type TypeEnum = 'PaymentFlowInstant' | 'PaymentFlowHold';
+    const TypeEnum: {
+        PaymentFlowInstant: TypeEnum;
+        PaymentFlowHold: TypeEnum;
+    };
+}

package/lib/model/payment-institution.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.
+ */
+/**
+ * Payment Institution
+ */
+export interface PaymentInstitution {
+    id: number;
+    name: string;
+    description?: string;
+    residences: Array<string>;
+    /**
+     * Payment institution\'s mode
+     */
+    realm: PaymentInstitution.RealmEnum;
+}
+export declare namespace PaymentInstitution {
+    type RealmEnum = 'test' | 'live';
+    const RealmEnum: {
+        Test: RealmEnum;
+        Live: RealmEnum;
+    };
+}

package/lib/model/payment-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
+ */
+export interface PaymentInteractionCompletedAllOf {
+    /**
+     * Payment ID
+     */
+    paymentID: string;
+    userInteraction?: UserInteraction;
+}

package/lib/model/payment-interaction-completed.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 { InvoiceChange } from './invoice-change';
+import { UserInteraction } from './user-interaction';
+export interface PaymentInteractionCompleted extends InvoiceChange {
+    /**
+     * Payment ID
+     */
+    paymentID: string;
+    userInteraction?: UserInteraction;
+}
+export declare namespace PaymentInteractionCompleted {
+}

package/lib/model/payment-interaction-requested-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';
+/**
+ * Require interaction with the customer to continue the payment process
+ */
+export interface PaymentInteractionRequestedAllOf {
+    /**
+     * Payment ID
+     */
+    paymentID: string;
+    userInteraction: UserInteraction;
+}

package/lib/model/payment-interaction-requested.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 { InvoiceChange } from './invoice-change';
+import { UserInteraction } from './user-interaction';
+export interface PaymentInteractionRequested extends InvoiceChange {
+    /**
+     * Payment ID
+     */
+    paymentID: string;
+    userInteraction: UserInteraction;
+}
+export declare namespace PaymentInteractionRequested {
+}

package/lib/model/payment-method.d.ts

@@ -0,0 +1,27 @@
+/**
+ * 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 PaymentMethod {
+    /**
+     * Payment method
+     */
+    method: PaymentMethod.MethodEnum;
+}
+export declare namespace PaymentMethod {
+    type MethodEnum = 'BankCard' | 'PaymentTerminal' | 'DigitalWallet' | 'CryptoWallet' | 'MobileCommerce';
+    const MethodEnum: {
+        BankCard: MethodEnum;
+        PaymentTerminal: MethodEnum;
+        DigitalWallet: MethodEnum;
+        CryptoWallet: MethodEnum;
+        MobileCommerce: MethodEnum;
+    };
+}