@ekoindia/eps-context-mcp 0.1.11 → 0.1.13

package/data/eps.json

@@ -2,7 +2,7 @@
   "meta": {
     "org": "ekoindia",
     "apiVersion": "v3",
-    "bundleVersion": "76929d24",
+    "bundleVersion": "c9e5f932",
     "environments": [
       {
         "id": "sandbox",
@@ -297,6 +297,14 @@
           "description": "Sender's 10-digit mobile number.",
           "example": "9123456789",
           "in": "path"
+        },
+        {
+          "name": "user_code",
+          "type": "string",
+          "required": true,
+          "description": "Agent user code (sent as a query parameter).",
+          "example": "20810200",
+          "in": "query"
         }
       ],
       "sampleRequest": {},
@@ -333,71 +341,109 @@
             {
               "name": "is_registered",
               "type": "number",
-              "imp": true,
-              "description": "1 = sender already registered, 0 = not registered.",
-              "example": 1
-            },
-            {
-              "name": "sender_name",
-              "type": "string",
-              "description": "Registered name of the sender.",
-              "imp": true,
-              "example": "Ramesh Kumar"
-            },
-            {
-              "name": "ekyc_enabled",
-              "type": "string",
-              "description": "Whether biometric eKYC is enabled (\"1\" = yes).",
-              "example": "1"
+              "description": "Registration flag from the profile lookup. Read customer_profile.kyc_state to determine KYC completion.",
+              "example": 0
             },
             {
               "name": "next_allowed_limit",
               "type": "number",
-              "description": "Remaining transfer limit for the current month (in INR).",
               "imp": true,
-              "example": 48000
+              "description": "Remaining remittance limit currently available (INR).",
+              "example": 25000
             },
             {
               "name": "kyc_state",
               "type": "number",
-              "description": "Sender account state: 0=Active, 10=Pending verification.",
+              "description": "Top-level KYC flag for the lookup response.",
               "example": 0
             },
             {
               "name": "customer_profile",
               "type": "object",
               "imp": true,
-              "description": "Sender profile summary.",
+              "description": "Sender profile summary (present once KYC is complete).",
               "children": [
                 {
                   "name": "name",
                   "type": "string",
-                  "description": "Sender's registered name.",
-                  "example": "Ramesh Kumar"
+                  "description": "Sender name.",
+                  "imp": true,
+                  "example": "Rahul"
                 },
                 {
                   "name": "mobile",
                   "type": "string",
                   "description": "Sender's mobile number.",
-                  "example": "9123456789"
+                  "example": "9155927131"
+                },
+                {
+                  "name": "balance",
+                  "type": "string",
+                  "description": "Sender wallet balance (INR).",
+                  "example": "0.00"
                 },
                 {
                   "name": "total_monthly_limit",
                   "type": "string",
-                  "description": "Total monthly transfer limit (INR).",
-                  "example": "50000"
+                  "description": "Sender's monthly remittance limit (INR).",
+                  "example": "25000.0"
                 },
                 {
                   "name": "next_allowed_limit",
                   "type": "string",
-                  "description": "Remaining monthly transfer limit (INR).",
-                  "example": "48000"
+                  "description": "Remaining limit currently available (INR).",
+                  "example": "25000.0"
                 },
                 {
-                  "name": "ekyc_enabled",
+                  "name": "kyc_state",
                   "type": "number",
-                  "description": "Whether eKYC is enabled (1 = yes).",
+                  "description": "Sender KYC state (1 = KYC complete on the profile).",
+                  "imp": true,
                   "example": 1
+                },
+                {
+                  "name": "chart",
+                  "type": "array",
+                  "description": "Per-period limit-usage breakdown.",
+                  "children": [
+                    {
+                      "name": "data_type_id",
+                      "type": "number",
+                      "description": "Identifier for the limit period/bucket.",
+                      "example": 10
+                    },
+                    {
+                      "name": "data",
+                      "type": "object",
+                      "description": "Limit usage for the period.",
+                      "children": [
+                        {
+                          "name": "unavailable",
+                          "type": "number",
+                          "description": "Amount blocked/unavailable (INR).",
+                          "example": 0
+                        },
+                        {
+                          "name": "used",
+                          "type": "number",
+                          "description": "Amount already used (INR).",
+                          "example": 0
+                        },
+                        {
+                          "name": "remaining",
+                          "type": "number",
+                          "description": "Remaining limit for the period (INR).",
+                          "example": 25000
+                        }
+                      ]
+                    },
+                    {
+                      "name": "label",
+                      "type": "string",
+                      "description": "Display label for the period.",
+                      "example": ""
+                    }
+                  ]
                 }
               ]
             }
@@ -406,34 +452,59 @@
       ],
       "sampleSuccessResponse": {
         "status": 0,
+        "response_status_id": -1,
         "response_type_id": 309,
         "message": "Success!",
-        "response_status_id": -1,
         "data": {
-          "is_registered": 1,
-          "sender_name": "Ramesh Kumar",
-          "ekyc_enabled": "1",
-          "next_allowed_limit": 48000,
+          "is_registered": 0,
+          "next_allowed_limit": 25000,
           "kyc_state": 0,
           "customer_profile": {
-            "name": "Ramesh Kumar",
-            "mobile": "9123456789",
-            "total_monthly_limit": "50000",
-            "next_allowed_limit": "48000",
-            "ekyc_enabled": 1
+            "total_monthly_limit": "25000.0",
+            "mobile": "9155927131",
+            "balance": "0.00",
+            "next_allowed_limit": "25000.0",
+            "name": "Rahul",
+            "kyc_state": 1,
+            "chart": [
+              {
+                "data_type_id": 10,
+                "data": {
+                  "unavailable": 0,
+                  "used": 0,
+                  "remaining": 25000
+                },
+                "label": ""
+              }
+            ]
           }
         }
       },
       "errorScenarios": [
         {
-          "scenario": "Sender not found — proceed to Onboard Sender",
+          "scenario": "Sender not enrolled — proceed to Onboard Sender",
           "statusCode": 200,
           "example": {
-            "status": 1,
-            "response_status_id": 463,
-            "message": "Customer not found",
+            "status": 308,
+            "response_status_id": 1,
+            "message": "Failure!Customer Not Enrolled",
             "response_type_id": 308,
-            "data": {}
+            "data": {
+              "ekyc_enabled": ""
+            }
+          }
+        },
+        {
+          "scenario": "Enrolled on Eko, KYC pending on Fino — proceed to Sender eKYC",
+          "statusCode": 200,
+          "example": {
+            "status": 0,
+            "response_status_id": 0,
+            "message": "Customer KYC Pending",
+            "response_type_id": 2134,
+            "data": {
+              "otp_ref_id": ""
+            }
           }
         }
       ],
@@ -470,7 +541,7 @@
       "summary": "Register a new customer as a DMT-Fino sender using basic KYC details.",
       "category": "bc",
       "relevance": "M",
-      "description": "Registers a new customer in the DMT-Fino system. Provide the customer's name, date of birth, and residence address. On success the sender is created in a pending state; biometric eKYC (via Sender KYC) must follow to activate full monthly limits. An OTP is dispatched to the customer's mobile number for confirmation.",
+      "description": "Registers a new customer in the DMT-Fino system. Provide the customer's name, date of birth, and residence address. On success the sender is opened on Eko but KYC on Fino is still pending — complete biometric eKYC (Sender eKYC → Validate eKYC OTP) next. If the sender was already onboarded on Fino externally, the response instead matches the KYC-complete profile from Get Sender Profile (response_type_id 309) and no eKYC is required. After onboarding, call Get Sender Profile to read the sender's current stage.",
       "bestFor": "First-time sender registration in the DMT flow.",
       "docsUrl": "https://eps.eko.in/docs/dmt-onboard-sender",
       "headers": [
@@ -549,8 +620,8 @@
           "name": "residence_address",
           "type": "string",
           "required": true,
-          "description": "Customer's residence address as a JSON-encoded array of address lines.",
-          "example": "[\"123 Main Street\", \"Connaught Place\", \"New Delhi\", \"110001\"]",
+          "description": "Customer's residence address as a JSON-encoded object with keys: line, city, state, pincode, district, area.",
+          "example": "{\"line\":\"India\",\"city\":\"Indore\",\"state\":\"Madhya Pradesh\",\"pincode\":\"226024\",\"district\":\"Indore\",\"area\":\"gita bhavan\"}",
           "in": "body"
         }
       ],
@@ -559,7 +630,7 @@
         "client_ref_id": "2026010100123456789",
         "name": "Ramesh Kumar",
         "dob": "1990-05-15",
-        "residence_address": "[\"123 Main Street\", \"Connaught Place\", \"New Delhi\", \"110001\"]"
+        "residence_address": "{\"line\":\"India\",\"city\":\"Indore\",\"state\":\"Madhya Pradesh\",\"pincode\":\"226024\",\"district\":\"Indore\",\"area\":\"gita bhavan\"}"
       },
       "responseFields": [
         {
@@ -591,30 +662,11 @@
           "type": "object",
           "description": "API-specific response payload.",
           "children": [
-            {
-              "name": "customer_id",
-              "type": "string",
-              "description": "Mobile number of the newly registered sender.",
-              "imp": true,
-              "example": "9123456789"
-            },
-            {
-              "name": "state",
-              "type": "number",
-              "description": "Account state: 10=Pending KYC verification.",
-              "example": 10
-            },
             {
               "name": "otp_ref_id",
               "type": "string",
-              "description": "Reference ID for the OTP sent to the sender's mobile. Used in the Validate eKYC OTP step.",
-              "example": "OTP20240101001"
-            },
-            {
-              "name": "available_limit",
-              "type": "number",
-              "description": "Initial transfer limit before eKYC (in INR). Typically ₹5,000.",
-              "example": 5000
+              "description": "OTP reference placeholder returned with the KYC-pending status. Empty until eKYC is initiated via Sender eKYC.",
+              "example": ""
             }
           ]
         }
@@ -622,29 +674,47 @@
       "sampleSuccessResponse": {
         "status": 0,
         "response_status_id": 0,
-        "message": "Customer registered successfully",
-        "response_type_id": 1388,
+        "message": "Customer KYC Pending",
+        "response_type_id": 2134,
         "data": {
-          "customer_id": "9123456789",
-          "state": 10,
-          "otp_ref_id": "OTP20240101001",
-          "available_limit": 5000
+          "otp_ref_id": ""
         }
       },
       "errorScenarios": [
         {
-          "scenario": "Sender already exists in the system",
+          "scenario": "Alternate success — sender already onboarded on Eko, KYC pending",
           "statusCode": 200,
           "example": {
-            "status": 1,
-            "response_status_id": 17,
-            "message": "User wallet already exists",
-            "response_type_id": 1388,
-            "data": {}
+            "status": 0,
+            "response_status_id": 0,
+            "message": "Wallet opened successfully.",
+            "response_type_id": 300,
+            "data": {
+              "customer_id_type": "mobile_number",
+              "state_desc": "Non-Kyc",
+              "state": "2",
+              "customer_id": "9002331157"
+            }
           }
         }
       ],
-      "responseTypes": []
+      "responseTypes": [
+        {
+          "id": 2134,
+          "meaning": "Onboarded, KYC pending — proceed to Sender eKYC",
+          "next": "dmt-fino-sender-ekyc"
+        },
+        {
+          "id": 300,
+          "meaning": "Already onboarded, KYC pending — re-check stage with Get Sender Profile",
+          "next": "dmt-get-sender"
+        },
+        {
+          "id": 309,
+          "meaning": "Already onboarded on Fino — KYC complete, proceed to Recipients",
+          "next": "dmt-get-recipients"
+        }
+      ]
     },
     {
       "slug": "dmt-fino-sender-ekyc",
@@ -656,7 +726,7 @@
       "summary": "Initiate biometric Aadhaar eKYC to verify and upgrade a DMT sender's account.",
       "category": "bc",
       "relevance": "M",
-      "description": "Performs biometric eKYC using fingerprint data linked to the sender's Aadhaar number. Requires a compatible RD-service device; the PID XML is captured at the agent's terminal and submitted with the RSA-encrypted Aadhaar number (include the `wadh` value when generating the PID). On success the system dispatches an OTP for confirmation; call Validate eKYC OTP next. A successful eKYC upgrades the sender's monthly limit from ₹5,000 to ₹25,000.",
+      "description": "Performs biometric eKYC using fingerprint data linked to the sender's Aadhaar number. Requires a compatible RD-service device; the PID XML is captured at the agent's terminal and submitted with the sender's Aadhaar number (include the `wadh` value when generating the PID). On success the system dispatches an OTP for confirmation; call Validate eKYC OTP next. A successful eKYC upgrades the sender's monthly limit from ₹5,000 to ₹25,000.\n\nTo capture the `piddata` PID block with an RDService-compliant fingerprint scanner, see the [Aadhaar Biometric Authentication guide](/docs/aadhaar-biometric-rdservice).",
       "bestFor": "KYC upgrade for new senders to raise monthly transfer limits.",
       "docsUrl": "https://eps.eko.in/docs/dmt-fino-sender-ekyc",
       "headers": [
@@ -768,24 +838,31 @@
           "type": "object",
           "description": "API-specific response payload.",
           "children": [
+            {
+              "name": "user_code",
+              "type": "string",
+              "description": "Agent user code associated with the KYC request.",
+              "example": "10472151"
+            },
+            {
+              "name": "intent_id",
+              "type": "string",
+              "description": "Reserved intent identifier (empty in the standard flow).",
+              "example": ""
+            },
             {
               "name": "kyc_request_id",
               "type": "string",
               "description": "Unique identifier for this KYC request. Required for the Validate eKYC OTP step.",
               "imp": true,
-              "example": "KYC20240101001"
+              "example": "9332126"
             },
             {
               "name": "otp_ref_id",
               "type": "string",
-              "description": "Reference ID for the OTP sent to the sender's Aadhaar-linked mobile.",
-              "example": "OTPREF20240101001"
-            },
-            {
-              "name": "mobile",
-              "type": "string",
-              "description": "Masked mobile number to which the OTP was dispatched.",
-              "example": "XXXXXXX789"
+              "description": "Reference ID for the OTP sent to the sender's Aadhaar-linked mobile. Required for the Validate eKYC OTP step.",
+              "imp": true,
+              "example": "666803844"
             }
           ]
         }
@@ -793,28 +870,50 @@
       "sampleSuccessResponse": {
         "status": 0,
         "response_status_id": 0,
-        "message": "OTP sent for eKYC verification",
-        "response_type_id": 1388,
+        "message": "Validate the OTP",
+        "response_type_id": 2129,
         "data": {
-          "kyc_request_id": "KYC20240101001",
-          "otp_ref_id": "OTPREF20240101001",
-          "mobile": "XXXXXXX789"
+          "user_code": "10472151",
+          "intent_id": "",
+          "kyc_request_id": "9332126",
+          "otp_ref_id": "666803844"
         }
       },
       "errorScenarios": [
         {
-          "scenario": "Sender already KYC verified — no further upgrade needed",
+          "scenario": "Incorrect PID data — eKYC verification failed",
           "statusCode": 200,
           "example": {
-            "status": 1,
-            "response_status_id": 585,
-            "message": "Customer already KYC approved",
-            "response_type_id": 1388,
-            "data": {}
+            "status": 2135,
+            "response_status_id": 1,
+            "message": "Customer KYC Pending",
+            "response_type_id": 2135,
+            "data": {
+              "description": "K-100 EKYC Verification failed"
+            }
+          }
+        },
+        {
+          "scenario": "Sender already has an existing relationship with the bank",
+          "statusCode": 200,
+          "example": {
+            "status": 2135,
+            "response_status_id": 1,
+            "message": "Customer KYC Pending",
+            "response_type_id": 2135,
+            "data": {
+              "description": "Sorry! Since you already have an existing relationship with the bank"
+            }
           }
         }
       ],
-      "responseTypes": []
+      "responseTypes": [
+        {
+          "id": 2129,
+          "meaning": "OTP sent — proceed to Validate eKYC OTP",
+          "next": "dmt-fino-validate-ekyc-otp"
+        }
+      ]
     },
     {
       "slug": "dmt-fino-validate-ekyc-otp",
@@ -948,24 +1047,11 @@
           "description": "API-specific response payload.",
           "children": [
             {
-              "name": "customer_id",
+              "name": "user_code",
               "type": "string",
-              "description": "Sender's mobile number (echoed back).",
-              "example": "9123456789"
-            },
-            {
-              "name": "kyc_verified",
-              "type": "boolean",
-              "description": "Confirms successful eKYC completion.",
-              "imp": true,
-              "example": true
-            },
-            {
-              "name": "available_limit",
-              "type": "number",
-              "description": "Updated monthly transfer limit after KYC (in INR).",
+              "description": "Agent user code for the now KYC-verified sender. eKYC is complete on success.",
               "imp": true,
-              "example": 25000
+              "example": "10472151"
             }
           ]
         }
@@ -973,35 +1059,50 @@
       "sampleSuccessResponse": {
         "status": 0,
         "response_status_id": 0,
-        "message": "eKYC verification successful",
-        "response_type_id": 1388,
+        "message": "Customer Registration Completed",
+        "response_type_id": 2132,
         "data": {
-          "customer_id": "9123456789",
-          "kyc_verified": true,
-          "available_limit": 25000
+          "user_code": "10472151"
         }
       },
       "errorScenarios": [
+        {
+          "scenario": "Sender already registered",
+          "statusCode": 200,
+          "example": {
+            "status": 2131,
+            "response_status_id": 1,
+            "message": "Validate OTP Failed",
+            "response_type_id": 2131,
+            "data": {
+              "description": "Customer Already registred"
+            }
+          }
+        },
         {
           "scenario": "Incorrect OTP entered",
           "statusCode": 200,
           "example": {
-            "status": 1,
+            "status": 2131,
             "response_status_id": 302,
-            "message": "Wrong OTP",
-            "response_type_id": 1388,
-            "data": {}
+            "message": "Validate OTP Failed",
+            "response_type_id": 2131,
+            "data": {
+              "description": "Wrong OTP"
+            }
           }
         },
         {
           "scenario": "OTP has expired",
           "statusCode": 200,
           "example": {
-            "status": 1,
+            "status": 2131,
             "response_status_id": 303,
-            "message": "OTP expired",
-            "response_type_id": 1388,
-            "data": {}
+            "message": "Validate OTP Failed",
+            "response_type_id": 2131,
+            "data": {
+              "description": "OTP expired"
+            }
           }
         }
       ],
@@ -1109,59 +1210,106 @@
           "description": "API-specific response payload.",
           "children": [
             {
-              "name": "count",
+              "name": "pan_required",
               "type": "number",
-              "description": "Total number of recipients registered under this sender.",
+              "description": "PAN requirement flag for the sender.",
               "example": 2
             },
             {
-              "name": "recipient",
+              "name": "remaining_limit_before_pan_required",
+              "type": "number",
+              "description": "Amount the sender can still transfer before PAN becomes mandatory (INR).",
+              "example": 50000
+            },
+            {
+              "name": "recipient_list",
               "type": "array",
-              "description": "List of registered beneficiaries.",
+              "description": "Registered beneficiaries for this sender.",
               "children": [
                 {
                   "name": "recipient_id",
                   "type": "number",
-                  "description": "Unique identifier for the recipient. Used as input to Send OTP and Initiate Transfer APIs.",
+                  "description": "Identifier used in the Send Transaction OTP and Execute Transaction APIs.",
                   "imp": true,
-                  "example": 98765
+                  "example": 117015428
+                },
+                {
+                  "name": "beneficiary_id",
+                  "type": "number",
+                  "description": "Beneficiary identifier (mirrors recipient_id).",
+                  "example": 117015428
+                },
+                {
+                  "name": "bank_recipient_id",
+                  "type": "number",
+                  "description": "Bank-side recipient identifier.",
+                  "example": 117015428
                 },
                 {
                   "name": "recipient_name",
                   "type": "string",
-                  "description": "Full name of the beneficiary.",
+                  "description": "Beneficiary name.",
                   "imp": true,
-                  "example": "Sunil Sharma"
+                  "example": "yashwant basnett"
                 },
                 {
-                  "name": "account",
+                  "name": "recipient_mobile",
+                  "type": "string",
+                  "description": "Beneficiary mobile number.",
+                  "example": "9002331157"
+                },
+                {
+                  "name": "bank",
                   "type": "string",
-                  "description": "Beneficiary's bank account number.",
-                  "example": "012345678901"
+                  "description": "Beneficiary bank name.",
+                  "example": "State Bank of India"
                 },
                 {
                   "name": "ifsc",
                   "type": "string",
-                  "description": "IFSC code of the beneficiary's bank branch.",
-                  "example": "SBIN0001234"
+                  "description": "Beneficiary bank IFSC code.",
+                  "example": "SBIN0007515"
                 },
                 {
-                  "name": "bank_name",
+                  "name": "account",
                   "type": "string",
-                  "description": "Name of the beneficiary's bank.",
-                  "example": "State Bank of India"
+                  "description": "Beneficiary bank account number.",
+                  "example": "38759149196"
                 },
                 {
-                  "name": "recipient_mobile",
+                  "name": "account_type",
                   "type": "string",
-                  "description": "Mobile number registered for the recipient.",
-                  "example": "9988776655"
+                  "description": "Type of the beneficiary account.",
+                  "example": "Bank Account"
+                },
+                {
+                  "name": "ifsc_status",
+                  "type": "number",
+                  "description": "Whether the IFSC is valid/active (1 = valid).",
+                  "example": 1
                 },
                 {
                   "name": "is_verified",
-                  "type": "boolean",
-                  "description": "Whether the recipient's account has been penny-drop verified.",
-                  "example": true
+                  "type": "number",
+                  "description": "Whether the account has been penny-drop verified (1 = verified).",
+                  "example": 0
+                },
+                {
+                  "name": "is_otp_required",
+                  "type": "string",
+                  "description": "Whether an OTP is required to transact to this recipient.",
+                  "example": "0"
+                },
+                {
+                  "name": "pipes",
+                  "type": "object",
+                  "description": "Available settlement pipes for this recipient, keyed by pipe id.",
+                  "example": {
+                    "3": {
+                      "pipe": 3,
+                      "status": 1
+                    }
+                  }
                 }
               ]
             }
@@ -1172,33 +1320,71 @@
         "status": 0,
         "response_status_id": 0,
         "message": "Success",
-        "response_type_id": 1388,
+        "response_type_id": 23,
         "data": {
-          "count": 2,
-          "recipient": [
+          "pan_required": 2,
+          "recipient_list": [
             {
-              "recipient_id": 98765,
-              "recipient_name": "Sunil Sharma",
-              "account": "012345678901",
-              "ifsc": "SBIN0001234",
-              "bank_name": "State Bank of India",
-              "recipient_mobile": "9988776655",
-              "is_verified": true
-            },
-            {
-              "recipient_id": 98766,
-              "recipient_name": "Priya Verma",
-              "account": "987654321098",
-              "ifsc": "HDFC0002345",
-              "bank_name": "HDFC Bank",
-              "recipient_mobile": "9811223344",
-              "is_verified": true
+              "recipient_id": 117015428,
+              "beneficiary_id": 117015428,
+              "bank_recipient_id": 117015428,
+              "recipient_name": "yashwant basnett",
+              "recipient_mobile": "9002331157",
+              "bank": "State Bank of India",
+              "ifsc": "SBIN0007515",
+              "account": "38759149196",
+              "account_type": "Bank Account",
+              "ifsc_status": 1,
+              "is_verified": 0,
+              "is_otp_required": "0",
+              "pipes": {
+                "3": {
+                  "pipe": 3,
+                  "status": 1
+                }
+              }
             }
-          ]
+          ],
+          "remaining_limit_before_pan_required": 50000
         }
       },
-      "errorScenarios": [],
-      "responseTypes": []
+      "errorScenarios": [
+        {
+          "scenario": "No recipients registered yet — add one",
+          "statusCode": 200,
+          "example": {
+            "status": 0,
+            "response_status_id": -1,
+            "message": "No recepients found",
+            "response_type_id": 22
+          }
+        },
+        {
+          "scenario": "Customer does not exist in system",
+          "statusCode": 200,
+          "example": {
+            "status": 463,
+            "response_status_id": 1,
+            "message": "customer_id does not exist in system",
+            "response_type_id": -1,
+            "invalid_params": {
+              "customer_id": "Customer does not exist in System"
+            }
+          }
+        }
+      ],
+      "responseTypes": [
+        {
+          "id": 22,
+          "meaning": "No recipients — add one before transacting",
+          "next": "dmt-add-recipient"
+        },
+        {
+          "id": 23,
+          "meaning": "Recipients found — proceed to Send Transaction OTP",
+          "next": "dmt-send-otp"
+        }
+      ]
     },
     {
       "slug": "dmt-add-recipient",
@@ -1206,11 +1392,11 @@
       "productName": "Domestic Money Transfer (DMT)",
       "name": "Add Recipient",
       "method": "POST",
-      "path": "/customer/payment/dmt-fino/sender/{customer_id}/recipient1",
+      "path": "/customer/payment/dmt-fino/sender/{customer_id}/recipient",
       "summary": "Register a new beneficiary under a sender's DMT-Fino account.",
       "category": "bc",
       "relevance": "M",
-      "description": "Adds a new beneficiary to the sender's saved recipients list. Provide the recipient's full name, bank account number, IFSC code, and mobile number. The bank_id identifies the destination bank (fetch from the bank list if needed). On success a recipient_id is returned; use it in Send OTP and Initiate Transfer. The system may validate the account via penny-drop before activating the recipient.",
+      "description": "Adds a new beneficiary to the sender's saved recipients list. Provide the recipient's full name, bank account number, IFSC code, and mobile number. On success a recipient_id is returned; use it in Send Transaction OTP and Execute Transaction. The system may validate the account via penny-drop before activating the recipient.",
       "bestFor": "Adding a new beneficiary before a first-time transfer.",
       "docsUrl": "https://eps.eko.in/docs/dmt-add-recipient",
       "headers": [
@@ -1270,19 +1456,19 @@
           "in": "path"
         },
         {
-          "name": "recipient_name",
+          "name": "recipient_mobile",
           "type": "string",
           "required": true,
-          "description": "Full name of the beneficiary as it appears on their bank account.",
-          "example": "Sunil Sharma",
+          "description": "Beneficiary's 10-digit mobile number.",
+          "example": "9002331157",
           "in": "body"
         },
         {
-          "name": "account",
+          "name": "recipient_name",
           "type": "string",
           "required": true,
-          "description": "Beneficiary's bank account number.",
-          "example": "012345678901",
+          "description": "Full name of the beneficiary as it appears on their bank account.",
+          "example": "yashwant basnett",
           "in": "body"
         },
         {
@@ -1290,43 +1476,25 @@
           "type": "string",
           "required": true,
           "description": "IFSC code of the beneficiary's bank branch.",
-          "example": "SBIN0001234",
+          "example": "SBIN0007515",
           "in": "body"
         },
         {
-          "name": "bank_id",
-          "type": "number",
-          "required": true,
-          "description": "Unique bank identifier from Eko's bank list API.",
-          "example": 20,
-          "in": "body"
-        },
-        {
-          "name": "recipient_mobile",
-          "type": "string",
-          "required": true,
-          "description": "10-digit mobile number of the recipient.",
-          "example": "9988776655",
-          "in": "body"
-        },
-        {
-          "name": "recipient_type",
+          "name": "account",
           "type": "string",
           "required": true,
-          "description": "Recipient type. Fixed value: \"3\" for DMT-Fino bank account recipients.",
-          "example": "3",
+          "description": "Beneficiary's bank account number.",
+          "example": "38759149196",
           "in": "body"
         }
       ],
       "sampleRequest": {
         "initiator_id": "9962981729",
         "client_ref_id": "2026010100123456789",
-        "recipient_name": "Sunil Sharma",
-        "account": "012345678901",
-        "ifsc": "SBIN0001234",
-        "bank_id": 20,
-        "recipient_mobile": "9988776655",
-        "recipient_type": "3"
+        "recipient_mobile": "9002331157",
+        "recipient_name": "yashwant basnett",
+        "ifsc": "SBIN0007515",
+        "account": "38759149196"
       },
       "responseFields": [
         {
@@ -1361,34 +1529,39 @@
             {
               "name": "recipient_id",
               "type": "number",
-              "description": "Unique identifier assigned to the newly added recipient. Required for Send OTP and Initiate Transfer.",
+              "description": "Unique identifier assigned to the newly added recipient. Required for Send Transaction OTP and Execute Transaction.",
               "imp": true,
-              "example": 98765
+              "example": 117015428
             },
             {
-              "name": "recipient_name",
+              "name": "customer_id",
               "type": "string",
-              "description": "Name of the recipient as registered.",
-              "imp": true,
-              "example": "Sunil Sharma"
+              "description": "Sender's mobile number (echoed back).",
+              "example": "9155927131"
             },
             {
-              "name": "account",
+              "name": "recipient_mobile",
               "type": "string",
-              "description": "Bank account number of the recipient.",
-              "example": "012345678901"
+              "description": "Beneficiary mobile number (echoed back).",
+              "example": "9002331157"
             },
             {
-              "name": "ifsc",
+              "name": "initiator_id",
               "type": "string",
-              "description": "IFSC code of the recipient's bank branch.",
-              "example": "SBIN0001234"
+              "description": "Partner initiator ID (echoed back).",
+              "example": "<initiator_id>"
             },
             {
-              "name": "is_verified",
-              "type": "boolean",
-              "description": "Whether the account passed penny-drop verification.",
-              "example": false
+              "name": "pipes",
+              "type": "object",
+              "description": "Available settlement pipes for the new recipient.",
+              "example": {}
+            },
+            {
+              "name": "otp_ref_id",
+              "type": "string",
+              "description": "OTP reference placeholder (empty on add).",
+              "example": ""
             }
           ]
         }
@@ -1396,14 +1569,15 @@
       "sampleSuccessResponse": {
         "status": 0,
         "response_status_id": 0,
-        "message": "Recipient added successfully",
-        "response_type_id": 1388,
+        "message": "Success!Please transact using Recipientid",
+        "response_type_id": 43,
         "data": {
-          "recipient_id": 98765,
-          "recipient_name": "Sunil Sharma",
-          "account": "012345678901",
-          "ifsc": "SBIN0001234",
-          "is_verified": false
+          "recipient_id": 117015428,
+          "customer_id": "9155927131",
+          "recipient_mobile": "9002331157",
+          "initiator_id": "<initiator_id>",
+          "pipes": {},
+          "otp_ref_id": ""
         }
       },
       "errorScenarios": [
@@ -1411,15 +1585,34 @@
           "scenario": "Recipient already registered for this sender",
           "statusCode": 200,
           "example": {
-            "status": 1,
-            "response_status_id": 342,
+            "status": 342,
+            "response_status_id": 1,
             "message": "Recipient already registered",
-            "response_type_id": 1388,
+            "response_type_id": -1,
             "data": {}
           }
+        },
+        {
+          "scenario": "Customer does not exist in system",
+          "statusCode": 200,
+          "example": {
+            "status": 463,
+            "response_status_id": 1,
+            "message": "customer_id does not exist in system",
+            "response_type_id": -1,
+            "invalid_params": {
+              "customer_id": "Customer does not exist in System"
+            }
+          }
         }
       ],
-      "responseTypes": []
+      "responseTypes": [
+        {
+          "id": 43,
+          "meaning": "Recipient added — proceed to Send Transaction OTP",
+          "next": "dmt-send-otp"
+        }
+      ]
     },
     {
       "slug": "dmt-send-otp",
@@ -1547,15 +1740,9 @@
             {
               "name": "otp_ref_id",
               "type": "string",
-              "description": "Reference ID for the OTP sent. Must be passed to Initiate Transfer along with the customer-entered OTP.",
+              "description": "Reference ID for the OTP sent. Must be passed to Execute Transaction along with the customer-entered OTP.",
               "imp": true,
-              "example": "TXNOTP20240101001"
-            },
-            {
-              "name": "mobile",
-              "type": "string",
-              "description": "Masked mobile number to which the OTP was sent (for display to agent/customer).",
-              "example": "XXXXXX6789"
+              "example": "666902416"
             }
           ]
         }
@@ -1563,11 +1750,10 @@
       "sampleSuccessResponse": {
         "status": 0,
         "response_status_id": 0,
-        "message": "OTP sent successfully",
-        "response_type_id": 1388,
+        "message": "Send OTP",
+        "response_type_id": 2133,
         "data": {
-          "otp_ref_id": "TXNOTP20240101001",
-          "mobile": "XXXXXX6789"
+          "otp_ref_id": "666902416"
         }
       },
       "errorScenarios": [
@@ -1575,15 +1761,45 @@
           "scenario": "Sender monthly limit exhausted",
           "statusCode": 200,
           "example": {
-            "status": 1,
-            "response_status_id": 945,
+            "status": 36,
+            "response_type_id": 36,
+            "response_status_id": 1,
             "message": "Sender/beneficiary monthly limit exhausted",
-            "response_type_id": 1388,
             "data": {}
           }
+        },
+        {
+          "scenario": "Beneficiary monthly limit exhausted",
+          "statusCode": 200,
+          "example": {
+            "status": 945,
+            "response_type_id": 945,
+            "response_status_id": 1,
+            "message": "Beneficiary monthly limit exhausted",
+            "data": {}
+          }
+        },
+        {
+          "scenario": "Customer does not exist in system",
+          "statusCode": 200,
+          "example": {
+            "status": 463,
+            "response_status_id": 1,
+            "message": "customer_id does not exist in system",
+            "response_type_id": -1,
+            "invalid_params": {
+              "customer_id": "Customer does not exist in System"
+            }
+          }
         }
       ],
-      "responseTypes": []
+      "responseTypes": [
+        {
+          "id": 2133,
+          "meaning": "Transaction OTP sent — proceed to Execute Transaction",
+          "next": "dmt-initiate-transfer"
+        }
+      ]
     },
     {
       "slug": "dmt-initiate-transfer",
@@ -1595,7 +1811,7 @@
       "summary": "Execute a DMT-Fino money transfer after OTP verification.",
       "category": "bc",
       "relevance": "M",
-      "description": "The final and only financial step in the DMT flow. Debits the agent's wallet and initiates an IMPS transfer to the registered recipient's bank account. Requires the OTP and otp_ref_id from Send Transaction OTP and the merchant's GPS coordinates (latlong). The response returns a tid (Eko transaction ID) and the banking UTR for the IMPS transaction. Always poll Get Transaction Status if tx_status is 2 (Awaited).",
+      "description": "The final and only financial step in the DMT flow. Debits the agent's wallet and initiates an IMPS transfer to the registered recipient's bank account after OTP validation. Requires the otp and otp_ref_id from Send Transaction OTP plus a unique client_ref_id per attempt for idempotency and reconciliation. The response returns tid (Eko transaction ID) and bank_ref_num (the IMPS RRN/UTR). Use a fresh otp_ref_id and OTP for each attempt — a consumed OTP is rejected — and always persist tid, bank_ref_num, and your client_ref_id to reconcile before retrying.",
       "bestFor": "Executing the actual money transfer — the only money-debit step in the DMT flow.",
       "docsUrl": "https://eps.eko.in/docs/dmt-initiate-transfer",
       "financial": true,
@@ -1639,28 +1855,20 @@
           "example": "9962981729",
           "in": "body"
         },
-        {
-          "name": "client_ref_id",
-          "type": "string",
-          "required": false,
-          "description": "Unique reference ID per API call, generated by your system (max 20 characters).",
-          "example": "2026010100123456789",
-          "in": "body"
-        },
         {
           "name": "recipient_id",
           "type": "number",
           "required": true,
           "description": "Unique recipient ID from Add Recipient or Get Recipients.",
-          "example": 98765,
+          "example": 117015428,
           "in": "body"
         },
         {
           "name": "amount",
           "type": "number",
           "required": true,
-          "description": "Transfer amount in INR (must match the amount sent to Send OTP).",
-          "example": 500,
+          "description": "Transfer amount in INR (must match the amount sent to Send Transaction OTP).",
+          "example": 100,
           "in": "body"
         },
         {
@@ -1668,7 +1876,7 @@
           "type": "string",
           "required": true,
           "description": "Sender's 10-digit mobile number.",
-          "example": "9123456789",
+          "example": "9155927131",
           "in": "body"
         },
         {
@@ -1676,7 +1884,7 @@
           "type": "string",
           "required": true,
           "description": "OTP entered by the customer, received on their registered mobile.",
-          "example": "251834",
+          "example": "4702",
           "in": "body"
         },
         {
@@ -1684,72 +1892,26 @@
           "type": "string",
           "required": true,
           "description": "OTP reference ID from the Send Transaction OTP response.",
-          "example": "TXNOTP20240101001",
-          "in": "body"
-        },
-        {
-          "name": "latlong",
-          "type": "string",
-          "required": true,
-          "description": "GPS coordinates of the agent/merchant's device at the time of transaction (required for regulatory compliance).",
-          "example": "28.6139,77.2090",
-          "in": "body"
-        },
-        {
-          "name": "state",
-          "type": "string",
-          "required": true,
-          "description": "Fixed value: \"1\".",
-          "example": "1",
+          "example": "667007109",
           "in": "body"
         },
         {
-          "name": "recipient_id_type",
+          "name": "client_ref_id",
           "type": "string",
           "required": true,
-          "description": "Fixed value: \"1\" for bank account recipients.",
-          "example": "1",
-          "in": "body"
-        },
-        {
-          "name": "channel",
-          "type": "number",
-          "required": false,
-          "description": "Transfer channel. Fixed value: 2 (IMPS). Defaults to 2.",
-          "example": 2,
-          "in": "body"
-        },
-        {
-          "name": "currency",
-          "type": "string",
-          "required": false,
-          "description": "Currency code. Defaults to \"INR\".",
-          "example": "INR",
-          "in": "body"
-        },
-        {
-          "name": "timestamp",
-          "type": "string",
-          "required": false,
-          "description": "ISO 8601 request timestamp.",
-          "example": "2024-01-01T10:30:00Z",
+          "description": "Unique partner reference for this transaction (idempotency & reconciliation). Use a fresh value per attempt.",
+          "example": "<unique_client_ref_id>",
           "in": "body"
         }
       ],
       "sampleRequest": {
         "initiator_id": "9962981729",
-        "client_ref_id": "2026010100123456789",
-        "recipient_id": 98765,
-        "amount": 500,
-        "customer_id": "9123456789",
-        "otp": "251834",
-        "otp_ref_id": "TXNOTP20240101001",
-        "latlong": "28.6139,77.2090",
-        "state": "1",
-        "recipient_id_type": "1",
-        "channel": 2,
-        "currency": "INR",
-        "timestamp": "2024-01-01T10:30:00Z"
+        "recipient_id": 117015428,
+        "amount": 100,
+        "customer_id": "9155927131",
+        "otp": "4702",
+        "otp_ref_id": "667007109",
+        "client_ref_id": "<unique_client_ref_id>"
       },
       "responseFields": [
         {
@@ -1793,157 +1955,248 @@
           "type": "object",
           "description": "API-specific response payload.",
           "children": [
+            {
+              "name": "tx_status",
+              "type": "string",
+              "description": "Transaction state within the data block: 0=Success, 1=Fail, 2=Awaited.",
+              "imp": true,
+              "example": "0"
+            },
+            {
+              "name": "txstatus_desc",
+              "type": "string",
+              "description": "Human-readable transaction status.",
+              "example": "Success"
+            },
             {
               "name": "tid",
               "type": "string",
-              "description": "Eko's internal transaction ID. Use this for status enquiries and reconciliation.",
+              "description": "Eko's internal transaction ID. Store for reconciliation and support queries.",
               "imp": true,
-              "example": "2309876543"
+              "example": "3570311831"
             },
             {
-              "name": "utrnumber",
+              "name": "bank_ref_num",
               "type": "string",
-              "description": "Unique Transaction Reference (UTR) from the IMPS network — the banking-side reference number.",
+              "description": "Bank reference number (RRN / UTR) for the IMPS transaction.",
               "imp": true,
-              "example": "412345678901"
+              "example": "620415011744"
             },
             {
               "name": "amount",
-              "type": "number",
-              "description": "Amount transferred in INR.",
+              "type": "string",
+              "description": "Amount transferred (INR).",
               "imp": true,
-              "example": 500
+              "example": "100.00"
             },
             {
-              "name": "recipient_name",
+              "name": "fee",
               "type": "string",
-              "description": "Name of the beneficiary credited.",
-              "imp": true,
-              "example": "Sunil Sharma"
+              "description": "Fee charged for the transfer (INR).",
+              "example": "10.0"
             },
             {
-              "name": "account",
+              "name": "collectable_amount",
               "type": "string",
-              "description": "Beneficiary account number credited.",
-              "example": "012345678901"
+              "description": "Total collectable from the sender (amount + fee).",
+              "example": "110.0"
             },
             {
-              "name": "ifsc",
+              "name": "service_tax",
               "type": "string",
-              "description": "IFSC code of the credited bank account.",
-              "example": "SBIN0001234"
+              "description": "Service tax component on the fee (INR).",
+              "example": "1.53"
             },
             {
-              "name": "fee",
-              "type": "number",
-              "description": "Transaction fee charged (in INR).",
-              "example": 5
+              "name": "tds",
+              "type": "string",
+              "description": "Tax deducted at source on the agent's commission (INR).",
+              "example": "0.01"
             },
             {
               "name": "commission",
-              "type": "number",
-              "description": "Commission earned by the agent on this transaction (in INR).",
-              "example": 3
+              "type": "string",
+              "description": "Commission earned by the agent on this transaction (INR).",
+              "example": "0.47"
             },
             {
-              "name": "balance",
+              "name": "sender_name",
+              "type": "string",
+              "description": "Name of the sender.",
+              "example": "Rahul"
+            },
+            {
+              "name": "recipient_name",
+              "type": "string",
+              "description": "Name of the beneficiary credited.",
+              "imp": true,
+              "example": "Master YASHWANT BASNETT"
+            },
+            {
+              "name": "recipient_id",
               "type": "number",
-              "description": "Remaining wallet balance of the agent after the transaction.",
-              "example": 4495
+              "description": "Recipient identifier credited.",
+              "example": 117015428
             },
             {
-              "name": "client_ref_id",
+              "name": "bank",
               "type": "string",
-              "description": "Your system's reference ID (echoed back).",
-              "example": "REF-20240101-001"
+              "description": "Beneficiary bank name.",
+              "example": "State Bank of India"
             },
             {
-              "name": "timestamp",
+              "name": "account",
               "type": "string",
-              "description": "Server-side timestamp of the transaction.",
-              "example": "2024-01-01T10:30:05Z"
-            }
-          ]
-        }
-      ],
-      "sampleSuccessResponse": {
-        "status": 0,
-        "response_status_id": 0,
-        "message": "Transaction successful",
-        "tx_status": "0",
-        "txstatus_desc": "Success",
-        "data": {
-          "tid": "2309876543",
-          "utrnumber": "412345678901",
-          "amount": 500,
+              "description": "Beneficiary account number credited.",
+              "example": "38759149196"
+            },
+            {
+              "name": "channel_desc",
+              "type": "string",
+              "description": "Settlement channel used (e.g. IMPS).",
+              "example": "IMPS"
+            },
+            {
+              "name": "balance",
+              "type": "string",
+              "description": "Agent wallet balance after the transaction (INR).",
+              "imp": true,
+              "example": "10131.18"
+            },
+            {
+              "name": "client_ref_id",
+              "type": "string",
+              "description": "Echo of the partner reference sent in the request.",
+              "example": "<unique_client_ref_id>"
+            },
+            {
+              "name": "currency",
+              "type": "string",
+              "description": "Currency code.",
+              "example": "INR"
+            },
+            {
+              "name": "timestamp",
+              "type": "string",
+              "description": "Server-side timestamp of the transaction.",
+              "example": "2026-07-23T09:46:35.396Z"
+            }
+          ]
+        }
+      ],
+      "sampleSuccessResponse": {
+        "status": 0,
+        "response_status_id": 0,
+        "message": "Transaction successful",
+        "response_type_id": 325,
+        "data": {
           "tx_status": "0",
-          "recipient_name": "Sunil Sharma",
-          "account": "012345678901",
-          "ifsc": "SBIN0001234",
-          "fee": 5,
-          "commission": 3,
-          "balance": 4495,
-          "client_ref_id": "REF-20240101-001",
-          "timestamp": "2024-01-01T10:30:05Z"
+          "txstatus_desc": "Success",
+          "tid": "3570311831",
+          "amount": "100.00",
+          "fee": "10.0",
+          "collectable_amount": "110.0",
+          "service_tax": "1.53",
+          "tds": "0.01",
+          "commission": "0.47",
+          "sender_name": "Rahul",
+          "recipient_name": "Master YASHWANT BASNETT",
+          "recipient_id": 117015428,
+          "bank": "State Bank of India",
+          "account": "38759149196",
+          "channel_desc": "IMPS",
+          "bank_ref_num": "620415011744",
+          "balance": "10131.18",
+          "client_ref_id": "<unique_client_ref_id>",
+          "currency": "INR",
+          "timestamp": "2026-07-23T09:46:35.396Z"
         }
       },
       "errorScenarios": [
         {
-          "scenario": "Insufficient balance in agent wallet",
+          "scenario": "Transaction declined — OTP already consumed",
           "statusCode": 200,
           "example": {
-            "status": 1,
-            "response_status_id": 347,
-            "message": "Insufficient balance",
-            "tx_status": "1",
-            "txstatus_desc": "Failed",
-            "data": {}
+            "status": 55,
+            "response_status_id": 1,
+            "message": "Transaction declined. Please try after sometime.",
+            "response_type_id": 55,
+            "data": {
+              "tx_status": "1",
+              "txstatus_desc": "Failed",
+              "reason": "OTP already Consumed",
+              "amount": "100.00",
+              "tid": "3570311840",
+              "client_ref_id": "<unique_client_ref_id>",
+              "balance": "10021.64"
+            }
           }
         },
         {
-          "scenario": "Transaction pending / awaited — poll Get Transaction Status",
+          "scenario": "Transaction declined — insufficient balance in agent wallet",
           "statusCode": 200,
           "example": {
-            "status": 0,
-            "response_status_id": 0,
-            "message": "Transaction in progress",
-            "tx_status": "2",
-            "txstatus_desc": "Awaited",
+            "status": 55,
+            "response_status_id": 1,
+            "message": "Transaction declined. Please try after sometime.",
+            "response_type_id": 55,
             "data": {
-              "tid": "2309876543",
-              "amount": 500
+              "tx_status": "1",
+              "txstatus_desc": "Failed",
+              "reason": "Insufficient balance"
             }
           }
         },
         {
-          "scenario": "Wrong OTP entered",
+          "scenario": "Transaction declined — wrong OTP entered",
           "statusCode": 200,
           "example": {
-            "status": 1,
-            "response_status_id": 302,
-            "message": "Wrong OTP",
-            "tx_status": "1",
-            "txstatus_desc": "Failed",
-            "data": {}
+            "status": 55,
+            "response_status_id": 1,
+            "message": "Transaction declined. Please try after sometime.",
+            "response_type_id": 55,
+            "data": {
+              "tx_status": "1",
+              "txstatus_desc": "Failed",
+              "reason": "Wrong OTP"
+            }
           }
         },
         {
-          "scenario": "Sender monthly limit exhausted",
+          "scenario": "Transaction declined — sender monthly limit exhausted",
           "statusCode": 200,
           "example": {
-            "status": 1,
-            "response_status_id": 945,
-            "message": "Sender/beneficiary monthly limit exhausted",
-            "tx_status": "1",
-            "txstatus_desc": "Failed",
-            "data": {}
+            "status": 55,
+            "response_status_id": 1,
+            "message": "Transaction declined. Please try after sometime.",
+            "response_type_id": 55,
+            "data": {
+              "tx_status": "1",
+              "txstatus_desc": "Failed",
+              "reason": "Sender/beneficiary monthly limit exhausted"
+            }
+          }
+        },
+        {
+          "scenario": "Transaction awaited (non-final) — reconcile by tid before retrying",
+          "statusCode": 200,
+          "example": {
+            "status": 0,
+            "response_status_id": 0,
+            "message": "Transaction in progress",
+            "data": {
+              "tx_status": "2",
+              "txstatus_desc": "Awaited",
+              "tid": "3570311831",
+              "amount": "100.00"
+            }
           }
         }
       ],
       "responseTypes": []
     },
     {
-      "slug": "aeps-activate-fingpay",
+      "slug": "activate-aeps-fingpay",
       "productId": "aeps",
       "productName": "AePS Cashout",
       "name": "Activate AePS Fingpay for Agent",
@@ -1954,7 +2207,7 @@
       "relevance": "M",
       "description": "This API enables an agent (identified by their `user_code`) to use the AePS Fingpay service. It accepts the agent's biometric device model, serial number, address proofs, and KYC documents (PAN card, Aadhaar front and back) as a multipart form submission. After submission, the activation enters a 'pending' state and is approved within 2–3 business days. Only activated agents can perform AePS transactions. File uploads must be JPEG/JPG/PDF format, each under 1 MB; PNG is not accepted.\n\n> [!NOTE]\n> This API must be called after onboarding your agent using the [**Onboard User API**](/docs/onboard-user).\n\n> [!WARNING]\n> The approval may take 1-2 business days.",
       "bestFor": "Platforms onboarding BC agents and CSPs to offer AePS services for the first time",
-      "docsUrl": "https://eps.eko.in/docs/aeps-activate-fingpay",
+      "docsUrl": "https://eps.eko.in/docs/activate-aeps-fingpay",
       "headers": [
         {
           "name": "developer_key",
@@ -2383,7 +2636,7 @@
         {
           "id": 2110,
           "meaning": "Shop-type list returned successfully",
-          "next": "aeps-activate-fingpay"
+          "next": "activate-aeps-fingpay"
         }
       ]
     },
@@ -2557,12 +2810,12 @@
         {
           "id": 2127,
           "meaning": "State list returned successfully",
-          "next": "aeps-activate-fingpay"
+          "next": "activate-aeps-fingpay"
         }
       ]
     },
     {
-      "slug": "aeps-send-otp-kyc",
+      "slug": "aeps-fingpay-send-otp-kyc",
       "productId": "aeps",
       "productName": "AePS Cashout",
       "name": "Send OTP (eKYC)",
@@ -2573,7 +2826,7 @@
       "relevance": "M",
       "description": "First-time KYC follows three steps in order: `Send OTP` → `Verify OTP` → `Biometric`. On subsequent days, use the Daily KYC (biometric-only) endpoint.\n\nThis is the first step in the one-time AePS Fingpay eKYC flow. The OTP is delivered to the number passed in `customer_id`. The eKYC flow — Send OTP → Verify OTP → Biometric — must be completed once per agent before they can perform any AePS transactions. This step is a prerequisite; do not confuse it with the Daily KYC which is required on each calendar day.",
       "bestFor": "Initial one-time KYC setup for newly activated AePS Fingpay agents",
-      "docsUrl": "https://eps.eko.in/docs/aeps-send-otp-kyc",
+      "docsUrl": "https://eps.eko.in/docs/aeps-fingpay-send-otp-kyc",
       "headers": [
         {
           "name": "developer_key",
@@ -2749,12 +3002,12 @@
         {
           "id": 1600,
           "meaning": "OTP request has been sent",
-          "next": "aeps-verify-otp-kyc"
+          "next": "aeps-fingpay-verify-otp-kyc"
         }
       ]
     },
     {
-      "slug": "aeps-verify-otp-kyc",
+      "slug": "aeps-fingpay-verify-otp-kyc",
       "productId": "aeps",
       "productName": "AePS Cashout",
       "name": "Verify OTP (eKYC)",
@@ -2765,7 +3018,7 @@
       "relevance": "M",
       "description": "The second step of the one-time AePS Fingpay eKYC flow (Send OTP → Verify OTP → Biometric). Submits the OTP the agent received, together with the `otp_ref_id` and `reference_tid` returned by the Send OTP API, to validate the agent's identity before biometric capture. Aadhaar must be RSA-encrypted and Base64-encoded.",
       "bestFor": "Completing OTP validation during initial one-time agent eKYC",
-      "docsUrl": "https://eps.eko.in/docs/aeps-verify-otp-kyc",
+      "docsUrl": "https://eps.eko.in/docs/aeps-fingpay-verify-otp-kyc",
       "headers": [
         {
           "name": "developer_key",
@@ -2959,12 +3212,12 @@
         {
           "id": 1604,
           "meaning": "Validation successful",
-          "next": "aeps-biometric-ekyc"
+          "next": "aeps-fingpay-biometric-ekyc"
         }
       ]
     },
     {
-      "slug": "aeps-biometric-ekyc",
+      "slug": "aeps-fingpay-biometric-ekyc",
       "productId": "aeps",
       "productName": "AePS Cashout",
       "name": "Biometric eKYC",
@@ -2973,9 +3226,9 @@
       "summary": "Complete one-time AePS Fingpay eKYC by submitting the agent's Aadhaar and live biometric fingerprint capture.",
       "category": "bc",
       "relevance": "M",
-      "description": "The final step in the one-time AePS Fingpay eKYC flow, called after OTP verification. Submits the agent's RSA-encrypted Aadhaar and live biometric PID to UIDAI; on success the agent is eligible for AePS transactions.\n\nIf you generate the PID block with your own code rather than the RD service default, set `wadh=E0jzJ/P8UopUHAieZn8CKqS4WPMi5ZSYXgfnlfkWjrc=` alongside `fCount`, `fType` and the other attributes.",
+      "description": "The final step in the one-time AePS Fingpay eKYC flow, called after OTP verification. Submits the agent's RSA-encrypted Aadhaar and live biometric PID to UIDAI; on success the agent is eligible for AePS transactions.\n\nIf you generate the PID block with your own code rather than the RD service default, set `wadh=E0jzJ/P8UopUHAieZn8CKqS4WPMi5ZSYXgfnlfkWjrc=` alongside `fCount`, `fType` and the other attributes.\n\nTo capture the `piddata` PID block with an RDService-compliant fingerprint scanner, see the [Aadhaar Biometric Authentication guide](/docs/aadhaar-biometric-rdservice).",
       "bestFor": "Completing the mandatory one-time biometric identity verification for AePS Fingpay agents",
-      "docsUrl": "https://eps.eko.in/docs/aeps-biometric-ekyc",
+      "docsUrl": "https://eps.eko.in/docs/aeps-fingpay-biometric-ekyc",
       "headers": [
         {
           "name": "developer_key",
@@ -3170,12 +3423,12 @@
         {
           "id": 1605,
           "meaning": "eKYC successful — agent may now complete Daily KYC",
-          "next": "aeps-daily-auth"
+          "next": "aeps-fingpay-daily-auth"
         }
       ]
     },
     {
-      "slug": "aeps-daily-auth",
+      "slug": "aeps-fingpay-daily-auth",
       "productId": "aeps",
       "productName": "AePS Cashout",
       "name": "Daily KYC",
@@ -3184,9 +3437,9 @@
       "summary": "Perform the mandatory daily biometric re-verification that authorises an agent to carry out AePS transactions for the current calendar day.",
       "category": "bc",
       "relevance": "H",
-      "description": "Biometric-only re-verification for the days after the one-time eKYC — no OTP step is required. AePS Fingpay requires every agent to re-authenticate themselves biometrically at the start of each working day, before their first transaction of the day.\n\nIf this fails with reason `Please complete bank eKYC to process the transaction.`, re-run the full first-time eKYC sequence — Send OTP → Verify OTP → Biometric — before retrying.",
+      "description": "Biometric-only re-verification for the days after the one-time eKYC — no OTP step is required. AePS Fingpay requires every agent to re-authenticate themselves biometrically at the start of each working day, before their first transaction of the day.\n\nIf this fails with reason `Please complete bank eKYC to process the transaction.`, re-run the full first-time eKYC sequence — Send OTP → Verify OTP → Biometric — before retrying.\n\nTo capture the `piddata` PID block with an RDService-compliant fingerprint scanner, see the [Aadhaar Biometric Authentication guide](/docs/aadhaar-biometric-rdservice).",
       "bestFor": "Agent-side automation to trigger the daily biometric KYC at session start before serving AePS customers",
-      "docsUrl": "https://eps.eko.in/docs/aeps-daily-auth",
+      "docsUrl": "https://eps.eko.in/docs/aeps-fingpay-daily-auth",
       "headers": [
         {
           "name": "developer_key",
@@ -3271,7 +3524,7 @@
           "name": "piddata",
           "type": "string",
           "required": true,
-          "description": "PID XML string from the UIDAI-certified biometric device (fType=2, Data type='X', mc in DeviceInfo). This represents the agent's own fingerprint, not the customer's. If you generate the PID block yourself, it must carry `wadh=E0jzJ/P8UopUHAieZn8CKqS4WPMi5ZSYXgfnlfkWjrc=`.",
+          "description": "PID XML string from the UIDAI-certified biometric device (fType=2, Data type='X', mc in DeviceInfo). This represents the agent's own fingerprint, not the customer's. If you generate the PID block yourself, the value of `wadh` must be blank/empty for Daily KYC.",
           "example": "<?xml version='1.0'?><PidData><Data type='X'>...</Data><DeviceInfo mc='...' /></PidData>",
           "in": "body"
         },
@@ -3395,12 +3648,12 @@
         {
           "id": 1714,
           "meaning": "Daily KYC failed — if `data.reason` is 'Please complete bank eKYC to process the transaction.', re-run the full eKYC from Send OTP",
-          "next": "aeps-send-otp-kyc"
+          "next": "aeps-fingpay-send-otp-kyc"
         }
       ]
     },
     {
-      "slug": "aeps-cash-withdrawal",
+      "slug": "aeps-fingpay-cash-withdrawal",
       "productId": "aeps",
       "productName": "AePS Cashout",
       "name": "AePS Cash Withdrawal",
@@ -3409,9 +3662,9 @@
       "summary": "Withdraw cash from any Aadhaar-linked bank account using biometric fingerprint authentication — no card or PIN required.",
       "category": "bc",
       "relevance": "H",
-      "description": "Allows a customer to withdraw cash from their bank account at an agent/BC point by providing their Aadhaar number and a live fingerprint scan. The agent's biometric device captures a PID XML blob which is passed verbatim to this API. The customer's Aadhaar is RSA-encrypted before transmission. Requires the agent to have completed AePS Fingpay activation, the one-time eKYC (Send OTP → Verify OTP → Biometric), and the Daily KYC for the current day.",
+      "description": "Allows a customer to withdraw cash from their bank account at an agent/BC point by providing their Aadhaar number and a live fingerprint scan. The agent's biometric device captures a PID XML blob which is passed verbatim to this API. The customer's Aadhaar is RSA-encrypted before transmission. Requires the agent to have completed AePS Fingpay activation, the one-time eKYC (Send OTP → Verify OTP → Biometric), and the Daily KYC for the current day.\n\nTo capture the `piddata` PID block with an RDService-compliant fingerprint scanner, see the [Aadhaar Biometric Authentication guide](/docs/aadhaar-biometric-rdservice).",
       "bestFor": "BC agents, CSPs, and kirana-store banking points enabling cardless cash withdrawal for rural customers",
-      "docsUrl": "https://eps.eko.in/docs/aeps-cash-withdrawal",
+      "docsUrl": "https://eps.eko.in/docs/aeps-fingpay-cash-withdrawal",
       "financial": true,
       "headers": [
         {
@@ -3874,7 +4127,7 @@
       ]
     },
     {
-      "slug": "aeps-balance-enquiry",
+      "slug": "aeps-fingpay-balance-enquiry",
       "productId": "aeps",
       "productName": "AePS Cashout",
       "name": "AePS Balance Enquiry",
@@ -3883,9 +4136,9 @@
       "summary": "Check a customer's bank account balance using Aadhaar number and biometric fingerprint — no card or PIN required.",
       "category": "bc",
       "relevance": "L",
-      "description": "Retrieves the real-time account balance from any Aadhaar-linked bank. Uses the dedicated `balance-enquiry` endpoint — the request shape matches Cash Withdrawal without the `amount` field. No money movement occurs and no debit takes place. The agent must have completed AePS Fingpay activation and the current-day daily authentication before calling this API.",
+      "description": "Retrieves the real-time account balance from any Aadhaar-linked bank. Uses the dedicated `balance-enquiry` endpoint — the request shape matches Cash Withdrawal without the `amount` field. No money movement occurs and no debit takes place. The agent must have completed AePS Fingpay activation and the current-day daily authentication before calling this API.\n\nTo capture the `piddata` PID block with an RDService-compliant fingerprint scanner, see the [Aadhaar Biometric Authentication guide](/docs/aadhaar-biometric-rdservice).",
       "bestFor": "Agent-assisted balance checks for rural customers without smartphone or internet access",
-      "docsUrl": "https://eps.eko.in/docs/aeps-balance-enquiry",
+      "docsUrl": "https://eps.eko.in/docs/aeps-fingpay-balance-enquiry",
       "financial": true,
       "headers": [
         {
@@ -4224,7 +4477,7 @@
       ]
     },
     {
-      "slug": "aeps-mini-statement",
+      "slug": "aeps-fingpay-mini-statement",
       "productId": "aeps",
       "productName": "AePS Cashout",
       "name": "AePS Mini Statement",
@@ -4233,9 +4486,9 @@
       "summary": "Retrieve the last few transactions from an Aadhaar-linked bank account via biometric authentication.",
       "category": "bc",
       "relevance": "L",
-      "description": "Fetches a mini statement (typically the last 5–10 transactions) from a customer's bank account by authenticating through Aadhaar biometrics. Uses the dedicated `mini-statement` endpoint — the request shape matches Balance Enquiry (no `amount`). No money movement occurs. The response includes a list of recent debit/credit transactions with amounts and dates. Useful for customers who want to verify recent activity at an agent point without visiting a branch.",
+      "description": "Fetches a mini statement (typically the last 5–10 transactions) from a customer's bank account by authenticating through Aadhaar biometrics. Uses the dedicated `mini-statement` endpoint — the request shape matches Balance Enquiry (no `amount`). No money movement occurs. The response includes a list of recent debit/credit transactions with amounts and dates. Useful for customers who want to verify recent activity at an agent point without visiting a branch.\n\nTo capture the `piddata` PID block with an RDService-compliant fingerprint scanner, see the [Aadhaar Biometric Authentication guide](/docs/aadhaar-biometric-rdservice).",
       "bestFor": "BC agents providing passbook-equivalent transaction history to Aadhaar-linked account holders",
-      "docsUrl": "https://eps.eko.in/docs/aeps-mini-statement",
+      "docsUrl": "https://eps.eko.in/docs/aeps-fingpay-mini-statement",
       "financial": true,
       "headers": [
         {
@@ -6523,7 +6776,7 @@
       "summary": "Check the current status of a BBPS bill payment by Eko TID or your client reference ID.",
       "category": "payment",
       "relevance": "M",
-      "description": "Generic transaction enquiry endpoint that works for all Eko transaction types including BBPS. Pass either the Eko `tid` or your `client_ref_id` as the path parameter. Returns the current `tx_status` (0=Success, 1=Fail, 2=Awaited, 3=Refund Pending, 4=Refunded, 5=On Hold), the operator reference, and the debited amount. Use this to handle `tx_status=2` (Response Awaited) cases from Pay Bill. A timeout or slow bank response is not a failure — re-query with your `client_ref_id` to get the real status instead of retrying the payment.",
+      "description": "Get the current status of a transaction using either Eko's TID or your own\n`client_ref_id`. This is a generic inquiry endpoint — it works for all Eko\nfinancial transaction types (fund transfer, BBPS, AePS settlement, NEFT, and\nmore).\n\nThe transaction reference goes in the URL path. Pass an Eko **TID as-is**; to\nlook up by your **`client_ref_id`, prefix it** with `client_ref_id:`:\n- By TID — `/tools/reference/transaction/<TID>`\n- By client_ref_id — `/tools/reference/transaction/client_ref_id:<your client_ref_id>`\n\n> [!NOTE]\n> **Examples**\n>\n> To check the status of a transaction using TID `2886601782`, call\n> `/tools/reference/transaction/2886601782`.\n>\n> If you never received Eko's TID (say, due to a network timeout) but sent your\n> own unique reference `567890`, look it up with\n> `/tools/reference/transaction/client_ref_id:567890`.\n\n> [!WARNING]\n> **Transaction timeout**\n>\n> A transaction can time out for many reasons — a slow partner-bank response, or\n> network connectivity causing a delayed or missing response.\n>\n> In such cases the transaction must **not** be treated as declined or failed.\n> Inquire about its real status using this API with your own `client_ref_id`,\n> instead of retrying the payment.\n\n## `tx_status` values\n\n| `tx_status` | Description |\n|---|---|\n| 0 | Success |\n| 1 | Fail |\n| 2 | Response Awaited / Initiated (in case of NEFT) |\n| 3 | Refund Pending |\n| 4 | Refunded |\n| 5 | Hold (Transaction Inquiry required) |",
       "bestFor": "Reconciling pending transactions and confirming payment outcomes when the Pay Bill response is awaited.",
       "docsUrl": "https://eps.eko.in/docs/bbps-transaction-status",
       "headers": [
@@ -6578,7 +6831,7 @@
           "name": "transaction-reference",
           "type": "string",
           "required": true,
-          "description": "Eko TID (`tid`) or your `client_ref_id` that uniquely identifies the transaction.",
+          "description": "Eko TID or your `client_ref_id` that identifies the transaction. Pass a TID as-is; to look up by `client_ref_id`, prefix it — e.g. `client_ref_id:567890`.",
           "example": "1734567890",
           "in": "path"
         }
@@ -7507,438 +7760,12 @@
           "name": "data",
           "type": "object",
           "description": "API-specific response payload.",
-          "children": [
-            {
-              "name": "reference_id",
-              "type": "number",
-              "description": "Unique identifier for the submitted batch. Pass this to the Bulk PAN Verification Status API to retrieve individual PAN results once processing is complete.",
-              "example": 123456
-            }
-          ]
-        }
-      ],
-      "sampleSuccessResponse": {
-        "status": 0,
-        "response_status_id": 0,
-        "message": "Bulk PAN verification request accepted. Poll status API for results.",
-        "response_type_id": 1388,
-        "data": {
-          "reference_id": 123456
-        }
-      },
-      "errorScenarios": [
-        {
-          "scenario": "Empty or missing entries array",
-          "statusCode": 400,
-          "example": {
-            "status": 1,
-            "message": "Bad request — entries array is required and must not be empty"
-          }
-        },
-        {
-          "scenario": "Malformed PAN in one or more entries",
-          "statusCode": 400,
-          "example": {
-            "status": 1,
-            "message": "Bad request — one or more entries contain an invalid PAN format"
-          }
-        }
-      ],
-      "responseTypes": []
-    },
-    {
-      "slug": "pan-bulk-status",
-      "productId": "pan",
-      "productName": "PAN Verification",
-      "name": "Check Bulk PAN Verification Status",
-      "method": "GET",
-      "path": "/tools/kyc/pan/bulk/status",
-      "summary": "Poll the result of a Bulk PAN Verification batch using the reference_id returned when the batch was submitted.",
-      "category": "verification",
-      "relevance": "M",
-      "description": "Retrieves the per-PAN results for a batch previously submitted via the Bulk PAN Verification API. Because bulk verification runs asynchronously, callers poll this endpoint with the reference_id from the submit response until the batch finishes processing. The response returns a count and an array of entries, one per PAN, each carrying the validity, registered name, name-match score/result, Aadhaar-seeding status, and PAN status.",
-      "bestFor": "Fetching individual PAN results after submitting a batch to the Bulk PAN Verification API.",
-      "docsUrl": "https://eps.eko.in/docs/pan-bulk-status",
-      "headers": [
-        {
-          "name": "developer_key",
-          "in": "header",
-          "type": "string",
-          "required": true,
-          "description": "Static API key issued to your account after KYC."
-        },
-        {
-          "name": "secret-key",
-          "in": "header",
-          "type": "string",
-          "required": true,
-          "description": "Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key)))."
-        },
-        {
-          "name": "secret-key-timestamp",
-          "in": "header",
-          "type": "string",
-          "required": true,
-          "description": "Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time."
-        },
-        {
-          "name": "content-type",
-          "in": "header",
-          "type": "string",
-          "required": true,
-          "description": "application/json",
-          "example": "application/json"
-        }
-      ],
-      "requestParams": [
-        {
-          "name": "initiator_id",
-          "type": "string",
-          "required": true,
-          "description": "Registered mobile number of the API user (see Platform Credentials).",
-          "example": "9962981729",
-          "in": "query"
-        },
-        {
-          "name": "client_ref_id",
-          "type": "string",
-          "required": false,
-          "description": "Unique reference ID per API call, generated by your system (max 20 characters).",
-          "example": "2026010100123456789",
-          "in": "query"
-        },
-        {
-          "name": "reference_id",
-          "type": "string",
-          "required": true,
-          "description": "Unique id returned by the Bulk PAN Verification API for the submitted batch.",
-          "example": "123456",
-          "in": "query"
-        },
-        {
-          "name": "bulk_reference_id",
-          "type": "string",
-          "required": false,
-          "description": "Unique id created to identify the bulk request, if you tracked one at submit time.",
-          "example": "BULK-PAN-20240101-001",
-          "in": "query"
-        }
-      ],
-      "sampleRequest": {},
-      "responseFields": [
-        {
-          "name": "status",
-          "type": "number",
-          "description": "Primary success indicator (0 = success).",
-          "example": 0
-        },
-        {
-          "name": "message",
-          "type": "string",
-          "description": "Human-readable response / error message.",
-          "example": "Verification successful"
-        },
-        {
-          "name": "response_status_id",
-          "type": "number",
-          "description": "Granular status id; see the shared error-codes table.",
-          "example": 0
-        },
-        {
-          "name": "response_type_id",
-          "type": "number",
-          "description": "A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.",
-          "example": 1388
-        },
-        {
-          "name": "data",
-          "type": "object",
-          "description": "API-specific response payload.",
-          "children": [
-            {
-              "name": "count",
-              "type": "number",
-              "description": "Number of entries in the results array.",
-              "imp": true,
-              "example": 2
-            },
-            {
-              "name": "entries",
-              "type": "array",
-              "description": "Per-PAN verification results for the batch.",
-              "imp": true,
-              "children": [
-                {
-                  "name": "pan",
-                  "type": "string",
-                  "description": "10-character PAN identifier.",
-                  "imp": true,
-                  "example": "ABCPV1234D"
-                },
-                {
-                  "name": "valid",
-                  "type": "string",
-                  "description": "PAN card validity status.",
-                  "example": "true"
-                },
-                {
-                  "name": "registered_name",
-                  "type": "string",
-                  "description": "Name on record against the PAN.",
-                  "example": "John Doe"
-                },
-                {
-                  "name": "name_provided",
-                  "type": "string",
-                  "description": "Name submitted in the bulk request for this PAN.",
-                  "example": "John"
-                },
-                {
-                  "name": "name_match_score",
-                  "type": "string",
-                  "description": "Name verification score.",
-                  "example": "82.5"
-                },
-                {
-                  "name": "name_match_result",
-                  "type": "string",
-                  "description": "Name match result.",
-                  "example": "GOOD_PARTIAL_MATCH"
-                },
-                {
-                  "name": "aadhaar_seeding_status",
-                  "type": "string",
-                  "description": "Aadhaar-PAN linkage status.",
-                  "example": "Y"
-                },
-                {
-                  "name": "pan_status",
-                  "type": "string",
-                  "description": "Current PAN status.",
-                  "example": "VALID"
-                },
-                {
-                  "name": "message",
-                  "type": "string",
-                  "description": "Success or failure details for this entry.",
-                  "example": "PAN verified successfully"
-                },
-                {
-                  "name": "reference_id",
-                  "type": "string",
-                  "description": "Unique reference identifier for the entry.",
-                  "example": "123456"
-                },
-                {
-                  "name": "last_updated_at",
-                  "type": "string",
-                  "description": "Timestamp when the entry was last updated.",
-                  "example": "2024-01-01 12:30:45"
-                }
-              ]
-            }
-          ]
-        }
-      ],
-      "sampleSuccessResponse": {
-        "status": 0,
-        "response_status_id": 0,
-        "message": "Success",
-        "response_type_id": 1388,
-        "data": {
-          "count": 2,
-          "entries": [
-            {
-              "pan": "ABCPV1234D",
-              "valid": "true",
-              "registered_name": "John Doe",
-              "name_provided": "John",
-              "name_match_score": "82.5",
-              "name_match_result": "GOOD_PARTIAL_MATCH",
-              "aadhaar_seeding_status": "Y",
-              "pan_status": "VALID",
-              "message": "PAN verified successfully",
-              "reference_id": "123456",
-              "last_updated_at": "2024-01-01 12:30:45"
-            },
-            {
-              "pan": "ABCPV1234L",
-              "valid": "true",
-              "registered_name": "John Doe",
-              "name_provided": "John Doe",
-              "name_match_score": "100",
-              "name_match_result": "EXACT_MATCH",
-              "aadhaar_seeding_status": "Y",
-              "pan_status": "VALID",
-              "message": "PAN verified successfully",
-              "reference_id": "123456",
-              "last_updated_at": "2024-01-01 12:30:46"
-            }
-          ]
-        }
-      },
-      "errorScenarios": [
-        {
-          "scenario": "Missing reference_id",
-          "statusCode": 400,
-          "example": {
-            "status": 1,
-            "message": "Bad request — reference_id is required"
-          }
-        },
-        {
-          "scenario": "Unknown or expired reference_id",
-          "statusCode": 404,
-          "example": {
-            "status": 1,
-            "message": "No batch found for the supplied reference_id"
-          }
-        }
-      ],
-      "responseTypes": []
-    },
-    {
-      "slug": "aadhaar-dmt-levin-validate",
-      "productId": "dmt",
-      "productName": "Domestic Money Transfer (DMT)",
-      "name": "Validate Aadhaar & Generate OTP",
-      "method": "POST",
-      "path": "/customer/payment/dmt-levin/sender/{customer_id}/aadhaar/otp",
-      "summary": "Validate a sender's Aadhaar number and trigger an OTP to the linked mobile for DMT Levin onboarding.",
-      "category": "bc",
-      "relevance": "M",
-      "description": "Submits the sender's Aadhaar number via the DMT Levin channel to initiate OTP-based Aadhaar validation. The `otp_ref_id` from the sender's existing profile plus the Aadhaar number are required. Returns a new `otp_ref_id` for the validation session. Part of the Levin DMT sender onboarding flow.",
-      "bestFor": "DMT Levin sender onboarding flows that require Aadhaar number validation as a step before completing identity verification.",
-      "docsUrl": "https://eps.eko.in/docs/aadhaar-dmt-levin-validate",
-      "headers": [
-        {
-          "name": "developer_key",
-          "in": "header",
-          "type": "string",
-          "required": true,
-          "description": "Static API key issued to your account after KYC."
-        },
-        {
-          "name": "secret-key",
-          "in": "header",
-          "type": "string",
-          "required": true,
-          "description": "Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key)))."
-        },
-        {
-          "name": "secret-key-timestamp",
-          "in": "header",
-          "type": "string",
-          "required": true,
-          "description": "Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time."
-        },
-        {
-          "name": "content-type",
-          "in": "header",
-          "type": "string",
-          "required": true,
-          "description": "application/json",
-          "example": "application/json"
-        }
-      ],
-      "requestParams": [
-        {
-          "name": "initiator_id",
-          "type": "string",
-          "required": true,
-          "description": "Registered mobile number of the API user (see Platform Credentials).",
-          "example": "9962981729",
-          "in": "body"
-        },
-        {
-          "name": "client_ref_id",
-          "type": "string",
-          "required": false,
-          "description": "Unique reference ID per API call, generated by your system (max 20 characters).",
-          "example": "2026010100123456789",
-          "in": "body"
-        },
-        {
-          "name": "customer_id",
-          "type": "integer",
-          "required": true,
-          "description": "Sender's mobile number.",
-          "example": 9876543210,
-          "in": "path"
-        },
-        {
-          "name": "aadhar",
-          "type": "string",
-          "required": true,
-          "description": "12-digit Aadhaar number of the sender.",
-          "example": "123456789012",
-          "in": "body"
-        },
-        {
-          "name": "otp_ref_id",
-          "type": "string",
-          "required": true,
-          "description": "Reference ID returned from the Get Sender Info (or Create Sender) API for this customer.",
-          "example": "73849201",
-          "in": "body"
-        },
-        {
-          "name": "additional_info",
-          "type": "string",
-          "required": true,
-          "description": "Additional info flag. Defaults to 1.",
-          "example": "1",
-          "in": "body"
-        }
-      ],
-      "sampleRequest": {
-        "initiator_id": "9962981729",
-        "client_ref_id": "2026010100123456789",
-        "aadhar": "123456789012",
-        "otp_ref_id": "73849201",
-        "additional_info": "1"
-      },
-      "responseFields": [
-        {
-          "name": "status",
-          "type": "number",
-          "description": "Primary success indicator (0 = success).",
-          "example": 0
-        },
-        {
-          "name": "message",
-          "type": "string",
-          "description": "Human-readable response / error message.",
-          "example": "Verification successful"
-        },
-        {
-          "name": "response_status_id",
-          "type": "number",
-          "description": "Granular status id; see the shared error-codes table.",
-          "example": 0
-        },
-        {
-          "name": "response_type_id",
-          "type": "number",
-          "description": "A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.",
-          "example": 1388
-        },
-        {
-          "name": "data",
-          "type": "object",
-          "description": "API-specific response payload.",
-          "children": [
-            {
-              "name": "otp_ref_id",
-              "type": "string",
-              "description": "New OTP reference ID for the Aadhaar validation session. Pass to Validate Sender Aadhaar OTP.",
-              "example": "93847201"
-            },
-            {
-              "name": "mobile_hint",
-              "type": "string",
-              "description": "Masked mobile number to which the OTP was dispatched.",
-              "example": "******3210"
+          "children": [
+            {
+              "name": "reference_id",
+              "type": "number",
+              "description": "Unique identifier for the submitted batch. Pass this to the Bulk PAN Verification Status API to retrieve individual PAN results once processing is complete.",
+              "example": 123456
             }
           ]
         }
@@ -7946,41 +7773,45 @@
       "sampleSuccessResponse": {
         "status": 0,
         "response_status_id": 0,
-        "message": "Aadhaar OTP dispatched successfully",
+        "message": "Bulk PAN verification request accepted. Poll status API for results.",
         "response_type_id": 1388,
         "data": {
-          "otp_ref_id": "93847201",
-          "mobile_hint": "******3210"
+          "reference_id": 123456
         }
       },
       "errorScenarios": [
         {
-          "scenario": "Invalid Aadhaar number",
-          "statusCode": 200,
+          "scenario": "Empty or missing entries array",
+          "statusCode": 400,
           "example": {
             "status": 1,
-            "response_status_id": 301,
-            "message": "Invalid Aadhaar number provided.",
-            "response_type_id": 1388,
-            "data": {}
+            "message": "Bad request — entries array is required and must not be empty"
+          }
+        },
+        {
+          "scenario": "Malformed PAN in one or more entries",
+          "statusCode": 400,
+          "example": {
+            "status": 1,
+            "message": "Bad request — one or more entries contain an invalid PAN format"
           }
         }
       ],
       "responseTypes": []
     },
     {
-      "slug": "aadhaar-dmt-levin-verify-otp",
-      "productId": "dmt",
-      "productName": "Domestic Money Transfer (DMT)",
-      "name": "Validate Sender Aadhaar OTP",
-      "method": "POST",
-      "path": "/customer/payment/dmt-levin/sender/{customer_id}/aadhaar/otp/verify",
-      "summary": "Verify the Aadhaar OTP for a DMT Levin sender to complete identity validation.",
-      "category": "bc",
+      "slug": "pan-bulk-status",
+      "productId": "pan",
+      "productName": "PAN Verification",
+      "name": "Check Bulk PAN Verification Status",
+      "method": "GET",
+      "path": "/tools/kyc/pan/bulk/status",
+      "summary": "Poll the result of a Bulk PAN Verification batch using the reference_id returned when the batch was submitted.",
+      "category": "verification",
       "relevance": "M",
-      "description": "Validates the OTP received on the sender's Aadhaar-linked mobile number in the DMT Levin flow. Use `intent_id: 20` for Aadhaar validation (as opposed to `intent_id: 19` for sender onboarding). On success, the sender's identity is confirmed and their DMT Levin wallet profile is updated.",
-      "bestFor": "Completing OTP-based Aadhaar validation in the DMT Levin sender onboarding flow.",
-      "docsUrl": "https://eps.eko.in/docs/aadhaar-dmt-levin-verify-otp",
+      "description": "Retrieves the per-PAN results for a batch previously submitted via the Bulk PAN Verification API. Because bulk verification runs asynchronously, callers poll this endpoint with the reference_id from the submit response until the batch finishes processing. The response returns a count and an array of entries, one per PAN, each carrying the validity, registered name, name-match score/result, Aadhaar-seeding status, and PAN status.",
+      "bestFor": "Fetching individual PAN results after submitting a batch to the Bulk PAN Verification API.",
+      "docsUrl": "https://eps.eko.in/docs/pan-bulk-status",
       "headers": [
         {
           "name": "developer_key",
@@ -8019,7 +7850,7 @@
           "required": true,
           "description": "Registered mobile number of the API user (see Platform Credentials).",
           "example": "9962981729",
-          "in": "body"
+          "in": "query"
         },
         {
           "name": "client_ref_id",
@@ -8027,57 +7858,26 @@
           "required": false,
           "description": "Unique reference ID per API call, generated by your system (max 20 characters).",
           "example": "2026010100123456789",
-          "in": "body"
+          "in": "query"
         },
         {
-          "name": "customer_id",
+          "name": "reference_id",
           "type": "string",
           "required": true,
-          "description": "Sender's mobile number.",
-          "example": "9876543210",
-          "in": "path"
-        },
-        {
-          "name": "otp",
-          "type": "integer",
-          "required": false,
-          "description": "OTP received on the Aadhaar-linked mobile number.",
-          "example": 123456,
-          "in": "body"
-        },
-        {
-          "name": "otp_ref_id",
-          "type": "integer",
-          "required": true,
-          "description": "Reference ID from the Validate Aadhaar (DMT Levin) response.",
-          "example": 93847201,
-          "in": "body"
-        },
-        {
-          "name": "intent_id",
-          "type": "string",
-          "required": false,
-          "description": "Set to \"19\" for sender onboarding or \"20\" for Aadhaar validation.",
-          "example": "20",
-          "in": "body"
+          "description": "Unique id returned by the Bulk PAN Verification API for the submitted batch.",
+          "example": "123456",
+          "in": "query"
         },
         {
-          "name": "additional_info",
+          "name": "bulk_reference_id",
           "type": "string",
           "required": false,
-          "description": "Additional info flag. Defaults to 1.",
-          "example": "1",
-          "in": "body"
+          "description": "Unique id created to identify the bulk request, if you tracked one at submit time.",
+          "example": "BULK-PAN-20240101-001",
+          "in": "query"
         }
       ],
-      "sampleRequest": {
-        "initiator_id": "9962981729",
-        "client_ref_id": "2026010100123456789",
-        "otp": 123456,
-        "otp_ref_id": 93847201,
-        "intent_id": "20",
-        "additional_info": "1"
-      },
+      "sampleRequest": {},
       "responseFields": [
         {
           "name": "status",
@@ -8109,39 +7909,86 @@
           "description": "API-specific response payload.",
           "children": [
             {
-              "name": "verified",
-              "type": "boolean",
-              "description": "True if Aadhaar OTP validation was successful.",
-              "imp": true,
-              "example": true
-            },
-            {
-              "name": "name",
-              "type": "string",
-              "description": "Verified sender name from Aadhaar.",
-              "imp": true,
-              "example": "Arjun Mehta"
-            },
-            {
-              "name": "gender",
-              "type": "string",
-              "description": "Gender from Aadhaar record.",
-              "imp": true,
-              "example": "M"
-            },
-            {
-              "name": "dob",
-              "type": "string",
-              "description": "Date of birth from Aadhaar.",
+              "name": "count",
+              "type": "number",
+              "description": "Number of entries in the results array.",
               "imp": true,
-              "example": "10-01-1988"
+              "example": 2
             },
             {
-              "name": "masked_aadhaar",
-              "type": "string",
-              "description": "Aadhaar number with first 8 digits masked.",
+              "name": "entries",
+              "type": "array",
+              "description": "Per-PAN verification results for the batch.",
               "imp": true,
-              "example": "XXXX-XXXX-3456"
+              "children": [
+                {
+                  "name": "pan",
+                  "type": "string",
+                  "description": "10-character PAN identifier.",
+                  "imp": true,
+                  "example": "ABCPV1234D"
+                },
+                {
+                  "name": "valid",
+                  "type": "string",
+                  "description": "PAN card validity status.",
+                  "example": "true"
+                },
+                {
+                  "name": "registered_name",
+                  "type": "string",
+                  "description": "Name on record against the PAN.",
+                  "example": "John Doe"
+                },
+                {
+                  "name": "name_provided",
+                  "type": "string",
+                  "description": "Name submitted in the bulk request for this PAN.",
+                  "example": "John"
+                },
+                {
+                  "name": "name_match_score",
+                  "type": "string",
+                  "description": "Name verification score.",
+                  "example": "82.5"
+                },
+                {
+                  "name": "name_match_result",
+                  "type": "string",
+                  "description": "Name match result.",
+                  "example": "GOOD_PARTIAL_MATCH"
+                },
+                {
+                  "name": "aadhaar_seeding_status",
+                  "type": "string",
+                  "description": "Aadhaar-PAN linkage status.",
+                  "example": "Y"
+                },
+                {
+                  "name": "pan_status",
+                  "type": "string",
+                  "description": "Current PAN status.",
+                  "example": "VALID"
+                },
+                {
+                  "name": "message",
+                  "type": "string",
+                  "description": "Success or failure details for this entry.",
+                  "example": "PAN verified successfully"
+                },
+                {
+                  "name": "reference_id",
+                  "type": "string",
+                  "description": "Unique reference identifier for the entry.",
+                  "example": "123456"
+                },
+                {
+                  "name": "last_updated_at",
+                  "type": "string",
+                  "description": "Timestamp when the entry was last updated.",
+                  "example": "2024-01-01 12:30:45"
+                }
+              ]
             }
           ]
         }
@@ -8149,37 +7996,55 @@
       "sampleSuccessResponse": {
         "status": 0,
         "response_status_id": 0,
-        "message": "Aadhaar OTP verified successfully",
+        "message": "Success",
         "response_type_id": 1388,
         "data": {
-          "verified": true,
-          "name": "Arjun Mehta",
-          "gender": "M",
-          "dob": "10-01-1988",
-          "masked_aadhaar": "XXXX-XXXX-3456"
+          "count": 2,
+          "entries": [
+            {
+              "pan": "ABCPV1234D",
+              "valid": "true",
+              "registered_name": "John Doe",
+              "name_provided": "John",
+              "name_match_score": "82.5",
+              "name_match_result": "GOOD_PARTIAL_MATCH",
+              "aadhaar_seeding_status": "Y",
+              "pan_status": "VALID",
+              "message": "PAN verified successfully",
+              "reference_id": "123456",
+              "last_updated_at": "2024-01-01 12:30:45"
+            },
+            {
+              "pan": "ABCPV1234L",
+              "valid": "true",
+              "registered_name": "John Doe",
+              "name_provided": "John Doe",
+              "name_match_score": "100",
+              "name_match_result": "EXACT_MATCH",
+              "aadhaar_seeding_status": "Y",
+              "pan_status": "VALID",
+              "message": "PAN verified successfully",
+              "reference_id": "123456",
+              "last_updated_at": "2024-01-01 12:30:46"
+            }
+          ]
         }
       },
       "errorScenarios": [
         {
-          "scenario": "Wrong OTP",
-          "statusCode": 200,
+          "scenario": "Missing reference_id",
+          "statusCode": 400,
           "example": {
             "status": 1,
-            "response_status_id": 302,
-            "message": "Wrong OTP. Please check and retry.",
-            "response_type_id": 1388,
-            "data": {}
+            "message": "Bad request — reference_id is required"
           }
         },
         {
-          "scenario": "OTP expired",
-          "statusCode": 200,
+          "scenario": "Unknown or expired reference_id",
+          "statusCode": 404,
           "example": {
             "status": 1,
-            "response_status_id": 303,
-            "message": "OTP expired. Please regenerate.",
-            "response_type_id": 1388,
-            "data": {}
+            "message": "No batch found for the supplied reference_id"
           }
         }
       ],
@@ -13726,7 +13591,7 @@
       "summary": "Activate a specific service (by service code) for one of your agents/retailers.",
       "category": "util",
       "relevance": "M",
-      "description": "Enables a service for the given agent so they can begin transacting on it. The agent is identified by their `user_code` and the service by its `service_code`, both supplied as path parameters. After activation, confirm the status with the Get User's Services API.",
+      "description": "Enables a service for the given user (agent/retailer/distributor) so they can begin transacting on it. Activating a service is mandatory before your users can use it in production. The user is identified by their `user_code` and the service by its `service_code`, both supplied as path parameters. Look up service codes via the Get All Services API. After activation, confirm the status with the Get User's Services API.",
       "bestFor": "Enabling a new service on an existing agent before their first transaction on it",
       "docsUrl": "https://eps.eko.in/docs/activate-user-service",
       "headers": [
@@ -14527,7 +14392,7 @@
           "name": "transaction-reference",
           "type": "string",
           "required": true,
-          "description": "Eko TID or your client_ref_id identifying the transaction.",
+          "description": "Eko TID or your `client_ref_id` that identifies the transaction. Pass a TID as-is; to look up by `client_ref_id`, prefix it — e.g. `client_ref_id:567890`.",
           "example": "12971397",
           "in": "path"
         }
@@ -22794,41 +22659,87 @@
   ],
   "recipes": [
     {
-      "id": "dmt-send-money",
-      "slug": "dmt-send-money",
-      "name": "DMT — Send Money",
-      "summary": "Full domestic money transfer flow: look up the sender, onboard them if new, add the recipient, then send an OTP-verified transfer.",
+      "id": "dmt-fino-send-money",
+      "slug": "dmt-fino-send-money",
+      "name": "DMT (Fino) — Send Money",
+      "summary": "Full Fino DMT money-transfer flow: look up the sender, onboard and biometric-eKYC them if new, pick or add the recipient, then send an OTP-verified transfer.",
       "productId": "dmt",
       "steps": [
         {
           "specSlug": "dmt-get-sender",
-          "purpose": "Check whether the customer is already a registered DMT sender.",
+          "purpose": "Check whether the customer is already a registered DMT sender, and which stage of onboarding they are at. The `response_type_id` decides where the flow enters.",
           "branches": [
             {
               "onResponseTypeId": 308,
               "goto": "dmt-onboard-sender",
               "note": "Sender not found — onboard them before continuing."
+            },
+            {
+              "onResponseTypeId": 2134,
+              "goto": "dmt-fino-sender-ekyc",
+              "note": "Sender found but biometric eKYC is pending — capture their fingerprint."
+            },
+            {
+              "onResponseTypeId": 2129,
+              "goto": "dmt-fino-validate-ekyc-otp",
+              "note": "Sender found mid-eKYC — only the OTP validation is left."
+            },
+            {
+              "onResponseTypeId": 309,
+              "goto": "dmt-get-recipients",
+              "note": "Sender found and KYC complete — skip onboarding and go straight to recipients."
             }
           ]
         },
         {
           "specSlug": "dmt-onboard-sender",
-          "purpose": "Register a new sender when Get Sender API returns `response_type_id=308`."
+          "purpose": "Register a new sender with name, date of birth and residence address. This opens the sender on Eko but leaves KYC pending on Fino (`response_type_id=2134`) — they cannot transact yet.",
+          "branches": [
+            {
+              "onResponseTypeId": 309,
+              "goto": "dmt-get-recipients",
+              "note": "Already onboarded on Fino externally, KYC complete — no eKYC needed."
+            }
+          ]
+        },
+        {
+          "specSlug": "dmt-fino-sender-ekyc",
+          "purpose": "Biometric Aadhaar eKYC — one-time per sender. Capture the PID block from an RD-service fingerprint scanner and submit it with the sender's Aadhaar number; the response returns the `kyc_request_id` and `otp_ref_id` the next step needs. Completing eKYC raises the sender's monthly limit from ₹5,000 to ₹25,000."
+        },
+        {
+          "specSlug": "dmt-fino-validate-ekyc-otp",
+          "purpose": "Confirm the eKYC by submitting the OTP sent to the sender's Aadhaar-linked mobile, along with the `kyc_request_id` and `otp_ref_id` from the biometric step. The sender is fully KYC-verified on success."
+        },
+        {
+          "specSlug": "dmt-get-recipients",
+          "purpose": "List the sender's saved beneficiaries. If the one they want is already there, reuse its `recipient_id` and skip Add Recipient.",
+          "branches": [
+            {
+              "onResponseTypeId": 22,
+              "goto": "dmt-add-recipient",
+              "note": "No recipients saved yet — add one before transacting."
+            },
+            {
+              "onResponseTypeId": 23,
+              "goto": "dmt-send-otp",
+              "note": "Recipient already saved — reuse its `recipient_id`."
+            }
+          ]
         },
         {
           "specSlug": "dmt-add-recipient",
-          "purpose": "Add the beneficiary the sender wants to transfer to."
+          "purpose": "Add the beneficiary the sender wants to transfer to; returns the `recipient_id` used by the two transaction steps."
         },
         {
           "specSlug": "dmt-send-otp",
-          "purpose": "Trigger the transaction OTP sent to the sender."
+          "purpose": "Pre-authorise the transfer: sends an OTP to the sender's registered mobile and returns the `otp_ref_id`. Required before every transfer — request a fresh one per attempt."
         },
         {
           "specSlug": "dmt-initiate-transfer",
-          "purpose": "Submit the OTP-verified transfer to complete the flow.",
+          "purpose": "Submit the transfer with the customer-entered OTP, its `otp_ref_id`, and a `client_ref_id` unique to this attempt. The only money-debit step — persist `tid` and `bank_ref_num` and reconcile before any retry.",
           "branches": [
             {
-              "onResponseStatusId": 0,
+              "onStatus": 0,
               "goto": "done"
             }
           ]
@@ -22836,43 +22747,43 @@
       ]
     },
     {
-      "id": "aeps-cash-withdrawal",
-      "slug": "aeps-cash-withdrawal",
-      "name": "AePS — Cash Withdrawal",
+      "id": "aeps-fingpay-cash-withdrawal",
+      "slug": "aeps-fingpay-cash-withdrawal",
+      "name": "AePS (Fingpay) — Cash Withdrawal",
       "summary": "Aadhaar-enabled cash withdrawal: one-time agent activation and eKYC, daily KYC, then the biometric withdrawal.",
       "productId": "aeps",
       "steps": [
         {
-          "specSlug": "aeps-activate-fingpay",
+          "specSlug": "activate-aeps-fingpay",
           "purpose": "One-time activation of AePS Fingpay for the agent.",
           "frequency": "once"
         },
         {
-          "specSlug": "aeps-send-otp-kyc",
+          "specSlug": "aeps-fingpay-send-otp-kyc",
           "purpose": "One-time eKYC step 1 (agent onboarding, not per transaction): OTP to the agent's Aadhaar-linked mobile.",
           "frequency": "once"
         },
         {
-          "specSlug": "aeps-verify-otp-kyc",
+          "specSlug": "aeps-fingpay-verify-otp-kyc",
           "purpose": "One-time eKYC step 2 (agent onboarding): verify the OTP with the otp_ref_id and reference_tid from step 1.",
           "frequency": "once"
         },
         {
-          "specSlug": "aeps-biometric-ekyc",
+          "specSlug": "aeps-fingpay-biometric-ekyc",
           "purpose": "One-time eKYC step 3 (agent onboarding): the agent's biometric PID completes eKYC.",
           "frequency": "once"
         },
         {
-          "specSlug": "aeps-daily-auth",
+          "specSlug": "aeps-fingpay-daily-auth",
           "purpose": "Daily KYC — biometric-only, repeated once per calendar day before the agent's first transaction.",
           "frequency": "daily"
         },
         {
-          "specSlug": "aeps-cash-withdrawal",
+          "specSlug": "aeps-fingpay-cash-withdrawal",
           "purpose": "Perform the biometric Aadhaar-enabled cash withdrawal.",
           "branches": [
             {
-              "onResponseStatusId": 0,
+              "onStatus": 0,
               "goto": "done"
             }
           ]