What this page covers
How static IP readiness fits Dhan trading automation and why live execution should stay blocked until server egress is verified.
Safe setup checklist
Keep credentials server-side, validate dry-runs first, confirm static IP and callback configuration, and avoid enabling live execution until readiness checks pass.
The user-facing state should distinguish dry-run readiness from live execution readiness. A missing setup item can still allow documentation and support review, but it should not quietly enable broker calls.
Implementation details
Static IP readiness means broker requests originate from an expected server egress address. If the broker requires IP registration and the request comes from an unapproved host, live execution should remain blocked. The product should show a clear blocker instead of asking the user to retry commands.
Vantaro handling
Vantaro treats setup issues as blockers for live execution while still allowing safe documentation and dry-run review where applicable.
Each blocker should create an audit event so support and users can review what happened without exposing tokens or sensitive account data.
Evidence and screenshots to add before final publication
FAQ
Can this page replace official broker docs?
No. Use it as a workflow guide and verify implementation details with official Dhan or Telegram documentation.