The rules we build by
Every change to Lodge Internet is held against a short written list of rules. Here they are in plain words, with the reason each one exists.
Lodge Internet · 14 November 2026 · 4 min read
A code review at Lodge can say "this breaks B4" and everyone knows what it means: a log line is about to write down something it shouldn't. Our rules are written down and numbered, so a reviewer can point at one instead of arguing from taste.
Most of them are for engineers. A handful hold everywhere, across the website and the WhatsApp and Telegram bot, and they shape what you see as a customer. These are those, and why we keep them.
One source of truth
There is one engine behind everything: the backend, a server we run that holds every price, every stock count and every wallet balance. The website and the bot are windows onto it. They hold no prices or rules of their own. They show what the engine says and pass back what you did.
Why: anything kept in two places drifts. If the bot had its own price list, one day it would disagree with the website, and you would have no way to know which was right.
One price
A plan's total is worked out in exactly one place on the server. The website and the bot both display that number. Neither does sums of its own. Since 21 October 2026, a plan costs the same wherever you buy it.
Why: you should never find a cheaper door to the same code, or a dearer one. More in One price, wherever you buy.
Money as whole numbers
Inside our systems, amounts move as kobo, the hundredth part of a naira, in whole numbers (or as whole naira, where an older part of the system already did). Never decimals. The naira sign and the commas are added only at the last moment, when the number reaches your screen.
Why: computers store most decimal fractions approximately, and a tiny rounding error repeated across many payments stops being tiny. Whole numbers don't round.
Every money path is safe to run twice
Paying, issuing a code, crediting a wallet and handling a payment notice from Paystack, our payment provider, must all give the same result if they happen twice. And a code is only ever issued one way: we set one aside for you, you pay, then you claim it.
Why: networks drop and retry. Your phone may report a payment at the same moment Paystack does. If doing something twice gave you two codes, or charged you twice, the system would be wrong every time the network hiccuped. See You never pay for a code you don't get.
Switched on, never "coming soon"
A feature that isn't live doesn't appear. No grey buttons, no "coming soon" banners. The server says which features are on, and a screen shows only those.
Why: a button that does nothing costs you a tap, a page load and some of your data, and tells you nothing useful.
Bot messages have to earn their place
WhatsApp bills us for every reply past a monthly allowance. So a new bot message has to justify itself, and where we can, we fold new text into a message the bot already sends.
Why: a chatty bot is an expensive bot, and the cost ends up somewhere. Fewer, clearer messages are also easier to read. More in Designing a chatbot when every message costs money.
Phone first
Every screen, for customers and for our own staff, is designed for a phone around 360 to 390 pixels wide, roughly the width of most phones held upright. Then it's widened for bigger screens. Our standards put it bluntly: nobody uses the desktop view.
Why: that's how people use Lodge. You buy Wi-Fi from your phone, often on the data you're about to run out of.
Done means checked
"The tests pass" isn't the same as "it works". A screen is looked at on a phone-sized display, in light and dark. A change in behaviour is checked by actually running the path that changed. And whatever wasn't checked gets said first, plainly, before anything that was.
The engineer who makes a change also doesn't ship it. It's handed over with a list of what changed and what was checked, and a person at Lodge decides when it goes live.
Why: confident claims that outrun what was checked are how bugs reach customers. We'd rather hear "I didn't test the bank transfer path" than find out from you.
A few more, briefly
- No secrets in the website. The only payment key a browser ever sees is the public one Paystack designs for that.
- Your details are masked in support screens, unless the screen exists to show them to you.
- Closing your account removes your personal data. The records the law makes us keep are kept without your name. See Closing your account.
- Code is written to be read top to bottom by the person who maintains it, with comments that explain why rather than what.
Breaking a rule
A rule can be broken, but only when the owner says so for that change, and the change has to say which rule it broke and why.
If you see one of our screens breaking one of these rules, a price that doesn't match or a button that goes nowhere, tell us. Getting help says who to message and what to send.
Last checked against the product on 14 November 2026.