Techbanq

Software · Absher interoperability

Absher answers the question; your platform still owns the journey

When a platform needs to verify who someone is or what a civil record says, the government service supplies one authoritative answer. Everything around that answer is your product: what you ask and when, what the user sees while waiting, what happens when the answer is no or unclear, and what your systems keep afterwards. That surrounding workflow is where these services succeed or quietly fail.

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The proportion of the work

Why the verification call to Absher is the easy tenth of the build

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

Calling a verification service is a bounded technical task: a request goes out in the specified shape, an answer comes back. Teams budget for that and are then surprised by the rest — the nine tenths that decide whether the product works. What does the user see during the seconds or longer the check takes? What is the experience when the answer is a mismatch caused by a typo rather than a fraud? Who reviews the cases that are neither a clean yes nor a clean no, and how does the applicant learn their case is being reviewed rather than rejected? None of that is answered by the service; all of it is answered by your platform.

There is also a fact of eligibility to respect. Which verification services exist, and which organisations may use them, is the operator’s decision — a matter of agreements between the ministry and your organisation, not of engineering. We design the workflow around what you are actually granted, and where a desired check is not available to you, the honest design is a different journey, not an implied capability the platform never promised.

The whole journey

An onboarding journey with the Absher check designed in, not bolted on

The verification is one stage of four. Each of the other three is your platform’s work, and each has a failure mode that only shows up when it was skipped.

01

Before the question

The applicant is asked for exactly the details the check requires, and told why they are being collected.

Input validation catches the transposed digit and the misspelt name here, where fixing them costs a keystroke instead of a failed verification.

  • Onboarding flow
  • Input validation
02

The verification moment

The request goes to the government service; the applicant waits on an honest status, not a frozen screen.

Timeouts, retries and idempotency are engineered so a slow answer does not become a duplicate request or an abandoned application.

  • Verification service
  • Status tracking
03

When the answer is no, or unclear

A mismatch or an ambiguous result lands with a person, not in a void.

A review queue with owners, deadlines and recorded outcomes turns the hard cases into a managed process instead of an unexplained rejection.

  • Review queue
  • Case management
04

After the answer

The applicant proceeds; your systems record what happened.

The record kept is the outcome and its timestamp — verified, when, for what purpose — not a copy of the underlying civil data, and it carries an expiry after which the question is asked again.

  • Case record
  • Retention policy

The shape of an engagement

An illustrative build for a platform that must verify before it serves

Illustrative engagement — not a named client

A regulated platform may only grant its service after confirming an applicant’s identity and standing. Its team can call the verification service it has been granted, but onboarding stalls: applicants abandon during silent waits, typo-driven mismatches read as rejections, and operations staff resolve edge cases over email with no record.

  1. 01The journey is redesigned around the check: validation before the question, honest status during it, and a distinct path for “we could not match your details” that invites correction instead of announcing failure.
  2. 02The email-based edge-case handling becomes a review queue inside the platform, with each case owned, time-bound and closed with a recorded reason a future audit can read.
  3. 03What the platform stores is reduced to outcomes with expiry dates, and the retention decision for each field is written into the design rather than left to whoever built the table.

Verification stops being the stage where applicants disappear: the clean cases pass without friction, the hard cases reach a person with a process, and the platform can show exactly what it kept and why.

Our role

What we orchestrate around Absher and what the ministry grants

  1. 01

    The workflow, designed whole

    We design and build the journey around the verification — the asking, the waiting, the mismatch path and the review queue — because the check is only as good as the workflow that carries it.

  2. 02

    The integration, built to specification

    Where your organisation is granted a verification service, we build against its specification with the timeout, retry and idempotency discipline a government dependency deserves.

  3. 03

    The records, minimised by design

    We make your systems remember outcomes rather than copies of civil data, with retention and access logging decided in the design — the posture PDPL expects and incidents reward.

Eligibility for verification services, and the agreements behind them, are between the Ministry of Interior’s platform and your organisation; we prepare you for that conversation and build the platform that uses what you are granted well.

Common questions

What buyers ask

Can any company build an integration with Absher?+

Any company can build the workflow; not every company will be granted the verification services. Which services exist and which organisations qualify to use them is decided by the platform operator, typically through agreements tied to a regulated need. We are not a channel to that access and no supplier honestly is. What we do is twofold: help you understand what your build needs before you approach the operator, and engineer the platform so that, once access is granted, the verification sits inside a workflow that handles the waits, the mismatches and the reviews properly.

What happens to our onboarding when the government service is unavailable?+

Whatever you designed to happen — which is why the design has to exist before the first outage rather than being improvised during it. The sound pattern is to separate the application from the verification: an applicant can complete their submission, be told honestly that verification is pending, and be notified when it resolves, while your system queues and retries the check with discipline. The wrong pattern is a journey that hard-fails at the moment of unavailability, because it converts someone else’s maintenance window into your abandonment rate.

Do we store the civil-record data a verification returns?+

As little of it as your obligation genuinely requires, and usually that means the outcome rather than the record. For most purposes what your platform needs to remember is that a person was verified, when, at what strength and for which purpose — with an expiry after which the verification is stale. Copying the underlying attributes into your database creates a store of sensitive data you must then protect, justify and eventually delete, often without a need that ever materialises. We make the keep-or-discard decision explicitly for every field in the design, which is both the PDPL-aligned posture and the smaller attack surface.

Walk the workflow with us

A workflow session that places the verification moment in your journey and designs the mismatch, review and unavailability paths before any build starts.

Start the conversation