You never pay for a code you don't get
Before you pay, a code is set aside for you. After you pay, our server checks with Paystack itself and hands it over, even if you closed the page. Here is each step, and what happens in the rare case a code can't be issued.
Lodge Internet · 14 November 2026 · 4 min read
The plan you want is down to its last code. You tap it. Somewhere in the next block, someone else taps the same plan at the same moment.
Only one of you gets that code, and the other is told before they've paid anything. That is the first of three steps every purchase goes through, on the website and in the bot alike: hold, pay, claim.
Step one: we hold a code for you
When you choose a plan and head to payment, our server takes one code from your hostel's stock and puts your name on it. Nobody else can be sold that code while it's held for you.
If the stock is empty, this is where you find out: the plan is sold out, and no money has moved. You're never sent to a payment screen for a code that doesn't exist.
Starting again doesn't use up a second code. If you back out and choose the same plan again, we refresh the hold you already have. A hold doesn't last for ever, either. If you walk away, the code goes back into stock for the next person.
Step two: you pay
You pay by card through Paystack, the payment company that handles our checkouts, or by bank transfer, or from your Lodge wallet. Whichever you use, the total is the one the plan list showed you (see One price, wherever you buy).
A bank transfer goes into your own Lodge account number, lands in your wallet, and then pays for the order that's waiting. Your wallet has its own bank account number explains how that works.
Step three: we check, then hand it over
Your browser telling us "I've paid" isn't enough on its own, and we don't take its word for it. Our server asks Paystack directly whether the payment went through, and whether it was for the full total.
Only then does the code change hands, in a single step. It comes out of stock and goes into a purchase record with your payment reference on it. That record is the reason one payment can never become two codes. Whichever part of our system gets there first issues the code. Anything that arrives later for the same payment finds the record and hands back the same code.
Then it's on your screen, in your email, and in your account, where you can see it again or have it resent.
Closing the browser loses nothing
Say your phone dies on the Paystack screen, or you close the tab too early, or the network drops just as you tap Pay. The payment still reaches us, by more than one road:
- Paystack tells us itself. When a payment succeeds, Paystack sends our server a message directly. Nothing on your phone is involved. We save that message before acting on it, so even a restart halfway through can't lose it.
- We go and ask. On a regular schedule, our server asks Paystack for recent successful payments and settles any it has no record of. It also retries anything that didn't finish the first time.
- Your page asks when you come back. Open the site again and it checks the payment for you, and shows the code as soon as it exists.
Every one of these is safe to run twice, or all at once. They all end in the same single purchase record.
If your hold ran out while you were paying
Bank transfers can take a while. If the code we held for you has meanwhile been used or has run out on the hostel's Wi-Fi system, we don't hand it over. We check the held code is still good, and if it isn't, we take a fresh one from the same plan's stock.
If a code really can't be issued
Because a code is held before you pay, this is rare. But it can happen, for instance when the code held for you stopped working and nothing else is left in stock. What we do depends on how you paid.
- From your wallet, or by bank transfer. The money goes straight back into your wallet and the order is cancelled. It's there to spend on another plan whenever you like.
- By card. The screen tells you the payment was received and asks you to keep your payment reference. We record it as an order we owe you, and our team is emailed at once with the details. Under our Refund & Wallet Policy, we then deliver the plan, credit your wallet, or refund your card.
Behind that, our server keeps watch. If anyone has paid and still hasn't been sorted out after a short while, it alerts the team. A paid order doesn't quietly sit there.
What to do if you're waiting
Keep your payment reference. It's the one detail that lets us find your payment quickly. If your code hasn't appeared, Paid, but no code yet? walks through exactly what to check and who to message.
Last checked against the product on 14 November 2026.