How to Verify Lords Mobile UID and Server Before Topping Up Diamonds for a Friend

How to Verify Lords Mobile UID and Server Before Topping Up Diamonds for a Friend

Before topping up Lords Mobile Diamonds for a friend, verify three things from a fresh in-game screenshot: the exact UID, the current kingdom or server, and the visible nickname. In practical terms, UID is the core account identifier, but server or kingdom context is what often catches the mistake that UID-only buyers miss. If you are buying across devices or regions, that does not automatically create a problem. Entering old, cropped, or mismatched account details does. The safest habit is simple: confirm the account live, save proof before checkout, and only pay once the details match exactly.

If you want the broader process after verification, see the Lords Mobile top up guide.

What should you confirm before topping up Diamonds for a friend?

Most wrong-account top-ups do not start with a payment failure. They start with a copied UID from an old chat, a screenshot that hides the kingdom, or a buyer who assumes the display name is enough. It usually is not.

For a safe Lords Mobile recipient confirmation, the minimum match set is:

• the recipient’s nickname
• the UID, also called the IGG ID
• the kingdom or server
• whether the account is bound
• a recent in-game screenshot showing those details together

That last point matters more than people expect. A typed UID in chat is useful, but it should only confirm what is already visible in the screenshot. The screenshot is stronger because it ties the account details to a live in-game session instead of a message that may be outdated, mistyped, or copied from another character.

In practical top-up terms, the UID is the unique account identifier used for recharge and account binding. The server or kingdom is the game-world context. Community experience consistently treats both as important, and some buyers learn the hard way that a wrong server can still lead to a charged order and a bad delivery outcome. So if you are wondering which matters most, the honest answer is this: UID is the primary identifier, but server or kingdom is the safety check that prevents many avoidable mistakes.

The safest screenshot to request is the recipient’s in-game settings or account page showing the UID, kingdom or server, nickname, and ideally the date visible from the device overlay or sent live in chat at the same time. If the image is cropped, old, blurry, or missing the kingdom, ask for a new one before you pay.

How do you verify the Lords Mobile UID and server step by step?

The recipient can find the Lords Mobile UID in game through the settings area. The usual path is straightforward: log in, tap the profile or settings gear, scroll to the account section, and copy the IGG UID. IGG ID and UID refer to the same identifier for top-up and binding purposes.

That sounds simple, but the real verification step is not just find the UID. It is find the UID in the right context. When your friend sends the screenshot, read it as a set of matching details rather than a single number. Does the nickname match the person you expect? Is the kingdom or server visible and current? Is the screenshot clearly from the account settings page rather than from a cropped profile image or an old gallery photo?

A good Lords Mobile UID check is really a comparison exercise:

• compare the typed UID in chat against the screenshot
• compare the visible nickname against the friend you intend to top up
• compare the kingdom or server mentioned in chat or mail against the screenshot
• confirm the account binding status if possible

Account binding is worth checking because it helps with recovery and support. In settings, the player can usually show whether the account is bound to IGG, Google, Apple, or another linked login. That does not change where the Diamonds should go, but it can make support conversations clearer if something later goes wrong.

If your friend recently changed phones, switched from iOS to Android, or changed login method, do not panic. Device changes alone are not the main risk if the UID and server match. Region and device mostly affect billing routes, especially app-store purchases. They do not replace the need to verify the recipient account itself. In other words, a new phone is not the red flag; an old screenshot is.

For overseas buyers, this distinction matters. App-store billing can be tied to country settings, while web checkout is generally more flexible across regions. But even when cross-region payment is possible, the recipient details still need to be verified first. A flexible checkout route cannot fix a wrong UID or wrong kingdom.

Why does server or kingdom still matter if you already have the UID?

This is the part many thin guides skip. Buyers often hear that UID is unique and conclude that server is optional. In practice, that is too casual.

The kingdom or server acts like a second layer of confirmation. It helps catch cases where the buyer was given details from the wrong character, where the screenshot is stale, or where the recipient copied information from the wrong account. Community guidance repeatedly treats server mismatch as a serious source of failed or misdirected top-ups, especially when third-party or web forms ask for both UID and server.

So the better way to think about it is not UID versus server. It is UID plus server. The UID identifies the account. The server or kingdom confirms the intended game-world destination. The nickname helps you spot obvious mismatch. Binding status helps if support later needs context.

This is especially important before a Lords Mobile diamonds for friend purchase, because the buyer is often not logged into the recipient account and cannot verify the destination directly. You are relying on shared information. The more complete that information is, the lower the chance of a wrong-account mistake.

If the buyer and recipient are in different regions, the same logic applies. Web checkout may be easier than app-store billing for cross-region purchases, but the account match still depends on the same proof set: UID, server, nickname, and a fresh screenshot.

Evidence that actually helps if something goes wrong

When a top-up fails, arrives late, or appears to go to the wrong account, support usually moves faster when the buyer has both recipient proof and payment proof. A payment screenshot alone only shows that money moved. It does not show where the Diamonds were supposed to go.

The most useful evidence set is small but specific:

The order ID is especially important because it is the transaction reference that ties your payment to the recharge request. If you only save a card screenshot or wallet deduction image, support may still need the order ID before they can trace anything.

A practical habit is to save four things before you leave checkout: the recipient screenshot, the entered UID and server details, the order ID, and the receipt. If you are using Google Play or Apple billing, keep the store receipt as well. If you are using web checkout, keep the confirmation page and any transaction record. If you are paying through a wallet or card, save the payment proof too.

If you need more help organizing that proof set, the Lords Mobile receipt and order ID guide and the Lords Mobile payment support and missing Diamonds hub are the next places to check.

When is waiting reasonable, and when should you escalate?

Not every missing delivery is a wrong-account case. Some are just processing delays. The first job is to separate delay from mismatch, because the support path changes depending on which one you are dealing with.

A reasonable first step is to wait 10 to 30 minutes and ask the recipient to check both their Diamonds balance and in-game mail. If nothing appears, do not immediately pay again. Duplicate attempts can create a second problem on top of the first.

A practical timeline looks like this:

• First 10 minutes: confirm the payment status and avoid retrying
• 10 to 30 minutes: ask the recipient to check Diamonds and in-game mail
• Within the first hour: contact seller support if nothing has arrived and send the proof set
• Same day: if the charge went through app-store billing, also check Google Play or Apple purchase status
• Up to 24 hours: some delays are still within normal processing range
• After 24 hours: escalate with full proof if the issue remains unresolved

Who should you contact first? Start with the seller or checkout support, because they can usually trace the order fastest using the order ID and entered account details. If the issue appears to be billing-related rather than delivery-related, then platform billing support may be relevant, especially for Google Play or Apple purchases. If the case remains unresolved, official Lords Mobile support is the final escalation path.

Official support contacts listed in the facts provided are:

• Android: help.lords.en@igg.com
• iOS: help.lords.apple@igg.com

When you open a support ticket, include the UID, server or kingdom, nickname, receipt, order ID, payment proof, and the screenshot of the recipient account details. The more complete the first message is, the less back-and-forth you usually face.

If your issue is specifically a delay rather than a mismatch, the Lords Mobile charged but Diamonds not received guide is the most relevant next read.

What if the Diamonds went to the wrong UID or the wrong server?

This is where honesty matters. Refund and reversal outcomes are uncertain when the wrong recipient details were used. Community guidance is consistent on the risk: mistaken UID or server top-ups are often non-refundable, and reversals are not something you should promise to yourself or to a friend before paying.

That does not mean you should do nothing. It means you should frame the situation correctly.

If the payment is pending, the issue may still be billing or processing. If the payment completed but the Diamonds did not appear, it may be a delay. If the order was completed to another account because the UID or server was wrong, recovery becomes much harder. In that last case, support will usually need very clear evidence of what was entered, what the recipient provided, and what was charged.

A useful support message should include:

• the intended recipient nickname
• the intended UID
• the intended server or kingdom
• the screenshot the recipient sent
• the order ID
• the receipt
• the payment proof
• a short explanation of whether the issue is delay, mismatch, or suspected wrong-account delivery

If you paid through an app store, there may be limited refund windows depending on platform policy, but outcomes vary and should never be assumed. If you used web checkout or another seller route, refunds are generally case by case and proof-driven. That is why the proof set matters so much before payment, not just after.

The blunt but useful rule is this: if you suspect a wrong UID or wrong server, stop retrying, gather everything, and escalate immediately. If you suspect only a delay, wait within the reasonable window first, then escalate with the same proof set if it does not resolve.

For a deeper walkthrough of this exact problem, see Lords Mobile wrong UID top up what to do.

Before you pay: a 30-second safer top-up check

Right before checkout, send your friend one short confirmation message and compare it against the screenshot:

Please confirm your current Lords Mobile nickname, UID, kingdom/server, and whether this is your active bound account. I’m topping up based on this screenshot.

That tiny pause is often what prevents the expensive mistake. Event urgency, guild timing, or cross-region payment stress can make buyers rush, but no discount or deadline is worth sending Diamonds to the wrong account.

So the safest final flow is simple. Get a fresh in-game screenshot. Match the nickname, UID, and kingdom or server. Check binding status if possible. Save the screenshot, order details, order ID, and receipt. Then pay once, and keep the proof until the Diamonds are confirmed on the recipient account.

If you’re ready to buy after confirming the UID and server details, use VGTopup and keep your order proof saved until the Diamonds are confirmed on the recipient account.