Skip to content
Smart Lead Tech
Home
Services
Our work
Saudi Arabia
About us
Blog
Contact us
🇸🇦العربيةContact now
Smart Lead Tech

Smart software solutions

Follow us

Company

  • About us
  • Our work
  • Our services
  • Saudi Arabia
  • Restaurant POS
  • Contact us
  • Book a call

Quick links

  • Blogs
  • Pricing
  • Refund policy
  • Privacy policy
  • Terms and conditions
  • Data deletion

Contact us

  • Egypt — Head Office

    Office 6, Bldg 23, Makkah Al-Mukarramah St., Omraneya, Giza 3540203, Egypt
  • Saudi Arabia — Branch

    Bldg 2646, Secondary 123, Street 7697, Ishbiliyah Dist., Jubail 35416, Kingdom of Saudi Arabia
  • Email address

    help@smartleadtech.com
  • Phone number 🇪🇬

    +20 102 201 4671
  • Phone number 🇸🇦

    +966 53 044 7112

© 2026 Smart Lead Tech. All rights reserved.

  • Smart Lead Tech Information Technology LLC·Commercial Register ⁦61239⁩·Tax ID ⁦774-391-316⁩

  • Smart Lead Tech Software Establishment·CR ⁦7054902585⁩·VAT

An engineer’s guide to Saudi government platform integrations: Nafath, Absher, Wathq, Ejar, Sakani — what repeats in every project

Every serious product in Saudi Arabia reaches the same moment: “we need to integrate with Nafath”. Then Wathq for commercial registrations, Ejar for contracts, then Sakani, Absher or Muqeem depending on the sector. We ha…

09/08/2026 — 10 min read

An integration map between an app and Saudi government platforms

Every serious product in Saudi Arabia reaches the same moment: “we need to integrate with Nafath”. Then Wathq for commercial registrations, Ejar for contracts, then Sakani, Absher or Muqeem depending on the sector. We have done it for property, booking, e-signature and HR platforms, and this is what repeats regardless of the platform.

The map: who does what

  • Nafath: unified national authentication — “log in with your identity”. Gives you a verified identity and basic data.
  • Absher / Yakeen: verifying and matching individuals’ data (ID, date of birth).
  • Wathq: commercial registration and establishment data — who owns and who represents the company.
  • Ejar: documenting residential and commercial tenancy contracts.
  • Sakani: the housing portal — projects, units and support.
  • Muqeem / Musaned: resident and workforce data — for HR and payroll systems.
  • Fatoora (ZATCA): e-invoicing — for anyone who sells.

Rule 1: onboarding is the real project

The code takes two weeks; getting approvals, certificates, the test environment and signatures takes two months. Start the paperwork the day the contract is signed, not the day the UI is done.

Rule 2: one abstraction layer per authority

An internal module called Identity with Nafath behind it, a Business module with Wathq behind it, a Tenancy module with Ejar behind it. Business logic talks to our modules, not to the authorities’ APIs. When an authority changes its interface (and it will), one file changes.

Never let the word “Nafath” appear in more than one folder of your repository.

Rule 3: every call has a log and a reason

Government bodies ask: why did you query this person? Record who asked, for which operation, when, and the result — before you are asked. That is also what makes PDPL compliance real rather than paper.

Rule 4: design for outages and slowness

  • Explicit timeouts and retries with exponential backoff.
  • A human fallback path: “verification unavailable right now — we will complete it within an hour and notify you”.
  • Never block the customer’s whole flow on a secondary lookup; make verification asynchronous where possible.

Rule 5: the simulator first

For every integration we build a local simulator returning the same shapes and errors we saw in production. The team develops and tests without depending on the authority’s environment being up, and automated tests include the real failure cases (expired certificate, unknown number, timeout).

Patterns by sector

  • Real estate: Nafath + Ejar (+ Sakani for subsidies). Tenant and owner verified and the contract documented before any payment.
  • HR and payroll: Muqeem/Musaned + Wage Protection. In our payroll systems the WPS file is generated from the approved payroll run, not from a manual Excel file.
  • E-signature: Nafath for identity + timestamp + audit trail — as in Tawqe3k.
  • Commerce: Wathq to verify the merchant + Fatoora for invoicing.

Takeaway for the decision maker

Government integrations are not a feature added at the end; they decide whether your product gets approved at all. Start early, isolate them architecturally, log everything, and build the simulator before the UI. The difference between a project launched on time and one delayed by half a year is usually this chapter.

Share

Projects related to this article

  • Real EstateLaravelVue.js

    Mashrouk — Real-Estate Co-Investment Platform

    A platform that brings individuals together to co-own and co-invest in real estate — securely and transparently from listing to closing.

    Show more
    Mashrouk — organised real-estate co-investment
  • Real EstateLaravel

    Tatweer — Real-Estate & Engineering Services Platform

    A platform built from scratch to serve landowners, engineers, consultants and contractors — with project, contract and payment management.

    Show more
    Tatweer — integrated real-estate and engineering services
  • Real EstateLaravel

    Real Estates Matcher — AI-Powered Property Matching

    A smart real-estate platform that matches demand and supply using AI and data analytics.

    Show more
    Real Estates Matcher — smart demand-supply matching

Related Blogs

  • A diagram linking escrow accounts, fractional ownership and rent-now-pay-later

    Where real estate meets fintech: escrow, fractional ownership and rent-now-pay-later in Saudi Arabia

    Property has always been the largest asset and the slowest deal. What has been happening in Saudi Arabia since 2024 is that the financial layer on top of property went digital: escrow accounts for off-plan projects, regu…

    09/09/2026 — 9 min read

  • A digital identity verification flow: ID card, live selfie and Nafath

    Know your customer in 90 seconds: how eKYC became the baseline in the Gulf and Egypt — Nafath, liveness and document AI

    Three years ago “opening an account” meant a branch, a form and a signature. Today, any financial, real-estate or even crowd-investing product that cannot verify a customer’s identity within two minutes on a phone loses …

    09/13/2026 — 10 min read

  • An Arabic invoice next to a field-extraction screen showing confidence scores

    343 pages and 99.42%: what building SLT OCR taught us about Arabic documents

    When we started SLT OCR we thought the problem was “reading Arabic letters”. After a year of invoices, purchase orders, ID cards and KYC packs, it turned out reading was the easy part. This is an honest post-mortem of wh…

    09/05/2026 — 11 min read