Paid, but no code yet? Here's exactly what happens
Every safety net between your card payment and your access code, in the order each one kicks in, and the three details to send us if none of them do.
Lodge Internet · 14 November 2026 · 3 min read
The Paystack window closes. The sheet on your screen says Payment successful, and underneath it a spinner keeps turning a little longer than feels right. This is the point where it's tempting to press refresh.
You can leave it alone. By this point your money is safe, and three separate things are working to get your code to you. Here they are, in the order they kick in.
A code was yours before you paid
When you choose to pay by card, the website first asks our server to set one code aside in your name. Only then does the Paystack window open. While you type your card details, nobody else can buy that code.
If you close the Paystack window without paying, the code goes straight back on sale. If even that message doesn't reach us, the hold runs out by itself after an hour.
So the last code on a plan can't be sold to someone else while you're halfway through paying for it.
The page keeps asking
The moment Paystack says paid, the page asks our server for your code. The server doesn't take the page's word for it. It checks with Paystack that the payment really went through, for the full total, and only then hands the code over.
If that answer is slow, or your connection drops for a moment, the page doesn't give up. The sheet changes to "Payment confirmed — securing your code…" and keeps checking quietly for a little over a minute.
However many times it asks, one payment can only ever become one code.
The server asks Paystack itself
Your browser isn't the only way a payment reaches us. Paystack also sends our server its own message for every successful payment, and that message issues your code even if you closed the tab the second you paid.
Messages like that can get lost on the way. So every few minutes our server also asks Paystack for its list of recent successful payments, and settles any it has no record of, exactly as if the message had arrived. If one still isn't settled after that, our team is alerted.
Whichever of these gets there first issues the code. The others find it already done and stop. Keeping the page open is still the quickest way to see your code, which is why we ask you to. Closing it doesn't lose anything.
Where the code turns up
Once it's issued, your code is emailed to you and saved to your Account. Open Account, find the plan under Recent purchases and tap Show code. Resend email sends it to you again. There's more on that in every code in one place.
If a code can't be issued at all
Rarely, a payment lands and there's genuinely no code to give, for example because the plan sold out at that exact moment. What happens next depends on how you paid.
- From your wallet, or by bank transfer: the money goes back into your Lodge Wallet by itself, ready for your next purchase. A transfer always lands in your wallet first, and only pays for the plan once a code can actually be issued.
- By card: the payment is recorded as owed to you and our team is told straight away. They either deliver the plan, credit your wallet or refund your card. Until then, the purchase shows as Awaiting fulfilment in your Account.
Either way, the screen tells you plainly that your payment was received, and shows your payment reference.
When to message us
Give it a few minutes first. Most of the time the code is in your email or your Account before you've finished worrying about it.
Message support if:
- a purchase in your Account says Awaiting fulfilment;
- the screen said your payment was received but a code couldn't be issued;
- your bank shows the charge, and after a few minutes there's still nothing in your Account or your email.
Send three things: your payment reference, the email on your account and your hostel. The reference is in the message the page showed you, and every purchase in your Account has a Ref button that copies it. With those, we can look your payment up with Paystack directly instead of asking you for screenshots.
Getting help lists who to message and where to find them.
Last checked against the product on 14 November 2026.