Back to Blogs Blog Image

goAML OTP Not Received in UAE: What Should You Do?

Getting an OTP is an important part of accessing the UAE Financial Intelligence Unit's goAML registration and related services. However, users may sometimes receive one OTP but not another, find that an OTP has expired, enter an incorrect mobile number, or encounter problems while completing the registration process.

These problems can be frustrating because the user may have already completed several registration steps and still be unable to continue.

The UAEFIU's official FAQ addresses several OTP-related situations, including expired OTPs, missing email OTPs, incorrect mobile numbers registered during SACM registration, and problems accessing the e-services portal.

If your goAML OTP is not received in the UAE, the first step should be identifying which stage of the process is affected. The solution can be different depending on whether the issue involves SACM pre-registration, email delivery, SMS delivery, or later access to goAML.

What Is a goAML OTP?

An OTP, or one-time password, is a temporary verification code used during parts of the UAEFIU access and registration process.

The goAML registration process involves different stages. SACM is used for access to the FIU's services, while the goAML platform is used for organization registration and reporting-related activities.

The official UAEFIU FAQ explains that users may receive both email and SMS OTPs during SACM-related registration.

Because different stages use different credentials and verification methods, it is important not to assume that every OTP problem has the same cause.

1. Check Whether the OTP Has Expired

One of the first things to check is whether the OTP is still valid.

The UAEFIU FAQ states that if a user receives the required OTPs but encounters an error after entering them, the OTPs may have expired. In that situation, the guidance is to contact the relevant support team to request that the OTPs be refreshed.

Therefore, if you waited too long before entering the code, avoid repeatedly entering an old OTP.

Instead:

  1. Check when the OTP was received.
  2. Confirm that you are using the latest code.
  3. Avoid using an older message after requesting another OTP.
  4. If the OTP has expired, follow the official support process.

Using an outdated code repeatedly may not resolve the underlying issue.

2. Did You Receive the SMS OTP but Not the Email OTP?

This is another situation specifically addressed by UAEFIU.

If the SMS OTP has arrived but the email OTP has not, first check the email account's junk or spam folder.

The official UAEFIU FAQ states that the email may have been blocked by the organization's mail server. It recommends asking the company's IT team to whitelist the relevant UAEFIU system email address and then informing the goAML Support Team so the OTP can be resent.

This means the problem may not actually be with the goAML registration itself.

It could be an email-delivery or corporate-mail filtering issue.

Quick email OTP checklist

  • Check Inbox.
  • Check Junk/Spam.
  • Search for UAEFIU system emails.
  • Confirm that the registered email address is correct.
  • Ask IT whether the message was blocked.
  • Ask IT to whitelist the relevant UAEFIU system address.
  • Contact official support if the OTP needs to be resent.

3. Check Whether the Correct Mobile Number Was Registered

An incorrect mobile number can create a different problem.

The UAEFIU FAQ specifically addresses situations where a user entered the wrong mobile number during SACM registration and therefore cannot receive the SMS OTP.

According to the official guidance, the existing request needs to be revoked so the user can register again using the correct mobile number.

This is important because users should not assume that support can simply edit the number inside the existing registration request.

If the mobile number was entered incorrectly, the appropriate process may involve cancelling or revoking the current request and starting the registration again with the correct information.

4. Are You Using a UAE Mobile Number?

The UAEFIU FAQ also addresses international mobile numbers.

It states that the service provider does not deliver SMS OTPs to international mobile numbers and advises users to use a UAE mobile number.

Therefore, if you are attempting SACM registration using an overseas number, check whether the mobile number meets the current registration requirements before troubleshooting other issues.

This is particularly relevant for businesses whose owners, directors or employees are located outside the UAE.

The registered person may need to use the appropriate UAE mobile number for the SACM registration process.

5. Do Not Confuse SACM OTP With Your goAML Password

Another common source of confusion is treating every credential in the process as though it serves the same purpose.

The official goAML registration process involves SACM access as part of the first stage and goAML registration as a subsequent stage.

The UAEFIU registration guide explains that users registering as persons under an existing organization need the correct Org ID, while the organization's admin user/MLRO subsequently approves the request.

So if your OTP has been received successfully but you still cannot access goAML, the problem may no longer be an OTP problem.

You may instead be dealing with:

  • SACM access
  • Username
  • Google Authenticator
  • goAML password
  • Organization ID
  • User approval
  • Organization registration status

Identifying the correct stage can prevent unnecessary troubleshooting.

6. What If the Google Authenticator Code Is the Problem?

A Google Authenticator code is different from an OTP received by SMS or email.

The UAEFIU FAQ explains that users access the e-services portal using a username and Google Authenticator passcode in the relevant login process. It also provides guidance for users who have changed their mobile phone or lost their Google Authenticator setup.

Therefore, if you are receiving OTPs but the Google Authenticator code is not working, do not keep requesting new OTPs as though that is the problem.

Instead, check the authenticator setup and follow the relevant official recovery or setup instructions.

7. What If You Registered the Wrong Mobile Number?

This situation deserves separate attention because entering the wrong number can affect the entire verification process.

Suppose an employee accidentally enters one digit incorrectly during SACM registration.

The SMS OTP will go to the wrong number, meaning the employee may not be able to complete the verification.

According to UAEFIU's FAQ, the registered details cannot simply be amended in that situation. The current request needs to be cancelled so the user can apply again with the correct mobile number.

Therefore, always verify the mobile number carefully before submitting the registration request.

8. What If the OTP Problem Continues?

If you have checked the email folder, confirmed the mobile number, considered OTP expiry and still cannot complete the process, avoid repeatedly submitting new registration requests without understanding the issue.

Instead, identify exactly what happened.

For example:

Stage: SACM pre-registration

Problem: SMS OTP not received

Possible cause: Incorrect mobile number

Or:

Stage: SACM verification

Problem: Email OTP not received

Possible cause: Corporate email filtering

Or:

Stage: OTP received

Problem: OTP rejected

Possible cause: Expired code

Providing this information when contacting official support can make the issue easier to understand.

9. Keep Your Registration Details Consistent

OTP problems can sometimes expose a broader registration-data issue.

Before starting again, check that the information you are using is consistent, including:

  • Full name
  • Registered email
  • Mobile number
  • Identification details
  • Organization information
  • Organization ID, where applicable

The goAML registration guide requires the correct organization information for users registering as persons under an existing entity.

Avoid copying incorrect information from an old application or document simply because it was used previously.

10. What Should Businesses Ask Their IT Team to Check?

For employees registering on behalf of a UAE business, the IT team can be useful when the problem involves email delivery or browser-related access.

Ask IT to check:

  • Whether UAEFIU emails are being blocked.
  • Whether messages are being redirected to spam.
  • Whether the organization's mail server is filtering automated emails.
  • Whether the relevant UAEFIU system addresses are whitelisted.
  • Whether browser pop-ups are being blocked when the registration process requires them.

The UAEFIU FAQ specifically notes that email notifications may be blocked by an organization's mail servers and recommends involving the IT team in whitelisting the relevant system email address.

goAML OTP Troubleshooting Checklist

Before contacting support, check the following:

  • Did the SMS OTP arrive?
  • Did the email OTP arrive?
  • Did you check the junk/spam folder?
  • Is the registered email address correct?
  • Is the mobile number correct?
  • Are you using a UAE mobile number where required?
  • Has the OTP expired?
  • Are you entering the newest OTP?
  • Is your corporate email server blocking the message?
  • Does your IT team need to whitelist the UAEFIU email address?
  • Are you actually dealing with a Google Authenticator issue rather than an OTP issue?
  • Are you using the correct registration stage?
  • If registering as a person, are you using the correct Org ID?

Final Takeaway

A goAML OTP not received problem does not always mean that the goAML system or registration itself has failed.

The cause may be an expired OTP, an email being filtered, an incorrect mobile number, an unsupported mobile-number situation, or confusion between SACM verification and later goAML access.

The UAEFIU's current FAQ provides specific guidance for these scenarios, including checking junk mail, involving IT where email filtering is involved, addressing incorrect mobile numbers, and dealing with expired OTPs.

The most useful approach is therefore to identify which stage of registration is affected first and then follow the relevant official troubleshooting process.

FAQs

Why am I not receiving my goAML OTP?

The reason depends on the registration stage. For email OTP problems, check the junk folder and whether your organization's mail server is blocking the message. For other OTP problems, check whether the code has expired or whether the registered mobile number is correct.

I received the SMS OTP but not the email OTP. What should I do?

Check your junk or spam folder. If the email is not there, ask your IT team whether the UAEFIU system email has been blocked and request that it be whitelisted. The official FAQ also advises contacting goAML Support so the OTP can be resent.

What if I entered the wrong mobile number during SACM registration?

UAEFIU guidance says the current request should be revoked so you can register again using the correct mobile number.

Can I use an international mobile number for SACM OTP?

The UAEFIU FAQ states that SMS OTPs are not delivered to international mobile numbers and advises users to use a UAE mobile number.

What if my OTP has expired?

If the OTP has expired, follow the official support process to request refreshed OTPs rather than repeatedly entering the expired code.

Is a Google Authenticator code the same as an OTP?

No. Google Authenticator provides a separate passcode used in the relevant access process. If the authenticator code is failing, the problem may be related to the authenticator setup rather than the SMS or email OTP.

What should I do if I still cannot complete registration?

Identify the exact stage where the problem occurs, note the error or missing step, verify your registration details, and use the official UAEFIU support channel for the relevant issue.