@ekyc_qoobiss/qbs-ect-cmp 1.6.5 → 1.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -17,10 +17,33 @@ The wev compoment has to be included in the html markup like this:
17
17
  \*.html
18
18
 
19
19
  ```sh
20
- <identification-component token="{{ token }}" order_id="{{ orderId }}"></identification-component>
20
+ <identification-component token="{{ token }}" order_id="{{ orderId }}" api_url="{{ apiUrl }}"></identification-component>
21
21
  ```
22
22
 
23
- There are two parameters:
23
+ ### There are two parameters:
24
24
 
25
25
  - token - which is the token that was obtained using the API Key on the server side;
26
- - order_id - is a unique ID that will be used for the current identification request when obtaining the processed data from the REST API Service.
26
+ - order_id - is a unique ID that will be used for the current identification request when obtaining the processed data from the REST API Service;
27
+ - api_url - is the base api url that we have provided for you.
28
+
29
+ ### Obtaining the token
30
+
31
+ To get the token you have to make a server-side GET request to this url: [apiUrl]/token
32
+ The authentication is done using the API Key that you received from us.
33
+
34
+ ### The component will raise these events:
35
+
36
+ - 'ect-started' - when the component was loaded and initialted
37
+ - 'ect-error' - when a critical error has ocurred and the flow cannot continue
38
+ - 'ect-session-expired' - when the token has expired
39
+ - 'ect-completed' - when the flow has ended.
40
+
41
+ ### Obtaining the result
42
+
43
+ To get the result of the collection process, you have to make a GET call to the endpoint [apiUrl]/validation/identity/result?orderId=[orderId]. The result will be a json with the details we have processesd. The result is encrypted using AES with a symmetrical key that you will be provided with. To be able to call the endpoint you have to use either a valid token or the API Key.
44
+ If the request is not yet processes, the response will be a json of this type:
45
+ {
46
+ "OrderID": "the id",
47
+ "Status": "[Incomplete|NotStarted|Running]"
48
+ }
49
+ When the processing has finished the response will return the encrypted data.
@@ -5263,7 +5263,7 @@ const IdBackCapture = class {
5263
5263
  }
5264
5264
  async componentWillLoad() {
5265
5265
  Events.init(this.component);
5266
- this.titleMesage = IdCaptureValues.Title;
5266
+ this.titleMesage = IdCaptureValues.TitleBack;
5267
5267
  if (!navigator.mediaDevices) {
5268
5268
  Events.flowError('This browser does not support webRTC');
5269
5269
  }
@@ -40,7 +40,7 @@ export class IdBackCapture {
40
40
  }
41
41
  async componentWillLoad() {
42
42
  Events.init(this.component);
43
- this.titleMesage = IdCaptureValues.Title;
43
+ this.titleMesage = IdCaptureValues.TitleBack;
44
44
  if (!navigator.mediaDevices) {
45
45
  Events.flowError('This browser does not support webRTC');
46
46
  }
@@ -5259,7 +5259,7 @@ const IdBackCapture = class {
5259
5259
  }
5260
5260
  async componentWillLoad() {
5261
5261
  Events.init(this.component);
5262
- this.titleMesage = IdCaptureValues.Title;
5262
+ this.titleMesage = IdCaptureValues.TitleBack;
5263
5263
  if (!navigator.mediaDevices) {
5264
5264
  Events.flowError('This browser does not support webRTC');
5265
5265
  }