How a Wi-Fi code gets from a hostel router to your phone
The short code you type into your hostel's Wi-Fi page was made by the hostel's own network, copied into our stock, held for you, handed over once, and emailed. Here's the whole trip.
Lodge Internet · 14 November 2026 · 4 min read
A short code goes into your hostel's Wi-Fi page, you tap Connect, and the internet arrives. It takes about as long as reading this sentence.
That code has had a busier day than it looks. It was made by the hostel's own network, copied into our stock, locked away, held for you, handed over exactly once, and emailed to you. Here's the trip, start to finish.
It starts at the hostel's network
The Wi-Fi in your hostel runs on TP-Link equipment. The access points around the building are run by a controller, the system that manages them all as one network. One controller can look after more than one hostel.
The controller is where codes are born. On TP-Link they're called vouchers, and each one is a ticket for a fixed amount of internet: so much data, for so many devices, for so many days. The controller makes them in batches, one batch per plan. Our team names each batch in a set pattern, so the name alone tells our system which plan its codes belong to.
That's the only place a code is ever created. We don't invent codes on our side. Every code we sell is one the hostel's network already knows and will accept.
Copying them into our stock
Our server signs in to each controller and reads its batches. This is the sync: it turns what the controller has into stock that the website and the bot can sell.
It is picky about what it takes. Only codes that are still unused and still have time left come across. A code that's been used, or is in use, or has run out is skipped every time. It never enters our stock again.
Each code is stored encrypted, so it's unreadable without the key, together with a fingerprint of it. The fingerprint lets the next sync recognise a code it has seen before without unlocking it, so the same code is refreshed in place rather than added twice.
Batch names matter here. A name that matches a plan we know goes straight to that plan. A name that's almost the same as a known plan, but not quite, is set aside for a person to check. We'd rather wait for a human than quietly mix two different plans together.
Our server doesn't read every controller all day long. On a schedule, it counts how many codes each plan has left, and only goes back to a controller when one of its plans is running low. Most checks find plenty and do nothing. Only one sync runs per controller at a time, so two can never trip over each other.
When a code disappears from the controller
Sometimes a code that was in our stock is no longer on the controller's list of unused codes. Someone used it, or it expired, or it was removed. The next sync notices and marks it unavailable, so it stops counting as stock.
There's a second check at the moment of sale. Before any code is held or handed over, we check it again, and a code marked as used, expired or unavailable is passed over, even if it's still sitting in our stock.
Held while you pay
When you choose a plan, one code from your hostel's stock is set aside with your name on it. Nobody else can be sold that code while you pay. If the stock is empty, you're told then, before you've paid anything.
You never pay for a code you don't get covers this step and the payment in detail.
Handed over, once
Once your payment is confirmed (for a card, our server checks with Paystack itself), the code changes hands in a single step. It leaves our stock, and a record of your purchase is written with the code and your payment reference. Those two things happen together or not at all.
That record is what makes "once" true. If two parts of our system try to finish the same payment, the second one finds the record and leaves the stock alone. One payment, one code.
Emailed and kept
Your code shows on the screen straight away. A moment later it's in your inbox too, with the details you need to connect at your hostel.
It's also kept on your account. On the website you can see it again or have the email sent again. In the bot, your purchases list can email you the record, code included. Every code you've bought, in one place shows where.
Then you type it in
Your phone talks to the hostel's network, the network asks the controller, and the controller recognises a code it made itself. Our server isn't even part of that conversation.
That's the trip. If a code you've bought doesn't connect, tell us with the code and your hostel, and we'll look at it. Getting help says how.
Last checked against the product on 14 November 2026.