Push API
A clean REST API accepting plain JSON snapshots with idempotency keys. Repeat a request safely; you always get the original outcome back.
Middleware for the Qatar National Directory
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.
Why it matters
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
The difference
How it works
Eight stages, fully automated. Every step is recorded, so you can see exactly where each record is at any moment.
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.
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.
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.
Syncora builds the exact bulk-file layout and management messages the specification requires — sequencing, file splitting, field ordering and encoding included.
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.
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.
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.
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
A single plain record goes in. Syncora runs every check, packages it to specification, signs it and tracks it until QND confirms.
{
"customer": {
"idType": "QID",
"idNumber": "28x-xxx-xxxx",
"nameEn": "Customer Name",
"nameAr": "اسم العميل"
},
"account": {
"iban": "QA58XXXX…",
"currency": "QAR",
"default": true
},
"aliases": ["mobile", "QID"]
}
Plug in any system
Vendor-neutral by design. Whatever runs your core — packaged, in-house or a wallet platform — Syncora meets it where it is.
A clean REST API accepting plain JSON snapshots with idempotency keys. Repeat a request safely; you always get the original outcome back.
A lightweight connector reads from your core database, detects changes on its own and feeds Syncora — no changes needed in the core application.
Phase 2Drag 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
One clean model for customers, profiles, accounts and aliases. Every intake produces the same shape, so the directory side stays standard.
Directory rules enforced before submission — identifier types, profile requirements, alias formats, default-account constraints — each with a stable error code.
Syncora remembers what QND has accepted and sends only what changed. Deactivations and migrations are always explicit, never inferred.
Generates conformant bulk files with per-day sequencing and automatic splitting, uploads over SFTP, and collects the results report for you.
Register, update, migrate and query over REST with signing, envelopes, OAuth token rotation and response verification handled end to end.
Phase 2Every 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.
Dashboards, batch timelines, row-level search, rejected-row export, reason-code maintenance and settings — built for operations teams, not developers.
Every state change is timestamped and attributed. Exact bytes of every file, message and response are kept for audit and dispute resolution.
Runs inside your data centre with PostgreSQL or SQLite. Customer data never leaves your perimeter except to QND itself.
Operator console
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.
Security & compliance
Built against QCB's Integration Specifications and Member Implementation Guide, with the security controls the directory requires.
Every outbound payload signed with your institution's certificate; every response verified against the bytes received.
All channels to the directory encrypted in transit, with SFTP for bulk files and HTTPS for messages.
Token acquisition, caching and rotation handled automatically — no credentials in your core system.
Exact bytes of every file, message and response retained for audit and non-repudiation.
Installed on your premises. Your data stays in your infrastructure under your controls.
Every transition timestamped and attributed to a user or process, from intake to reconciliation.
Who it's for
Retail and corporate registration at scale, with bulk migration of your entire IBAN base and ongoing real-time maintenance.
Meet directory obligations without diverting your technology team from strategic programmes.
Wallet and mobile-alias registration with a lightweight footprint — start with spreadsheet uploads and grow into the API.
Getting started
A live demo and a review of your systems, data and timelines.
We install Syncora on-premises and map your data to the canonical model.
End-to-end runs against the directory's test environment, with us handling the conformance work.
Bulk migration, then ongoing synchronisation — supported by our team.
FAQ
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.
On your premises, inside your own infrastructure, using PostgreSQL (recommended for production) or SQLite.
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.
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.
Specification updates are absorbed by Syncora. Because your systems only send plain data, they are insulated from changes in message formats and file layouts.
Pricing depends on your institution and deployment. Contact us for a demo and a tailored proposal.
Request a demo
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