The UAE PASS staging environment is the test copy of the national digital identity service. It has its own mobile app, its own user accounts, its own credentials and its own hostname, so nothing done in it touches a real identity. This guide puts the pieces a developer or tester needs in one place, in the order they are needed, with a link to the official page behind each one.

Everything below comes from the public documentation at docs.uaepass.ae, checked on 18 November 2026. Where two official pages disagree we say so, because a mismatch there is easy to copy into a first test.

What You Need for a First Test

WhatWhere it comes fromWorth knowing
Staging appQR codes on the official Staging Apps pageA separate app from the one in the app stores
Staging accountCreated inside the staging appNo Emirates ID needed, and it can be created from any location
Verified accountUpgraded in the staging self-care portal at stg.uaepass.aeNeeded for signing and for the full set of profile fields
Sandbox credentialsPublished in the quick start guideFor a proof of concept only
EndpointsThe production paths on stg-id.uaepass.aeOnly the hostname changes between environments

How to Get the UAE PASS Staging App

The staging app is not the UAE PASS app from the App Store or Google Play. The official Staging Apps page hands it out by QR code, one for Android and one for iOS, and shows no store listing for either. Scan the code with the device you will test on.

Android

The QR code points to stg-android.uaepass.ae. The staging build has its own package id, ae.uaepass.mainapp.stg, where production uses ae.uaepass.mainapp.

iOS

After installing, the page's one instruction is to open Settings, then Device Management, and trust the developer named Dubai Smart Government. The staging app answers to the URL scheme uaepassstg://, where production uses uaepass://.

How to Create a Staging Test Account

Your everyday UAE PASS login is not a staging login. The documentation has each developer or tester create a user in the staging app, and it confirms that this can be done from any location.

  1. Choose to create a new account and accept the terms.
  2. Proceed as a citizen or resident.
  3. Either scan the back of an Emirates ID, or pick the option for not having one and type the details in.
  4. Enter the one-time password sent to the mobile number, then the one sent to the email address.
  5. Set a PIN for the app.
  6. When the app offers to upgrade the account, choose Later. Neither upgrade route offered inside the app works in staging.

The result is a basic account, which the documentation calls SOP1. That is enough to test sign-in.

Account Types and the Data Each One Returns

The account type decides what your application receives after sign-in, so test with the type your real users will hold. The table covers citizens and residents and follows the official account types and attributes list pages, which give the exact field names.

TypeWhat it isSigningProfile data returned
SOP1 BasicUnverified. Mobile and email confirmed by one-time passwordNoneUser type, mobile, email, unique user id, first and last name in English
SOP2 AdvancedVerified against an Emirates IDAdvanced signatureEverything in SOP1, plus full name, Arabic names, Emirates ID number, nationality, gender, id type and title
SOP3 QualifiedVerified with face or fingerprint biometricsQualified signatureThe same as SOP2

A basic account never returns the Emirates ID number

If your application relies on the Emirates ID number, nationality or the Arabic name fields, a basic test account will not send them, however correct the integration is. Upgrade the test account before deciding that something is broken. Visitor accounts differ again, and the Emirates ID number is not returned for them at all.

How to Upgrade a Test Account to Verified

Face and kiosk verification do not work in the staging app, so a test account is upgraded in the staging self-care portal instead.

  1. Sign in at https://stg.uaepass.ae with the basic account.
  2. Select Upgrade and change the user type from SOP1 to SOP3.
  3. Fill in the missing fields. Without an Emirates ID, a dummy number is accepted.
  4. Sign out and back in so that the change shows.
  5. Under the signing credentials option, create the qualified certificate, setting a signing password when asked, and then the advanced certificate.

The staging app then shows the account as verified, with signing available. The documentation warns against moving a verified account back down. The only way to a basic account again is to delete the account in the staging app and create a new one, so it is worth keeping one basic and one verified test account from the start.

Sandbox Credentials and Staging Endpoints

The quick start guide publishes one shared set of credentials for proof-of-concept work. The client id is sandbox_stage, the client secret is the same value, and any callback address is accepted. They work in staging only. During onboarding the UAE PASS onboarding team issues the organisation its own staging credentials, and from that point the registered callback address has to match exactly.

EndpointStagingProduction
Authorisationhttps://stg-id.uaepass.ae/idshub/authorizehttps://id.uaepass.ae/idshub/authorize
Tokenhttps://stg-id.uaepass.ae/idshub/tokenhttps://id.uaepass.ae/idshub/token
User infohttps://stg-id.uaepass.ae/idshub/userinfohttps://id.uaepass.ae/idshub/userinfo
Logouthttps://stg-id.uaepass.ae/idshub/logouthttps://id.uaepass.ae/idshub/logout

How to Test Sign-In End to End

The official proof-of-concept walkthrough comes down to four moves, shown here with the sandbox client.

# 1. Open in a browser
https://stg-id.uaepass.ae/idshub/authorize
  ?response_type=code
  &client_id=sandbox_stage
  &scope=urn:uae:digitalid:profile:general
  &state={random_value}
  &redirect_uri={your_callback}
  &acr_values=urn:safelayer:tws:policies:authentication:level:low

# 2. Approve the request in the staging app

# 3. Exchange the code, server to server
POST https://stg-id.uaepass.ae/idshub/token
  grant_type=authorization_code
  redirect_uri={the same callback as step 1}
  code={code from the redirect}
  Authorization: Basic base64(client_id:client_secret)

# 4. Read the profile, server to server
GET https://stg-id.uaepass.ae/idshub/userinfo
  Authorization: Bearer {access_token}

# Source: docs.uaepass.ae quick start guide

In step 1 the browser asks for the test account's email, mobile number or Emirates ID and then shows a number. The staging app receives a request at the same moment, and the tester confirms it by picking the matching number. Steps 3 and 4 never run in the browser, and the official page attaches a Postman collection for them.

Where the Official Pages Disagree

PointOne page saysAnother saysSafe reading
Life of the authorisation codeThe walkthrough gives it ten minutesThe common issues page says to use it within ten secondsExchange the code the moment it arrives, and only once
Callback in the samplesThe sample request uses localhost:8000The sample redirect and token call use localhost:8080Send an identical callback in the authorisation and token calls

How to Test a Mobile App Against Staging

For app-to-app sign-in, the environment your app targets has to match the UAE PASS app installed on the device, which means the staging app for staging and the store app for production. Per the mobile integration guide, an Android app checks for the package ae.uaepass.mainapp.stg and an iOS app checks for the uaepassstg:// scheme. The on-device flow opens the login address in a web view inside your app with acr_values=urn:digitalid:authentication:flow:mobileondevice.

When the UAE PASS app is not on the device, the documented fallback is the browser-style sign-in with the level:low value from the walkthrough above, which the user approves from another device that does have the app.

Staging Errors and What They Mean

These come from the official common integration issues page, which lists more, including the signing errors.

What you seeDocumented causeWhat to do
Consumer Key not foundThe client is not registered on the UAE PASS sideSend the client id, secret and callback address to the onboarding team
Callback URL does not matchThe callback differs between the registration and your requestsMake it identical in the registration, the authorisation request and the token request
Invalid ScopeThe scope in the authorisation address is wrongCorrect the scope string
Invalid grantThe authorisation code was used too lateExchange the code straight away
Invalid basic header authenticationThe client id or secret is not sent as configuredCheck the Basic header on the token call
Access token validation failedThe token is not reaching the profile call correctlySend it as a Bearer token in the Authorization header
The wrong UAE PASS app opens on AndroidThe environment your app selected does not match the installed appMatch the environment to the app on the device
Extra logout parameters are ignoredLogout accepts only stateEncode the extra values into state and decode them on return

Moving From Sandbox to Your Own Credentials

The sandbox client proves the flow, but using it does not start onboarding. In the documented development phase, the onboarding team shares the organisation's own staging credentials and starts the agreement, which is a Service Provider Agreement for private entities and a Memorandum of Understanding for government ones. The organisation then completes its staging integration against the assessment checklist and tells the UAE PASS team, and that notice is what schedules the staging assessment.

When production follows, the endpoint paths stay the same and only the hostname changes, while the credentials and the registered callback addresses are new. Keeping all three in environment configuration, with nothing shared between staging and production, avoids carrying a staging value into a live release. Our UAE PASS integration guide covers eligibility and the wider onboarding sequence.

Frequently Asked Questions

From the Staging Apps page of the official documentation, which gives a QR code for Android and one for iOS. That page shows no App Store or Google Play listing for the staging app. The store version is the production app, and the app on the device has to match the environment being tested.

No. The staging app offers an option for people without an Emirates ID, where the details are typed in. When the account is later upgraded in the staging self-care portal, a dummy Emirates ID number is accepted.

Yes. The documentation states that staging accounts can be created from any location, which suits teams with developers or testers based abroad.

Both are sandbox_stage, and any callback address is accepted. They are published for proof-of-concept work, they work in staging only, and each organisation receives its own staging credentials during onboarding.

Because face and kiosk verification are switched off in staging. Choose Later when the app offers the upgrade, then upgrade the account to SOP3 in the staging self-care portal at stg.uaepass.ae.

Yes, with a verified test account. Signing needs an account upgraded to SOP3 with its signing certificates created in the self-care portal, and the sandbox credentials are documented as covering both authentication and signing. Signing uses its own endpoints and scopes, which the signature guides in the official documentation set out.

Sources

All checked on 18 November 2026.

BY BANKS designs and builds bespoke platforms for UAE organisations, including government and regulated services where UAE PASS sign-in is part of the build. If that is what you are planning, get in touch.

UAE PASS endpoints, credentials, app distribution and account rules may change. Treat docs.uaepass.ae as the canonical reference and this article as a summary of it. BY BANKS is an independent software engineering company. References to UAE PASS, TDRA, Digital Dubai and any other named bodies are descriptive only and do not imply endorsement, partnership or affiliation.