How to integrate RENIEC identity validation into your system

In Peru there is a single source of truth about who is who: RENIEC and its Single Registry of Identification of Natural Persons (RUIPN). If your system needs to confirm that someone really is who they claim to be —to enroll, pay, sign, open an account or grant a benefit— sooner or later you will want to validate against RENIEC. The good news: it is an official service, with defined modalities and public fees. The less good news: the bottleneck is almost never the code, but the convenio (the agreement). This is the practical guide.

What it actually solves (and what it doesn't)

Validating with RENIEC is not showing the data on a DNI —anyone can type in a number—, but confirming against the official registry that the person, the fingerprint or the face correspond to the real holder of that document. That is what shuts the door on identity fraud.

Validating with RENIEC is not “showing the data on a DNI.” Anyone can type in a number. What the service solves is confirming that the person, the fingerprint or the face correspond to the real holder of that DNI according to the official registry — and that is what kills identity fraud. It is exactly the piece that, in the cashier system of a national university we built, shut the door on forged receipts: every operation was validated in real time against RENIEC, not against a text field.

The RENIEC menu: which modality to choose

There are two decisions: what to validate —data, fingerprint or face— and how much to integrate. If usage is occasional and low-volume, the online queries or the biometric app require no development. If validation is part of your flow, the web service is the way.

According to RENIEC's identity verification service, there are several modalities. The first decision is what you want to validate (data, fingerprint or face) and the second, how much you will integrate (a ready-to-use web interface vs. a web service you consume from your own system):

Rule of thumb: if it is low-volume and occasional, the online queries or the biometric app spare you from developing anything. If validation is part of your flow (every enrollment, every onboarding, every payment), the web service is the way: it integrates into your system and validates in bulk and in real time.

What it costs and what you need

You pay per query: S/ 0.40 for the data web service, S/ 0.70 for the fingerprint biometric, and between S/ 0.90 and S/ 1.60 for the online queries depending on the access level. But before the first sol, you must sign an agreement with RENIEC — the step that takes the longest.

The cost is per query, so it feeds straight into your operating model: S/ 0.40 for the data web service, S/ 0.70 for the fingerprint biometric, and from S/ 0.90 to S/ 1.60 for the online queries by access level. Multiply by your expected volume — unlike a per-user license, here you pay for real usage.

But before the first sol there are requirements, and this is where the project's real timeline sits. The service is aimed at notaries, public entities and legal persons incorporated in Peru, and it requires:

What the technical integration looks like

On the code side it is a service integration like any other, with three demands of its own: digital certificates to authenticate the server, specific formats —especially in biometrics— and a design built for real time and volume. More work than it looks, but it is not magic.

On the code side, consuming RENIEC's web service is a service integration like any other, with three demands of its own: digital certificates to authenticate the server, specific formats (especially in biometrics) and a design built for real time and volume. It is not magic — but, like any integration with an external entity, it is more work than it looks: each modality brings its own documentation, its errors and its testing. That is why, in any budget, integrations are among the line items that weigh the most (we explain it in our cost guide). And it is also the perfect example of why this is built to measure and not bought off the shelf: the validation is wired into your rules and your flows, not those of a generic product.

The 2025-2026 context: why it matters more now

Ley N.° 32314, in force since April 2025, penalizes crimes committed with artificial intelligence, including deepfakes. Combined with digital onboarding in banking and the digital DNI mandated by Supreme Decree 098-2025-PCM, verified identity has become the security perimeter of any serious system.

Identity verification stopped being a “nice to have.” With Ley N.° 32314 (in force since April 2025), Peru penalizes crimes committed with artificial intelligence — including deepfakes and automated identity fraud. At the same time, in banking and fintech, digital onboarding forces you to validate identity in seconds without sacrificing security, and the de facto technical standard for liveness detection (avoiding being fooled by a photo or a video) is ISO/IEC 30107-3, PAD level 2. And there is more coming: Supreme Decree 098-2025-PCM tasks RENIEC with completing the digital DNI (DNId). Translation: verified identity will increasingly be the security perimeter of any serious system.

Best practices and common mistakes

The most expensive mistake is not technical: it is leaving the agreement with RENIEC for the end and stalling the whole project. Start it on day one, choose the modality by your real flow, add liveness detection if you validate faces, and don't store biometric data “just in case.”

In short

Integrating RENIEC is not hard because of the code, but because of the agreement and choosing the right modality. Define what you need to validate, weigh the per-query cost against your volume, start the paperwork early, and handle biometric data with the care the law requires.

Integrating RENIEC is not hard because of the code — it is a web service with certificates, formats and a design for real time — but because of the convenio and choosing the right modality. Define what you need to validate (data, fingerprint or face), weigh the per-query cost against your volume, start the paperwork early, and handle biometric data with the care the law requires. Done right, it is the piece that turns your system into one where identity truly matters — and in the Peru of 2026, with AI-powered fraud, that is no longer optional.