Reference · SNIP

What SNIP is and its role in PUI

SNIP is the National Personal Identification Service, the piece that articulates the interconnection of the Single Identity Platform. Its Operations Manual, still pending publication as of June 2026, is the key that will formally open access to the system. This page explains what SNIP is, why its manual matters and how it fits into PUI Law compliance.

What SNIP is and why it comes up so often

SNIP stands for National Personal Identification Service. In the PUI scheme, SNIP is the component around which the interconnection revolves: the service that lets the identity registered by establishments be queried in an orderly and secure way. Anyone following PUI closely hears “SNIP” at every step, because its operation is what remains to be switched on.

It helps not to confuse concepts. PUI is the platform; SNIP is the identification service that articulates it; the LGMDFP is the law that creates the obligation; and the DOF is the medium where everything is officially published. SNIP, specifically, is the operational link: the place where identity and the query meet.

As of June 2026, the decisive SNIP piece still missing is its Operations Manual. Technical Manual v1.0 (23 January 2026) is already published and defines the “how to connect”; what is missing is the manual that governs operation and formally enables access to the system.

SNIP in a few ideas

What it is, what is missing and what it means for a lodging establishment.

An identification service

SNIP is the National Personal Identification Service: the component that articulates identity within PUI.

Its Operations Manual is pending

As of June 2026 it is not yet published in the DOF. It is the piece that will formally enable access to the system.

45-business-day window

Once the manual is published, it opens a 45-business-day period to request access; this is a requirement for granting it.

Connection already specified

Technical Manual v1.0 (23 January 2026) already defines REST/JSON, JWT, AES-256-GCM encryption, SHA3-256 hashing and TLS.

Registering identity is already required

It does not depend on SNIP: the duty to register the guest’s identity is already enforceable as of June 2026.

A missing-persons search purpose

Like all of PUI, SNIP serves the LGMDFP’s purpose: to locate people reported missing.

Why its Operations Manual is the decisive piece

Technical Manual v1.0 already answered the engineering question: how the connection must be technically built. But there is a second question, operational and administrative in nature, that only the SNIP Operations Manual answers: under what rules access is requested and granted, how the service is operated day to day and what formal requirements apply. Without that manual, full interconnection cannot be switched on.

That is why its publication is the milestone many await. As foreseen, when it appears it will open a 45-business-day window to request access, and that procedure is a requirement for granting it. In other words, the manual is not just one more document: it is the key that turns preparation into operational interconnection.

In the meantime, the correct reading is twofold. On one hand, registering the guest’s identity is already required and does not wait for the manual. On the other, full interconnection with the system does. Whoever understands this distinction complies today with what is enforceable and stands ready to connect the moment SNIP allows it.

How SNIP fits into compliance

The sequence, from identity registration to operational interconnection.

  1. Register the guest’s identityIt is the underlying duty and already enforceable. CURP, name, date of birth and document are captured and stored securely.
  2. Prepare the technical connectionTechnical Manual v1.0 already defines the specifications, so the connection can be designed and made ready now.
  3. Await the SNIP Operations ManualThe pending piece. Once published, it defines how access to the system is requested and granted.
  4. Request access within its windowOnce the manual is published, the 45-business-day window to request access runs — a requirement for operational interconnection.

Official sources

SNIP = National Personal Identification Service. Framework: General Law on the Forced Disappearance of Persons (LGMDFP), Art. 12 Bis (obligation) and Art. 43 Bis (penalty). Bodies: SEGOB, RENAPO, National Search Commission (CNB) and, in technical support, the ATDT.

Reference publications in the Federal Official Gazette (DOF): LGMDFP reform in July 2025; Guidelines on 27 November 2025; Technical Manual v1.0 on 23 January 2026; SNIP Operations Manual, pending publication as of June 2026.

Frequently asked questions about SNIP

What does SNIP stand for?
National Personal Identification Service. It is the component that articulates identification within the Single Identity Platform (PUI).
Is SNIP the same as PUI?
They are not the same. PUI is the platform; SNIP is the identification service that articulates it and around which the interconnection revolves.
Why is the SNIP Operations Manual talked about so much?
Because it is the pending piece that will formally enable access to the system. Technical Manual v1.0 already defines the engineering part; the Operations Manual defines how access is requested and granted.
Do I have to wait for SNIP to start complying?
No. Registering the guest’s identity is already enforceable and does not depend on SNIP. What awaits the Operations Manual’s publication is full interconnection with the system.
What is the 45-business-day window?
It is the period that, as foreseen, will run from the publication of the SNIP Operations Manual to request access to the system, a requirement for granting it.
What does SNIP ultimately serve?
It serves the LGMDFP’s purpose: to locate people reported missing, by allowing registered identity to be queried in an orderly and secure way.

Put PUIhoteles to work for you

Get started