Production ISP automation requires more than a dashboard. These resources explain the operational inputs Sirmillion needs and the security boundaries that should be verified during rollout.
Identify the MikroTik management address, RouterOS version and connection path before enrollment. Use a dedicated least-privilege API user, API-SSL certificate and management-address restriction rather than reusing the router administrator account.
Every ISP signs in through its resolved hostname and authenticated sessions carry that tenant context. Backend guards enforce scope and role; frontend navigation is only a convenience and is never the security boundary.
An ISP using its own M-Pesa production integration needs a Safaricom Daraja application, approved shortcode or till configuration, consumer credentials, passkey where applicable and a public HTTPS callback origin.
Plan tenant identity, package catalogue, customer migration, router enrollment, payment verification and staff permissions as separate acceptance stages. Network changes should always include router backups and a tested rollback path.