Verify puts the official sources behind a single query: RENAP for a DPI, SAT for an RTU, the bureaus, and a biometric check for when the document is not enough. One query, one source, one shape of answer — and every one of them written down, because a query nobody can account for is a query nobody can bill either.
The thirteen digits of a DPI carry their own check digit, so a typo gets caught here, for free, before anything leaves. That is the shape of the whole product: what can be settled locally is settled locally, and only what needs an official answer costs a query.
Each source has its portal, its credential and its own way of answering. Somebody opens three tabs, copies what each one says into the file, and nowhere does it say who asked what, or when, or how many times. Which is another way of saying nobody can tell you what last month cost.
The same three sources, with one door in front of them. The answer comes back in the same shape wherever it came from, so whatever reads it does not have to know. And the query writes itself down on the way out: that line is the audit trail and the invoice at once.
A query can come from somebody at a form, from a process that reached the step where it checks, from an agent that needs to be sure before it answers, or from your own code. All of them get the same answer, and all of them leave the same line behind.
The photograph on a DPI runs to hundreds of kilobytes, so it does not come with the answer unless you ask for it. Most of the time what you need is the name RENAP has on file, not the picture.
Four sources and the thing that remembers. There are more sources than these and they get added here as they land — the part that does not change is that all of them answer through the same door and all of them leave the same line.
The thirteen digits of a DPI, resolved against RENAP. The check digit is verified here before anything goes out, so a typo does not cost a query. The photograph is optional: it weighs hundreds of kilobytes and most answers do not need it.
The RTU behind a NIT, straight from SAT: the name that is actually on the registry, and whether it is the one you were given.
For when the document is not enough and it has to be that person. This is the check you run when what is at stake is not a typo but somebody else's identity.
What the bureaus have on file. It is the one source here that does not answer yes or no: it answers with a history, and reading it is a decision.
Every query: who asked, against which source, what came back and when. It is the audit trail and it is also the invoice — the same line does both jobs, which is exactly why neither can drift from the other.
The onboarding where somebody opens RENAP in one tab and SAT in another. Tell us how many of those you do in a month and we will show you what it looks like as one query — and what the log would already have told you about last month.
Talk to us
