DHA DataFlow status, explained

DataFlow is a third-party verification agency, not DHA itself — DHA has used it as its verification partner since 2007. Primary Source Verification means DataFlow's own team contacts the university, licensing council or employer that issued your document and asks them, directly, to confirm it is genuine and that they actually issued it. It also checks that the issuing institution itself is accredited. This is a different job from attestation: attestation confirms a signature and seal are real; PSV confirms the underlying qualification is real. DataFlow does not require your documents to be attested, apostilled, or translated first — send clear scans of the originals and let the verification run on its own track.

Two places, both official. If you applied through DHA's portal, log in at dha.dfgateway.com and use "Check Your Status." If you have your DataFlow Case Number and passport number, you can also track directly at dataflowstatus.com, which shows visibility on each document in your case separately rather than one combined status. Email notification is automatic when your report completes; SMS updates at each stage are available as a paid add-on if you want to watch it move in real time.

A finished case lands in one of three places. Positive / verified — the issuing institution confirmed everything, your final report is issued, and it moves straight to DHA. Unable to Verify — the institution did not respond, or could not be reached, despite DataFlow's attempts. This is not evidence your document is fake; it means the loop back to the source could not close, and DHA treats it as a negative result until it does. Discrepancy — the institution responded, and something they said does not match what you submitted (a name, a date, a grade, a course title). This is the one that needs an actual explanation or corrected document, not just a resend.

DataFlow's own published range is 15 to 25 working days from the date you pay and submit a complete set of documents. That range is not really DataFlow's own processing time — it is dominated by how fast the issuing institution answers their request. A university exam cell that replies in three days finishes fast regardless of DataFlow's internal queue; one that takes six weeks to check its own archives will hold your case for six weeks no matter how complete your submission was. If your deadline is tight, the leverage point is making sure your documents list the correct, current contact details for whoever issued them — not chasing DataFlow itself.

The most common reason a case stalls isn't DataFlow's fault or yours: it's an issuing institution that has not replied. The fixable causes are different. A name on your passport that does not match your certificate needs a proper name-change document attached before verification can proceed. Scans that are blurry, cropped, or missing a page get treated as incomplete. Wrong or outdated contact details for the issuing institution mean DataFlow's request goes nowhere. Check these three before you submit, and a stalled case is far more likely to be "waiting on the university" than "waiting on something you did wrong."

Neither replaces the other, and they serve different people. DataFlow's PSV report satisfies DHA's own licensing requirement. But the visa process, your employer's HR file, or a different regulator entirely may still ask for MEA attestation or apostille on the very same certificate — that requirement doesn't disappear because DataFlow verified it. People sometimes pay for DataFlow, assume the document is now "cleared" everywhere, and then get stopped at a visa counter asking for an attested copy. Confirm what your specific destination and employer need before you assume one process covers the other.

DataFlow's own checklist is shorter than people expect: a passport copy, clear and complete scans of every credential you're submitting (degrees, licences, transcripts, employment and experience certificates), and — if any document was issued under a different name than the one on your current passport — a name-change certificate to bridge the two. A Good Standing Certificate, where your case needs one, has to be current: get it too early and it can age out before your case closes, so time its request against when you expect to actually submit, not months ahead. No attested, apostilled, or translated version of any of these is needed; upload the originals as scanned.

Many applicants assume they must wait for a Positive DataFlow result before sitting their DHA exam, and delay booking it as a result. That's not how DHA's own process is structured — PSV and the exam are parallel prerequisites, not sequential ones. Both need to be complete before your registration can be finalised, but neither has to finish first. If your exam eligibility is otherwise ready, booking it while your DataFlow case is still active is normal practice, not jumping the queue.

We don't run your DataFlow case — DataFlow does that directly with the issuing institution. What we handle is everything DataFlow doesn't touch: getting your certificates through the state, MEA and embassy attestation chain your DHA registration or visa still needs, in parallel with your DataFlow file rather than waiting on it. See DataFlow verification for nurses, for MBBS doctors, or the full DHA DataFlow catalog by profession — or message +91 89434 68088 with your document and role for the exact list.