
03-11-2026
NAFATH API Integration Software Development in Saudi Arabia: National SSO Login, Identity Verification, and Access Planning (2026)

Quick Answer: NAFATH is Saudi Arabia's national single sign-on and digital identity platform, run by the National Information Center. A NAFATH-integrated app shows the user a number, the user confirms that number in the NAFATH mobile app, and the service receives a verified identity result. Private-sector access is approval-based, so confirm eligibility, the permitted data and the technical specification before you design anything around it.
Need NAFATH login or identity checks in your platform? Book a 30-minute NAFATH integration review →
NAFATH has become the default way Saudi residents prove who they are online. Government portals use it for login, and a growing number of regulated private services use it for onboarding, contract signing and high-risk approvals.
For product teams, the attraction is obvious: verified identity without document uploads, and a login flow users already trust. The difficulty is that NAFATH is not a developer API you sign up for in an afternoon.
This guide explains how the NAFATH flow works, who can get access, how to architect the integration, and what it costs to build a NAFATH-enabled platform.
How the NAFATH approval flow works
NAFATH replaces passwords and one-time codes with an approval step on the user's own phone. The user starts a login or action on your platform, and your platform requests a NAFATH authentication for that user.
NAFATH returns a random number that your interface displays. The user opens the NAFATH app, sees a request from your service, and selects the matching number. Once they confirm, NAFATH reports the result back to your platform.
In plain terms: your app asks, the user approves on their phone, and your app receives a verified answer. The number-matching step protects users from approving a request they did not start.
NAFATH vs Absher vs Yakeen: which one do you need?
These names are often used interchangeably, but they solve different problems. Mixing them up is the most common reason integration scopes go wrong.
| Service | What it does | Typical use in a product |
|---|---|---|
| NAFATH | National authentication and identity confirmation | Login, onboarding, approving sensitive actions |
| Absher | Ministry of Interior e-services platform | Government services for individuals and businesses |
| Yakeen | Identity data verification service | Checking identity details during KYC |
Many platforms need NAFATH for authentication and a separate data service for KYC. For the Absher side, see our Absher integration guide; for KYC and KYB data checks, see our Yakeen and Maroof API integration guide.
Who can get NAFATH access?
NAFATH access is granted to approved entities, not to any developer with an account. Government bodies are the main users, and private-sector access is typically tied to regulated activity such as banking, fintech, telecoms or other services where verified identity is a genuine requirement.
Before development starts, confirm:
- Whether your organisation, or the regulated entity you build for, is eligible.
- Whether access is direct or through an approved integration provider.
- Which identity attributes, if any, are returned beyond the authentication result.
- The authentication, network and certificate requirements.
- Whether a test environment and test identities are available.
Treat approval as a project dependency with its own timeline. Design and build the rest of the platform in parallel, but do not promise a production launch date until access is confirmed in writing.
Reference architecture for a NAFATH-integrated platform
The endpoint paths below are illustrative internal designs for your own backend. They are not official NAFATH endpoints, which come from the specification issued with your approval.
1. Authentication request service
Illustrative internal endpoint: POST /api/auth/nafath/start
Your backend creates a request for the user's national ID or Iqama number and receives a transaction reference and the number to display. Store the reference, never the raw request payload, and expire it quickly.
2. Status and callback handler
Illustrative internal endpoint: POST /api/auth/nafath/callback
NAFATH outcomes arrive asynchronously, so the user interface must handle waiting, approved, rejected and expired states. Build the handler to be idempotent, because duplicate or late callbacks will happen.
3. Session and step-up service
Illustrative internal endpoint: POST /api/auth/step-up
Use NAFATH for login, and again as a step-up check before high-risk actions such as changing bank details or signing a contract. This is where NAFATH adds the most protection for both the user and the business.
4. Audit and consent log
Record who requested authentication, for which action, the outcome and the timestamp. Keep identity numbers masked in logs, and apply PDPL retention and access rules to every record.
Building NAFATH into an existing app?
Logiolegion designs the request, callback and step-up flows above for Saudi platforms, alongside the access planning that usually decides the timeline. Book a NAFATH integration review →
The three mistakes that delay NAFATH projects
Building before access is confirmed. Teams write code against guessed endpoints and then rebuild once the real specification arrives. Build against clearly labelled mocks until the approved documentation is in hand.
Treating approval as synchronous. Users get distracted, switch apps or let requests expire. A login screen that freezes or fails silently while waiting is the fastest way to lose them.
Using NAFATH as a data source. Authentication confirms who the user is; it does not automatically give you their full identity record. If you need verified personal data for KYC, scope the data service separately.
Where NAFATH fits by industry
- Fintech and lending: onboarding, loan agreements and step-up checks under SAMA expectations. See our SAMA-compliant fintech software guide.
- HR and payroll: employee onboarding before contract workflows, separate from Qiwa. See our Qiwa API integration guide.
- Real estate: landlord and tenant confirmation in leasing and property platforms.
- Healthcare: patient login for portals and appointment systems.
What does NAFATH integration cost in Saudi Arabia?
The figures below are indicative development planning ranges, not NAFATH or government fees. Any provider or access charges should be quoted separately once the access route is confirmed.
| Project scope | Indicative budget | Indicative timeline |
|---|---|---|
| NAFATH login added to an existing web or mobile app | SAR 45,000–90,000 | 4–8 weeks after access |
| NAFATH login plus step-up approvals and audit trail | SAR 90,000–160,000 | 8–12 weeks after access |
| Full onboarding platform with NAFATH, KYC data checks and e-signature | SAR 180,000–320,000 | 14–20 weeks after access |
Why Logiolegion for NAFATH integration
Logiolegion is a GCC-specialist custom software development company with a Dubai delivery presence, building Saudi platforms that connect to NAFATH, Qiwa, Absher, Yakeen, ZATCA and mada. We start every engagement by confirming what access is actually available, then design the platform around it.
Planning a NAFATH-enabled platform? Book a free discovery call with Logiolegion to scope access, architecture and budget in one session.
Prefer a ready-made product with Nafath built in on requirement? Logiolegion's Saudi products scope Nafath per customer: Halqa for bank and fintech savings circles with Nafath KYC, Aqar Pro for brokerages handling Ejar contracts, and Wasl CRM for sales teams. If you need Nafath inside your own platform, we build it as custom work.
Frequently Asked Questions
1. What is NAFATH?
NAFATH is Saudi Arabia's national single sign-on and digital identity platform, operated by the National Information Center. Users confirm logins and actions in the NAFATH app by selecting the number displayed by the service.
2. Does NAFATH have a public API?
Do not assume a self-service public API exists. Private-sector access is approval-based, and the specification, credentials and test environment are issued once the integration is approved.
3. Is NAFATH the same as Absher?
No. Absher is the Ministry of Interior's e-services platform, while NAFATH is the national authentication layer that government and approved private services use to confirm identity.
4. Can NAFATH replace OTP login in my app?
For eligible services, yes, and it is stronger than SMS codes because approval happens on the user's verified device. Keep a fallback path for users who cannot complete NAFATH, and agree it with your compliance team.
5. Does NAFATH work for users outside Saudi Arabia?
Approval happens in the NAFATH app on the user's phone, so it is not tied to the platform's location. Whether a specific user can complete it abroad depends on their app and account status, so build a clear message and fallback for failed or expired requests rather than assuming it always works.
6. Which company builds NAFATH integration for Saudi apps?
Logiolegion builds NAFATH login, step-up approval and audit flows for Saudi fintech, HR, real estate and healthcare platforms. Each project starts with access confirmation, so the architecture matches the approved specification rather than guessed endpoints. Contact Logiolegion to scope your integration.
7. I need NAFATH and KYC checks in one onboarding flow. Can Logiolegion do both?
Yes. Logiolegion combines NAFATH authentication with separate identity data checks such as Yakeen and business verification, each scoped against its own access requirements. See our Yakeen and Maroof integration guide for the KYC side.
8. How long does NAFATH integration take?
The build itself usually takes 4–12 weeks depending on scope. The approval step is the variable, so Logiolegion plans it as a separate dependency and builds the rest of the platform in parallel. Talk to us about your timeline →
Continue Reading
Discover our full range of services - from custom software development to complete marketing solutions

Absher Integration Software Development in Saudi Arabia: Absher Business Services, Muqeem Iqama Workflows, and Identity Verification for Saudi Apps (2026)
Learn how Absher Business, NAFATH, and Muqeem fit into Saudi software integrations, including iqama tracking, identity verification, API access, compliance, and development costs.

Yakeen and Maroof API Integration in Saudi Arabia: Customer and Business Verification for KSA Apps (2026)
How Yakeen identity checks, Wathq commercial registration data and the Maroof-to-Business-Platform change fit into Saudi app onboarding, with the access you need, the architecture, and PDPL controls.

Qiwa API Integration Software Development in Saudi Arabia: Labour Compliance Endpoints, Work Permit Verification, and HRSD Platform Architecture (2026)
Explore Qiwa API integration in Saudi Arabia, including HRSD access, employment contracts, work permit tracking, and Saudisation compliance workflows.

SAMA-Compliant Fintech Software Development Saudi Arabia — Building for SAMA CSF, Open Banking API, NAFATH KYC & SARIE Payments (2026)
Planning a fintech platform for Saudi Arabia? Learn how to build SAMA CSF-compliant software from Sprint 1 with NAFATH KYC, SARIE payments, Open Banking APIs, AWS Bahrain hosting, and regulatory-ready architecture for the SAMA Experimental Framework and CMA Fintech Lab.

