How to integrate your system with the Peruvian State via PIDE

Sooner or later, nearly every serious system in Peru needs to talk to the State: validate a DNI against RENIEC, verify a RUC with SUNAT, confirm the ownership of a property with SUNARP. The right door to do it well —without scraping pages or relying on shortcuts— is the PIDE, the State Interoperability Platform. This is the practical guide: what it is, which services it exposes, how access is requested (the real bottleneck is not the code) and what the integration looks like — from the experience of having put identity validation against RENIEC into a production system.

What is the PIDE and why does it save you half the project?

The PIDE is the infrastructure, managed by the Secretaría de Gobierno y Transformación Digital (SGTD), that enables the secure exchange of data between State entities. Instead of integrating with each entity separately, you consume their services from a single point: RENIEC, SUNAT, SUNARP and more.

The State Interoperability Platform has operated since 2011 (D.S. 083-2011-PCM) and today more than 450 entities of the Executive Branch and of regional and local governments use it. Its value for anyone building software is concrete: it consolidates in a single place queries that would otherwise require negotiating and integrating with each entity separately. Fewer agreements, fewer integrations, fewer points of failure.

The legal framework: the Ley de Gobierno Digital (D.L. 1412)

The PIDE rests on Decreto Legislativo N.° 1412, the Ley de Gobierno Digital, and its regulation (D.S. 029-2021-PCM), which defines interoperability as the ability of entities to share data automatically. The governing body is the PCM through the SGTD.

The Ley de Gobierno Digital establishes the governance framework for digital identity, digital services, architecture, security and the interoperability of the State. It defines the latter on two levels: the technical (interfaces, interconnection, integration and data exchange) and the legal (compliance with the regulations that enable that exchange). Translated: interoperating with the State is not a favor granted to you — it is a capability the law mandates you build, and the PIDE is the means.

Which services you can consume today

The PIDE exposes queries from several entities from a single point: RENIEC (DNI), SUNAT (RUC), SUNARP (domain ownership), MIGRACIONES (foreigner ID card), MTC (driver's licenses), among others. You choose the service your process needs and consume it via web service.

The catalog grows over time, but the logic is always the same: instead of building a separate integration with each entity, you consume a web service standardized from the platform. For identity validation, which tends to be the most requested, we wrote a guide dedicated to RENIEC.

The bottleneck is not the code: it is the consumption agreement

As with RENIEC, the real timeline of a PIDE project is not the technical integration but the paperwork: submitting an official letter to the SGTD with the Acuerdo de Consumo de Servicio (Form 1), the registration of the responsible party (Form 2) and a Form A-1 for each service. Start it on day one.

If your entity needs to consume PIDE services, it must submit an information-consumption request to the SGTD. In practice this is an official letter, signed by the highest administrative authority, that attaches the Acuerdo de Consumo de Servicio (ACS), the registration of the party responsible for managing the consumption, and one form for each service you want to enable. It is an institutional process, not a technical one — and that is why it is the project's critical path. If you are defining a TDR that includes integration with the State, declare this access explicitly and start it before development.

What the technical integration looks like

On the code side, consuming the PIDE is a web-services integration like any other, with the State's own demands: authentication, defined formats and a design built for real time and traceability. It is not magic — but each service comes with its documentation, its errors and its tests.

The integration itself is familiar to any team that works with APIs, with three demands you cannot skip: authenticate the consumption, respect the formats each service defines, and design for real time and traceability — recording who queried what, when and with what result. In the cashier system of a national university that we built, real-time validation against RENIEC was exactly that piece: every operation was verified against the official registry, not against a text field. It is more work than it looks, but it is known work.

Interoperating with the State is not only for the public sector

It is not only public entities that consume these services. Banks, fintechs, notaries and companies that validate identity, RUC or background records also depend on official State data. If your business decides based on that data, interoperating stops being optional.

A digital onboarding that opens an account, a credit system that assesses an applicant, a notary that verifies an identity: they all need data that only the State holds as the source of truth. The exact channel varies (PIDE for entities, direct agreements with RENIEC or SUNAT for private firms), but the pattern is the same — and the decision to build it well, tailored to your process, is what separates a serious system from one that guesses.

Common mistakes when integrating with the State

PIDE projects almost always stall for the same reasons: leaving the paperwork for the end, integrating entity by entity instead of through the platform, or handling personal data without the care the law requires. None of these is a code problem.

How we do it

We integrate State services into production systems — real-time validation against RENIEC in the cashier desk of a national university. We help you choose the right services, resolve the consumption agreement and build the integration tailored to your process.

We know the path from both sides: the institutional paperwork and the technical integration. If your system —public or private— needs to talk to the State, we help you choose which services to consume, resolve access and build an integration that respects real time, traceability and public-sector compliance where it applies.

In summary

The PIDE is the right door for your system to talk to the State: a single point to consume RENIEC, SUNAT, SUNARP and more, backed by the Ley de Gobierno Digital. The technical integration is well understood; what defines the timeline is the consumption agreement before the SGTD — start it early. Choose only the services your process uses, design for real time and traceability, and handle personal data with the care the law requires. Done well, your system stops guessing and starts deciding with the country's source of truth.