skyflow-js 1.4.0 → 1.8.0

package/CHANGELOG.md

@@ -2,6 +2,49 @@
 
 All notable changes to this project will be documented in this file.
 
+## [1.8.0] - 2021-12-07
+
+### Added
+- `setError(error: string)` method to set custom UI error to be displayed on the collect and reveal Elements
+- `resetError()` method is used to clear the custom UI error message set through setError 
+- `format` parameter in `collectElementOptions` to support different type of date formats for `EXPIRATION_DATE` element
+- `setValue(value: string)` and `clearValue()` method in DEV env, to set/clear the value of a collect element.
+- `setToken(value: string)` method to set the token for a reveal element.
+- `setAltText(value: string)` and `clearAltText()` method to set/clear the altText for a reveal 
+### Changed
+
+- Changed error messages in the logs and callback errors.
+- `altText` support has been deprecated for collect element
+- `vaultID` and `vaultURL` are now optional parameters in Configuration constructor
+
+### Fixed
+- Updating UI error messages
+
+## [1.7.0] - 2021-11-24
+### Added
+- `validations` option in `CollectElementInput` that takes an array of validation rules
+- `REGEX_MATCH_RULE`, `LENGTH_MATCH_RULE` & `ELEMENT_MATCH_RULE` Validation rules types
+- `PIN` Element type
+
+### Fixed
+- Card Number validation
+
+
+## [1.6.0] - 2021-11-16
+
+### Added
+- `enableCardIcon` option to configure Card Icon visibility
+- `INPUT_FIELD` Element type for custom UI elements
+- `unmount` method to reset collect element to initial state
+
+### Changed
+- New VISA Card Icon with updated Logo
+
+## [1.5.0] - 2021-11-10
+
+### Changed
+- Renamed invokeGateway to invokeConnection
+- Renamed gatewayURL to connectionURL
 ## [1.4.0] - 2021-10-26
 
 ### Added

package/README.md

@@ -8,7 +8,7 @@ Skyflow’s Javascript SDK can be used to securely collect, tokenize, and reveal
 - [**Initializing Skyflow.js**](#Initializing-Skyflowjs)
 - [**Securely collecting data client-side**](#Securely-collecting-data-client-side)
 - [**Securely revealing data client-side**](#Securely-revealing-data-client-side)
-- [**Securely invoking gateway client-side**](#Securely-invoking-gateway-client-side)
+- [**Securely invoking Connections client-side**](#Securely-invoking-Connections-client-side)
 
 ---
 
@@ -125,13 +125,16 @@ For `env` parameter, there are 2 accepted values in Skyflow.Env
 # Securely collecting data client-side
 -  [**Inserting data into the vault**](#inserting-data-into-the-vault)
 -  [**Using Skyflow Elements to collect data**](#using-skyflow-elements-to-collect-data)
+-  [**Using validations on Collect Elements**](#validations)
 -  [**Event Listener on Collect Elements**](#event-listener-on-collect-elements)
+-  [**UI Error for Collect Eements**](#ui-error-for-collect-elements)
+- [**Set and Clear value for Collect Elements (DEV ENV ONLY)**](#set-and-clear-value-for-collect-elements-dev-env-only)
 ## Inserting data into the vault
 
 To insert data into the vault from the browser, use the `insert(records, options?)` method of the Skyflow client. The `records` parameter takes a JSON object of the records to be inserted in the below format. The `options` parameter takes a dictionary of optional parameters for the insertion. See below: 
 
 ```javascript
-var records = {
+const records = {
   "records": [
   	{
       table: "string", //table into which record should be inserted
@@ -144,7 +147,7 @@ var records = {
   ]
 }
 
-var options = {
+const options = {
   tokens: true  //indicates whether or not tokens should be returned for the inserted data. Defaults to 'true'  
 }
 
@@ -199,7 +202,7 @@ const container = skyflowClient.container(Skyflow.ContainerType.COLLECT)
 A Skyflow collect Element is defined as shown below: 
 
 ```javascript
-var collectElement =  {
+const collectElement =  {
    table: "string",             //optional, the table this data belongs to
    column: "string",            //optional, the column into which this data should be inserted
    type: Skyflow.ElementType,   //Skyflow.ElementType enum
@@ -208,12 +211,15 @@ var collectElement =  {
    errorTextStyles:{},          //optional styles that will be applied to the errorText of the collect element
    label: "string",             //optional label for the form element
    placeholder: "string",       //optional placeholder for the form element
-   altText: "string"            //optional string that acts as an initial value for the collect element
+   altText: "string"            //(DEPRECATED) string that acts as an initial value for the collect element
+   validations:[]               // optional array of validation rules
 }
 ```
-The `table` and `column` fields indicate which table and column in the vault the Element corresponds to. **Note**: 
+The `table` and `column` fields indicate which table and column in the vault the Element corresponds to. 
+
+**Note**: 
 -  Use dot delimited strings to specify columns nested inside JSON fields (e.g. `address.street.line1`)
--  `table` and `column` are optional only if the element is being used in invokeGateway()
+-  `table` and `column` are optional only if the element is being used in invokeConnection()
 
 The `inputStyles` field accepts a style object which consists of CSS properties that should be applied to the form element in the following states:
 - `base`: all other variants inherit from these styles
@@ -272,16 +278,44 @@ errorTextStyles: {
 }
 ```
 
-Finally, the `type` field takes a Skyflow ElementType. Each type applies the appropriate regex and validations to the form element. There are currently 4 types:
+Finally, the `type` field takes a Skyflow ElementType. Each type applies the appropriate regex and validations to the form element. There are currently 5 types:
 - `CARDHOLDER_NAME`
 - `CARD_NUMBER`
 - `EXPIRATION_DATE`
 - `CVV`
+- `INPUT_FIELD`
+- `PIN`
+
+The `INPUT_FIELD` type is a custom UI element without any built-in validations.  See the section on [validations](#validations) for more information on validations.
 
-Once the Element object has been defined, add it to the container using the `create(element, options)` method as shown below. The `element` param takes a Skyflow Element object as defined above and the `options` parameter takes a dictionary of optional parameters as described below: 
+Along with CollectElement we can define other options which takes a dictionary of optional parameters as described below:
 
 ```javascript
-var collectElement =  {
+const options = {
+  required: false,  //optional, indicates whether the field is marked as required. Defaults to 'false'
+  enableCardIcon: true // optional, indicates whether card icon should be enabled (only applicable for CARD_NUMBER ElementType)
+  format: String //optinal, format for the element (only applicable currently for EXPIRATION_DATE ElementType)
+}
+```
+
+`required` parameter indicates whether the field is marked as required or not. If not provided, it defaults to false
+
+`enableCardIcon` paramenter indicates whether the icon is visible for the CARD_NUMBER element, defaults to true
+
+`format` parameter takes string value and indicates the format pattern applicable to the element type. It is currently applicable to EXPIRATION_DATE element type only, the values that are accepted are
+
+- `MM/YY`
+- `MM/YYYY`
+- `YY/MM`
+- `YYYY/MM`
+
+`NOTE` : If not specified or invalid value is passed to the format for EXPIRATION_DATE element, then it defaults to MM/YY format.
+
+
+Once the Element object and options has been defined, add it to the container using the `create(element, options)` method as shown below. The `element` param takes a Skyflow Element object and options as defined above:
+
+```javascript
+const collectElement =  {
    table: "string",             //the table this data belongs to
    column: "string",            //the column into which this data should be inserted
    type: Skyflow.ElementType,   //Skyflow.ElementType enum
@@ -290,11 +324,14 @@ var collectElement =  {
    errorTextStyles:{},          //optional styles that will be applied to the errorText of the collect element
    label: "string",             //optional label for the form element
    placeholder: "string",       //optional placeholder for the form element
-   altText: "string"            //optional string that acts as an initial value for the collect element
+   altText: "string"            //(DEPRECATED) string that acts as an initial value for the collect element
+   validations:[]               // optional array of validation rules
 }
 
-var options = {
-  required: false  //indicates whether the field is marked as required. Defaults to 'false'
+const options = {
+  required: false,  //optional, indicates whether the field is marked as required. Defaults to 'false'
+  enableCardIcon: true // optional, indicates whether card icon should be enabled (only applicable for CARD_NUMBER ElementType)
+  format: String //optinal, format for the element (only applicable currently for EXPIRATION_DATE ElementType)
 }
 
 const element = container.create(collectElement, options)
@@ -322,7 +359,10 @@ Now, when the `mount(domElement)` method of the Element is called, the Element w
 ```javascript
 element.mount("#cardNumber")
 ```
-
+you can use the `unmount` method to reset any collect element to it's initial state.
+```javascript
+element.unmount();
+```
 
 ### Step 4: Collect data from Elements
 
@@ -332,7 +372,7 @@ When the form is ready to be submitted, call the `collect(options?)` method on t
 - `additionalFields`: Non-PCI elements data to be inserted into the vault which should be in the `records` object format as described in the above [Inserting data into vault](#inserting-data-into-the-vault) section.
 
 ```javascript
-var options = {
+const options = {
   tokens: true  //optional, indicates whether tokens for the collected data should be returned. Defaults to 'true'
   additionalFields: {  
     records: [
@@ -421,7 +461,126 @@ container.collect({
 }
 ```
 
+### Validations
+
+Skyflow-JS provides two types of validations on Collect Elements
+
+#### 1. Default Validations:
+Every Collect Element except of type `INPUT_FIELD` has a set of default validations listed below:
+- `CARD_NUMBER`: Card number validation with checkSum algorithm(Luhn algorithm), available card lengths for defined card types
+- `CARD_HOLDER_NAME`: Name should be 2 or more symbols, valid characters should match pattern -  `^([a-zA-Z\\ \\,\\.\\-\\']{2,})$`
+- `CVV`: Card CVV can have 3-4 digits
+- `EXPIRATION_DATE`: Any date starting from current month. By default valid expiration date should be in short year format - `MM/YY`
+- `PIN`: Can have 4-12 digits
+
+#### 2. Custom Validations:
+Custom validations can be added to any element which will be checked after the default validations have passed. The following Custom validation rules are currently supported:
+- `REGEX_MATCH_RULE`: You can use this rule to specify any Regular Expression to be matched with the input field value
+
+```javascript
+const regexMatchRule = {
+  type: Skyflow.ValidationRuleType.REGEX_MATCH_RULE,
+  params: {
+    regex: RegExp,
+    error: string // optional, default error is "VALIDATION FAILED"
+  }
+}
+```
+
+- `LENGTH_MATCH_RULE`: You can use this rule to set the minimum and maximum permissible length of the input field value
 
+```javascript
+const lengthMatchRule = {
+  type: Skyflow.ValidationRuleType.LENGTH_MATCH_RULE,
+  params: {
+    min : number, // optional
+    max : number, // optional 
+    error: string // optional, default error is "VALIDATION FAILED"
+  }
+}
+```
+
+- `ELEMENT_VALUE_MATCH_RULE`: You can use this rule to match the value of one element with another element
+
+```javascript
+const elementValueMatchRule = {
+  type: Skyflow.ValidationRuleType.ELEMENT_VALUE_MATCH_RULE,
+  params: {
+    element: CollectElement,
+    error: string // optional, default error is "VALIDATION FAILED"
+  }
+}
+```
+
+The Sample code snippet for using custom validations:
+
+```javascript
+/*
+  A simple example that illustrates custom validations.
+  Adding REGEX_MATCH_RULE , LENGTH_MATCH_RULE to collect element.
+*/
+
+// this rule allows 1 or more alphabets
+const alphabetsOnlyRegexRule = {
+  type: Skyflow.ValidationRuleType.REGEX_MATCH_RULE,
+  params:{
+    regex: /^[A-Za-z]+$/,
+    error: "Only alphabets are allowed"
+  }
+}; 
+
+// this rule allows input length between 4 and 6 characters
+const lengthRule = {
+  type: Skyflow.ValidationRuleType.LENGTH_MATCH_RULE,
+  params:{
+    min: 4,
+    max: 6,
+    error: "Must be between 4 and 6 alphabets"
+  }
+}; 
+
+ const cardHolderNameElement = collectContainer.create({
+      table: "pii_fields",
+      column: "first_name",
+      ...collectStylesOptions,
+      label: "Card Holder Name",
+      placeholder: "cardholder name",
+      type: Skyflow.ElementType.INPUT_FIELD,
+      validations: [alphabetsOnlyRegexRule, lengthRule]
+    });
+
+/*
+  Reset PIN - A simple example that illustrates custom validations.
+  The below code shows an example of ELEMENT_VALUE_MATCH_RULE
+*/
+
+// for the PIN element
+const pinElement = collectContainer.create({
+  label: "PIN",
+  placeholder: "****",
+  type: Skyflow.ElementType.PIN,
+});
+
+// this rule allows to match the value with pinElement
+let elementMatchRule = {
+  type: Skyflow.ValidationRuleType.ELEMENT_VALUE_MATCH_RULE,
+  params:{
+    element: pinElement,
+    error: "PIN doesn't match"
+  }
+}
+const confirmPinElement = collectContainer.create({
+  label: "Confirm PIN",
+  placeholder: "****",
+  type: Skyflow.ElementType.PIN,
+  validations: [elementMatchRule]
+});
+
+// mount elements on screen - errors will be shown if any of the validaitons fail
+pinElement.mount("#collectPIN");
+confirmPinElement.mount("#collectConfirmPIN");
+
+```
 ### Event Listener on Collect Elements
 
 
@@ -461,7 +620,7 @@ values of SkyflowElements will be returned in elementstate object only when `env
 
 ##### Sample code snippet for using listeners
 ```javascript
-//create skyflow client with loglevel:"DEBUG"
+//create skyflow client
 const skyflowClient = Skyflow.init({
    vaultID: <VAULT_ID>,          
    vaultURL: <VAULT_URL>,
@@ -511,12 +670,70 @@ cardNumber.on(Skyflow.EventName.CHANGE,(state) => {
 }
 ```
 
+### UI Error for Collect Elements
+
+Helps to display custom error messages on the Skyflow Elements through the methods `setError` and `resetError` on the elements.
+
+`setError(error: string)` method is used to set the error text for the element, when this method is trigerred, all the current errors present on the element will be overridden with the custom error message passed. This error will be displayed on the element until `resetError()` is trigerred on the same element.
+
+`resetError()` method is used to clear the custom error message that is set using `setError`.
+
+##### Sample code snippet for setError and resetError
+
+```javascript
+
+const container = skyflowClient.container(Skyflow.ContainerType.COLLECT)
+
+const cardNumber = container.create({
+    table: "pii_fields",
+    column: "primary_card.card_number",
+    type: Skyflow.ElementType.CARD_NUMBER,
+});
+
+//Set custom error
+cardNumber.setError("custom error");
+
+//reset custom error
+cardNumber.resetError();
+
+```
+
+### Set and Clear value for Collect Elements (DEV ENV ONLY)
+
+`setValue(value: string)` method is used to set the value of the element. This method will override any previous value present in the element.
+
+`clearValue()` method is used to reset the value of the element.
+
+`Note:` This methods are only available in DEV env for testing/developmental purposes and MUST NOT be used in PROD env.
+
+##### Sample code snippet for setValue and clearValue
+
+```javascript
+const container = skyflowClient.container(Skyflow.ContainerType.COLLECT)
+
+const cardNumber = container.create({
+    table: "pii_fields",
+    column: "primary_card.card_number",
+    type: Skyflow.ElementType.CARD_NUMBER,
+});
+
+// Set a value programatically
+cardNumber.setValue("4111111111111111");
+
+// Clear the value
+cardNumber.clearValue();
+
+```
+
 ---
 
 
 # Securely revealing data client-side
 -  [**Retrieving data from the vault**](#retrieving-data-from-the-vault)
 -  [**Using Skyflow Elements to reveal data**](#using-skyflow-elements-to-reveal-data)
+-  [**UI Error for Reveal Elements**](#ui-error-for-reveal-elements)
+-  [**Set token for Reveal Elements**](#set-token-for-reveal-elements)
+- [**Set and clear altText for Reveal Elements**](#set-and-clear-alttext-for-reveal-elements)
 
 ## Retrieving data from the vault
 
@@ -526,7 +743,7 @@ For non-PCI use-cases, retrieving data from the vault and revealing it in the br
     For retrieving using tokens, use the `detokenize(records)` method. The records parameter takes a JSON object that contains `records` to be fetched as shown below.
 
 ```javascript
-var records = {
+const records = {
   "records": [
       {
         token: "string",                    // token for the record to be fetched
@@ -645,17 +862,17 @@ const container = skyflowClient.container(Skyflow.ContainerType.REVEAL)
 Then define a Skyflow Element to reveal data as shown below. 
 
 ```javascript
-var revealElement = {
+const revealElement = {
   token: "string",                    //optional, token of the data being revealed 
   inputStyles: {},                    //optional styles to be applied to the element
   labelStyles: {},                    //optional, styles to be applied to the label of the reveal element
   errorTextStyles: {},                //optional styles that will be applied to the errorText of the reveal element
-  label: "string",                     //label for the form element
+  label: "string",                    //optional, label for the form element
   altText: "string"                   //optional, string that is shown before reveal, will show token if altText is not provided
 }
 ```
 `Note`: 
-- `token` is optional only if it is being used in invokeGateway()
+- `token` is optional only if it is being used in invokeConnection()
 
 The `inputStyles`, `labelStyles` and  `errorTextStyles` parameters accepts a styles object as described in the [previous section](#step-2-create-a-collect-element) for collecting data but only a single variant is available i.e. base. 
 
@@ -693,7 +910,7 @@ errorTextStyles: {
 Once you've defined a Skyflow Element, you can use the `create(element)` method of the container to create the Element as shown below: 
 
 ```javascript
-const element = container.create(revealElement, options={})
+const element = container.create(revealElement)
 ```
 
 ### Step 3: Mount Elements to the DOM
@@ -792,12 +1009,71 @@ The response below shows that some tokens assigned to the reveal elements get re
 }
 ```
 
-# Securely invoking gateway client-side
-Using Skyflow gateway, end-user applications can integrate checkout/card issuance flow without any of their apps/systems touching the PCI compliant fields like cvv, card number. To invoke gateway, use the `invokeGateway(gatewayConfig)` method of the Skyflow client.
+### UI Error for Reveal Elements
+Helps to display custom error messages on the Skyflow Elements through the methods `setError` and `resetError` on the elements.
+
+`setError(error: string)` method is used to set the error text for the element, when this method is trigerred, all the current errors present on the element will be overridden with the custom error message passed. This error will be displayed on the element until `resetError()` is trigerred on the same element.
+
+`resetError()` method is used to clear the custom error message that is set using `setError`.
+
+##### Sample code snippet for setError and resetError
+
+```javascript
+
+const container = skyflowClient.container(Skyflow.ContainerType.REVEAL)
+
+const cardNumber = container.create({
+   token: "89024714-6a26-4256-b9d4-55ad69aa4047",
+});
+
+//Set custom error
+cardNumber.setError("custom error");
+
+//reset custom error
+cardNumber.resetError();
+
+```
+### Set token for Reveal Elements
+
+The `setToken(value: string)` method can be used to set the token of the Reveal Element. If no altText is set, the set token will be displayed on the UI as well. If altText is set, then there will be no change in the UI but the token of the element will be internally updated.
+
+##### Sample code snippet for setToken
+```javascript
+const container = skyflowClient.container(Skyflow.ContainerType.REVEAL)
+
+const cardNumber = container.create({
+   altText:"Card Number",
+});
+
+// set token 
+cardNumber.setToken("89024714-6a26-4256-b9d4-55ad69aa4047");
+
+```
+### Set and Clear altText for Reveal Elements
+The `setAltText(value: string)` method can be used to set the altText of the Reveal Element. This will cause the altText to be displayed in the UI regardless of whether the token or value is currently being displayed.
+
+`clearAltText()` method can be used to clear the altText, this will cause the element to display the token or actual value of the element. If the element has no token, the element will be empty.
+##### Sample code snippet for setAltText and clearAltText
+
+```javascript
+const container = skyflowClient.container(Skyflow.ContainerType.REVEAL)
+
+const cardNumber = container.create({
+   token:"89024714-6a26-4256-b9d4-55ad69aa4047",
+});
+
+// set altText
+cardNumber.setAltText("Card Number");
+
+//clear altText
+cardNumber.clearAltText(); 
+```
+# Securely invoking Connections client-side
+Using Skyflow Connections, end-user applications can integrate checkout/card issuance flow without any of their apps/systems touching the PCI compliant fields like cvv, card number. To invoke Connections, use the `invokeConnection(connectionConfig)` method of the Skyflow client.
 
 ```javascript
-const gatewayConfig = {
-  gatewayURL: string, // gateway url recevied when creating a skyflow gateway integration
+const connectionConfig = {
+  connectionURL: string, // connection url recevied when creating a skyflow Connection integration
   methodName: Skyflow.RequestMethod,
   pathParams: any,	// optional
   queryParams: any,	// optional
@@ -806,7 +1082,7 @@ const gatewayConfig = {
   responseBody: any	// optional
 }
 
-const response =  skyflowClient.invokeGateway(gatewayConfig);
+const response =  skyflowClient.invokeConnection(connectionConfig);
 ```
 `methodName` supports the following methods:
 
@@ -816,14 +1092,14 @@ const response =  skyflowClient.invokeGateway(gatewayConfig);
 - PATCH
 - DELETE
 
-**pathParams, queryParams, requestHeader, requestBody** are the JSON objects that will be sent through the gateway integration url.
+**pathParams, queryParams, requestHeader, requestBody** are the JSON objects that will be sent through the Connection integration url.
 
 The values in the above parameters can contain collect elements, reveal elements or actual values. When elements are provided inplace of values, they get replaced with the value entered in the collect elements or value present in the reveal elements
 
 **responseBody**:  
 It is a JSON object that specifies where to render the response in the UI. The values in the responseBody can contain collect elements or reveal elements. 
 
-Sample use-cases on using invokeGateway():
+Sample use-cases on using invokeConnection():
 
 ###  Sample use-case 1:
 
@@ -832,8 +1108,6 @@ Merchant acceptance - customers should be able to complete payment checkout with
 ```javascript
 // step 1
 const skyflowClient = skyflow.init({
-	 vaultID: <vault_Id>, 
-	 vaultURL: <vault_url>, 
 	 getBearerToken: <helperFunc>
 });
 
@@ -852,8 +1126,8 @@ const cvvElement = collectContainer.create({
 cvvElement.mount("#cvv")
 
 // step 4
-const gatewayConfig = { 
-  gatewayURL: "https://area51.gateway.skyflow.com/v1/gateway/inboundRoutes/abc-1213/v2/pay”,
+const connectionConfig = { 
+  connectionURL: <connection_url>,
   methodName: Skyflow.RequestMethod.POST,
   requestBody: {
    card_number: cardNumberElement, //it can be skyflow element(collect or reveal) or actual value
@@ -861,7 +1135,7 @@ const gatewayConfig = {
   }
 }
 
-const response =  skyflowClient.invokeGateway(gatewayConfig);
+const response =  skyflowClient.invokeConnection(connectionConfig);
 ```
 
 Sample Response:
@@ -875,7 +1149,7 @@ In the above example,  CVV is being collected from the user input at the time of
 
 `Note:`  
 - card_number can be either container element or plain text value (tokens or actual value)
-- `table` and `column` names are not required for creating collect element, if it is used for invokeGateway method, since they will not be stored in the vault
+- `table` and `column` names are not required for creating collect element, if it is used for invokeConnection method, since they will not be stored in the vault
 
  ### Sample use-case 2:
  
@@ -883,8 +1157,6 @@ In the above example,  CVV is being collected from the user input at the time of
 ```javascript
 // step 1
 const skyflowClient = skyflow.init({
-	 vaultID: <vault_Id>, 
-	 vaultURL: <vault_url>, 
 	 getBearerToken: <helperFunc>
 });
 
@@ -904,8 +1176,8 @@ const expiryDateElement = collectContainer.create({
 expiryDateElement.mount("#expirationDate")
 
 //step 4
-const gatewayConfig = { 
-  gatewayURL: "https://area51.gateway.skyflow.com/v1/gateway/inboundRoutes/abc-1213/cards/{card_number}/cvv2generation",
+const connectionConfig = { 
+  connectionURL: <connection_url>,
   methodName: Skyflow.RequestMethod.POST,
   pathParams: {
      card_number: "0905-8672-0773-0628"	//it can be skyflow element(collect/reveal) or token or actual value
@@ -915,13 +1187,13 @@ const gatewayConfig = {
  },
  responseBody: {
      resource: {
-         cvv2: cvvElement   // pass the element where the cvv response from the gateway will be mounted
+         cvv2: cvvElement   // pass the element where the cvv response from the Connection will be mounted
        }
      }  
    }
 }
 
-const response = skyflowClient.invokeGateway(gatewayConfig);
+const response = skyflowClient.invokeConnection(connectionConfig);
 ```
 
 Sample Response:
@@ -933,5 +1205,5 @@ Sample Response:
 ```
 
 `Note`:
-- `token` is optional for creating reveal element, if it is used for invokeGateway
-- responseBody contains collect or reveal elements to render the response from the gateway on UI 
+- `token` is optional for creating reveal element, if it is used for invokeConnection
+- responseBody contains collect or reveal elements to render the response from the Connection on UI