Mandatory IP in MOB/MOBB

[tanmay-dixit]

Summary

Add IP validation for Mobile (MOB) and Mobile Banking (MOBB) channels to align with NPCI specification requirements.

Changes

• Updated ValidateAgentParams function in internal/pkg/validators/agent.go to require IP address for MOB and MOBB channels
• Previously, IP validation only applied to INT and INTB channels
• Now validates IP for all four channels: INT, INTB, MOB, MOBB as per NPCI device block parameter specification

Impact

• Breaking Change: Requests with MOB/MOBB channels missing IP address will now be rejected
• Ensures compliance with NPCI specification (Section 21.1 - Initiating Channel Vs Device Block Parameters)
• Improves data quality and security posture for mobile channel transactions

Testing

• Verify MOB channel requests without IP are rejected
• Verify MOBB channel requests without IP are rejected
• Verify existing other agent channel validations continue to work

Reference

BBPS v14 API Spec: Section 21.1 - Device Block Tags for Mobile channels require: IP, IMEI, OS, APP

[github-actions]

Checklist to merge a PR 🚀

To merge this pull request, please take time to complete the checklist.

What action did you perform?

Review the corresponding checklist items for the action you performed and mark them done.

Edit an existing content (MDX) page

Checklist

• Review changes using the MDX preview option
• If the length of content >15000 chars, use the Content preview portal to view changes
• If a redirect is needed to the existing page, add a key, value pair in redirects.json

---

Edit an existing API reference page

Checklist

• Use the Content preview portal to view changes
• API reference is in JSON format (OpenAPI or Swagger)

---

Add a new content (MDX) page

Checklist

• Create a .mdx file with the path as its name in the content folder
• Add frontmatter with all the metadata
• Review the order of items in Sidebar using the Sidebar preview option
• Review changes using the MDX preview option
• If the length of content >15000 chars, use the Content preview portal to view changes
• Created a folder with the same name, if any children were to be added to the page
• Once all changes are done, update the menu items by using the Menu Items option
• Add a key, and value pair in redirects.json if you wish to have a redirect to the new page

---

Add a new API reference page

Checklist

• Create a .json file with the product path as its name
• Create an api-reference.mdx file in the respective product folder inside content folder
• Add frontmatter with all the metadata
• Review the order of items in Sidebar using the Sidebar preview option
• Add API reference in JSON format (OpenAPI or Swagger) into created .json file.
• Used the Content preview portal to view changes
• Once all changes are done, update the menu items by using the Menu Items option