@enfuce/nextgen-sdk 0.0.1

package/dist/esm/wallet/base.d.ts

@@ -0,0 +1,66 @@
+/**
+ * Wallet operations
+ * Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.  #### Terms used <table>   <tr>     <th>Term</th>     <th>Definition</th>   <tr>     <td>Customer</td>     <td>End customer using financial institution\'s mobile application</td>   </tr>   <tr>     <td>In-app activation</td>     <td>Wallet provisioning using financial institution app as authentication method</td>   </tr>   <tr>     <td>In-app provisioning</td>     <td>Mastercard\'s term for push provisioning</td>   </tr>   <tr>     <td>Push provisioning</td>     <td>VISA\'s term for pushing card details from within mobile application. This term will be used in this document</td>   </tr>   <tr>     <td>Wallet provider</td>     <td>Such as Apple Pay, Google Pay or Samsung Pay </td>   </tr> </table>  It\'s called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed.  ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg)  In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view.
+ *
+ * The version of the OpenAPI document: 1
+ * Contact: info@enfuce.com
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import type { Configuration } from './configuration';
+import type { AxiosInstance, RawAxiosRequestConfig } from 'axios';
+export declare const BASE_PATH: string;
+/**
+ *
+ * @export
+ */
+export declare const COLLECTION_FORMATS: {
+    csv: string;
+    ssv: string;
+    tsv: string;
+    pipes: string;
+};
+/**
+ *
+ * @export
+ * @interface RequestArgs
+ */
+export interface RequestArgs {
+    url: string;
+    options: RawAxiosRequestConfig;
+}
+/**
+ *
+ * @export
+ * @class BaseAPI
+ */
+export declare class BaseAPI {
+    protected basePath: string;
+    protected axios: AxiosInstance;
+    protected configuration: Configuration | undefined;
+    constructor(configuration?: Configuration, basePath?: string, axios?: AxiosInstance);
+}
+/**
+ *
+ * @export
+ * @class RequiredError
+ * @extends {Error}
+ */
+export declare class RequiredError extends Error {
+    field: string;
+    constructor(field: string, msg?: string);
+}
+interface ServerMap {
+    [key: string]: {
+        url: string;
+        description: string;
+    }[];
+}
+/**
+ *
+ * @export
+ */
+export declare const operationServerMap: ServerMap;
+export {};

package/dist/esm/wallet/base.js

@@ -0,0 +1,60 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Wallet operations
+ * Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.  #### Terms used <table>   <tr>     <th>Term</th>     <th>Definition</th>   <tr>     <td>Customer</td>     <td>End customer using financial institution\'s mobile application</td>   </tr>   <tr>     <td>In-app activation</td>     <td>Wallet provisioning using financial institution app as authentication method</td>   </tr>   <tr>     <td>In-app provisioning</td>     <td>Mastercard\'s term for push provisioning</td>   </tr>   <tr>     <td>Push provisioning</td>     <td>VISA\'s term for pushing card details from within mobile application. This term will be used in this document</td>   </tr>   <tr>     <td>Wallet provider</td>     <td>Such as Apple Pay, Google Pay or Samsung Pay </td>   </tr> </table>  It\'s called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed.  ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg)  In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view.
+ *
+ * The version of the OpenAPI document: 1
+ * Contact: info@enfuce.com
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import globalAxios from 'axios';
+export const BASE_PATH = "http://localhost".replace(/\/+$/, "");
+/**
+ *
+ * @export
+ */
+export const COLLECTION_FORMATS = {
+    csv: ",",
+    ssv: " ",
+    tsv: "\t",
+    pipes: "|",
+};
+/**
+ *
+ * @export
+ * @class BaseAPI
+ */
+export class BaseAPI {
+    constructor(configuration, basePath = BASE_PATH, axios = globalAxios) {
+        var _a;
+        this.basePath = basePath;
+        this.axios = axios;
+        if (configuration) {
+            this.configuration = configuration;
+            this.basePath = (_a = configuration.basePath) !== null && _a !== void 0 ? _a : basePath;
+        }
+    }
+}
+;
+/**
+ *
+ * @export
+ * @class RequiredError
+ * @extends {Error}
+ */
+export class RequiredError extends Error {
+    constructor(field, msg) {
+        super(msg);
+        this.field = field;
+        this.name = "RequiredError";
+    }
+}
+/**
+ *
+ * @export
+ */
+export const operationServerMap = {};

package/dist/esm/wallet/common.d.ts

@@ -0,0 +1,65 @@
+/**
+ * Wallet operations
+ * Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.  #### Terms used <table>   <tr>     <th>Term</th>     <th>Definition</th>   <tr>     <td>Customer</td>     <td>End customer using financial institution\'s mobile application</td>   </tr>   <tr>     <td>In-app activation</td>     <td>Wallet provisioning using financial institution app as authentication method</td>   </tr>   <tr>     <td>In-app provisioning</td>     <td>Mastercard\'s term for push provisioning</td>   </tr>   <tr>     <td>Push provisioning</td>     <td>VISA\'s term for pushing card details from within mobile application. This term will be used in this document</td>   </tr>   <tr>     <td>Wallet provider</td>     <td>Such as Apple Pay, Google Pay or Samsung Pay </td>   </tr> </table>  It\'s called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed.  ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg)  In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view.
+ *
+ * The version of the OpenAPI document: 1
+ * Contact: info@enfuce.com
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import type { Configuration } from "./configuration";
+import type { RequestArgs } from "./base";
+import type { AxiosInstance, AxiosResponse } from 'axios';
+/**
+ *
+ * @export
+ */
+export declare const DUMMY_BASE_URL = "https://example.com";
+/**
+ *
+ * @throws {RequiredError}
+ * @export
+ */
+export declare const assertParamExists: (functionName: string, paramName: string, paramValue: unknown) => void;
+/**
+ *
+ * @export
+ */
+export declare const setApiKeyToObject: (object: any, keyParamName: string, configuration?: Configuration) => Promise<void>;
+/**
+ *
+ * @export
+ */
+export declare const setBasicAuthToObject: (object: any, configuration?: Configuration) => void;
+/**
+ *
+ * @export
+ */
+export declare const setBearerAuthToObject: (object: any, configuration?: Configuration) => Promise<void>;
+/**
+ *
+ * @export
+ */
+export declare const setOAuthToObject: (object: any, name: string, scopes: string[], configuration?: Configuration) => Promise<void>;
+/**
+ *
+ * @export
+ */
+export declare const setSearchParams: (url: URL, ...objects: any[]) => void;
+/**
+ *
+ * @export
+ */
+export declare const serializeDataIfNeeded: (value: any, requestOptions: any, configuration?: Configuration) => any;
+/**
+ *
+ * @export
+ */
+export declare const toPathString: (url: URL) => string;
+/**
+ *
+ * @export
+ */
+export declare const createRequestFunction: (axiosArgs: RequestArgs, globalAxios: AxiosInstance, BASE_PATH: string, configuration?: Configuration) => <T = unknown, R = AxiosResponse<T>>(axios?: AxiosInstance, basePath?: string) => Promise<R>;

package/dist/esm/wallet/common.js

@@ -0,0 +1,149 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Wallet operations
+ * Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.  #### Terms used <table>   <tr>     <th>Term</th>     <th>Definition</th>   <tr>     <td>Customer</td>     <td>End customer using financial institution\'s mobile application</td>   </tr>   <tr>     <td>In-app activation</td>     <td>Wallet provisioning using financial institution app as authentication method</td>   </tr>   <tr>     <td>In-app provisioning</td>     <td>Mastercard\'s term for push provisioning</td>   </tr>   <tr>     <td>Push provisioning</td>     <td>VISA\'s term for pushing card details from within mobile application. This term will be used in this document</td>   </tr>   <tr>     <td>Wallet provider</td>     <td>Such as Apple Pay, Google Pay or Samsung Pay </td>   </tr> </table>  It\'s called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed.  ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg)  In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view.
+ *
+ * The version of the OpenAPI document: 1
+ * Contact: info@enfuce.com
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
+    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
+    return new (P || (P = Promise))(function (resolve, reject) {
+        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
+        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
+        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
+        step((generator = generator.apply(thisArg, _arguments || [])).next());
+    });
+};
+import { RequiredError } from "./base";
+/**
+ *
+ * @export
+ */
+export const DUMMY_BASE_URL = 'https://example.com';
+/**
+ *
+ * @throws {RequiredError}
+ * @export
+ */
+export const assertParamExists = function (functionName, paramName, paramValue) {
+    if (paramValue === null || paramValue === undefined) {
+        throw new RequiredError(paramName, `Required parameter ${paramName} was null or undefined when calling ${functionName}.`);
+    }
+};
+/**
+ *
+ * @export
+ */
+export const setApiKeyToObject = function (object, keyParamName, configuration) {
+    return __awaiter(this, void 0, void 0, function* () {
+        if (configuration && configuration.apiKey) {
+            const localVarApiKeyValue = typeof configuration.apiKey === 'function'
+                ? yield configuration.apiKey(keyParamName)
+                : yield configuration.apiKey;
+            object[keyParamName] = localVarApiKeyValue;
+        }
+    });
+};
+/**
+ *
+ * @export
+ */
+export const setBasicAuthToObject = function (object, configuration) {
+    if (configuration && (configuration.username || configuration.password)) {
+        object["auth"] = { username: configuration.username, password: configuration.password };
+    }
+};
+/**
+ *
+ * @export
+ */
+export const setBearerAuthToObject = function (object, configuration) {
+    return __awaiter(this, void 0, void 0, function* () {
+        if (configuration && configuration.accessToken) {
+            const accessToken = typeof configuration.accessToken === 'function'
+                ? yield configuration.accessToken()
+                : yield configuration.accessToken;
+            object["Authorization"] = "Bearer " + accessToken;
+        }
+    });
+};
+/**
+ *
+ * @export
+ */
+export const setOAuthToObject = function (object, name, scopes, configuration) {
+    return __awaiter(this, void 0, void 0, function* () {
+        if (configuration && configuration.accessToken) {
+            const localVarAccessTokenValue = typeof configuration.accessToken === 'function'
+                ? yield configuration.accessToken(name, scopes)
+                : yield configuration.accessToken;
+            object["Authorization"] = "Bearer " + localVarAccessTokenValue;
+        }
+    });
+};
+function setFlattenedQueryParams(urlSearchParams, parameter, key = "") {
+    if (parameter == null)
+        return;
+    if (typeof parameter === "object") {
+        if (Array.isArray(parameter)) {
+            parameter.forEach(item => setFlattenedQueryParams(urlSearchParams, item, key));
+        }
+        else {
+            Object.keys(parameter).forEach(currentKey => setFlattenedQueryParams(urlSearchParams, parameter[currentKey], `${key}${key !== '' ? '.' : ''}${currentKey}`));
+        }
+    }
+    else {
+        if (urlSearchParams.has(key)) {
+            urlSearchParams.append(key, parameter);
+        }
+        else {
+            urlSearchParams.set(key, parameter);
+        }
+    }
+}
+/**
+ *
+ * @export
+ */
+export const setSearchParams = function (url, ...objects) {
+    const searchParams = new URLSearchParams(url.search);
+    setFlattenedQueryParams(searchParams, objects);
+    url.search = searchParams.toString();
+};
+/**
+ *
+ * @export
+ */
+export const serializeDataIfNeeded = function (value, requestOptions, configuration) {
+    const nonString = typeof value !== 'string';
+    const needsSerialization = nonString && configuration && configuration.isJsonMime
+        ? configuration.isJsonMime(requestOptions.headers['Content-Type'])
+        : nonString;
+    return needsSerialization
+        ? JSON.stringify(value !== undefined ? value : {})
+        : (value || "");
+};
+/**
+ *
+ * @export
+ */
+export const toPathString = function (url) {
+    return url.pathname + url.search + url.hash;
+};
+/**
+ *
+ * @export
+ */
+export const createRequestFunction = function (axiosArgs, globalAxios, BASE_PATH, configuration) {
+    return (axios = globalAxios, basePath = BASE_PATH) => {
+        var _a;
+        const axiosRequestArgs = Object.assign(Object.assign({}, axiosArgs.options), { url: (axios.defaults.baseURL ? '' : (_a = configuration === null || configuration === void 0 ? void 0 : configuration.basePath) !== null && _a !== void 0 ? _a : basePath) + axiosArgs.url });
+        return axios.request(axiosRequestArgs);
+    };
+};

package/dist/esm/wallet/configuration.d.ts

@@ -0,0 +1,91 @@
+/**
+ * Wallet operations
+ * Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.  #### Terms used <table>   <tr>     <th>Term</th>     <th>Definition</th>   <tr>     <td>Customer</td>     <td>End customer using financial institution\'s mobile application</td>   </tr>   <tr>     <td>In-app activation</td>     <td>Wallet provisioning using financial institution app as authentication method</td>   </tr>   <tr>     <td>In-app provisioning</td>     <td>Mastercard\'s term for push provisioning</td>   </tr>   <tr>     <td>Push provisioning</td>     <td>VISA\'s term for pushing card details from within mobile application. This term will be used in this document</td>   </tr>   <tr>     <td>Wallet provider</td>     <td>Such as Apple Pay, Google Pay or Samsung Pay </td>   </tr> </table>  It\'s called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed.  ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg)  In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view.
+ *
+ * The version of the OpenAPI document: 1
+ * Contact: info@enfuce.com
+ *
+ * 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 ConfigurationParameters {
+    apiKey?: string | Promise<string> | ((name: string) => string) | ((name: string) => Promise<string>);
+    username?: string;
+    password?: string;
+    accessToken?: string | Promise<string> | ((name?: string, scopes?: string[]) => string) | ((name?: string, scopes?: string[]) => Promise<string>);
+    basePath?: string;
+    serverIndex?: number;
+    baseOptions?: any;
+    formDataCtor?: new () => any;
+}
+export declare class Configuration {
+    /**
+     * parameter for apiKey security
+     * @param name security name
+     * @memberof Configuration
+     */
+    apiKey?: string | Promise<string> | ((name: string) => string) | ((name: string) => Promise<string>);
+    /**
+     * parameter for basic security
+     *
+     * @type {string}
+     * @memberof Configuration
+     */
+    username?: string;
+    /**
+     * parameter for basic security
+     *
+     * @type {string}
+     * @memberof Configuration
+     */
+    password?: string;
+    /**
+     * parameter for oauth2 security
+     * @param name security name
+     * @param scopes oauth2 scope
+     * @memberof Configuration
+     */
+    accessToken?: string | Promise<string> | ((name?: string, scopes?: string[]) => string) | ((name?: string, scopes?: string[]) => Promise<string>);
+    /**
+     * override base path
+     *
+     * @type {string}
+     * @memberof Configuration
+     */
+    basePath?: string;
+    /**
+     * override server index
+     *
+     * @type {number}
+     * @memberof Configuration
+     */
+    serverIndex?: number;
+    /**
+     * base options for axios calls
+     *
+     * @type {any}
+     * @memberof Configuration
+     */
+    baseOptions?: any;
+    /**
+     * The FormData constructor that will be used to create multipart form data
+     * requests. You can inject this here so that execution environments that
+     * do not support the FormData class can still run the generated client.
+     *
+     * @type {new () => FormData}
+     */
+    formDataCtor?: new () => any;
+    constructor(param?: ConfigurationParameters);
+    /**
+     * Check if the given MIME is a JSON MIME.
+     * JSON MIME examples:
+     *   application/json
+     *   application/json; charset=UTF8
+     *   APPLICATION/JSON
+     *   application/vnd.company+json
+     * @param mime - MIME (Multipurpose Internet Mail Extensions)
+     * @return True if the given MIME is JSON, false otherwise.
+     */
+    isJsonMime(mime: string): boolean;
+}

package/dist/esm/wallet/configuration.js

@@ -0,0 +1,40 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Wallet operations
+ * Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.  #### Terms used <table>   <tr>     <th>Term</th>     <th>Definition</th>   <tr>     <td>Customer</td>     <td>End customer using financial institution\'s mobile application</td>   </tr>   <tr>     <td>In-app activation</td>     <td>Wallet provisioning using financial institution app as authentication method</td>   </tr>   <tr>     <td>In-app provisioning</td>     <td>Mastercard\'s term for push provisioning</td>   </tr>   <tr>     <td>Push provisioning</td>     <td>VISA\'s term for pushing card details from within mobile application. This term will be used in this document</td>   </tr>   <tr>     <td>Wallet provider</td>     <td>Such as Apple Pay, Google Pay or Samsung Pay </td>   </tr> </table>  It\'s called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed.  ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg)  In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view.
+ *
+ * The version of the OpenAPI document: 1
+ * Contact: info@enfuce.com
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export class Configuration {
+    constructor(param = {}) {
+        var _a;
+        this.apiKey = param.apiKey;
+        this.username = param.username;
+        this.password = param.password;
+        this.accessToken = param.accessToken;
+        this.basePath = param.basePath;
+        this.serverIndex = param.serverIndex;
+        this.baseOptions = Object.assign(Object.assign({}, param.baseOptions), { headers: Object.assign({}, (_a = param.baseOptions) === null || _a === void 0 ? void 0 : _a.headers) });
+        this.formDataCtor = param.formDataCtor;
+    }
+    /**
+     * Check if the given MIME is a JSON MIME.
+     * JSON MIME examples:
+     *   application/json
+     *   application/json; charset=UTF8
+     *   APPLICATION/JSON
+     *   application/vnd.company+json
+     * @param mime - MIME (Multipurpose Internet Mail Extensions)
+     * @return True if the given MIME is JSON, false otherwise.
+     */
+    isJsonMime(mime) {
+        const jsonMime = new RegExp('^(application\/json|[^;/ \t]+\/[^;/ \t]+[+]json)[ \t]*(;.*)?$', 'i');
+        return mime !== null && (jsonMime.test(mime) || mime.toLowerCase() === 'application/json-patch+json');
+    }
+}

package/dist/esm/wallet/index.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Wallet operations
+ * Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.  #### Terms used <table>   <tr>     <th>Term</th>     <th>Definition</th>   <tr>     <td>Customer</td>     <td>End customer using financial institution\'s mobile application</td>   </tr>   <tr>     <td>In-app activation</td>     <td>Wallet provisioning using financial institution app as authentication method</td>   </tr>   <tr>     <td>In-app provisioning</td>     <td>Mastercard\'s term for push provisioning</td>   </tr>   <tr>     <td>Push provisioning</td>     <td>VISA\'s term for pushing card details from within mobile application. This term will be used in this document</td>   </tr>   <tr>     <td>Wallet provider</td>     <td>Such as Apple Pay, Google Pay or Samsung Pay </td>   </tr> </table>  It\'s called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed.  ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg)  In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view.
+ *
+ * The version of the OpenAPI document: 1
+ * Contact: info@enfuce.com
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export * from "./api";
+export * from "./configuration";

package/dist/esm/wallet/index.js

@@ -0,0 +1,15 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Wallet operations
+ * Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.  #### Terms used <table>   <tr>     <th>Term</th>     <th>Definition</th>   <tr>     <td>Customer</td>     <td>End customer using financial institution\'s mobile application</td>   </tr>   <tr>     <td>In-app activation</td>     <td>Wallet provisioning using financial institution app as authentication method</td>   </tr>   <tr>     <td>In-app provisioning</td>     <td>Mastercard\'s term for push provisioning</td>   </tr>   <tr>     <td>Push provisioning</td>     <td>VISA\'s term for pushing card details from within mobile application. This term will be used in this document</td>   </tr>   <tr>     <td>Wallet provider</td>     <td>Such as Apple Pay, Google Pay or Samsung Pay </td>   </tr> </table>  It\'s called in two cases: - *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used. - *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed.  ![ Provisioning example ](https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/wallet_push_prov.svg)  In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view.
+ *
+ * The version of the OpenAPI document: 1
+ * Contact: info@enfuce.com
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export * from "./api";
+export * from "./configuration";

package/dist/index.d.ts

@@ -0,0 +1,12 @@
+export * as oauth from './oauth';
+export * as card from './card';
+export * as wallet from './wallet';
+export * as cardholder from './cardholder';
+export * as pin from './pin';
+export * as issuerEvents from './issuer-events';
+export * as authorisationControl from './authorisation-control';
+export * as cards from './cards';
+export * as threeds from './threeds';
+export * as threedsOob from './threeds-oob';
+export * as clearingFileCopy from './clearing-file-copy';
+export * as transactionEvent from './transaction-event';

package/dist/index.js

@@ -0,0 +1,17 @@
+"use strict";
+/* AUTO-GENERATED by scripts/generate.sh - do not edit. */
+/* One namespaced export per API. Usage: import { card } from '@enfuce/nextgen-sdk'; */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.transactionEvent = exports.clearingFileCopy = exports.threedsOob = exports.threeds = exports.cards = exports.authorisationControl = exports.issuerEvents = exports.pin = exports.cardholder = exports.wallet = exports.card = exports.oauth = void 0;
+exports.oauth = require("./oauth");
+exports.card = require("./card");
+exports.wallet = require("./wallet");
+exports.cardholder = require("./cardholder");
+exports.pin = require("./pin");
+exports.issuerEvents = require("./issuer-events");
+exports.authorisationControl = require("./authorisation-control");
+exports.cards = require("./cards");
+exports.threeds = require("./threeds");
+exports.threedsOob = require("./threeds-oob");
+exports.clearingFileCopy = require("./clearing-file-copy");
+exports.transactionEvent = require("./transaction-event");