refacil-pay-mcp 1.1.2 → 1.1.4

package/README.md

@@ -194,7 +194,12 @@ kubectl get pods -l app=refacil-pay-mcp
 
 ### `auth_login`
 
-POST /auth/login
+To make the request and obtain the login you must have very clear your username and password for each environment where you are going to perform the integration, this information should be requested to our support team ([soportetecnico@refacil.com](https://mailto:soportetecnico@refacil.co)).
+
+Within the post you will see below are the fields to make your request
+
+> Note that for the consumption of any of the API services it is necessary to send the authentication token that you get when consuming the **auth/login** service as an Authorization indicating the Type and Token.  
+The authentication token does not expire. However, if at any time it were to expire, it will be necessary to generate a new authentication token. This could occur due to internal security measures that lead to manual or mass expiration of the token.
 
 **Parámetros:**
 
@@ -205,7 +210,17 @@ POST /auth/login
 
 ### `trx_token_generate`
 
-POST /trx-token/generate
+This service allows security validation for the execution of a transaction on the platform, generating a single-use token.
+
+> The transactional token service is obtained in three ways, depending on the action to be performed. For this, the value sent in the _**service**_ parameter must be set according to what is required:  
+1\. For Payment Link: **“/cash-in/generate/payment-link/token”**.  
+2\. For Payment method: **“/cash-in/generate/payment-method/token”**.  
+3\. For Withdraw: **“/cash-out/generate/withdraw-method/token”**.  
+4\. For Merchant Key: \[ “/merchant-key/create”, “/merchant-key/cancel” \] 
+  
+> The generated token is single-use for each transaction and cannot be consumed more than once. In addition, the transactional token will be valid for 60 seconds.
+
+ Generates a transactional token for payment link service.
 
 **Parámetros:**
 
@@ -215,7 +230,17 @@ POST /trx-token/generate
 
 ### `transactional_token_method`
 
-POST /trx-token/generate
+This service allows security validation for the execution of a transaction on the platform, generating a single-use token.
+
+> The transactional token service is obtained in three ways, depending on the action to be performed. For this, the value sent in the _**service**_ parameter must be set according to what is required:  
+1\. For Payment Link: **“/cash-in/generate/payment-link/token”**.  
+2\. For Payment method: **“/cash-in/generate/payment-method/token”**.  
+3\. For Withdraw: **“/cash-out/generate/withdraw-method/token”**.  
+4\. For Merchant Key: \[ “/merchant-key/create”, “/merchant-key/cancel” \] 
+  
+> The generated token is single-use for each transaction and cannot be consumed more than once. In addition, the transactional token will be valid for 60 seconds.
+
+ Generates a transactional token for payment method service.
 
 **Parámetros:**
 
@@ -225,7 +250,17 @@ POST /trx-token/generate
 
 ### `transactional_token_withdraw`
 
-POST /trx-token/generate
+This service allows security validation for the execution of a transaction on the platform, generating a single-use token.
+
+> The transactional token service is obtained in three ways, depending on the action to be performed. For this, the value sent in the _**service**_ parameter must be set according to what is required:  
+1\. For Payment Link: **“/cash-in/generate/payment-link/token”**.  
+2\. For Payment method: **“/cash-in/generate/payment-method/token”**.  
+3\. For Withdraw: **“/cash-out/generate/withdraw-method/token”**.  
+4\. For Merchant Key: \[ “/merchant-key/create”, “/merchant-key/cancel” \] 
+  
+> The generated token is single-use for each transaction and cannot be consumed more than once. In addition, the transactional token will be valid for 60 seconds.
+
+ Generates a transactional token for withdraw service.
 
 **Parámetros:**
 
@@ -235,7 +270,17 @@ POST /trx-token/generate
 
 ### `transactional_token_merchan_key_create`
 
-POST /trx-token/generate
+This service allows security validation for the execution of a transaction on the platform, generating a single-use token.
+
+> The transactional token service is obtained in three ways, depending on the action to be performed. For this, the value sent in the _**service**_ parameter must be set according to what is required:  
+1\. For Payment Link: **“/cash-in/generate/payment-link/token”**.  
+2\. For Payment method: **“/cash-in/generate/payment-method/token”**.  
+3\. For Withdraw: **“/cash-out/generate/withdraw-method/token”**.  
+4\. For Merchant Key: \[ “/merchant-key/create”, “/merchant-key/cancel” \] 
+  
+> The generated token is single-use for each transaction and cannot be consumed more than once. In addition, the transactional token will be valid for 60 seconds.
+
+ Generates a transactional token for creating merchant keys.
 
 **Parámetros:**
 
@@ -245,7 +290,17 @@ POST /trx-token/generate
 
 ### `transactional_token_merchant_key_cancel`
 
-POST /trx-token/generate
+This service allows security validation for the execution of a transaction on the platform, generating a single-use token.
+
+> The transactional token service is obtained in three ways, depending on the action to be performed. For this, the value sent in the _**service**_ parameter must be set according to what is required:  
+1\. For Payment Link: **“/cash-in/generate/payment-link/token”**.  
+2\. For Payment method: **“/cash-in/generate/payment-method/token”**.  
+3\. For Withdraw: **“/cash-out/generate/withdraw-method/token”**.  
+4\. For Merchant Key: \[ “/merchant-key/create”, “/merchant-key/cancel” \] 
+  
+> The generated token is single-use for each transaction and cannot be consumed more than once. In addition, the transactional token will be valid for 60 seconds.
+
+ Generates a transactional token for canceling merchant keys.
 
 **Parámetros:**
 
@@ -255,7 +310,9 @@ POST /trx-token/generate
 
 ### `cash_in_generate_payment_link_token`
 
-## 📥 Request Body Parameters
+With the following request you can obtain a payment resource with a link that will redirect your customer to the payment gateway where he will see a list of the different payment methods available.
+
+ ## 📥 Request Body Parameters
 
 | **Field** | **Type** | **Required** | **Description** |
 | --- | --- | --- | --- |
@@ -609,7 +666,23 @@ This is **not** an error in our platform.
 
 ### `cash_out_generate_withdraw_method_token`
 
-This endpoint allows you to **generate withdrawal (cash-out) requests** through the available payout methods.
+This service allows you to generate withdrawal requests through the enabled dispersion means.
+
+> 🔐 Authentication 
+  
+
+All requests must include the following headers:
+
+| **Header** | **Description** | **Example** |
+| --- | --- | --- |
+| Authorization | Bearer token generated by the authentication service. | Bearer eyJhbGciOiJIUzI1NiIs... |
+| x-transaction-token | Transactional token specific to the service. | 9b48edde-652d-11ed-984e-02c840fe**** |
+| Content-Type | Content type of the request body. | application/json |
+
+> Important fields within the requests:  
+Webhook: This is the url of the client's webhook to where our service sends the transaction status and transaction detail information.
+
+ This endpoint allows you to **generate withdrawal (cash-out) requests** through the available payout methods.
 
 ---
 
@@ -701,7 +774,23 @@ The `key` field must contain a valid Bre-B account alias in the format `@USERNAM
 
 ### `customer_getbalance`
 
-This service allows you to consult the balance exchange and the dispersion exchange associated with the client's identifier.
+This service allows you to generate withdrawal requests through the enabled dispersion means.
+
+> 🔐 Authentication 
+  
+
+All requests must include the following headers:
+
+| **Header** | **Description** | **Example** |
+| --- | --- | --- |
+| Authorization | Bearer token generated by the authentication service. | Bearer eyJhbGciOiJIUzI1NiIs... |
+| x-transaction-token | Transactional token specific to the service. | 9b48edde-652d-11ed-984e-02c840fe**** |
+| Content-Type | Content type of the request body. | application/json |
+
+> Important fields within the requests:  
+Webhook: This is the url of the client's webhook to where our service sends the transaction status and transaction detail information.
+
+ This service allows you to consult the balance exchange and the dispersion exchange associated with the client's identifier.
 
 > To use the service, an authentication token is required, which must be sent as an Authorization header. 
   
@@ -723,7 +812,23 @@ Body
 
 ### `payment_transfiya_banks`
 
-This service allows you to consult the balance exchange and the dispersion exchange associated with the client's identifier.
+This service allows you to generate withdrawal requests through the enabled dispersion means.
+
+> 🔐 Authentication 
+  
+
+All requests must include the following headers:
+
+| **Header** | **Description** | **Example** |
+| --- | --- | --- |
+| Authorization | Bearer token generated by the authentication service. | Bearer eyJhbGciOiJIUzI1NiIs... |
+| x-transaction-token | Transactional token specific to the service. | 9b48edde-652d-11ed-984e-02c840fe**** |
+| Content-Type | Content type of the request body. | application/json |
+
+> Important fields within the requests:  
+Webhook: This is the url of the client's webhook to where our service sends the transaction status and transaction detail information.
+
+ This service allows you to consult the balance exchange and the dispersion exchange associated with the client's identifier.
 
 > To use the service, an authentication token is required, which must be sent as an Authorization header. 
   
@@ -745,7 +850,9 @@ Body
 
 ### `payment_status`
 
-This service allows you to check the status of a transaction made, for this you must have the _reference_ data that returned the response when generating any payment resource.
+These services will allow us to validate the status of a transaction and consult the characteristics of a payment method.
+
+ This service allows you to check the status of a transaction made, for this you must have the _reference_ data that returned the response when generating any payment resource.
 
 In the response you will get the _status_ _id_ which will mean the following
 
@@ -778,7 +885,9 @@ Body
 
 ### `payment_customer_reference_status`
 
-## 🔍 Check Transaction by Customer Reference
+These services will allow us to validate the status of a transaction and consult the characteristics of a payment method.
+
+ ## 🔍 Check Transaction by Customer Reference
 
 This endpoint allows **API Pay** users to query the status of a transaction using only the `customerReference` value originally provided when generating a resource as `reference1` through any of the following endpoints:
 
@@ -829,7 +938,9 @@ This endpoint **requires** a valid Bearer Token in the request headers. Requests
 
 ### `payment_features`
 
-This service allows you to consult the necessary characteristics of a payment method to successfully generate a resource. For example, obtain the PSE banks
+These services will allow us to validate the status of a transaction and consult the characteristics of a payment method.
+
+ This service allows you to consult the necessary characteristics of a payment method to successfully generate a resource. For example, obtain the PSE banks
 
 Headers
 
@@ -848,7 +959,109 @@ Body
 
 ### `webhook_notify`
 
-Body
+This component must be built by the merchant to receive the transaction notification data.
+
+You must take into account the following steps:
+
+**1.**You must create a Webhook without authentication.
+
+**2\. The** Url created will be the one you send in all requests when generating the payment resource in the “_WebhookUrl_” field. It is important to keep in mind that if for some reason you change the webhook you must modify the urls that you send in each generated resource.
+
+<img src="https://content.pstmn.io/10fdac74-e60a-41f2-b9ff-8b5777a7afc0/aW1hZ2UucG5n" width="322" height="117">
+
+A signature must be generated to validate the integrity of the messages sent to the webhook and the fields must be concatenated in the following way:
+
+_**HASH_KEY**_ _\=This data must be requested to the support area_.
+
+_**let signature**_ _\= referenceId-resourceId-amount-updatedAt-HASH_KEY; signature = crypto.createHmac(“sha1”, HASH_KEY).update(signature).digest(“hex”);_
+
+Example of a response that will reach your Webhook
+
+**Response**
+
+``` json
+{
+  "realAmount": 20000,
+  "amount": 19405,
+  "cost": "$595.00",
+  "referenceId": "38**",
+  "moduleId": 9,
+  "productId": 117,
+  "referenceKey": "3538d790-ae14-11ed-be2d-4d9b1bc987e6",
+  "paymentMethod": "PSE",
+  "userId": 189067,
+  "resourceId": "10024**",
+  "updatedAt": "2023-02-16 11:11:55",
+  "providerId": 8,
+  "providerReference": "3122330",
+  "reference1": "435sdfsd**",
+  "reference2": {
+    "Label": {
+      "Information": "Por seguridad algunos datos se encuentran cifrados",
+      "Name": "L**A",
+      "Email": "l**am@**",
+      "CellPhone": "3**4",
+      "DocumentType": "C",
+      "DocumentNumber": "52019859",
+      "Description": "Abono",
+      "Commerce": "Skandia",
+      "Reference1": null,
+      "Reference2": null,
+      "Reference3": null
+    },
+    "Data": {
+      "ConciliationCode": "FCO",
+      "ConciliationContract": "1277840",
+      "DocType": "N",
+      "DocNumber": "800194363"
+    },
+    "returnUrl": "https://www.google.com/"
+  },
+  "bankId": "1022",
+  "bankName": "BANCO UNION COLOMBIANO",
+  "status": 2,
+  "transfiyaStatus": "PENDING",
+  "sign": "aa2f472ad7e84524a02d1716b56fc16ec2a87***",
+  "error": {
+        "code": "20-07A",
+        "message": "Error técnico en Lambda"
+      }
+}
+
+ ```
+
+- Within the webhook an **"error** ” object is sent that shows the error _**code**_ and _**message**_ associated with rejections received from the supplier/bank or cancellation of the transaction when the generation of the resource is not completed.
+    
+- The error codes are printed when the transaction is _**Rejected**_ by the bank or when it is _**Cancelled**_ because the resource generation could not be completed.
+    
+
+**Notification for Withdraw**
+
+For withdraws, a notification will be sent to the webhook provided in the application. This notification will follow the structure mentioned above and will additionally include the withdrawal data. An example is provided below:
+
+``` json
+{
+    ..."webhook",
+    "withdraw": {
+        "id": "1403**",
+        "transactionId": "5690**",
+        "userId": 189067,
+        "providerReference": "3122330",
+        "accountNumber": "3051000002",
+        "accountId": null,
+        "createdAt": "2023-02-16 11:10:55",
+        "updatedAt": "2023-02-16 11:12:55",
+        "deletedAt": null,
+        "infoReference": "435sdfsd**",
+        "observation": null
+    },
+}
+
+ ```
+
+> _**The implementation of the webhook by the API user is mandatory. The reception and storage of the information for the reconciliation process by the API user with RefácilPay must be ensured.**__**This item will be evaluated during the certification process and will be mandatory for the transition to Production.**_
+
+ Body
 
 
 
@@ -875,15 +1088,153 @@ Body
 
 ### `merchant_enrollment`
 
-This endpoint initiates the merchant enrollment process required to use the QR interoperable payment method. Once the request is made, the enrollment process may take up to **7 minutes** to complete.
+This service allows merchants to enroll for the use of the QR interoperable payment method and key creation.
+
+To use the service, an authentication token is required and must be sent as an `Authorization` header.
+
+---
+
+### **Enrollment Process**
+
+1. **Merchant Enrollment**
+    
+    - Initiates the enrollment process. The enrollment can take up to **7 minutes** to complete.
+        
+2. **Retrieve Enrollment Data**
+    
+    - Retrieves the merchant’s enrollment information once the process is completed.
+        
+
+---
+
+### **Merchant Enrollment Statuses**
+
+- **`approved`**
+    
+    The merchant has been approved and is authorized to generate QR codes.
+    
+- **`enrolled_other`**
+    
+    The merchant is already enrolled with another entity. To proceed:
+    
+    - Contact the commercial representative and request unenrollment from the current entity.
+        
+    - Submit a letter signed by the legal representative.
+        
+    - Be aware that this process may take up to **5 business days**.
+        
+        The commercial representative will provide guidance throughout the process.
+        
+- **`rejected`**
+    
+    The merchant has been rejected. Please contact your commercial representative for further details.
+    
+- **`pending`**
+    
+    The enrollment is in progress. The query may take a few minutes. If a final status is not received shortly, contact **RefacilPay support** to verify the situation.
+    
+- **`not_started`**
+    
+    No enrollment process has been initiated for the requested merchant.
+    
+
+---
+
+### **Important Note on the "cellphone" Field in the Enrollment Process**
+
+During the merchant creation flow for the QR Interoperable product, the API retrieves the merchant's registered information from the system. However, for the **"cellphone number"** field, the **Refacil** system automatically replaces the merchant’s actual phone number with a **generic alias number**.
+
+This behavior follows technical and operational requirements from the provider, as the real phone number may already exist in the provider’s databases, potentially causing integration conflicts.
+
+To avoid these issues, a randomly generated alias is used as a placeholder. This alias is **exclusive to this product** and does **not affect** the merchant’s operation in other services.
+
+ This endpoint initiates the merchant enrollment process required to use the QR interoperable payment method. Once the request is made, the enrollment process may take up to **7 minutes** to complete.
 
 ### `merchant_enrollment_data`
 
-This endpoint retrieves the merchant's enrollment details after the enrollment process has been completed. It provides necessary information to use the QR interoperable payment method.
+This service allows merchants to enroll for the use of the QR interoperable payment method and key creation.
+
+To use the service, an authentication token is required and must be sent as an `Authorization` header.
+
+---
+
+### **Enrollment Process**
+
+1. **Merchant Enrollment**
+    
+    - Initiates the enrollment process. The enrollment can take up to **7 minutes** to complete.
+        
+2. **Retrieve Enrollment Data**
+    
+    - Retrieves the merchant’s enrollment information once the process is completed.
+        
+
+---
+
+### **Merchant Enrollment Statuses**
+
+- **`approved`**
+    
+    The merchant has been approved and is authorized to generate QR codes.
+    
+- **`enrolled_other`**
+    
+    The merchant is already enrolled with another entity. To proceed:
+    
+    - Contact the commercial representative and request unenrollment from the current entity.
+        
+    - Submit a letter signed by the legal representative.
+        
+    - Be aware that this process may take up to **5 business days**.
+        
+        The commercial representative will provide guidance throughout the process.
+        
+- **`rejected`**
+    
+    The merchant has been rejected. Please contact your commercial representative for further details.
+    
+- **`pending`**
+    
+    The enrollment is in progress. The query may take a few minutes. If a final status is not received shortly, contact **RefacilPay support** to verify the situation.
+    
+- **`not_started`**
+    
+    No enrollment process has been initiated for the requested merchant.
+    
+
+---
+
+### **Important Note on the "cellphone" Field in the Enrollment Process**
+
+During the merchant creation flow for the QR Interoperable product, the API retrieves the merchant's registered information from the system. However, for the **"cellphone number"** field, the **Refacil** system automatically replaces the merchant’s actual phone number with a **generic alias number**.
+
+This behavior follows technical and operational requirements from the provider, as the real phone number may already exist in the provider’s databases, potentially causing integration conflicts.
+
+To avoid these issues, a randomly generated alias is used as a placeholder. This alias is **exclusive to this product** and does **not affect** the merchant’s operation in other services.
+
+ This endpoint retrieves the merchant's enrollment details after the enrollment process has been completed. It provides necessary information to use the QR interoperable payment method.
 
 ### `merchant_key_create`
 
-This endpoint will allow you to create 4 types of keys: `alias`, `email`, `cellphone`, and `document`.
+These services allow merchants to create and manage their Bre-b keys.
+
+To use these services, an authentication token is required, which must be sent as an authorization header.
+
+---
+
+⚠ **Important**: Before using this payment method, the merchant enrollment process must be completed. Detailed instructions can be found in the **Merchant Enrollment** section.
+
+**🔄 Open resource:** The creation of a key functions as an open resource, which means that once the Bre-b key has been generated, the user can receive multiple transactions through it.
+
+---
+
+### Recommendations
+
+- API users are strongly encouraged to **implement additional application-level validations** to detect, identify, and manage multiple payment records originating from a Bre-b key.
+    
+- **Actively monitor transactions** originating from generated keys and validate the status of operations before confirming payment to the end user.
+
+ This endpoint will allow you to create 4 types of keys: `alias`, `email`, `cellphone`, and `document`.
 
 ⚠ **Important**:
 
@@ -922,7 +1273,25 @@ Body
 
 ### `merchant_key_cancel`
 
-This endpoint allows you to cancel an existing key, which will then become inactive and unable to receive transactions.
+These services allow merchants to create and manage their Bre-b keys.
+
+To use these services, an authentication token is required, which must be sent as an authorization header.
+
+---
+
+⚠ **Important**: Before using this payment method, the merchant enrollment process must be completed. Detailed instructions can be found in the **Merchant Enrollment** section.
+
+**🔄 Open resource:** The creation of a key functions as an open resource, which means that once the Bre-b key has been generated, the user can receive multiple transactions through it.
+
+---
+
+### Recommendations
+
+- API users are strongly encouraged to **implement additional application-level validations** to detect, identify, and manage multiple payment records originating from a Bre-b key.
+    
+- **Actively monitor transactions** originating from generated keys and validate the status of operations before confirming payment to the end user.
+
+ This endpoint allows you to cancel an existing key, which will then become inactive and unable to receive transactions.
 
 Headers
 
@@ -944,7 +1313,25 @@ Body
 
 ### `merchant_key_generate_otp`
 
-This endpoint will allow you to generate and send an OTP. It is only permitted and necessary for `email` and `cellphone` keys. This OTP will be sent to its corresponding destination.
+These services allow merchants to create and manage their Bre-b keys.
+
+To use these services, an authentication token is required, which must be sent as an authorization header.
+
+---
+
+⚠ **Important**: Before using this payment method, the merchant enrollment process must be completed. Detailed instructions can be found in the **Merchant Enrollment** section.
+
+**🔄 Open resource:** The creation of a key functions as an open resource, which means that once the Bre-b key has been generated, the user can receive multiple transactions through it.
+
+---
+
+### Recommendations
+
+- API users are strongly encouraged to **implement additional application-level validations** to detect, identify, and manage multiple payment records originating from a Bre-b key.
+    
+- **Actively monitor transactions** originating from generated keys and validate the status of operations before confirming payment to the end user.
+
+ This endpoint will allow you to generate and send an OTP. It is only permitted and necessary for `email` and `cellphone` keys. This OTP will be sent to its corresponding destination.
 
 Headers
 
@@ -964,7 +1351,25 @@ Body
 
 ### `merchant_key_get_keys`
 
-This endpoint allows you to obtain all keys created and in active status that belong to the merchant.
+These services allow merchants to create and manage their Bre-b keys.
+
+To use these services, an authentication token is required, which must be sent as an authorization header.
+
+---
+
+⚠ **Important**: Before using this payment method, the merchant enrollment process must be completed. Detailed instructions can be found in the **Merchant Enrollment** section.
+
+**🔄 Open resource:** The creation of a key functions as an open resource, which means that once the Bre-b key has been generated, the user can receive multiple transactions through it.
+
+---
+
+### Recommendations
+
+- API users are strongly encouraged to **implement additional application-level validations** to detect, identify, and manage multiple payment records originating from a Bre-b key.
+    
+- **Actively monitor transactions** originating from generated keys and validate the status of operations before confirming payment to the end user.
+
+ This endpoint allows you to obtain all keys created and in active status that belong to the merchant.
 
 
 ## 📝 Logs

package/dist/core/resources.js

@@ -23,7 +23,7 @@ export const resources = [
         "name": "Transactional token - Documentation",
         "description": "This service allows security validation for the execution of a transaction on the platform, generating a single-use token.\n\n> The transactional token service is obtained in three ways, depending on the action to be performed. For this, the value sent in the _**service**_ parameter must be set according to what is required:  \n1\\. For Payment Link: **“/cash-in/generate/payment-link/token”**.  \n2\\. For Payment method: **“/cash-in/generate/payment-method/token”**.  \n3\\. For Withdraw: **“/cash-out/generate/withdraw-method/token”**.  \n4\\. For Merchant Key: \\[ “/merchant-key/create”, “/merchant-key/cancel” \\] \n  \n> The generated token is single-use for each transaction and cannot be consumed more than once. In addition, the transactional token will be valid for 60 seconds.",
         "mimeType": "text/markdown",
-        "content": "# Transactional token\n\nThis service allows security validation for the execution of a transaction on the platform, generating a single-use token.\n\n> The transactional token service is obtained in three ways, depending on the action to be performed. For this, the value sent in the _**service**_ parameter must be set according to what is required:  \n1\\. For Payment Link: **“/cash-in/generate/payment-link/token”**.  \n2\\. For Payment method: **“/cash-in/generate/payment-method/token”**.  \n3\\. For Withdraw: **“/cash-out/generate/withdraw-method/token”**.  \n4\\. For Merchant Key: \\[ “/merchant-key/create”, “/merchant-key/cancel” \\] \n  \n> The generated token is single-use for each transaction and cannot be consumed more than once. In addition, the transactional token will be valid for 60 seconds.\n\n## Endpoints\n\n### Transactional token link\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n### Transactional token method\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n### Transactional token withdraw\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n### Transactional token merchan key create\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n### Transactional token merchant key cancel\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n"
+        "content": "# Transactional token\n\nThis service allows security validation for the execution of a transaction on the platform, generating a single-use token.\n\n> The transactional token service is obtained in three ways, depending on the action to be performed. For this, the value sent in the _**service**_ parameter must be set according to what is required:  \n1\\. For Payment Link: **“/cash-in/generate/payment-link/token”**.  \n2\\. For Payment method: **“/cash-in/generate/payment-method/token”**.  \n3\\. For Withdraw: **“/cash-out/generate/withdraw-method/token”**.  \n4\\. For Merchant Key: \\[ “/merchant-key/create”, “/merchant-key/cancel” \\] \n  \n> The generated token is single-use for each transaction and cannot be consumed more than once. In addition, the transactional token will be valid for 60 seconds.\n\n## Endpoints\n\n### Transactional token link\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\nGenerates a transactional token for payment link service.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/cash-in/generate/payment-link/token` |\n\n### Transactional token method\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\nGenerates a transactional token for payment method service.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/cash-in/payment-method/token` |\n\n### Transactional token withdraw\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\nGenerates a transactional token for withdraw service.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/cash-out/generate/withdraw-method/token` |\n\n### Transactional token merchan key create\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\nGenerates a transactional token for creating merchant keys.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/merchant-key/create` |\n\n### Transactional token merchant key cancel\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\nGenerates a transactional token for canceling merchant keys.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/merchant-key/cancel` |\n\n"
     },
     {
         "uri": "postman://collection/refacil-pay-api/folder/payments",
@@ -84,37 +84,37 @@ export const resources = [
     {
         "uri": "postman://collection/refacil-pay-api/endpoint/post/trx-token/generate",
         "name": "POST /trx-token/generate - Endpoint Documentation",
-        "description": "| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |",
+        "description": "Generates a transactional token for payment link service.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/cash-in/generate/payment-link/token` |",
         "mimeType": "text/markdown",
-        "content": "# Transactional token link\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/cash-in/generate/payment-link/token\"\n}\n```\n\n"
+        "content": "# Transactional token link\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\nGenerates a transactional token for payment link service.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/cash-in/generate/payment-link/token` |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/cash-in/generate/payment-link/token\"\n}\n```\n\n"
     },
     {
         "uri": "postman://collection/refacil-pay-api/endpoint/post/trx-token/generate",
         "name": "POST /trx-token/generate - Endpoint Documentation",
-        "description": "| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |",
+        "description": "Generates a transactional token for payment method service.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/cash-in/payment-method/token` |",
         "mimeType": "text/markdown",
-        "content": "# Transactional token method\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/cash-in/payment-method/token\"\n}\n```\n\n"
+        "content": "# Transactional token method\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\nGenerates a transactional token for payment method service.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/cash-in/payment-method/token` |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/cash-in/payment-method/token\"\n}\n```\n\n"
     },
     {
         "uri": "postman://collection/refacil-pay-api/endpoint/post/trx-token/generate",
         "name": "POST /trx-token/generate - Endpoint Documentation",
-        "description": "| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |",
+        "description": "Generates a transactional token for withdraw service.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/cash-out/generate/withdraw-method/token` |",
         "mimeType": "text/markdown",
-        "content": "# Transactional token withdraw\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/cash-out/generate/withdraw-method/token\"\n}\n```\n\n"
+        "content": "# Transactional token withdraw\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\nGenerates a transactional token for withdraw service.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/cash-out/generate/withdraw-method/token` |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/cash-out/generate/withdraw-method/token\"\n}\n```\n\n"
     },
     {
         "uri": "postman://collection/refacil-pay-api/endpoint/post/trx-token/generate",
         "name": "POST /trx-token/generate - Endpoint Documentation",
-        "description": "| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |",
+        "description": "Generates a transactional token for creating merchant keys.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/merchant-key/create` |",
         "mimeType": "text/markdown",
-        "content": "# Transactional token merchan key create\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/merchant-key/create\"\n}\n```\n\n"
+        "content": "# Transactional token merchan key create\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\nGenerates a transactional token for creating merchant keys.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/merchant-key/create` |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/merchant-key/create\"\n}\n```\n\n"
     },
     {
         "uri": "postman://collection/refacil-pay-api/endpoint/post/trx-token/generate",
         "name": "POST /trx-token/generate - Endpoint Documentation",
-        "description": "| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |",
+        "description": "Generates a transactional token for canceling merchant keys.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/merchant-key/cancel` |",
         "mimeType": "text/markdown",
-        "content": "# Transactional token merchant key cancel\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | Value of the service to be consumed |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/merchant-key/cancel\"\n}\n```\n\n"
+        "content": "# Transactional token merchant key cancel\n\n## Request Details\n\n**Method**: `POST`\n\n**Path**: `/trx-token/generate`\n\n## Description\n\nGenerates a transactional token for canceling merchant keys.\n\n| **Name** | **Type** | **Description** |\n| --- | --- | --- |\n| **service** \\* | string | MUST be: `/merchant-key/cancel` |\n\n## Headers\n\n- **Authorization**: Bearer {{tokenLogin}}\n\n## Request Body\n\n**Type**: `raw`\n\n```json\n{\n  \"service\": \"/merchant-key/cancel\"\n}\n```\n\n"
     },
     {
         "uri": "postman://collection/refacil-pay-api/endpoint/post/cash-in/generate/payment-link/token",