Guest Registration

Guest registration is the general practice, found, in some form, in many countries, of an accommodation provider recording a staying guest's identity and reporting it to a public authority. It is older than any digital system: long before electronic filing existed, hotels kept a paper guest ledger that police could inspect, precisely because "who is staying where" is information governments have historically wanted visibility into, especially for foreign or transient visitors.

The specific mechanics, which authority receives the data, what fields are required, whether it's real-time electronic filing or a periodic paper submission, and what the penalty is for non-compliance, vary by country and sometimes by region within a country. Turkey's current implementation, KBS (see that entry), is the concrete, well-documented instance behind this Lexicon entry: a mandatory electronic filing to the national police (EGM) or gendarmerie, rooted in a 1972 law, that predates and now supersedes the old paper form.

Who actually built this

No single body invented guest registration; it's a category of national public-order law, not a standard anyone drafted once for the world. What Solidus's own research covers in depth is Turkey's version, the law (No. 1774), the operating authority (EGM/Jandarma), and the software vendors (Sistemotel, Elektraweb, Protel/OPERA Cloud, AKINSOFT WOLVOX, HMS Otel, and others) that already handle the filing inside their property-management systems. None of that work is Solidus's; the vendors solved the reporting problem years ago.

The pattern worth understanding

The interesting shape of this problem, wherever it appears, is a squeeze between two obligations that pull in opposite directions: a business must record and report a guest's identity data to satisfy a public-order law, but a separate data-protection regime may restrict how it retains the underlying document that produced that data. In Turkey this shows up as the KBS-versus- KVKK tension (see KBS); the same structural tension, required to log the data, discouraged or forbidden from hoarding the document, tends to recur anywhere a business sits between a reporting mandate and a privacy law, not just in hospitality.

Solidus today

Nothing here is built. What exists is Solidus Verify's general identity- verification pipeline, document capture, liveness, face matching, live on Solidus's public testnet, and a set of internal vertical-strategy documents studying Turkey's hospitality sector specifically. No PMS integration, no hotel customer, no filed guest record of any kind. The idea of turning a one-time guest-registration event into a reusable, guest-held credential (so a returning guest doesn't repeat document capture at their next stay) is a commercial thesis under discussion, not a deployed feature.

See also

KBS is the specific, researched Turkish instance of this pattern. KYC and IDV are the general identity-verification techniques any guest-registration product would need. Credential Portability is the reuse concept, verified once, carried to the next hotel: that makes this pattern interesting beyond one-off compliance.