Last Asylum: Plague Top Up Not Working? Common Recharge Problems & Fixes

Top up Last Asylum: Plague through the official Topuplist storefront for verified delivery, or compare safe options at Topuplist before you buy.

Last Asylum: Plague Top Up Not Working? (Quick Answer)

If your Last Asylum: Plague top up is not working, the purchase is usually not lost — it is stuck at the payment step or the in-game redemption step. Most failures fall into one of three buckets: the card or payment method was declined, the order went through but the diamonds have not been delivered yet, or the redemption code / exchange link failed to apply.

The game is published by 37GAMES GLOBAL and runs as a mobile title. According to the official community wiki, account linking is limited to Google and Facebook, and the safest purchase is always made from inside your own account. That single fact explains a large share of "top up not working" reports: players on the wrong bind, the wrong server, or an unsupported login path hit a wall before the transaction ever completes.

The most common reason a recharge fails

The number-one cause is a payment-side rejection, not a missing item. Banks frequently flag cross-border mobile-game purchases as suspicious, especially when the card issuer, the player's location, and the store region do not line up. A 3-D Secure (OTP) step that never arrives, a daily spending limit, or simply "insufficient funds" will abort the order at the gateway — and the game shows nothing because the game never received a completed order.

The second most common cause is a redemption step that was never finished. On many purchase paths the diamonds are not auto-credited; you must complete an exchange inside the game (or keep a redemption screen open) before the items land. Close that screen too early and the order sits in a pending state.

3 things to check in the first 5 minutes

1. Your email / payment app receipt. If you have no charge and no receipt, the order did not complete — retry the payment, do not wait for items.

1. The in-game mailbox and "pending" area. Some deliveries arrive in the mailbox rather than instantly to your balance.

1. Server and UID. Items are sent to the exact server + UID you entered at checkout. A mismatch makes a successful purchase look "missing."

Topuplist keeps the verified Last Asylum: Plague top-up page updated with supported methods so you can rule out an unsupported route before troubleshooting.

Why Your Last Asylum: Plague Recharge Failed (Root Causes)

Understanding the root cause saves you from "fixing" the wrong thing. Below are the failure modes players report most often, mapped to what is actually happening behind the screen.

Payment declined or card rejected

When the bank blocks the charge, you may see "payment failed," "transaction declined," or the spinner never resolves. Common triggers:

• International transaction block. Many debit and credit cards block foreign game stores by default.

• 3-D Secure / OTP failure. The verification step times out or the code never arrives.

• Daily or per-transaction limit. A large pack exceeds the card's ceiling.

• Insufficient funds or expired card. Obvious but frequent.

• Store region vs card region mismatch. Some gateways reject cards whose country differs from the store's billing region.

Action principle: if you were never charged, the item was never sent. This is a payment problem, not a delivery problem.

Order paid but diamonds not credited

This is the most anxious failure: money left your account, but the balance did not move. Usually the order is real but incomplete on the delivery side. Causes:

• The redemption step was not finished inside the game.

• You logged into the game from another device while delivery was processing, which interrupts the grant.

• The delivery method has a built-in wait (some routes are near-instant; others queue).

• The items landed in the mailbox rather than the wallet.

The official account wiki notes that purchases should be completed within your own account for them to apply correctly — a reminder that the grant is tied to the logged-in session and UID, not just the payment.

Redemption code or exchange link not working

Some purchase routes issue a code or a time-limited exchange link instead of an instant grant. These fail when:

• The code is case-sensitive and was pasted with an extra space or wrong casing.

• It was entered in the wrong menu (e.g., the wrong "redeem" field).

• The link expired — certain regional payment links are valid for only a few minutes.

• The code was already single-use consumed on a different account.

Because some links expire in minutes, treat any "open this to complete your purchase" prompt as time-critical.

"Interface closed" error during self top-up

On self-redemption flows you must keep the redemption screen open until confirmation. Closing the tab, refreshing, or backgrounding the app cancels the process. Players often report the order "disappeared" when in fact the screen was closed before the grant finalized. Re-open the redemption screen and let it run to 100%.

Wrong server or UID selected

Last Asylum: Plague is a server-based game. The diamonds are delivered to the exact server and UID captured at checkout. If you selected the wrong server — or typed the UID of an alt account — the items arrive somewhere, just not where you are looking. This is why double-checking server/UID before paying prevents the majority of "missing diamond" tickets.

Region or currency mismatch

The official in-game store prices and currency vary by account region. Players who switched regions (a change that is limited and not reversible on a whim) sometimes find the store rejecting a method or showing a currency that no longer matches their card. Mismatches here produce silent failures at checkout.

Apple ID account can't use agent top-up

Per the official wiki, account linking supports Google and Facebook only. Accounts bound solely to Apple ID frequently cannot use agent-assisted top-up paths and must first bind a Google or Facebook account before a purchase route will accept them. This shows up as "top up not supported for this account" even when the player has funds.

Verification code (OTP) not received

When a purchase requires an OTP — either from the bank (3-D Secure) or from the game's own verification — a missing code stalls everything. Causes: network lag, the code landing in spam, a device clock that is out of sync (TOTP apps fail), or carrier delay. Resyncing the clock and checking spam resolves most cases.

[Compare supported, verified methods on the Last Asylum: Plague page at Topuplist to avoid an unsupported route that silently fails.](https://topuplist.com/)

Step-by-Step Fixes for Each Problem

Match your symptom to the fix below. Work top to bottom; most players resolve the issue in one step.

Fix — payment declined

• Retry with a different card or method (wallet, another card brand).

• Enable international purchases with your bank, then retry.

• Wait 10–15 minutes and retry once — transient gateway errors clear.

• Confirm limits and funds before retrying a large pack.

• If the bank keeps blocking, use a method issued in the same region as the store.

Fix — paid but not received

• Do not log in from another device until delivery completes.

• Restart the game and check both the wallet and the mailbox.

• Wait the method's delivery window — instant routes are usually under a few minutes; queued routes can take longer.

• Keep your Order ID and UID ready (you'll need them for support if it still has not arrived).

Fix — redemption / code failure

• Re-copy the code without trailing spaces and respect upper/lower case.

• Use the correct in-game redemption menu (not a generic "gift" field).

• Respect the expiry — if a link expired, request a fresh one from where you bought it.

• If it says "already used," check whether it was applied to an alt account on the same server.

Fix — "interface closed" mid top-up

• Re-open the redemption screen and keep it active.

• Do not switch accounts or close the tab until you see the confirmation.

• If the order shows as paid but un-granted, repeat the redemption step rather than buying again.

Fix — wrong server or UID

• Verify server and UID before every purchase — this prevents the problem entirely.

• If you already bought on the wrong target, contact support with proof (Order ID + correct UID + server); some routes can re-route, though not all.

• Log into the exact account/server you intended to receive on and check there.

Fix — region / currency issue

• Prefer matching your real location to the store region to avoid future blocks.

• Understand that region switches are limited; do not switch casually hoping for a better price.

• If the store rejects your method after a region change, revert or use a method valid in that region.

Fix — Apple ID limitation

• Bind a Google or Facebook account to your profile (per the official wiki's supported links).

• Once bound, retry the purchase path that previously showed "not supported."

• Keep the Apple ID as a login but rely on the Google/Facebook bind for purchasing.

Fix — OTP / verification not arriving

• Check spam/junk for the code email.

• Resync your device clock (auto-set time) if using an authenticator.

• Retry on a stable network; carrier delays resolve in a few minutes.

• If the bank OTP fails repeatedly, use a different card or a non-OTP method.

How to Avoid Top Up Problems Before They Happen

Prevention is cheaper than a support ticket. Five habits remove almost every common failure.

Double-check server and UID before every purchase

This single step prevents the "diamonds went to the wrong account" class of problems. Screenshot your UID and server from the in-game profile and compare it to the checkout field every time.

Keep the redemption screen open until confirmation

If your route uses an in-game or browser redemption step, do not close, refresh, or background it until you see the success state. A cancelled screen is the most avoidable failure on this list.

Don't log into the game from another device during top-up

Delivery is tied to your active session and UID. Logging in elsewhere mid-delivery interrupts the grant. Stay on one device until the items are in your wallet.

Use a stable network and supported payment method

A flaky connection is why OTPs vanish and screens time out. Use Wi-Fi or solid mobile data, and pick a method known to work in your region. The official wiki's account page is the reference for what binds and what does not.

Save your Order ID and in-game UID immediately

The moment you pay, copy the Order ID and your UID + server into a note. If anything goes wrong, support will ask for exactly these, and having them ready turns a multi-day ticket into a same-day fix.

[For a verified, lower-friction route, the Last Asylum: Plague storefront on Topuplist documents supported methods up front.](https://topuplist.com/)

When to Contact Support (and What to Send)

If the fixes above do not recover your items, it is time to open a ticket — but only after you have waited the right amount of time.

Wait the right amount of time first

Learn the difference between "still delivering" and "stuck." Near-instant routes should credit within minutes; if yours is a queued route, allow its stated window before panicking. Opening a ticket too early often just tells you to wait.

Info support needs: Order ID, UID, server, receipt, timestamp

Have these ready:

• Order ID from your payment receipt.

• In-game UID and server (exactly as on your profile).

• Payment receipt (amount, method, time).

• Timestamp of the purchase.

Send them through the official support channel referenced on the game's official account wiki — not through a reseller chat, which cannot grant items directly.

Use official support channels only

The official community wiki at wiki-last-asylum.com/en/wiki/account documents the supported account links and the correct help path. The publisher's official site, last-asylum.com, is the other authoritative reference. Use these — never a third-party top-up site's "support" — for a missing-item claim, because only the official side can verify and re-grant.

Avoid chargebacks — they can make a missing item permanent

If the item is late, do not reverse the card payment. A chargeback is treated as fraud by the publisher and can escalate into an account penalty or ban, turning a delayed delivery into a permanent loss. Wait for support; reversing the charge is the worst possible move.

FAQ

1. Why is my Last Asylum: Plague top up not working after I paid?
Most likely the redemption step was not finished, or you logged in from another device during delivery. Restart the game, check the mailbox, and keep the redemption screen open next time. If you were never charged, it is a payment decline, not a delivery issue.

2. How long does Last Asylum: Plague top up take to arrive?
Near-instant routes usually credit within minutes. Queued or code-based routes can take longer, and some regional exchange links expire in minutes if not used promptly. Allow the method's stated window before contacting support.

3. My Last Asylum: Plague redemption code is not working — what do I do?
Re-copy it without trailing spaces and respect upper/lower case, enter it in the correct in-game redemption menu, and check the expiry. If it says "already used," verify whether it was applied to an alt account on the same server.

4. Why was my Last Asylum: Plague payment declined?
Common reasons: international transaction block, failed 3-D Secure OTP, daily limit, insufficient funds, or a store-region vs card-region mismatch. Retry with another card or enable international purchases with your bank.

5. Can an Apple ID account top up Last Asylum: Plague?
Accounts bound only to Apple ID often cannot use agent-assisted top-up. Per the official wiki, binding supports Google and Facebook — bind one of those, then retry the purchase path.

6. Who do I contact if my Last Asylum: Plague diamonds never arrived?
Use the official support channel documented on the game's official account wiki, and send your Order ID, UID, server, receipt, and timestamp. Avoid chargebacks, which can trigger an account penalty.