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

package/lib/api/payouts.service.d.ts

@@ -1,209 +0,0 @@
-import { HttpClient, HttpHeaders, HttpResponse, HttpEvent, HttpParameterCodec, HttpContext } from '@angular/common/http';
-import { Observable } from 'rxjs';
-import { Payout } from '../model/payout';
-import { PayoutParams } from '../model/payoutParams';
-import { PayoutTool } from '../model/payoutTool';
-import { Schedule } from '../model/schedule';
-import { Configuration } from '../configuration';
-import * as i0 from "@angular/core";
-export interface CreatePayoutRequestParams {
-    /** Unique identifier of the request to the system */
-    xRequestID: string;
-    payoutParams: PayoutParams;
-    /** Maximum request processing time */
-    xRequestDeadline?: string;
-}
-export interface GetPayoutRequestParams {
-    /** Unique identifier of the request to the system */
-    xRequestID: string;
-    /** Withdrawal ID */
-    payoutID: string;
-    /** Maximum request processing time */
-    xRequestDeadline?: string;
-}
-export interface GetPayoutToolByIDRequestParams {
-    /** Unique identifier of the request to the system */
-    xRequestID: string;
-    /** Contract ID */
-    contractID: string;
-    /** Payout tool ID */
-    payoutToolID: string;
-    /** Maximum request processing time */
-    xRequestDeadline?: string;
-}
-export interface GetPayoutToolByIDForPartyRequestParams {
-    /** Unique identifier of the request to the system */
-    xRequestID: string;
-    /** Contract ID */
-    contractID: string;
-    /** Payout tool ID */
-    payoutToolID: string;
-    /** The participant\'s unique identifier within the system. */
-    partyID: string;
-    /** Maximum request processing time */
-    xRequestDeadline?: string;
-}
-export interface GetPayoutToolsRequestParams {
-    /** Unique identifier of the request to the system */
-    xRequestID: string;
-    /** Contract ID */
-    contractID: string;
-    /** Maximum request processing time */
-    xRequestDeadline?: string;
-}
-export interface GetPayoutToolsForPartyRequestParams {
-    /** Unique identifier of the request to the system */
-    xRequestID: string;
-    /** Contract ID */
-    contractID: string;
-    /** The participant\'s unique identifier within the system. */
-    partyID: string;
-    /** Maximum request processing time */
-    xRequestDeadline?: string;
-}
-export interface GetScheduleByRefRequestParams {
-    /** Unique identifier of the request to the system */
-    xRequestID: string;
-    /** Schedule reference */
-    scheduleID: number;
-    /** Maximum request processing time */
-    xRequestDeadline?: string;
-}
-export declare class PayoutsService {
-    protected httpClient: HttpClient;
-    protected basePath: string;
-    defaultHeaders: HttpHeaders;
-    configuration: Configuration;
-    encoder: HttpParameterCodec;
-    constructor(httpClient: HttpClient, basePath: string | string[], configuration: Configuration);
-    private addToHttpParams;
-    private addToHttpParamsRecursive;
-    /**
-     * Create a new payout and send it to pre-moderation.
-     * @param requestParameters
-     * @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
-     * @param reportProgress flag to report request and response progress.
-     */
-    createPayout(requestParameters: CreatePayoutRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset=utf-8';
-        context?: HttpContext;
-    }): Observable<Payout>;
-    createPayout(requestParameters: CreatePayoutRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpResponse<Payout>>;
-    createPayout(requestParameters: CreatePayoutRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpEvent<Payout>>;
-    /**
-     * Get payout data
-     * @param requestParameters
-     * @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
-     * @param reportProgress flag to report request and response progress.
-     */
-    getPayout(requestParameters: GetPayoutRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<Payout>;
-    getPayout(requestParameters: GetPayoutRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpResponse<Payout>>;
-    getPayout(requestParameters: GetPayoutRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpEvent<Payout>>;
-    /**
-     * Get a payout tool data by identifier
-     * @param requestParameters
-     * @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
-     * @param reportProgress flag to report request and response progress.
-     */
-    getPayoutToolByID(requestParameters: GetPayoutToolByIDRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<PayoutTool>;
-    getPayoutToolByID(requestParameters: GetPayoutToolByIDRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpResponse<PayoutTool>>;
-    getPayoutToolByID(requestParameters: GetPayoutToolByIDRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpEvent<PayoutTool>>;
-    /**
-     * Get a payout tool data by identifier
-     * @param requestParameters
-     * @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
-     * @param reportProgress flag to report request and response progress.
-     */
-    getPayoutToolByIDForParty(requestParameters: GetPayoutToolByIDForPartyRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<PayoutTool>;
-    getPayoutToolByIDForParty(requestParameters: GetPayoutToolByIDForPartyRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpResponse<PayoutTool>>;
-    getPayoutToolByIDForParty(requestParameters: GetPayoutToolByIDForPartyRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpEvent<PayoutTool>>;
-    /**
-     * Get all payout tools to the specified contract
-     * @param requestParameters
-     * @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
-     * @param reportProgress flag to report request and response progress.
-     */
-    getPayoutTools(requestParameters: GetPayoutToolsRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<Array<PayoutTool>>;
-    getPayoutTools(requestParameters: GetPayoutToolsRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpResponse<Array<PayoutTool>>>;
-    getPayoutTools(requestParameters: GetPayoutToolsRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpEvent<Array<PayoutTool>>>;
-    /**
-     * Get all payout tools to the specified contract
-     * @param requestParameters
-     * @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
-     * @param reportProgress flag to report request and response progress.
-     */
-    getPayoutToolsForParty(requestParameters: GetPayoutToolsForPartyRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<Array<PayoutTool>>;
-    getPayoutToolsForParty(requestParameters: GetPayoutToolsForPartyRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpResponse<Array<PayoutTool>>>;
-    getPayoutToolsForParty(requestParameters: GetPayoutToolsForPartyRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpEvent<Array<PayoutTool>>>;
-    /**
-     * Get payout schedule data by identifier
-     * @param requestParameters
-     * @param observe set whether or not to return the data Observable as the body, response or events. defaults to returning the body.
-     * @param reportProgress flag to report request and response progress.
-     */
-    getScheduleByRef(requestParameters: GetScheduleByRefRequestParams, observe?: 'body', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<Schedule>;
-    getScheduleByRef(requestParameters: GetScheduleByRefRequestParams, observe?: 'response', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpResponse<Schedule>>;
-    getScheduleByRef(requestParameters: GetScheduleByRefRequestParams, observe?: 'events', reportProgress?: boolean, options?: {
-        httpHeaderAccept?: 'application/json; charset&#x3D;utf-8';
-        context?: HttpContext;
-    }): Observable<HttpEvent<Schedule>>;
-    static ɵfac: i0.ɵɵFactoryDeclaration<PayoutsService, [null, { optional: true; }, { optional: true; }]>;
-    static ɵprov: i0.ɵɵInjectableDeclaration<PayoutsService>;
-}

package/lib/index.d.ts

@@ -1,6 +0,0 @@
-export * from './api/api';
-export * from './model/models';
-export * from './variables';
-export * from './configuration';
-export * from './api.module';
-export * from './param';

package/lib/model/accessToken.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 AccessToken {
-    /**
-     * Access token payload
-     */
-    payload: string;
-}

package/lib/model/allocationBodyAmountAllOf.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 AllocationBodyAmountAllOf {
-    /**
-     * The amount transferred to the selected destination in minor monetary units, e.g. cents if US 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;
-}

package/lib/model/allocationBodyTotalAllOf.d.ts

@@ -1,27 +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 { AllocationFee } from './allocationFee';
-export interface AllocationBodyTotalAllOf {
-    /**
-     * Total transaction amount (includes fees) in minor monetary units, e.g. cents if US dollars are specified as the currency.
-     */
-    total: number;
-    /**
-     * The amount transferred to the selected destination in minor monetary units, e.g. cents if US dollars are specified as the currency.
-     */
-    readonly amount?: number;
-    /**
-     * Currency character code according to [ISO 4217](http://www.iso.org/iso/home/standards/currency_codes.htm).
-     */
-    currency: string;
-    fee: AllocationFee;
-}

package/lib/model/allocationFee.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 { AllocationFeeTarget } from './allocationFeeTarget';
-/**
- * Transaction fee
- */
-export interface AllocationFee {
-    target?: AllocationFeeTarget;
-    allocationFeeType: AllocationFee.AllocationFeeTypeEnum;
-}
-export declare namespace AllocationFee {
-    type AllocationFeeTypeEnum = 'AllocationFeeFixed' | 'AllocationFeeShare';
-    const AllocationFeeTypeEnum: {
-        AllocationFeeFixed: AllocationFeeTypeEnum;
-        AllocationFeeShare: AllocationFeeTypeEnum;
-    };
-}

package/lib/model/allocationFeeFixedAllOf.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 AllocationFeeFixedAllOf {
-    /**
-     * The value of the fee in minor monetary units, e.g. cents if US dollars are specified as the transaction currency.
-     */
-    amount: number;
-}

package/lib/model/allocationFeeShareAllOf.d.ts

@@ -1,19 +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 { Decimal } from './decimal';
-export interface AllocationFeeShareAllOf {
-    share: Decimal;
-    /**
-     * The value of the fee in minor monetary units, e.g. cents if US dollars are specified as the transaction currency.
-     */
-    readonly amount?: number;
-}

package/lib/model/allocationFeeTarget.d.ts

@@ -1,23 +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.
- */
-/**
- * Target of the transaction
- */
-export interface AllocationFeeTarget {
-    allocationTargetType: AllocationFeeTarget.AllocationTargetTypeEnum;
-}
-export declare namespace AllocationFeeTarget {
-    type AllocationTargetTypeEnum = 'AllocationTargetShop';
-    const AllocationTargetTypeEnum: {
-        AllocationTargetShop: "AllocationTargetShop";
-    };
-}

package/lib/model/allocationTarget.d.ts

@@ -1,23 +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.
- */
-/**
- * Target of the transaction
- */
-export interface AllocationTarget {
-    allocationTargetType: AllocationTarget.AllocationTargetTypeEnum;
-}
-export declare namespace AllocationTarget {
-    type AllocationTargetTypeEnum = 'AllocationTargetShop';
-    const AllocationTargetTypeEnum: {
-        AllocationTargetShop: "AllocationTargetShop";
-    };
-}

package/lib/model/allocationTargetShop.d.ts

@@ -1,23 +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 { AllocationTarget } from './allocationTarget';
-/**
- * The shop as the target of the transaction
- */
-export interface AllocationTargetShop extends AllocationTarget {
-    /**
-     * Shop ID
-     */
-    shopID: string;
-}
-export declare namespace AllocationTargetShop {
-}

package/lib/model/allocationTargetShopAllOf.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 AllocationTargetShopAllOf {
-    /**
-     * Shop ID
-     */
-    shopID: string;
-}

package/lib/model/allocationTransaction.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.
- */
-import { AllocationTarget } from './allocationTarget';
-import { InvoiceLine } from './invoiceLine';
-/**
- * Cash allocation transaction
- */
-export interface AllocationTransaction {
-    target: AllocationTarget;
-    /**
-     * Transaction body
-     */
-    allocationBodyType: AllocationTransaction.AllocationBodyTypeEnum;
-    /**
-     * Products and services cart
-     */
-    cart?: Array<InvoiceLine>;
-}
-export declare namespace AllocationTransaction {
-    type AllocationBodyTypeEnum = 'AllocationBodyAmount' | 'AllocationBodyTotal';
-    const AllocationBodyTypeEnum: {
-        AllocationBodyAmount: AllocationBodyTypeEnum;
-        AllocationBodyTotal: AllocationBodyTypeEnum;
-    };
-}

package/lib/model/apiExtensionRequest.d.ts

@@ -1,18 +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 ApiExtensionRequest extends UserInteraction {
-    /**
-     * API type to use in subsequent requests
-     */
-    apiType: string;
-}

package/lib/model/apiExtensionRequestAllOf.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 ApiExtensionRequestAllOf {
-    /**
-     * API type to use in subsequent requests
-     */
-    apiType: string;
-}

package/lib/model/applePay.d.ts

@@ -1,24 +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 { TokenizedCardData } from './tokenizedCardData';
-export interface ApplePay extends TokenizedCardData {
-    /**
-     * Apple Pay merchant identifier
-     */
-    merchantID: string;
-    /**
-     * Aggregate of open and encrypted payment data
-     */
-    paymentToken: object;
-}
-export declare namespace ApplePay {
-}

package/lib/model/applePayAllOf.d.ts

@@ -1,24 +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.
- */
-/**
- * Apple Pay data
- */
-export interface ApplePayAllOf {
-    /**
-     * Apple Pay merchant identifier
-     */
-    merchantID: string;
-    /**
-     * Aggregate of open and encrypted payment data
-     */
-    paymentToken: object;
-}

package/lib/model/articlesOfAssociation.d.ts

@@ -1,19 +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 { RepresentativeDocument } from './representativeDocument';
-/**
- * Articles of association
- */
-export interface ArticlesOfAssociation extends RepresentativeDocument {
-}
-export declare namespace ArticlesOfAssociation {
-}