UAE PASS integration for your website or app: who can apply, the onboarding steps, the login flow, account linking and digital signature
By Dr. Hani Elimam Manager & CEO, SmartTech Studio
UAE PASS is the national digital identity app that citizens and residents use to sign in to government services across the emirates. For a private platform, a UAE PASS integration promises verified names and Emirates ID numbers without asking anyone to type them, fewer passwords to reset, and, if you need it, legally meaningful digital signatures inside your own product. It also comes with an approval process, design rules and account-linking requirements that catch teams out when they treat it like adding one more social login button.
This guide is for UAE businesses and product owners in fintech, real estate, healthcare, education, HR and similar fields who want “Sign in with UAE PASS”, identity verification or digital signing in a website or app. It is based on the official developer documentation at docs.uaepass.ae, which we read page by page: who may integrate, the onboarding phases, the login flow, account levels and linking, mobile apps, signatures and data protection.
SmartTech Studio builds custom software and apps in Abu Dhabi. We have not published a UAE PASS case study, so nothing below is a client story. It is what the documentation requires and how we would plan the work. Where the documentation is silent, for example on timelines, we say so rather than guess.
Can a private company integrate UAE PASS?
Yes. The opening page of the documentation lists three capabilities and who may use each. Authentication, and digital signature and eSeal, are available to government entities and private organizations alike. Data and document sharing is available to private organizations only, with a note that government entities reach document sharing through GSB.
UAE PASS is described there as part of the Smart Government National Plan initiative managed by Digital Dubai (DDA), the Telecommunications and Digital Government Regulatory Authority (TDRA) and the Abu Dhabi Digital Authority (ADDA), giving each user a single profile across service providers. Your company becomes one of those service providers.
The practical entry condition for a private company is a UAE trade licence. In the first onboarding step you request integration through the UAE PASS developer portal (uaepass.ae/developers) and state whether you are a government or a private entity. The onboarding team then asks private entities for a valid UAE trade licence and, according to the docs, guides you through the process based on the emirate where you are registered. The documentation lists no sector restrictions. What it does require is a defined use case, which the onboarding team must approve before you get credentials.
Settle one more thing early. UAE PASS is meant to carry the whole sign-in journey, not one isolated step. The implementation guidelines say that using UAE PASS for a limited scope must be avoided, and give the example of using it only to update a user’s email address or mobile number.
The onboarding process, phase by phase
Onboarding runs in four phases: initiation, development, assessment and go-live. Every step in the docs names who is responsible, either the service provider or the UAE PASS onboarding team. The table condenses them.
| Phase | What you do | What the UAE PASS team does |
|---|---|---|
| Initiation | Request integration on the developer portal; return the questionnaire for each feature, a workflow diagram based on a standard use case, and UI mockups | Asks for your trade licence, sends the welcome pack, evaluates and approves the use case |
| Development | Integrate against the staging environment, check your work against the assessment checklist, then ask for the staging assessment | Issues staging credentials and starts the Service Provider Agreement (private entities) or MOU (government entities) |
| Assessment | Fix anything found, record videos of every tested scenario, and, as a private entity, sign the Service Provider Agreement | Runs the assessment and a second round if needed, then has management approve the videos and the use case |
| Go-live | Submit the go-live form, implement in production, and set the go-live date | Issues production credentials, runs the production assessment, and gives you service desk access for support |
The documentation publishes no durations, but it does flag what slows projects down: a use case that deviates from the standard use-case guidelines needs management approval. The quickest route is to choose one of the standard scenarios, draw your flow around it, and mark its use-case number on the diagram, as the docs ask.
Your developers can start learning before any of this. The docs publish shared test credentials for proof-of-concept work, valid on staging only, for use with the UAE PASS staging app. Your own staging credentials come later, during onboarding.
How UAE PASS login works: the OAuth 2.0 authorization code flow
Technically, UAE PASS authentication is an OAuth 2.0 integration using the authorization code grant. The docs mention OpenID Connect in places, but the documented web flow fetches the user’s profile from a userinfo endpoint. There are two environments on separate hosts, staging at stg-id.uaepass.ae and production at id.uaepass.ae, each with authorize, token, userinfo and logout endpoints under /idshub.
1. Your site sends the browser to the authorize endpoint with response_type=code, your client_id, a registered redirect_uri, a scope (the standard one is urn:uae:digitalid:profile:general), acr_values, a state value and, optionally, ui_locales set to en or ar so the UAE PASS page opens in the visitor’s language. The docs recommend the state parameter as protection against cross-site request forgery.
2. The user enters an identifier (email, mobile number or Emirates ID) and approves a push notification in the UAE PASS app. UAE PASS then redirects back to your redirect URI with a one-time authorization code.
3. Your server exchanges that code at the token endpoint, authenticating with your client ID and secret in an HTTP Basic header. The docs stress that this is a back-channel call, never made from the browser, and that the redirect URI must match the one used in step 1 exactly, or the call fails. The code is single-use and short-lived, so exchange it immediately.
4. With the access token, your server calls userinfo and receives the profile. According to the documentation’s FAQ, access tokens currently expire after 3600 seconds (one hour) in production, and the lifetime is the same for every service provider.
5. When the user signs out of your portal, the docs say you should log them out of UAE PASS too, through the logout endpoint with a redirect back to your site.
SOP1, SOP2, SOP3: account levels and the data you receive
Every UAE PASS account has a level, which the documentation calls the strength of profile, or SOP. SOP1 is a basic account: email and mobile number verified by OTP, Emirates ID not verified. SOP2 is an advanced, verified account: the Emirates ID is verified and the user can sign documents at advanced level. SOP3 is a qualified account, verified with finger or face biometrics, with signatures at qualified level. Authentication supports all three. Your use case decides which you accept, and the docs ask you to state the SOP level on your use-case diagram.
The level controls what userinfo returns. For citizens and residents, every level gives you userType (the level itself), a verified mobile number and email, the UUID, and the first and last name in English. The verified Emirates ID number (idn), the full name in English and Arabic, nationality, gender, ID type and title come back only for SOP2 and SOP3. The docs are explicit that SOP1 accounts return no Emirates ID number, and that you should show SOP1 users an appropriate message if your service needs one.
That message is not yours to word freely. The design guidelines publish the error texts in English and in Arabic. The SOP1 restriction, for example, reads: “You are not eligible to access this service. Your account is either not upgraded or you have a visitor account.” A bilingual product should use those strings as published.
A practical rule: ask for the lowest level your service genuinely needs. Data you never request is data you never have to protect.
Account linking: the part most projects underestimate
If your platform already has users, each one who arrives through UAE PASS must be matched to the right existing account once, and then recognised on every later visit. The documentation gives this its own section and design guidelines, and the assessment checks it.
The key is the UUID, UAE PASS’s unique user identifier. The implementation guidelines make storing it mandatory after linking or registration, and later sign-ins should match on it. For the first link, the docs allow two methods. Automatic linking matches a unique, verified attribute you already hold, typically a verified Emirates ID number. Manual linking asks the user to sign in once with their existing username and password, then stores the UUID against that account. Linking on email or mobile number alone is discouraged, because users can change both in UAE PASS at any time, which leaves orphaned links and duplicate accounts.
New users get a third path: registration with your form pre-filled from UAE PASS. The rules here surprise most teams. Data auto-populated from UAE PASS must not be editable. The user must not be asked to create a username and password during UAE PASS registration, and if you create local credentials in the background, you may not send them by email or SMS; the user receives them only through your normal forgot-password flow, if they ever choose it. The guidelines also say not to link verified UAE PASS accounts with unverified local accounts or the reverse, and to release automatic linking, manual linking and new registration together, in the same go-live.
This is where a clean data model pays off. A real estate CRM or a clinic management system that already stores verified Emirates ID numbers can link automatically. One that stored whatever customers typed cannot treat those numbers as verified: the guidelines say a manually entered Emirates ID, email or mobile number, without an OTP, an activation link or a document check, does not count as a verified attribute.
Mobile apps: the app-to-app switch
On a phone, the user should not have to type anything. The docs describe the mobile integration through a WebView inside your app rather than the system browser. Your app first checks whether the UAE PASS app is installed, by package ID on Android and by URL scheme on iOS.
If it is installed, your app opens the login URL with the acr_values setting for on-device authentication, watches the WebView for UAE PASS’s deep link, rewrites that link’s success and failure URLs to point to your app’s own URI scheme, and opens it so the UAE PASS app takes over. When the user confirms, UAE PASS calls your app back, your app loads the saved success URL in the same WebView, and the authorization code arrives. From there, the token and userinfo calls are the same as on the web, made by your server.
If the UAE PASS app is not on that phone, the login page asks for the user’s identifier and sends a push notification to whichever other device has UAE PASS installed.
Three details save days of debugging. Register your own URI scheme, not the one from the demo app, or callbacks can land in another provider’s app. Make sure the staging build of your app talks to the staging UAE PASS app, which uses its own scheme. And remember that client credentials are channel-specific: web and mobile get separate ones, and reusing them on another channel needs UAE PASS approval. Our app development team plans this flow from the first wireframe, because it shapes the onboarding screens.
Visitors, companies and minors: who UAE PASS does not cover on its own
Verified UAE PASS accounts for citizens and residents rest on the Emirates ID, and not everyone in your audience holds one. The docs say visitors can register and upgrade their accounts with a passport or GCC ID, and a service provider can choose to accept visitor authentication. If you do, you add two scopes to receive profileType (1 for citizens and residents, 2 for visitors) and unifiedId, and you handle the flow according to what comes back. Visitors never return an Emirates ID number, so any logic keyed on it needs a second path.
For tourists and overseas customers with no UAE PASS at all, keep your existing sign-in. The guidelines require the UAE PASS flow to stay completely separate from your local login and registration, never merged into them, so the two sit side by side on the sign-in page. They also require consistency: users who may sign in locally should be able to sign in with UAE PASS as well.
Companies are a separate question. UAE PASS gives accounts to verified individuals, not to organizations. If your platform serves businesses, deciding who may act for which company is your job after authentication, for example by mapping Emirates ID numbers to authorized representatives. The same logic applies to the elderly and to minors: the FAQ says service providers must offer other channels, or an authorized-representative model, so that no one is left behind.
Digital signature, eSeal and document sharing
Beyond sign-in, UAE PASS can let users sign documents inside your product. The signing guide makes UAE PASS authentication before signing mandatory, so that the person signing is the person signed in. SOP1 users cannot sign at all. SOP2 users sign at advanced level, and only if your implementation allows advanced signatures. SOP3 users sign at qualified level. There are single-signer and multiple-signer flows. The FAQ lists the supported formats: PAdES for PDF documents, CAdES for other files and XAdES for XML.
If documents must not leave your servers, the hash-signing feature sends only the document’s hash to UAE PASS, which signs it and returns it; your system then embeds the signature in the PDF. Signed documents can be verified in the UAE PASS app, on its self-care portal, or through a verification API inside your own system.
An eSeal is different. It is applied by an authorized user on behalf of the entity, not of a person, and it needs a certificate. For Dubai entities the docs describe a process with the DESC certification authority; for entities outside Dubai the process runs through ICP, whose vetting confirms that the signatory is authorized to sign for the entity under a general power of attorney. A document can carry two eSeals, but each entity can apply only one.
Finally, the newer data processing consent feature lets a service provider request documents held by another provider, with the user’s approval. Its scope page sets clear limits: documents only, not attributes or plain text; SOP3 users only; and approval happens in the UAE PASS mobile app, not the web portal.
Handling UAE PASS data: PDPL and security basics
A working integration puts verified identity data in your database: names in two languages, nationality, Emirates ID numbers, phone numbers. In the UAE, Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data applies to processing personal data, including through electronic systems. The government portal u.ae notes that it came into force on 2 January 2022 and that it prohibits processing personal data without the owner’s consent, subject to exceptions. The same page lists the DIFC’s own Data Protection Law (DIFC Law No. 5 of 2020) among related laws, so confirm with your lawyer which regime applies to your company.
In practice that means: request only the scopes and attributes your service needs; tell users in your privacy notice what you receive from UAE PASS and why; keep the client secret and tokens on the server, never in the app or the browser; encrypt identity data at rest; limit who in your team can see Emirates ID numbers; and log every access.
None of these controls is a UAE PASS extra. Role-based access, an audit log, encryption, automated backups and a separate staging environment are standard in the systems we build. For the wider picture, see our guide to preventing data breaches and staying compliant in the UAE.
Planning the work, and what it costs with us
If you are scoping a UAE PASS integration, prepare the onboarding inputs before any code: the features you need (authentication only, or signature and eSeal too), the minimum SOP level, the standard use case you will follow, a flow diagram, wireframes in English and Arabic, and a decision on how existing accounts will be linked. These are exactly what the initiation phase asks for, and they decide most of the build effort.
We have not published a UAE PASS case study, so we will not claim one. What we can say is this: our builds include identity, roles and audit logs as standard, our products are bilingual with right-to-left Arabic interfaces, and we scope an integration like this as part of a custom software project. Our custom software starts from AED 25,000 and a cross-platform mobile app from AED 10,000, both excluding VAT; the final price depends on how much of your system already exists. For how such budgets break down, see custom software development cost in the UAE, and for the web side, custom web app development. Your domain, code and accounts stay in your company’s name.
If you already run a platform, send us a short description and we will tell you what adding UAE PASS would involve.
Sources
- UAE PASS developer documentation: UAE PASS capabilities and who can use them
- UAE PASS developer documentation: Onboarding, initiation phase
- UAE PASS developer documentation: User account types (SOP1, SOP2, SOP3)
- UAE PASS developer documentation: Attributes list
- UAE PASS developer documentation: Standard implementation guidelines
- UAE Government portal (u.ae): Data protection laws
FAQ
Is UAE PASS integration free for private companies?
The documentation’s FAQ says there are currently no charges for integrating with UAE PASS, but the same answer refers to a review in 2021, so treat it as dated. Check the current terms in the Service Provider Agreement that private entities sign during onboarding. Your own development and hosting costs are separate.
Do we need a UAE trade licence to integrate UAE PASS?
For a private entity, yes in practice: in the initiation phase the onboarding team asks private entities for a valid UAE trade licence. The FAQ says the staging and production APIs are reachable from overseas, so a development team abroad can build and test, but the request comes from the business that holds the licence.
How long does UAE PASS onboarding take?
The documentation publishes no timeline. It depends on how quickly you return the questionnaires, flow diagram and mockups, whether you pass the staging assessment in one round, and whether your use case follows the standard guidelines. Non-standard use cases need management approval, which the docs say may extend the processing time.