Most billing software treats payment and network access as two systems: invoices in one place, router config in another, a sync job in the middle. On a mobile-money hotspot that gap is the whole product. The payment callback is the login button. Every second between "payment confirmed" and "you're online" is a customer staring at a captive portal, wondering if they just lost their money. So we built Centipid Billing with RADIUS and the payment gateways in one place: when a payment confirms, access renews. No operator in the loop. Where does the payment-to-access gap live in your stack?
commit 074e4b3