Skip to main content
Rasad

Blog

Blog Overview

Nafath integration: what to settle before you connect a national identity

PublisherAbwab Admin
Published OnNov 15, 2026
Reading Duration7 min read
Last UpdateNov 15, 2026
Nafath integration: what to settle before you connect a national identity

Nafath proves identity, not entitlement. This article explains the journeys, roles, consent, logs, test environment and fallback that protect the product after launch.

Nafath is not a “login with national ID” button. It is a trust decision: is the person at the screen really the holder of that identity, are they entitled to this account, and can we prove what happened afterwards? When you connect Nafath to a product, you are not adding a login method; you are moving part of the verification responsibility to a national service, and you need to organise what remains on your side.

This article separates what has to be settled before integration: journeys, roles, consent, logs, the test environment, and the fallback when a user cannot use the app. It does not provide API details, because those change and are managed through the approved provider. It provides the decisions that, if left open, will surface in the first week of production.

What Nafath changes in the product

The first thing that changes is the user model. An account is no longer only an email and a password; it is linked to a national identity. That means separating “account” from “person”: one person may have one account or several by role, and their entitlement may change without their identity changing. If you conflate the two, every edit becomes a data problem.

The second thing that changes is the journey. First registration is not the same as a returning login, and login is not the same as a high-risk action. You may need normal verification for login and stronger verification before changing account data or signing a contract. Define those levels before design, because each level adds a screen, a message and a failure state.

JourneyDecision requiredCommon failure
First registrationIs the account created automatically or after approval? What data do we keep?Creating a duplicate account for an existing identity
Returning loginVerify every time or use a trusted session? How long does the session last?Asking for verification on every click
High-risk actionWhich actions need stronger verification? Who approves?Changing sensitive data from an old session
Account recoveryWhat happens if the user loses the device or number?A support channel that transfers the account by hand
Internal staffDo staff log in with their identity or an admin account?Mixing client and staff permissions
Account closureWhat do we retain after closure, and why?Deleting the record that proves consent

Roles and responsibilities

Integrating with a national identity service means a third party sits in the login path. Define who does what: who approves a registration, who sees the verification result, who can disable an account, and who answers the user when verification fails. If these roles are not written down, every exception becomes a phone call.

Separate three levels: who verifies identity, who grants entitlement, and who reviews an incident. The national service may own the first, your product the second, and the security team the third. Mixing them makes investigation impossible: you cannot tell whether the problem is identity, entitlement or the event log.

Consent and privacy

A national identity is personal data, and any system that collects it falls under the Personal Data Protection Law. Collect as little as possible: do not store an ID image if a verification token is enough, and do not store the full ID number if the last four digits are enough. Every field you keep needs a reason, a retention period, and an access list.

Consent is not a screen at first registration only. It is a record: what the user agreed to, when, and which version of the text. If processing relies on a legitimate interest or a legal obligation, state that in the privacy policy and do not call it consent. The difference shows during a review or a complaint.

From reading to shipping

Want this built, not just explained?

Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.

Log retention has limits too. Login logs are useful for investigation, but they are not an open archive. Define the retention period, who can read them, and how they are protected. If data is processed outside the Kingdom, review the legal basis; the draft amendments to the Implementing Regulation propose a general requirement to store personal data inside the Kingdom with limited exceptions, but they remain a draft for now.

The test environment and the fallback

Do not test identity in production. Ask for a test environment and test identities, and test the cases that never appear in a demo: a new user, an existing user, a duplicate identity, a lost device, an old number, and an expired verification. Each case needs a clear message and a route to support.

The fallback is not a rare exception. Some users have no smartphone, or a phone that does not support the app, or are in an area with weak connectivity. If there is no documented alternative channel, support will drift into a manual workaround that opens a gap. Design the fallback before launch: a documented human check, a visit, or an agent, depending on the service.

The pre-integration checklist

Use this list in the first meeting with the provider. Every line needs a written answer, not a verbal promise.

  1. Journey: which flows will use Nafath, and which stay on a normal account?

  2. Identity: is the account tied to a person or a role, and how do we prevent duplicates?

  3. Consent: what is agreed, and how do we retain the version and date?

  4. Data: what is the minimum we keep, and for how long?

  5. Logs: who reads the login log, how is it protected, and how long is it kept?

  6. Testing: is there a test environment and test identities, and who supports them?

  7. Fallback: what does a user do when they cannot use the app?

  8. Incident: who calls whom when verification fails, and what is the response time?

  9. Exit: how do accounts and logs move if the provider changes?

Frequently asked questions

Is Nafath a replacement for a password? Not necessarily. It can be an additional factor or the primary login, depending on design. What matters is deciding what happens when it fails.

Do we keep the ID number? Do not keep it unless you have a functional reason and a defined retention period. Many systems need the verification result, not the number itself.

Does it work for non-Saudi users? It depends on the service and audience. If your product serves residents or visitors, you will need a documented alternative path.

How long does integration take? It depends on the number of flows and the test environment. What matters is starting with the core journey, not every case.

Who is responsible when a user fails verification? The user, but the product is responsible for explaining why and offering a fallback. “Verification failed” with no context is worse than nothing.

Do you help with integration? Yes, from journey design to testing and handover, in coordination with the approved provider.

Sources

Cover image: Mark Pellegrini, CC BY-SA 2.5, via Wikimedia Commons.

Get in Touch

We'd love to hear from you. Fill out the form and we'll get back to you soon.