cordova-digital-onboarding 1.0.0 → 1.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,62 @@
+# Wultra Digital Onboarding for mobile JS Platforms
+
+<!-- begin remove -->
+<p align="center"><img src="docs/images/intro.jpg" alt="Wultra Digital Onboarding for mobile JS Platforms" width="100%" /></p>
+<!-- end -->
+
+<!-- begin box info -->
+The Wultra Digital Onboarding SDK functions as an extension of [Wultra Mobile Authentication (PowerAuth)](https://wultra.com/powerauth) that is required.
+<!-- end -->
+
+## Introduction
+
+Elevate your standard device activation, user login, and request signing scenarios by incorporating facial recognition and document scanning in diverse situations:
+
+- Reclaim access or recover lost credentials through authenticating the user's genuine presence and verifying document validity.
+- Reinforce conventional password or PIN-based authentication with an extra layer of security through face recognition.
+- Seamlessly onboard new customers into your systems, authenticating them with identification cards and facial scans for access to your app.
+
+### Other resources
+
+We also provide an [Android](https://github.com/wultra/digital-onboarding-android) and [iOS](https://github.com/wultra/digital-onboarding-apple) versions of this library.
+
+## What will you need before the implementation
+
+<!-- begin box info -->
+The Wultra Digital Onboarding SDK functions as an extension of Wultra Mobile Authentication that is required.
+<!-- end -->
+
+Before initiating the integration, it's essential to ensure that your server environment is prepared with appropriately configured services capable of managing user verification and onboarding, seamlessly connecting to your systems.
+
+Given the unique characteristics of each customer system, the utilization of this SDK may vary. To accurately outline the user verification process, we recommend consulting with our technical team for tailored guidance.
+
+## Document OCR and face verification
+
+We seamlessly incorporate industry-leading solutions for document scanning, ensuring versatility and effectiveness in your operations.
+
+- iProov for genuine presence
+- Innovatrics for document scanning and genuine presence
+- ZenID for document scanning
+- BlinkID for document scanning
+
+Our dedicated technical and sales representatives are available to guide you in selecting the optimal solution that aligns perfectly with your needs.
+
+## Documentation
+
+<!-- begin box warning -->
+Please be aware that the scenarios outlined in the documentation are illustrative examples. Your user flow and implementation may vary based on your specific requirements and circumstances.
+<!-- end -->
+
+The documentation is available at the [Wultra Developer Portal](https://developers.wultra.com/components/digital-onboarding-js) or inside the [docs folder](docs).
+
+## License
+
+All sources are licensed using the Apache 2.0 license.
+
+## Contact
+
+If you need any assistance, do not hesitate to drop us a line at [hello@wultra.com](mailto:hello@wultra.com) or our official [wultra.com/discord](https://wultra.com/discord) channel.
+
+### Security Disclosure
+
+If you believe you have identified a security vulnerability with Wultra Digital Onboarding, you should report it as soon as possible via email to [support@wultra.com](mailto:support@wultra.com). Please do not post it to a public issue tracker.

package/docs/Changelog.md

@@ -0,0 +1,24 @@
+# Changelog
+
+## 1.1.0 (Dec, 2025)
+
+- PowerAuth Cordova SDK dependency now requires v. `4.2.0`.
+- Process cache is now persistent across app restarts.
+- Changes to `WDOError`:
+    - added `reason: WDOErrorReason` property to specify the error cause.
+    - added `allowOnboardingOtpRetry: boolean` property to indicate if OTP retry is allowed (during activation failure).
+    - modified `onboardingOtpRemainingAttempts` to parse the remaining attempts from the original exception (during activation failure).
+- `WDOActivaitonService` changes:
+   - `hasActiveProcess()` now returns Promise<boolean> instead of boolean. 
+   - `clear()` is now asynchronous and returns Promise<void>.
+- `WDOActivaitonService` changes:
+   - removed `consent` state
+   - replaced `consentApprove` with `start` method with a `consent` argument.
+   - `consentGet` now returns Promise<string> instead of the verification state.
+   - `documentsInitSDK` method now returns strongly typed response.
+   - `presenceCheckInit` method now returns strongly typed response.
+   - `intro` state now contains `consentRequired: boolean` property in the corresponding union type.
+
+## 1.0.0 (Nov, 2025)
+
+Initial release.

package/docs/Device-Activation.md

@@ -0,0 +1,194 @@
+# Device Activation
+
+With `WDOActivationService` you can onboard PowerAuth with just a piece of user information like his email, phone number, or login name.
+
+PowerAuth enrolled in such a way will need [further user verification](Verifying-User.md) until fully operational (able to sign operations).
+
+## Example app flow
+
+<p align="center"><img src="images/activation-mockup.png" alt="Example application flow for the activation" width="100%" /></p>
+
+## Creating an instance
+
+To create an instance you will need a `PowerAuth` instance that is __ready to be activated__.
+
+<!-- begin box info -->
+[Documentation for `PowerAuth Mobile JS SDK`](https://developers.wultra.com/components/react-native-powerauth-mobile-sdk/). 
+<!-- end -->
+
+
+Example with `PowerAuth` instance:
+
+```typescript
+const powerAuth = new PowerAuth("my-pa-instance")
+powerAuth.configure({
+    configuration: "ARCB+...jg==", // base64 PowerAuth configuration
+    baseEndpointUrl: "https://my-server-deployment.com/enrollment-server/"
+})
+const activationService = new WDOActivationService(
+    powerAuth,
+    "https://my-server-deployment.com/enrollment-server-onboarding/"
+)
+```
+
+## Retrieving the status
+
+To figure out if the activation process was already started and what is the status, you can use `hasActiveProcess`.
+
+```typescript
+/**
+ * If the activation process is in progress.
+ *
+ * Note that even if this property is `true` it can be already discontinued on the server.
+ * Calling `status()` for example after the app is launched in this case is recommended.
+ */
+get hasActiveProcess(): boolean;
+```
+
+If the process was started, you can verify its status by calling the `status` function. You can show an appropriate UI to the user based on this status.
+
+```typescript
+/**
+ * Retrieves status of the onboarding activation.
+ *
+ * @return Promise resolved with onboarding status.
+ */
+status(): Promise<WDOOnboardingStatus>;
+```
+
+`WDOOnboardingStatus` possible values.
+
+```typescript
+declare enum WDOOnboardingStatus {
+    /** Activation part of the process is in progress */
+    activationInProgress = "ACTIVATION_IN_PROGRESS",
+    /** Verification part of the process is in progress */
+    verificationInProgress = "VERIFICATION_IN_PROGRESS",
+    /** Onboarding process has failed */
+    failed = "FAILED",
+    /** Onboarding process is completed */
+    finished = "FINISHED"
+}
+```
+
+## Starting the process
+
+To start the activation process, you can use any credentials that are sufficient to you that can identify the user.
+
+Often, such data are user email, phone number, or userID. The definition of such data is up to your server implementation and requirements.
+
+To start the activation, use the `start` function.
+
+```typescript
+/**
+     * Start onboarding activation with user credentials.
+     *
+     * For example, when you require email, your object would look like this:
+     * ```
+     * {
+     *   email: "<user_email>"
+     * }
+     * ```
+     * @param credentials Object with credentials. Which credentials are needed should be provided by a system/backend provider.
+     * @param processType The process type identification. If not specified, the default process type will be used.
+     */
+    start(credentials: any, processType?: string): Promise<void>;
+```
+
+### Example
+
+```typescript
+
+class MyUserService {
+    // prepared service
+    private activationService: WDOActivationService
+    
+    async startActivation(id: string) {
+        const data = { userId: id}
+        try {
+            await this.activationService.start(data)
+            // success, continue with `activate()`
+            // at this moment, the `hasActiveProcess` starts return true
+        } catch (error) {
+            // show error to the user
+        }
+    }
+}
+```
+
+## Creating the activation
+
+To activate the user (activating the `PowerAuth` instance), data retrieved from the process start can be used with optional `OTP`. The OTP is usually sent via SMS, email, or other channel. To decide if the OTP is needed, you can use the [Configuration API](Process-Configuration.md) or have it hardcoded.
+
+Use the `activate` function to create the activation.
+
+```typescript
+/**
+ * Activate the PowerAuth instance that was passed in the initializer.
+ *
+ * @param activationName Name of the activation. Usually something like John's iPhone or similar.
+ * @param otp OTP code received by the user (via SMS or email). Optional when not required.
+ * @return Promise resolved with activation result.
+ */
+activate(activationName: string, otp?: string): Promise<WDOPowerAuthActivationResult>;
+```
+
+Example implementation:
+
+```typescript
+class MyUserService {
+    // prepared service
+    private activationService: WDOActivationService
+    
+    async activate(smsOTP?: string) {
+        try {
+            const activationResult = await activationService.activate("my-test-activation", smsOTP)
+            // PowerAuthSDK instance was activated.
+            // At this moment, navigate the user to
+            // the PIN keyboard to finish the PowerAuthSDK initialization.
+            // For more information, follow the PowerAuthSDK documentation.
+        } catch (error) {
+            if (error instanceof WDOError && error.allowOnboardingOtpRetry) {
+                // User entered the wrong OTP, prompt for a new one.
+                // Remaining OTP attempts count: error.onboardingOtpRemainingAttempts
+            } else {
+                // show error UI
+            }
+        }
+    }
+}
+```
+
+## Canceling the process
+
+To cancel the process, just call the `cancel` function.
+
+```typescript
+/**
+ * Cancel the activation process (issues a cancel request to the backend and clears the local process ID).
+ *
+ * @param forceCancel When true, the process will be canceled in the SDK even when fails on backend. `true` by default.
+ */
+cancel(forceCancel?: boolean): Promise<void>;
+```
+
+## OTP resend
+
+In some cases, you need to resent the OTP:  
+ - OTP was not received by the user (for example when the email ends in the spam folder).  
+ - OTP expired. 
+
+ For such cases, use `resendOTP` function.
+ 
+ ```typescript
+/**
+* OTP resend request.
+*
+* This is intended to be displayed for the user to use in case of the OTP is not received.
+* For example, when the user does not receive SMS after some time, there should be a button to "send again".
+*/
+resendOTP(): Promise<void>;
+ ```
+
+## Read next
+- [Verifying User With Document Scan And Genuine Presence Check](Verifying-User.md)

package/docs/Language-Configuration.md

@@ -0,0 +1,13 @@
+# Language Configuration
+
+The language of content that might be localized can be configured via `changeAcceptLanguage` method on both `WDOActivationService` and `WDOVerificationService`.
+
+The default language is `en`. Availability of languages depends on server configuration and implementation.
+
+<!-- begin box info -->
+The language configuration is a wrap-around of the underlying networking language configuration described in [our networking library documentation](https://github.com/wultra/networking-js).
+<!-- end -->
+
+## Read next
+
+- [Logging](Logging.md)

package/docs/Logging.md

@@ -0,0 +1,22 @@
+# Logging
+
+You can set up logging for the library using the `WDOLogger` class.
+
+<!-- begin box info -->
+Networking traffic is logged in its own logger described in the [networking library documentation](https://github.com/wultra/networking-js).
+<!-- end -->
+
+### Verbosity Level
+
+You can limit the amount of logged information via the `verboseLevel` property.
+
+| Level                  | Description                                       |
+| ---------------------- | ------------------------------------------------- |
+| `NONE`                 | Silences all messages.                            |
+| `ERROR`  _(default)_   | Only errors will be logged.                       |
+| `WARNING`              | Errors and warnings will be logged.               |
+| `INFO`                 | Error, warning and info messages will be logged.  |
+| `DEBUG`                | All messages will be logged.                      |
+### Logger Delegate
+
+In case you want to process logs on your own (for example log into a file or some cloud service), you can set `WDOLogger.listener`.

package/docs/Process-Configuration.md

@@ -0,0 +1,59 @@
+# Process Configuration
+
+With `WDOConfigurationService` you can retrieve the configuration of the onboarding process from the server. The configuration contains information about which steps are required to be performed during the onboarding process and which document types are supported or required for scanning.
+
+## Retrieving the configuration
+
+To retrieve the configuration, create an instance of `WDOConfigurationService` and call the `getConfiguration` method with the process type identifier.
+
+Example:
+
+```typescript
+
+const powerAuth = new PowerAuth("my-pa-instance")
+powerAuth.configure({
+    configuration: "ARCB+...jg==", // base64 PowerAuth configuration
+    baseEndpointUrl: "https://my-server-deployment.com/enrollment-server/"
+})
+const configurationService = new WDOConfigurationService(
+    powerAuth,
+    "https://my-server-deployment.com/enrollment-server-onboarding/"
+)
+
+const procesType = "onboarding" // defined on your server
+const config = await configurationService.getConfiguration(procesType)
+console.log("Configuration:", config)
+```
+
+## Configuration response
+
+```typescript
+/** Configuration for the onboarding process */
+interface WDOConfigurationResponse {
+    /** Is the onboarding process enabled */
+    enabled: boolean;
+    /** Is OTP required for the first part - identification/activation. */
+    otpForIdentification: boolean;
+    /** Is OTP required for the second part - identity verification. */
+    otpForIdentityVerification: boolean;
+    /** Documents required for identity verification. */
+    documents: {
+        /** Number of required documents */
+        requiredDocumentsCount: number;
+        /** List of documents */
+        items: Array<WDOConfigurationDocument>;
+    }
+}
+/** Configuration for a document */
+interface WDOConfigurationDocument {
+    /** Type of the document */
+    type: string;
+    /** Is the document mandatory */
+    mandatory: boolean;
+    /** Number of sides the document has */
+    sideCount: number;
+}
+```
+
+## Read next
+- [Device Activation](Device-Activation.md)

package/docs/Readme.md

@@ -0,0 +1,61 @@
+# Wultra Digital Onboarding for JS Mobile Platforms
+
+<!-- begin remove -->
+<p align="center"><img src="images/intro.jpg" alt="Wultra Digital Onboarding for JS Mobile Platforms" width="100%" /></p>
+<!-- end -->
+
+Elevate your standard device activation, user login, and request signing scenarios by incorporating facial recognition and document scanning in diverse situations:
+
+- Reclaim access or recover lost credentials through authenticating the user's genuine presence and verifying document validity.
+- Reinforce conventional password or PIN-based authentication with an extra layer of security through face recognition.
+- Seamlessly onboard new customers into your systems, authenticating them with identification cards and facial scans for access to your app.
+
+### Supported Platforms
+
+- Cordova
+- (TBA) React Native
+
+### Other resources
+
+We also provide an [Android](https://github.com/wultra/digital-onboarding-android) and [iOS](https://github.com/wultra/digital-onboarding-apple) version of the Wultra Digital Onboarding SDK.
+
+## What will you need before the implementation
+
+<!-- begin box info -->
+The Wultra Digital Onboarding SDK functions as an extension of [Wultra Mobile Authentication (PowerAuth)](https://github.com/wultra/react-native-powerauth-mobile-sdk) that is required.
+<!-- end -->
+
+Before initiating the integration, it's essential to ensure that your server environment is prepared with appropriately configured services capable of managing user verification and onboarding, seamlessly connecting to your systems.
+
+Given the unique characteristics of each customer system, the utilization of this SDK may vary. To accurately outline the user verification process, we recommend consulting with our technical team for tailored guidance.
+
+## Document OCR and face verification
+
+We seamlessly incorporate industry-leading solutions for document scanning, ensuring versatility and effectiveness in your operations.
+
+- iProov for genuine presence
+- BlinkID for document scanning
+- Innovatrics for document scanning and genuine presence
+- ZenID for document scanning
+
+Our dedicated technical and sales representatives are available to guide you in selecting the optimal solution that aligns perfectly with your needs.
+
+## Open Source Code
+
+The code of the library is open source and you can freely browse it in our GitHub at [https://github.com/wultra/digital-onboarding-js](https://github.com/wultra/digital-onboarding-js/tree/develop/)
+
+<!-- begin remove -->
+## Integration Tutorials
+- [SDK Integration](SDK-Integration.md)
+- [Process Configuration](Process-Configuration.md)
+- [Device Activation (With Weak Credentials)](Device-Activation.md)
+- [Verifying User With Document Scan And Genuine Presence Check](Verifying-User.md)
+- [Language Configuration](Language-Configuration.md)
+- [Logging](Logging.md)
+- [Changelog](Changelog.md)
+
+<!-- end -->
+
+## Read next
+
+- [SDK Integration](SDK-Integration.md)

package/docs/SDK-Integration.md

@@ -0,0 +1,20 @@
+# SDK Integration
+
+## Cordova Installation
+
+### Requirements
+
+- Cordova >=12.0.0
+- [PowerAuth Mobile JS SDK](https://github.com/wultra/react-native-powerauth-mobile-sdk) needs to be available in your project
+
+### Add via cordova CLI
+
+Add `cordova-digital-onboarding` package to your Cordova project using the following command:
+
+```bash
+cordova plugin add cordova-digital-onboarding
+```
+
+## Read next
+
+- [Process Configuration](Process-Configuration.md)