![\"Original](\"https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/10\/lalamove-roblox-gift-card-rider-scam-original-example.jpg\" "\\"\\"")
<\/figure>\nOverview<\/h2>\nA real delivery order becomes a request for redeemable codes<\/h3>\n
The Lalamove Roblox gift card scam targets delivery riders through \u201cBuy For Me\u201d orders. The customer asks the rider to purchase cards with an apparent reimbursement promise.<\/p>\n
Instead of receiving the cards at an address, the customer wants the redemption information. The rider can lose the purchase cost before completing the trip.<\/p>\n
The Singapore Police Force’s rider warning<\/a> confirms this method. It describes at least 13 reported cases and S$2,000 in losses since September 2026.<\/p>\n Those figures belong to the October 6 warning, not a running count. Lalamove and Roblox are legitimate services being used in a customer’s deception.<\/p>\n The customer falsely claims that sending the codes allows remote completion, without traveling to the delivery location.<\/p>\n Once redeemed, the balance is no longer protected by the rider holding the physical cards. The valuable part was the information sent in the photo.<\/p>\n The documented pattern includes:<\/p>\n Check unexpected instructions through the platform’s established support process. A customer’s chat message doesn’t create a reliable reimbursement guarantee.<\/p>\n The original conversation above was published by police with identifying details obscured. It shows the progression from an ordinary purchase request to exposed codes.<\/p>\n This differs from a fake Lalamove payment page sent to a Marketplace seller. Here, the person taking the financial risk is the delivery rider.<\/p>\n Buying something on a customer’s behalf can fit the purpose of a purchase-and-delivery job. The request doesn’t arrive completely outside the rider’s work.<\/p>\n The conversation can also remain polite. A customer promising to pay later may sound disorganized rather than dishonest.<\/p>\n What changes the situation is the request for usable codes before a verified payment or legitimate completion process. That transfers value away from the rider.<\/p>\n A suggested extra payment can make the job feel worthwhile. Don’t let the promised bonus distract from whose money is funding the cards.<\/p>\n The customer may also say no travel is needed after purchase. Saving time sounds helpful when you’re balancing multiple jobs.<\/p>\n But convenience isn’t payment protection. Sending a code can complete the customer’s real objective while leaving the rider’s expenses unsettled.<\/p>\n Keeping the conversation inside a real platform helps preserve evidence. It doesn’t make every customer instruction authorized by that platform.<\/p>\n You can report a suspicious request without accusing every purchase-and-delivery customer. The issue is this request for spendable information and unverified reimbursement.<\/p>\n The rider encounters the request through a normal-looking job. It appears to involve buying items at one location and taking them to another.<\/p>\n That starting point matters. The rider has already accepted a work task before the customer introduces the gift-card instructions.<\/p>\n Don’t assume that accepting an order commits you to every later request. A material change still needs to fit the platform’s actual rules.<\/p>\n The customer contacts the rider and asks for Roblox gift cards from a convenience store. The apparent plan is to reimburse the purchase.<\/p>\n Before spending personal funds, clarify how payment and completion are handled through the real service. Don’t rely solely on a stranger’s promise in chat.<\/p>\n If the request is unclear, contact support before buying. Having already reached the store isn’t a reason to take an unexplained financial risk.<\/p>\n A photograph of the front can identify a product without revealing redemption information. The sensitive details underneath the scratch area are a different matter.<\/p>\n The rider is told there is no need to deliver the physical cards. Sharing their codes supposedly lets the job finish remotely.<\/p>\n This changes the transaction. You’re no longer just transporting a purchase; you’re sending the information that lets someone consume its value.<\/p>\n Check that claim with the platform instead of letting the customer explain the rules. The person benefiting from the shortcut isn’t an independent authority.<\/p>\n If you’re uncomfortable, pause the job through the appropriate support route. Don’t disclose a code simply to avoid an argument about completion.<\/p>\n The customer asks the rider to reveal the hidden information and send it. A clear photo can supply everything needed to redeem the card.<\/p>\n The original police conversation pairs a scratch-and-photo request with promises of later payment. The photo supplies spendable information, not proof of delivery.<\/p>\n Earlier in that conversation, the rider asks whether the photographed product is correct. That is a normal product check, before redemption details enter the exchange.<\/p>\n The next instruction is different: no delivery is needed, but the scratch area must be revealed and photographed. The customer promises payment after checking it.<\/p>\n That distinction gives you a useful stopping point. A photo showing which item you found needn’t disclose the hidden information that spends its balance.<\/p>\n Don’t test a code by entering it into your own gaming account. That may consume or attach the balance and complicate the purchase further.<\/p>\n If the customer already received a usable photo, treat the code as exposed even if they claim it wasn’t received or didn’t work.<\/p>\n Police describe customers becoming unreachable or canceling after the codes are redeemed. The rider remains responsible for money spent buying the cards.<\/p>\n A cancellation notice doesn’t rewind redemption. Nor does keeping the packaging put the balance back under the rider’s control.<\/p>\n Don’t purchase another card because the first supposedly failed. Stop the exchange and involve the platform and relevant card support immediately.<\/p>\n Refund possibilities depend on the transaction and redemption status. Nobody in the suspicious conversation can guarantee that your expenses will be restored.<\/p>\n The original exchange also shows the rider asking for partial payment while the customer postpones reimbursement. Later messages ask whether this is a scam.<\/p>\n You don’t need to reach that stage before involving support. Repeated promises of payment aren’t a replacement for funds actually received.<\/p>\n If several cards were bought, keep a private record of which details were shared. That helps support distinguish exposed cards from any still protected.<\/p>\n Your receipt helps establish when, where, and how much you paid. It does not show that the customer has settled the amount owed to you.<\/p>\n Check actual funds through your trusted payment records. A customer’s screenshot saying \u201csent\u201d isn’t the same as money arriving.<\/p>\n If the platform displays a payment status, distinguish what that status covers. Don’t assume it includes every separate personal expense without checking.<\/p>\n A redeemable code carries value independently of delivery. Someone doesn’t need to collect the plastic card to use the balance it represents.<\/p>\n That is why the request to expose the scratch area is so important. It isn’t ordinary proof that you’ve found the right product.<\/p>\n Keep photographs containing codes private when asking for help. Posting them in a rider group can expose the same value to additional people.<\/p>\n A platform can record a job without validating every statement made during its chat. Account presence isn’t a personal guarantee against deception.<\/p>\n Likewise, don’t assume the account holder’s displayed name identifies the criminal. Preserve it for investigation rather than publicly accusing someone with a matching name.<\/p>\n Report the account and order through the service. The useful evidence is what happened inside the transaction, including requests, purchases, and cancellations.<\/p>\n Stop before revealing the redemption information. A purchase already made doesn’t mean you must complete the customer’s proposed shortcut.<\/p>\n Keep the cards and receipts intact. Ask the store or issuer what options exist without assuming gift cards can always be returned.<\/p>\n Contact Lalamove through the actual app or its official Singapore website<\/a>. Explain the code request and ask how to handle the order.<\/p>\n Don’t let the customer dictate a support number or move the dispute to another chat. That can separate the instruction from the platform’s record.<\/p>\n If the customer threatens a complaint, keep the messages. Provide them to support rather than sending codes to prevent a bad rating.<\/p>\n If reimbursement appears later, check the actual transaction before acting. Never send a separate \u201cverification\u201d payment to release money you are supposedly receiving.<\/p>\n For a genuine delivery, use the service’s established workflow. This warning doesn’t authorize ignoring legitimate customer property or bypassing platform procedures.<\/p>\n Stop sending card information.<\/strong> Don’t provide additional photos, replacement codes, or another purchase because the customer says the previous card failed.<\/p>\n Save the conversation before blocking or leaving it. You may need the exact order reference to connect the report to the customer account.<\/p>\n<\/li>\n Contact the card’s legitimate support promptly.<\/strong> Explain that redemption details were disclosed through a fraudulent delivery request and ask whether any value remains protectable.<\/p>\n Use contact information from the authentic card or issuer website. Keep purchase receipts available, but don’t assume support can reverse a completed redemption.<\/p>\n<\/li>\n Report the order to Lalamove.<\/strong> Include the customer messages, requested items, purchase costs, and the point at which codes were disclosed.<\/p>\n Ask how to preserve the job record and handle any disputed cancellation. Platform compensation isn’t guaranteed by the existence of a police warning.<\/p>\n<\/li>\n Discuss the purchase with your payment provider.<\/strong> If you used a bank card, explain that the underlying purchase funded a gift-card scam.<\/p>\n Be accurate about what you authorized. A real store purchase isn’t automatically an unauthorized bank transaction simply because the customer later deceived you.<\/p>\n<\/li>\n Keep a clear financial record.<\/strong> Separate the card face value, any delivery earnings, promised extras, and actual reimbursements received.<\/p>\n Retain receipts and card packaging for private reporting. Don’t destroy them because the balance seems spent or because the customer canceled.<\/p>\n<\/li>\nThe supposed shortcut is where the value leaves<\/h3>\n
\n
Don’t let the customer redefine how the order is completed<\/h3>\n
Why a Rider Might Agree Before Recognizing the Risk<\/h2>\n
How the Lalamove Roblox Gift Card Scam Works<\/h2>\n
Step 1: The customer places a purchase-and-delivery order<\/h3>\n
Step 2: The requested purchase becomes Roblox cards<\/h3>\n
Step 3: The customer offers remote completion<\/h3>\n
Step 4: Scratched codes or photos provide the spendable balance<\/h3>\n
Step 5: The customer redeems the value and avoids repayment<\/h3>\n
What the Card Photo Does and Doesn’t Prove<\/h2>\n
A receipt proves a purchase, not reimbursement<\/h3>\n
The physical card can be empty while still in your hand<\/h3>\n
A real order doesn’t make a customer trustworthy<\/h3>\n
If You Bought the Cards but Haven’t Sent Anything<\/h2>\n
What to Do if You Have Fallen Victim to This Scam<\/h2>\n
\n