// interoperability · public sector · peru
Integration with the Peruvian State
RENIEC, SUNAT, SUNARP and the rest of the State, consumed from your own system — with the paperwork that unlocks them handled too.
Almost every serious process in Peru ends up needing the State: verifying that a DNI is real, issuing an invoice that SUNAT accepts, checking a property record, reporting revenue to the SIAF. Each of those lives behind a different door, and none of them opens with a credit card — they open with a formal agreement and a technical conformity process.
That is the part nobody quotes for. We have gone through it: for a national university we built the central cashier with real-time RENIEC validation, running in production. We know both halves — the paperwork that gets you the credentials, and the integration that survives once you have them.
// what we solve
What we build for you.
Identity validation (RENIEC)
Real-time DNI verification against RENIEC, in production. The piece that, in a real case, closed the door on forged receipts.
Access through the PIDE
The State Interoperability Platform exposes RENIEC, SUNAT, SUNARP, MIGRACIONES and more from a single point. We handle the request to the SGTD and the integration.
SUNAT electronic invoicing
Issuance through an OSE or direct, with UBL 2.1 and the CDR as the only proof that the document truly exists.
Revenue reporting to the SIAF
Reconciliation between what your system collected and what the SIAF records — including the Recognized and Collected phases.
Terms of reference and conformity
We help write the TDR under Law 32069 and meet the functional and technical conformity the public sector requires.
Traceability and audit trail
Every query and every response stored: who asked, when, and what the entity answered. It is what you show when someone asks.
- Java / Spring
- APIs REST
- SOAP
- RENIEC
- PIDE
- SUNAT
// how we work
From the first meeting to production.
- 01
Define what you need from the State
Identity, tax status, registry records, revenue reporting. Each one sits behind a different door with a different process, so the list gets closed before starting.
- 02
Choose the route and start the paperwork
The PIDE if you are a public entity, a direct agreement if you are private. This step goes on day one because its timeline is not controlled by anyone on the team — it is what delays these projects most.
- 03
Build against the test environment
While the paperwork advances, development runs against the sandbox. That way the day credentials arrive the project does not start: verification does.
- 04
Traceability of every query
Who asked, when, and what the entity answered, stored. In an integration with the State the trail is not optional: it is what you show when somebody asks.
- 05
Verification and balancing
A real charge, a real query, and the cross-check against the source of truth before opening to the public. A correct response code does not prove the process balances.
When this is not for you
If what you need is an occasional manual lookup —verifying a handful of ID numbers a month— the official web lookups serve you without integrating anything. And if your organization cannot sustain the agreement process, with the documentation and time it demands, the integration will sit stalled there however good the code is. We would rather assess it with you before quoting than discover it midway.
Senior engineering
Whoever designs your system writes it. No juniors learning at your expense.
The code is 100% yours
We hand over the repository and the documentation. No lock-in.
Real cases
Not theory: systems in production, including the public sector.
// real cases
Systems we’ve already built.
Want to go deeper? How to integrate your system with the State via PIDE.
// frequently asked questions
What people usually ask us.
Can I query State services without an agreement?
For occasional manual use, the official web lookups are open. To consume them from your system, automatically or in bulk, the process and the agreement are required: there is no shortcut, and anyone offering one is worth looking at carefully.
How long does getting access take?
It depends on the entity and on who is requesting, and it is an administrative process, not a sign-up form. We do not promise dates we do not control, but we do tell you what to prepare so it does not stall, and we build in parallel.
What happens if the State service goes down?
It is designed for that. Retries, controlled degradation and a business decision made in advance: if the service does not answer, does the operation block or pass through with a flag? That answer belongs in the scope, not in launch week.
What is the PIDE and what can you query through it?
The Plataforma de Interoperabilidad del Estado is the single point through which one public entity consumes another's data: RENIEC for identity, SUNAT for tax status, SUNARP for records, MIGRACIONES and others. It is run by the Secretaría de Gobierno Digital, under the Digital Government Law framework.
Do I need the PIDE to validate a DNI?
Not necessarily. RENIEC also offers its own service under a direct agreement, and for many private-sector cases that is the shorter path. Which one fits depends on who you are and what you need — it is the first thing we settle.
How long does getting access take?
It varies by entity and by who is requesting: it is an administrative process, not a sign-up form. We cannot promise a date, but we can tell you what to prepare so it does not stall, and build against a test environment while it moves.
Do you work with public entities?
Yes. We built the central cashier for a national university, meeting the public sector's functional and technical conformity.
Let’s talk about your project.
You talk with the engineer who’d design your system, not a salesperson. No strings attached.