Payment and operations identity
Assign named Identity Addresses to critical hotel systems.
POS / PMS Systems
POS / PMS Systems
Public network identity for POS, PMS, and hospitality operations.
Hospitality payment systems, property management platforms, supplier access, and operational tools may need public-address documentation. LARUS One can assign eligible hotel systems named Identity Addresses with evidence for independent review; vendors and payment partners decide whether to accept them, and acceptance is not guaranteed.
Identity capacity
One Identity Unit. Up to 254 globally unique Identity Addresses
Each LARUS One Identity Unit can activate up to 254 globally unique Identity Addresses at one deployed location, for the devices, endpoints, computers, servers, gateways, applications, APIs, and trusted access points that need stable public network identity.
The Identity Location is the selected home, office, family office, hotel, enterprise site, API edge, or private network where the Identity Unit is deployed through the LARUS One delivery network.
Actual usable count may depend on delivery design, security policy, and local network configuration.
Value
Give hospitality operations a clean identity layer
Use Identity Addresses for POS systems, PMS systems, payment access, supplier systems, staff networks, hotel APIs, and operational gateways.
Identity Address examples
Assign public network identity to the systems that need recognition
- POS gateway
- PMS platform endpoint
- Payment operations identity
- Supplier access point
- Hotel API gateway
- Staff operations network
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network
Supplier access
Submit Identity Passport and Allowlist Pack evidence for independent review. Vendors and payment partners decide whether to accept it, and acceptance is not guaranteed.
Delivery changes
A provider or location change requires a fresh technical and delivery assessment. Keeping the same address is not guaranteed.
FAQ
Answers to common questions
Can POS and PMS systems have separate Identity Addresses?
Yes. Customers can assign Identity Addresses by system, gateway, or operational workflow.
Can suppliers receive allowlist documentation?
LARUS One provides Identity Passport and Allowlist Pack documentation for independent supplier review. Each supplier decides whether to allowlist an address, and acceptance is not guaranteed.
Related use cases
Explore related ways to use network identity
Deploy
Deploy one Identity Unit to one selected location
Deploy one Identity Unit to one selected location and activate up to 254 globally unique Identity Addresses for the systems that need stable public network identity.
LARUS maintains the Identity Unit, Identity Addresses, Identity Passport, Allowlist Pack, and continuity record. The selected provider delivers the local network service.