In registration-data validation there is one variable that rarely appears in marketing but defines everything: how current the returned information is. That is where D+0 comes in.
What D+0 means
D+0 means "day zero": the lookup reflects the record at the moment it is made, straight from the official source — not a copy processed weeks ago. Static databases often operate at D+30, D+90 or far more, delivering a stale snapshot.
D+0 vs. static databases in practice
- Registration status: a CPF/CNPJ that recently changed shows correctly at D+0; in a static base it wrongly stays "valid".
- Ownership structure: partner changes reflect immediately.
- Completeness: real-time lookups carry the current set; old copies accumulate gaps.
Why it changes everything
- Fraud prevention: current data closes the windows exploited with old information.
- Credit: deciding on today’s snapshot means deciding with less risk.
- Onboarding: less rework and fewer false positives.
How to tell if a provider is truly D+0
- Ask where the data comes from and how often it is obtained.
- Test a record you know has changed and check whether the response reflects it.
- Beware instant but "frozen" answers: speed is not currency.
Conclusion
Speed without currency is an illusion of quality. See the full picture in Registration data and the LGPD and the guide on leaked databases. CPF.CNPJ delivers real-time (D+0) lookups in under 1 second. See the packages.
