Basic search by CURP
Completes a report's basic data by querying your policy or account core by CURP.
orbit PUI
/
Interoperability
Meet the missing persons search law without building the connector from scratch.
orbit PUI connects your institution to the government's Single Identity Platform: the three search phases the manual requires, encrypted biometrics, and a verifiable status per case.
orbit PUI
interoperability
01 · Context
The problem we are solving.
On November 27, 2025, Mexico's Federal Register published the guidelines for the government's Single Identity Platform: insurers, banks, pension funds, and other institutions with relevant administrative databases are now required to interconnect their systems to support the search for missing persons. The technical manual demands secure authentication, three search phases with distinct rules, biometric encryption, and security testing before authorizing the connection. Building all of that from scratch takes months. orbit PUI already has it built.
02 · What it is
orbit PUI in one sentence
The connector and control panel that implements the flows required by the PUI Technical Manual: it sits on your core, queries by CURP, resolves the three search phases, and encrypts biometrics before notifying the government of any match.
03 · How it works
Four steps, per the manual.
From the search report to case closure: a governed flow that follows the PUI Technical Manual step by step.
01
Receives the report
The PUI notifies your institution with the unique search folio and the person's CURP. orbit PUI activates the case automatically.
02
Queries your core
Looks up the CURP in your policy, client, or account databases and builds the case across the manual's three phases: basic, historical up to 12 years, and continuous.
03
Notifies with encryption
If there is a match, it is sent to the PUI with photos and fingerprints encrypted in AES-256-GCM, and the report status is logged.
04
Closes the case
When the person is located, the PUI orders deactivation and orbit PUI stops the continuous search automatically.
Functional flow · orbit PUI live
04 · What it does
What it solves in the search operation.
Built to the PUI Technical Manual and in implementation with contracted insurers: these are the flows it solves.
Historical search
Reviews records from the date of disappearance, within the 12-year cap the manual sets.
Continuous search
Periodically reviews new and modified records that match an active report, with no manual intervention.
Encrypted biometric notification
Sends a file's photos and fingerprints encrypted with AES-256-GCM before they leave your institution.
Compliance panel
Visual tracking of every report's status without giving legal direct database access.
Automatic closure
Once the person is located, the report is deactivated and the continuous search stops on its own.
05 · Benefits
What changes when you have it.
We do not promise transformation. We promise meeting the technical manual without your team interpreting it line by line.
Request demo1
Direct legal compliance
Implements what the PUI Technical Manual published in the Federal Register requires, without your team interpreting it line by line.
2
Biometrics encrypted at the source
Photos and fingerprints are encrypted with AES-256-GCM before leaving your institution for the government.
3
All three phases, solved
Basic, historical capped at 12 years, and continuous search, with the manual's deadline and field logic already built.
4
Visibility for compliance
A control panel with every report's status, so the legal team never queries the database directly.
5
Runs on your existing core
Queries your current systems by CURP; no data migration or core replacement required.
06 · Video
Let us see it in action.
The orbit PUI demo video is in production. In the meantime, book a live demo with your team.
07 · Industries
For the institutions the law obligates.
The interconnection mandate reaches every institution with relevant administrative databases: insurers now in implementation, pension funds, and other entities under article 12 Bis.
01 / Insurers
Search in policies and claims
Queries life and health policies by CURP and notifies matches with encrypted biometrics.
02 / Pension funds
Individual accounts by CURP
The same three-phase flow, applied to individual retirement accounts and their historical records.
03 / Other obligated institutions
Obligated by article 12 Bis
Banks and other entities with relevant administrative databases that the law requires to interconnect with the PUI.
08 · Before and after
What changes, side by side.
An honest comparison between meeting the mandate on your own and meeting it with orbit PUI.
Before / Without orbit PUI
Building it on your own
- ✕ Interpreting the technical manual line by line, between legal and IT
- ✕ Months of development for authentication, search phases, and encryption
- ✕ Risk of failing the security tests the government requires
- ✕ Sensitive biometrics handled without a specific encryption scheme
- ✕ No record of each search report's status
After / With orbit PUI
The day-to-day with orbit PUI
- ✓ The manual's flows already implemented and ready to test
- ✓ All three search phases with their deadline logic built
- ✓ Photos and fingerprints encrypted with AES-256-GCM before leaving
- ✓ Verifiable status and date at every report transition
- ✓ A dedicated instance per institution, no crossed data
09 · Metrics
What every case guarantees.
Guarantees verified in the product's code, not commercial projections: this is how orbit PUI processes every search report.
100%
Cases with a verifiable status and date at every transition
3/3
Search phases of the manual implemented
0
Data crossed between institutions
10 · Illustrative scenario
This is what it looks like in operation.
An illustrative example of how orbit PUI operates, not a published client case.
An insurer receives a search report
The PUI sends a folio with the CURP of a missing person. orbit PUI queries the institution's policies, completes the basic phase, schedules the historical and continuous ones, and notifies the match with encrypted biometrics. Compliance follows the whole case from the panel, without touching the database.
3/3
Phases resolved
100%
Status traced per case
11 · Impact · No brainer
The PUI interconnection stopped being a months-long project.
What the technical manual requires is already built: authentication, three search phases, and biometric encryption. Your team connects its core and operates from a panel with verifiable status.
Run the discovery with rocky100%
Status traced per case
3/3
Search phases of the manual
0
Data crossed between institutions
12 · Security and compliance
Built for data that admits no errors.
Biometrics of missing persons: the most sensitive data an institution can handle. This is the floor, not the ceiling.
Encryption
AES-256-GCM on biometrics
Photos and fingerprints are encrypted before leaving your institution for the PUI.
Authentication
JWT per the manual
Tokens renewed at 80% of their lifetime, as the PUI Technical Manual requires.
Isolation
A dedicated instance per institution
Each client gets its own database, credentials, and encryption key; no crossed data.
Traceability
Verifiable status per case
Every report transition is logged with status and date: pending, queried, notified, and closed.
13 · Contact
Let's get orbit PUI running in your institution.
30 minutes to review your PUI interconnection mandate and the state of your core. If it fits, we define the implementation. If not, we'll tell you which orbit product does fit.