A common pattern with small ISPs and hotspot operators is a billing spreadsheet in one place and a MikroTik router configuration in another, connected only by whoever remembers to update both.
LipaNet's package model maps directly to MikroTik bandwidth profiles, so changing a customer's plan — or suspending them for non-payment — is one action that reaches the router, not two disconnected ones. The tradeoff is that the integration has to handle router connectivity failures gracefully: a billing change should never silently fail to reach the network, and the system needs to surface that clearly rather than reporting false success.
This is the piece of LipaNet still furthest from finished — multi-router failover support is on the roadmap specifically because a single point of failure in the network layer is worse than one in the billing layer alone.