Middleware for the Qatar National Directory

Connect to QND without rebuilding your core.

Syncora sits between your systems and the Qatar National Directory. You send plain customer, account and alias data — Syncora handles validation, signing, transport, reconciliation and audit.

  • Built to QCB's ISD & Member Implementation Guide
  • Any core system
  • Deployed on your premises
Data flows from your systems through Syncora to the Qatar National Directory and results flow back. Core banking Push API Wallet / PSP Connector Excel / CSV File upload Syncora Validating QND National Directory
Plain data in Signed & conformant out Results reconciled

Why it matters

One national directory. Every participant connected.

The Qatar National Directory consolidates the customer and account registries previously held separately by QMP and FAWRAN into a single, authoritative source, used for beneficiary lookup across Qatar's payment systems.

Every licensed bank, financial institution and PSP must register its customers, accounts and aliases, keep them current through signed management messages, and migrate its existing base through bulk files. That is a demanding integration — and it should not consume your technology roadmap.

QND serves lookups for

FAWRAN TAHWEEL RTGS E-Cheque
QND

The difference

Your team sends facts. Syncora speaks QND.

Building it in-house

  • Core-system changes to produce QND-specific formats
  • Implementing byte-exact digital signatures and envelopes
  • Hand-built bulk files, SFTP jobs and results parsing
  • Tracking what QND holds versus what your core holds
  • Re-work every time the specification is revised

With Syncora

  • Send plain data through an API, connector or spreadsheet
  • Signing, envelopes and transport handled for you
  • Bulk files generated, uploaded and reconciled automatically
  • A directory mirror that knows exactly what QND accepted
  • Specification changes absorbed by the middleware, not your core

How it works

Follow a record from your core to the directory

Eight stages, fully automated. Every step is recorded, so you can see exactly where each record is at any moment.

01

Your systems send plain data

Customers, accounts and aliases arrive through the push API, a pull connector or an Excel/CSV upload. Every source maps into one canonical data model — no QND formats on your side.

02

Every rule checked before anything leaves

A shared validation engine applies the directory's identifier, profile, account and alias rules, plus format and length checks. Invalid rows stay inside Syncora with a clear reason — they never reach QND.

03

Only real changes go out

A diff engine compares each record with a mirror of what QND has already accepted and classifies it as new, changed, unchanged or deactivated. No duplicate submissions, no guesswork.

04

Conformant files and messages, generated

Syncora builds the exact bulk-file layout and management messages the specification requires — sequencing, file splitting, field ordering and encoding included.

05

Digitally signed, byte for byte

Payloads are signed with your institution's certificate using SHA256withRSA and wrapped in the required envelope, exactly as transmitted, so signatures verify at the directory every time.

06

Delivered over secure channels

Bulk files travel over SFTP with completion markers; real-time messages over REST with OAuth 2.0 token management and TLS 1.2+. Retries and back-off are built in.

07

Every result matched to its source row

Results reports and responses are collected, verified and mapped back to the original intake row. Accepted records update the directory mirror; rejections come back with QND's reason, ready to correct and resubmit.

08

Full visibility in one console

Operators track batches, rows, files and results in real time, with a complete audit trail and the exact bytes of every file and message retained for non-repudiation.

From raw to ready

You provide the facts. We do the heavy lifting.

A single plain record goes in. Syncora runs every check, packages it to specification, signs it and tracks it until QND confirms.

What you send
{
  "customer": {
    "idType": "QID",
    "idNumber": "28x-xxx-xxxx",
    "nameEn": "Customer Name",
    "nameAr": "اسم العميل"
  },
  "account": {
    "iban": "QA58XXXX…",
    "currency": "QAR",
    "default": true
  },
  "aliases": ["mobile", "QID"]
}
  • Format & field-length checks
  • Identifier & profile rules
  • Account, alias & default rules
  • Compared with directory mirror
  • Packaged to specification
  • Signed SHA256withRSA
  • Transmitted & tracked
What QND receives
Signed envelope
Conformant document
Your validated data
Processing… Accepted by QND

Plug in any system

Three ways in. One standard way out.

Vendor-neutral by design. Whatever runs your core — packaged, in-house or a wallet platform — Syncora meets it where it is.

Push API

A clean REST API accepting plain JSON snapshots with idempotency keys. Repeat a request safely; you always get the original outcome back.

Pull connectors

A lightweight connector reads from your core database, detects changes on its own and feeds Syncora — no changes needed in the core application.

Phase 2

Excel / CSV upload

Drag and drop a spreadsheet from a ready-made template. Ideal for migration, small PSPs and one-off corrections, with a parse summary before anything is accepted.

Platform

Everything QND integration demands, in one product

Canonical data model

One clean model for customers, profiles, accounts and aliases. Every intake produces the same shape, so the directory side stays standard.

Validation engine

Directory rules enforced before submission — identifier types, profile requirements, alias formats, default-account constraints — each with a stable error code.

Diff engine & directory mirror

Syncora remembers what QND has accepted and sends only what changed. Deactivations and migrations are always explicit, never inferred.

Bulk migration pipeline

Generates conformant bulk files with per-day sequencing and automatic splitting, uploads over SFTP, and collects the results report for you.

Real-time signed messaging

Register, update, migrate and query over REST with signing, envelopes, OAuth token rotation and response verification handled end to end.

Phase 2

Reconciliation & correction loop

Every accepted or rejected line is matched to its source row. Fix rejections in place or re-upload; corrections go out as a new batch automatically.

Operator console

Dashboards, batch timelines, row-level search, rejected-row export, reason-code maintenance and settings — built for operations teams, not developers.

Audit & non-repudiation

Every state change is timestamped and attributed. Exact bytes of every file, message and response are kept for audit and dispute resolution.

On-premises deployment

Runs inside your data centre with PostgreSQL or SQLite. Customer data never leaves your perimeter except to QND itself.

Operator console

See every batch, every row, every result

Your operations team gets a purpose-built console: batches move through a clear lifecycle, rejected rows surface with QND's reason, and corrections are one click away.

  • Live dashboard of batches and outcomes
  • Drag-and-drop upload with parse preview
  • Rejected-row export and resubmission
  • Directory mirror search by identifier, account or alias

Security & compliance

Engineered for a regulated environment

Built against QCB's Integration Specifications and Member Implementation Guide, with the security controls the directory requires.

SHA256withRSA

Every outbound payload signed with your institution's certificate; every response verified against the bytes received.

TLS 1.2+

All channels to the directory encrypted in transit, with SFTP for bulk files and HTTPS for messages.

OAuth 2.0

Token acquisition, caching and rotation handled automatically — no credentials in your core system.

Byte-exact archive

Exact bytes of every file, message and response retained for audit and non-repudiation.

Data residency

Installed on your premises. Your data stays in your infrastructure under your controls.

Full traceability

Every transition timestamped and attributed to a user or process, from intake to reconciliation.

Who it's for

For every QND participant in Qatar

01

Banks

Retail and corporate registration at scale, with bulk migration of your entire IBAN base and ongoing real-time maintenance.

02

Financial institutions

Meet directory obligations without diverting your technology team from strategic programmes.

03

Payment service providers

Wallet and mobile-alias registration with a lightweight footprint — start with spreadsheet uploads and grow into the API.

Getting started

From first conversation to go-live

  1. 1

    Discover

    A live demo and a review of your systems, data and timelines.

  2. 2

    Connect

    We install Syncora on-premises and map your data to the canonical model.

  3. 3

    Test

    End-to-end runs against the directory's test environment, with us handling the conformance work.

  4. 4

    Go live

    Bulk migration, then ongoing synchronisation — supported by our team.

FAQ

Common questions

Do we need to make any modifications to our existing systems?

Little to none. Your systems keep running as they do today — Syncora only needs your customer, account and alias data, pushed through its API, read by a connector or uploaded as a spreadsheet. QND-specific formats, validation, signing and transport all live in the middleware.

Where is Syncora hosted?

On your premises, inside your own infrastructure, using PostgreSQL (recommended for production) or SQLite.

Does Syncora handle the initial bulk migration?

Yes. It generates conformant bulk files, uploads them over SFTP, collects the results report and reconciles every line back to your source data, with a built-in correction loop for rejected rows.

What about certification with QCB?

Certification is granted to each participant by QCB. Syncora is built to the published specifications, and our team supports you through testing and the conformance workload so certification goes smoothly.

What happens when the specification changes?

Specification updates are absorbed by Syncora. Because your systems only send plain data, they are insulated from changes in message formats and file layouts.

How is pricing structured?

Pricing depends on your institution and deployment. Contact us for a demo and a tailored proposal.

Request a demo

See Syncora with your own data flows

Tell us about your institution and we'll arrange a walkthrough tailored to your systems and QND timeline.

Or email us directly: info@pibas.com

Your request is sent straight to our team — no email app needed.