To add Nafath login to a mobile app, you first need approved access as a service provider. There is no public self-serve sign-up, so you apply through the operator or an approved provider. Then your backend sends a login request with the user’s National ID or Iqama number; your app shows the request number, and the user approves it in the Nafath app. After a successful result, your server creates its own session for the user.
The sign-in is simple for users. The hard parts are access, backend design, and edge cases. This guide covers all three, and it says clearly where official sources stay silent.
Nafath is Saudi Arabia’s Unified National Access system. It lets people sign in to government and private digital services with one national identity. The Saudi Data and AI Authority (SDAIA) runs it, and it works with a Nafath mobile app.
Nafath began as a joint effort of the National Information Center and the Ministry of Interior, and Elm helped build it. Public figures from November 2024 show more than 23.5 million users, more than 530 connected platforms, and more than 3 billion verification operations.
If you are planning a launch in the Kingdom, working with a mobile app development company in Saudi Arabia helps you plan identity, payments, and Arabic UX together.
Nafath is not Absher. Absher is the Ministry of Interior’s services platform. Nafath is the sign-in layer other services use, and its password route uses the Absher account password.
SDAIA’s user guide documents the app route. The user sees these steps:
The user has about 60 seconds to approve. A wrong number ends the attempt, and the user must start a new request from your service.
A second route needs no app. The user enters an ID number and the Absher password, then a one-time code sent to the Absher mobile number. Plan for both routes in your design.
Private companies can use Nafath. SDAIA describes it as a sign-in for public and private sector platforms. But there is no public developer portal in the official sources reviewed, and integration fees and onboarding lead times are not published.
You have three practical routes:
| Route | What it means | Watch out for |
| Onboard with the operator | Apply to SDAIA and the National Information Center as a service provider | Requirements and contract terms come through the application, not public pages |
| Use an approved service provider | A licensed partner connects you to Nafath | Pricing and lead times vary, so request them in writing |
| Document route | Verify identity with an ID document, chip reading, and face match | It does not replace Nafath where a regulator requires it |
If your company is a financial institution, check the SAMA rule. Saudi Central Bank circular No. 44037856 (26 November 2022) requires supervised institutions to use biometric authentication “with a high level of verification or above” for remote customer onboarding. It ties that feature to the Nafath application and tells institutions to integrate with an approved service provider. Treat this as a separate duty from identity risk checks, and confirm details with your compliance team.
Saudi fintech and government-adjacent teams plan this early. Our mobile app development company in Riyadh works with SAMA-related requirements during discovery, before any login screen is designed.
Follow this order to avoid rework.
Community integrations built for Nafath describe separate sandbox, staging, and production environments, app credentials, and server IP allowlisting. Treat these as examples, and follow the specification your provider gives you.
| Layer | Responsibility |
| Mobile app | Collect the ID number, show the request number and countdown, then show the result |
| Your backend | Hold credentials, create and track requests, verify results, issue your session |
| Nafath service | Send the request to the user’s Nafath app and return the outcome |
| Nafath app | Let the user approve with the matching number and PIN or biometrics |
The key rule is simple: the mobile app never talks to Nafath with secrets. The app talks to your backend. Your backend talks to Nafath. Our mobile app development team keeps this split on every identity project, so a leaked app build never exposes credentials.
A technically correct flow can still frustrate users. Pay attention to these details.
We cover layout and typography rules in detail in our guide to next-generation mobile apps for Saudi businesses.
Identity data is sensitive. Build these protections in from the start.
After the first Nafath sign-in, you can offer device biometrics (Face ID or fingerprint) for quick return logins. This improves the experience without asking for Nafath every time. Decide this with your compliance team, because some regulated flows require fresh verification.
Do not assume you will receive a full profile. Official public sources do not publish an attribute list. They show that the sign-in is tied to a National ID or Iqama number and that a request ends as accepted, rejected, or expired.
Community integrations report fields such as an identifier, an Arabic full name, and a user type, such as citizen or resident. Confirm the exact list in your onboarding agreement. If you need a date of birth, an address, or a photo, plan a second step to collect them.
Official sources do not publish an integration fee, a per-sign-in fee, or an onboarding lead time. Do not trust a number that comes without a source.
Ask for a written quote and timeline from the operator or provider before you commit. Include the development work in your budget as well. Login, backend, security, testing, and Arabic UX all take effort. See how Arabic localization and compliance affect budgets in our guide to mobile app development cost in Saudi Arabia.
To add Nafath login to a mobile app, treat access as the first milestone, not the last. Get approval, request the specification in writing, and design the backend so your app never touches secrets. Then build the flow around the real user: a number to match, 60 seconds to act, and a clear way to retry.
Teams that plan fallbacks, Arabic-first copy, and privacy rules early launch faster and see fewer failed logins. Nafath gives users a trusted way in. Your design decides whether it feels easy.
Yes. Nafath is described as a sign-in for public and private platforms. You still need approved access through the operator or an approved provider.
The official sources reviewed show no public developer portal. Access comes through onboarding. Community packages exist, but your provider’s specification is the source of truth.
The user has about 60 seconds to approve. After that, the request expires, and the user must start a new one from your service.
Yes. The login accepts a National ID number or an Iqama number. People who hold neither need another sign-in or verification route.
For institutions supervised by SAMA, circular No. 44037856 requires biometric authentication at a high level of verification for remote onboarding, and ties it to the Nafath application. Check the circular and your compliance team for your exact case.
No official fee is published. Ask the operator or an approved provider for a written quote.
Yes. A fallback helps users without a National ID or Iqama, users who miss the time window, and in case of any service interruption.
Facts in this guide come from the SDAIA Nafath user guide, Saudi Press Agency figures from November 2024, the SAMA Rulebook circular No. 44037856, and public integration documentation. Official sources do not publish fees, lead times, or a full attribute list. Confirm current details with the operator before you build.
We design the full flow: backend, Arabic-first screens, fallbacks, and security. Talk to our team, and we will scope your Nafath integration before you commit to a build.