How To Top Up Free Fire Diamonds With Digi In Malaysia
The official way to load diamonds into your Free Fire account using a Digi line goes through the mobile carrier billing portal. You enter your UID, pick a diamond package, confirm with your Digi number, and wait for the SMS code. It usually lands within 30 seconds if you're on 4G. The whole thing takes about two minutes from start to finish on a good connection. There's a catch most guides don't mention. Digi's system sometimes holds the transaction for up to five minutes during peak hours, usually between 7pm and 10pm on weekdays. If your diamonds haven't shown up after three minutes, don't close the app. Refresh your game client and check your in-game mail instead. Garena often processes them through the mail system rather than a direct pop-up notification.
Top Up Ff Diamonds In Malaysia With Digi A Quick Guide
Open Free Fire on your phone. Tap the diamond icon on the home screen. Select "Top Up via Carrier" and choose Digi from the list. Input your FF UID correctly — double check the last four digits. Pick your diamond package, confirm the amount, then hit submit. You'll get a USSD prompt on your screen asking for PIN authorization. Enter your Digi payment PIN. Wait for the confirmation SMS. Diamonds should appear within two minutes. The minimum top-up amount is typically RM10 for around 100 diamonds. Higher bundles give better value per diamond but require larger upfront payments. I once accidentally ordered a RM50 bundle when I meant to get RM20 because the button sizes are confusingly similar on the confirmation screen. Nothing I could do about it at that point. The transaction had already been authorized through my Digi PIN. Make sure you read the amount before confirming. If the SMS code never arrives, the most common fix is toggling your data connection off and on again. Sometimes Digi's gateway drops the handoff between their billing system and Garena's server. I've also found that using WiFi instead of mobile data during the actual top-up step reduces failures by about half, even though you're paying through your carrier balance. The billing goes through Digi regardless of which network you're on for the transaction.
Another thing nobody warns you about: your Digi postpaid plan has a monthly spending cap on carrier billing items. If you've already maxed out your entertainment allowance for the month, the top-up will fail silently. You'll see a generic error message instead of a clear "limit reached" notification. Check your Digi app under Spending Limit to confirm you still have room before attempting a purchase. Free Fire diamonds purchased through carrier billing cannot be refunded through Garena if something goes wrong. Your recourse is Digi's dispute process, and that takes anywhere from three to fourteen business days depending on their ticket queue. Keep screenshots of every step — the confirmation page, the SMS receipt, and a screenshot of your in-game diamond balance afterward. Without those, disputing a failed top-up becomes nearly impossible. Sometimes the carrier billing option simply won't appear in the top-up menu. This happens more often than you'd think with certain Digi plans or if your number hasn't been fully verified with the latest KYC requirements. If that occurs, switching to a third-party reseller site like Codashop or in-game direct payment through Touch 'n Go eWallet is faster and usually costs the same since there's no carrier markup on the base price.
Get the Full Details
One more edge case: if you link multiple FF accounts to the same device, the wrong UID gets selected automatically half the time. I've lost diamonds to this at least twice. Always verify the player name that appears next to the UID before hitting submit. The number itself looks identical whether it's your main account or a alt you barely use. Carrier billing through Digi works fine if you're comfortable with the minor friction points. It's not broken, just occasionally unreliable during busy windows. Most people complete the transaction without issue. A smaller group runs into the problems I described above and ends up frustrated because the official documentation doesn't cover any of them.
